Forums / Setup & design / Apostrophe not working in xml field

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Apostrophe not working in xml field

Author Message

Ivan Imanishi

Tuesday 26 August 2003 12:13:25 pm

Hello,
I've been having some problems with apostrophe in xml fields. Whenever I use it the content is lost.
For example:
<link href='http://somesite.com'> doesn't work, and becomes:
<link href=''>

The same code using quotes work perfectly.

Ideas?

Thank you,

Ivan

ben m

Tuesday 26 August 2003 12:26:24 pm

I'm experiencing a similar problem in 3.1-1 where my quotation marks are all being converted to question marks (?). Is this a magic quotes issue? I couldn't find any similar posts in the forum...
thanks!
Ben

Alex Jones

Tuesday 26 August 2003 12:37:51 pm

Make sure you aren't pasting content copied from a Microsoft Office product. The XML fields and some Web browsers don't recognize the curly quotes and apostrophes that MS products use in place of the straight variants.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Ivan Imanishi

Tuesday 26 August 2003 1:46:20 pm

It's not a problem with copy and paste from office (though I have experienced that problem too).
The problem occurs even when typing the text directly into the browser.
In fact, when i first noticed the problem i began using quotes instead. And the link worked. But whenever I edited the article, the system would replace the quotes for apostrophes automaticaly in the text field. So, if I just publish the article, the link would be lost. I then edited the kernel so that it would not use apostrophes when rebuilding the link tag.
This has made it possible for me to use the system, but I still have to avoid using apostrophes, which should not be the case.