Forums / Setup & design / Parse error in cache (?xml version)

Parse error in cache (?xml version)

Next topic

Author	Message
Aaron Weiss	Friday 26 March 2004 10:42:02 am Suppose I clear the content cache. Then, I load a page from my site. No problem, loads fine. EZ generates a cache file in the cache subdir. Next time page is loaded, EZ grabs cached file and spits out a "Parse Error" at the top of the page. I have tried this with several pages and the offending line is ALWAYS the same (line 48 in my page): <?xml version="1.0" encoding="UTF-8"?> It looks like the PHP parser is choking on this line, but I'm not exactly sure. What can I do to stop this from happening? thanks! Aaron
Aaron Weiss	Friday 26 March 2004 11:01:50 am Nevermind, answered my own question. I was outputting an XML Text Field using: {$node.object.data_map.story.data_text} And this was causing EZ to put the <?xml...> tag into the body of the page. I changed my code to output the field thusly: {$node.object.data_map.story.content.output.output_text} And now EZ doesn't generate the tag that causes PHP to choke in the cache. -Aaron

Author

Message

Friday 26 March 2004 10:42:02 am

Suppose I clear the content cache. Then, I load a page from my site. No problem, loads fine. EZ generates a cache file in the cache subdir. Next time page is loaded, EZ grabs cached file and spits out a "Parse Error" at the top of the page. I have tried this with several pages and the offending line is ALWAYS the same (line 48 in my page):

<?xml version="1.0" encoding="UTF-8"?>

It looks like the PHP parser is choking on this line, but I'm not exactly sure. What can I do to stop this from happening?

thanks!
Aaron

Aaron Weiss

Friday 26 March 2004 11:01:50 am

Nevermind, answered my own question. I was outputting an XML Text Field using:

{$node.object.data_map.story.data_text}

And this was causing EZ to put the <?xml...> tag into the body of the page. I changed my code to output the field thusly:

{$node.object.data_map.story.content.output.output_text}

And now EZ doesn't generate the tag that causes PHP to choke in the cache.

-Aaron