> Both custom fields are textareas. But I think it happened with a
> textinput as well.
Well, I still have no idea how you got the names without double quotes
around them, but the HTML escaping bug is fixed on Bitkeeper and will be
available on our next release.
> [What we really wanted was to enable the customer fields
> without having
> a customer integration backend, instead filling them manually
> - I know
> this is not likely to be implemented though!]
I'm not sure what you mean here. The custom fields that you created are
exactly what you are referring to above -- customers fields that don't
require the customer integration stuff.
Did I misunderstand something here?