Questionmarktarius

The problem isn’t with this plugin, but with the SimplePie reader.
SimplePie is just too picky, and gives up when it gets a mimetype it doesn’t expect. SimplePie does have a flag that tells it to ignore goofy mimetypes, but WP doesn’t implement that flag.

FBF FB widget is asking WP to get the feed, and WP is asking SimplePie to get the feed. SimplePie gives up (because WP didn’t tell it not to), thus WP assumes the feed is broken, thus FBF FB Widget assumes the feed is broken.

The other “broken” thread has a simple (but naughty) fix.

There’s not a whole lot a plugin update can do to fix the problem in SimplePie.

Facebook is sending the wrong mimetype.

Then please kindly forward the request to the wordpress devs to add that one line to feed.php in the next WP update.
SimplePie is unreliable without it, thus any plugin relying fetch_feed() is also unreliable.

Thanks.

The “other way” would be informing SimplePie that their RSS reader is too damn picky, or sit back for an indeterminate amount of time and wait for FB to fix the feed MIME-type, while explaining to clients that Facebook did it and it can’t be fixed until Facebook fixes it.

Alternately, it should be possible to bypass WP’s obfuscation of SimplePie’s too-damn-picky parser, and redo the entire way FBF Facebook Feed Widget fetches and processes RSS.

Or, just add a single line to a core file.

This is exactly why I always discourage throwing social network feeds into websites: They break all the damn time.

Go into /wp-includes/feed.php and look around line 532 for:
$feed = new SimplePie();
Add this line immediately after:
$feed->force_feed(true);

Facebook screwed up the MIME-type of the feeds, sending them as “application/xhtml+xml”
They very likely boogered it up on purpose, with the express intent to foul up rss grabbers such as SimplePie.