Thread

Hi,

This is the first time that this “error” occurs…

In my HTML-page I use

&

&

&

&

&

Which causes again some warnings…

Anybody an idea? The text with the

&

is static, so it isn’t from any weblog…

Thanks!

Do you have a link you can post? Sounds weird!

Sorry! My post is also messed up because I can’t use the & amp; inhere..

A line from my template:

<label id="lbl_street"  for="street">street & nr</label>
<input type="text" name="street" id="street" />

Output in my browser source or when I check it with W3C Validator:

<label id="lbl_street"  for="street">street & nr</label>
<input type="text" name="street" id="street" />

Almost the same, but my template parsed ‘&’ to ‘&’

Thanks!

Hm, I can’t help you there sorry. It seems to work as expected on my templates, so if there’s a setting that changes this I’m not sure what it is.

Could it be ‘Automatically Convert High ASCII Text to Entities’ under CP Home ›  Admin ›  Section Administration ›  Global Section Preferences ?

This option is “no” :-s

That wouldn’t affect your template submission in any case (nor entry input for that matter).  Perhaps there is some filter on the server that is converting POST data upon submission.  ExpressionEngine certainly doesn’t alter what you input into your templates, nor change it during output.

There’s no PHP on the page and on my other pages I haven’t this problem… It seems like only the entities inside my freeform that are converted…

Wait, what do you mean “inside my freeform”?  I think we haven’t gotten the full context here, glamorous_be.

Well,

It seems to be occure only inside my <form> tags created by the Freeform module…
When I use & amp; or & euro; or something like that outside my form in the same template, everything is fine. But when i use those characters inside the form in an input-tag or label then it’s parsed wrong…

Thanks for your help!

Sounds like something the FreeForm module is doing intentionally.  You’ll need to get assistance for this over at Solspace’s forums.

Thanks Derek, I’ve posted the bug on their forum, hope I can get some response soon!