Plugin Contributor
Jason
(@verysimple)
The error is coming from SimplePie, which is part of WordPress that is utilized by HungryFEED, but not really a part of the plugin.
According to the error message you should install multi-byte extensions on your server or else upgrade PHP. If that’s not an option, I would check with Broken Link Checker plugin author to see if they are doing something specifically triggering multi-byte?
I would be suspicious that it is actually either of the plugins, rather that a particular feed you are reading has included a multi-byte character and that is tripping up SimplePie because multibyte support is not enabled on your server. (multibyte could be a non-ascii character like a pound sign £ or anything like that. If there is one single character like that in the feed you are reading but your server doesn’t support multi-byte then you will get an error.
Thread Starter
Dave
(@dvaer)
Thank you for your reply 🙂
I’m going to throw a few more things into the mix:
- My server is running PHP version 5.2. so I think I can exclude that (but please correct me if I’m wrong)
- Yes, there may be a non-ascii character in the feed, but
- When I deactivate Broken Link Checker the feed displays fine
- The feed I’m displaying is from WordPress.com blog (not sure that’s relevant, but just a clue perhaps)
I have the same problem on a different WordPress site (on the same server) with a very similar plugin setup. There I downgraded to WP version 3.3.1 and the problem went away without disabling any plugins.
I’ve cross-posted my question to the Broken Link Checker support thread here http://wordpress.org/support/topic/conflict-with-hungyfeed and will report back with any updates.
Thanks again for your help and a great plugin!
Plugin Contributor
Jason
(@verysimple)
well as the error message says, installing the multibyte extension would most likely solve the issue. Not to discredit your troubleshooting but my gut would tell me that it’s not really the broken link plugin, but perhaps the feed cache or something else is causing things to appear as though enabling/disabling the plugin is affecting the error. But, then again I don’t really know what all Broken Link Checker does. I just say that because it doesn’t make any sense why that plugin would have any effect on SimplePie multibyte support.
Anyway, If downgrading worked, my guess is that it basically downgraded the SimplePie library to a previous version that didn’t attempt to deal with multibyte chars (which might not be a problem if your site is in english and you don’t really care about seeing an occasional gibberish character in a feed). The older version is a single file located at ~/wp-includes/class-simplepie.php. In the new version class-simplepie.php is still there, but it actually loads in the SimplePie library which is a whole bunch of files. You can find that version in ~/wp-includes/SimplePie/Core.php
