Serendipity Forums

I'm happily running the latest stable s9y version on Apache2/MySQL4 on top of Debian 3.1 for a year now. I'm also using the web-based RSS aggregator Gregarius & web-based bookmarking system Scuttle on the same webspace. These apps are supporting rss output as well and I'm using it to show the latest 7 news items marked sticky and latest 7 bookmarks saved in s9y's sidebar via the remoterss plugin. Everything is UTF-8 and worked well, no matter if latin, cyrillic or chinese characters have to be displayed.

Now I have to switch servers this month, the new server is also Debian 3.1 based which makes things easy. So I copied over my Apache2 & MySQL4 settings, the web dirs + databases and it's working like expected except for these two rss feeds! They're still being displayed, special chars included, but I get an ugly error message on top of the items destroying the layout: Line 192 is a UTF-8 character, but s9y is set to UTF-8, the feeds are UTF-8 and set to UTF-8 in the plugin settings and this setup worked flawlessly before! Even if I let the plugin fetch the feeds from the old server I get this error message.

Any ideas what could be responsible for this? Thanks in advance!

Hi!

Could you please give us the URL to the feed that Onyx reports errors for?

Best regards,
Garvin

Yes, of course:

Website:
http://cmund.de

RSS feed from Gregarius:
http://cmund.de/rss/state.php?state=sticky&media=rss

RSS feed from Scuttle:
http://cmund.de/scuttle/rss.php

Temporary URL of the new server:
http://m8s09.vlinux.de
(remoterss currently set to fetch those feeds from the old server)

Edit:
It's most certainly not a s9y issue, see the cyrillic entry here:
http://m8s09.vlinux.de/scuttle/bookmark ... =date_desc
http://cmund.de/scuttle/bookmarks.php/k ... =date_desc

But I would still be thankful for any hint

Does it return that XML error for both of those 2 RSS feeds, or only for one of them?

Regards,
Garvin

For both feeds. Looks like some server setting is responsible for this problem... But which one? I've basically cloned the old server as far as possible.

Hi!

On your new server, could you tell me if the PHP version is different than your original one?

Please compare phpinfo() output from the two servers. Might be that the one PHP version is outdated and/or not having iconv/recode capabilities!

If possible you should use PHP5 on the server, since that is the only really well working PHP version for UTF-8 recoding

Best regards,
Garvin

garvinhicking wrote:On your new server, could you tell me if the PHP version is different than your original one?

Please compare phpinfo() output from the two servers. Might be that the one PHP version is outdated and/or not having iconv/recode capabilities!

It's all exactly the same, same packages, same repositories.

garvinhicking wrote:If possible you should use PHP5 on the server, since that is the only really well working PHP version for UTF-8 recoding

I really would like to use PHP5, but it isn't included in the current Debian stable and it would lead to much bigger problems if I'd use unofficial debs or hack it together somehow. I'd even try but the old server proves that it's possible to have a working setup with these versions, too.

Hi!

That's really strange...if I got you right, the servers are basically the same but the error only happens on one server?

phpinfo() is exactly identical, as well as your php.ini?

Would you be able to give me (temporary) FTP access to that new machine, so then I could try to see what's going on? If so, please contact me via PM.

Regards,
Garvin

garvinhicking wrote:That's really strange...if I got you right, the servers are basically the same but the error only happens on one server?

phpinfo() is exactly identical, as well as your php.ini?

Yes, you got it right and I'm still not exactly sure about the cause, but it looks like it had something todo with MySQL.

The only things I hadn't copied file-by-file were the databases. I did a mysqldump from the command line ('--default-charcater-set=utf8' switch included tho) and imported the output also via cli on the new server.

Since the new server runs exactly the same software & config I've now just copied /var/lib/mysql over to the new server and restarted mysqld. Now it works, no matter if I let remoterss fetch the feeds from the old server or the local server.

Thanks for the quick help! It was not for the first time, so I thought it was time to remove a book from your wishlist

Oh, that was a tough thing to solve then. Glad you got down to it, I guess it would've taken me ages to guess this. *g*

Best regards,
Garvin