Serendipity Forums

Someone pointed me at this error in my page.

After some research i found out ALL xml feeds are not working.

Theyre not parsed.

I get this error:

XML-parsefout: XML-declaratie niet aan begin van externe entiteit
Locatie: http://www.sothq.net/feeds/index.rss1
Regelnummer 1, kolom 2:
<?xml version="1.0" encoding="utf-8" ?>
-^

It says xml is not declared atthe start of external identity.
Line 1 column 2.

I have no clue where to look for the bug
Ive reinstalled the plugin but that didnt change anything.

I just found out it DOES work in IE6

Im using FF1.5 mainly and in there it doesnt work. The person reporting the error uses FF aswell.

This error means that the "<?xml" element is not the first line of your document.

This can happen if you accidently added any linebreaks or empty lines before the first <?php or the last ?> of either any of your plugin files, your language files or your rss.php files. Please go through the files you edited and make sure your editor does not insert any superfluous linebreaks.

Then the error will disappear.

Best regards,
Garvin

but i didnt edit the rss files by my knowledge..

ill look into it tho.

Any language or plugin file can be responsible for it; it must not be any rss file, it can be every language file.

Check out your serendipity admin interface, if there is also a linebreak on top of the HTML output. It should also be there, but on the frontend we use smarty templating so it wouldn't show there.

Regards,
Garvin

i found out its in my theme... when i change it to some other theme the xml works

ill investigate more soon...

Its not the theme but the emoticons.inc.php

but: now it gets tricky.
Theres no whitespave in the file...!

How to proceed?

[update]
Actually there was.. all the way up the end...
I think this should not make a difference! can this in the next release be fixed for ease of use sake

THanks for the tip btw!

The best way is to not put any "?>" tags in your file, since that is not needed.

Sadly the error is caused by PHP, so there it gets a bit hard to code it differently without a performance hit by using output buffering...

Best regards,
Garvin