Hey all,

This issue should be fixed in the most recent release of FeedWordPress, v. 2012.1212, available now at:

http://wordpress.org/extend/plugins/feedwordpress/

Let me know if it fixes the problem you're encountering, or if there are any outstanding issues you're still seeing after making the upgrade.

Thanks,
-C

Hey all,

This issue should be fixed in the most recent release of FeedWordPress, v. 2012.1212, available now at:

http://wordpress.org/extend/plugins/feedwordpress/

Let me know if it fixes the problem you're encountering, or if there are any outstanding issues you're still seeing after making the upgrade.

Thanks,
-C

artc,

In the absence of more information about your setup, it's hard to know whether or not the most recent release fixes the issue that you were encountering, but there were some outstanding issues with PHP 5.4 in particular that could cause fatal errors; if that is the issue you were encountering, the most recent release, 2012.1212, fixes the issue. If that's not the issue you were encountering, then I'd be happy to take a look at the problem if you can let me know something about what version of FWP you downloaded, what version of WordPress you were attempting to use it with, and what version of PHP your web hosting environment was running.

In any case, the recent update that fixes the PHP 5.4 compatibility issue is now available at http://wordpress.org/extend/plugins/feedwordpress/

Thanks,
-C

Well, there are a variety of reasons why a new release has been slow in coming, but in any case, there is a fix out today which should help with at least some of the compatibility issues you're reporting -- v. 2012.1212. Take a look:

http://wordpress.org/extend/plugins/feedwordpress/

Let me know if this solves the problems you've been encountering, or if there are other issues that remain to be resolved.

Thanks,
-C

Hi debbrancheau,

Sorry to hear you're running into this problem. I believe that it should be fixed in the most recent release of FeedWordPress (v. 2012.1212, released earlier today), which includes a series of compatibility fixes for changes recently introduced in the WordPress admin UI.

Could you take a look at the new version at http://wordpress.org/extend/plugins/feedwordpress/ and let me know if making the upgrade solves the problem you're encountering?

Thanks,
-C

@zcytunoy, thanks for supplying the explanation and work-around fix on this issue.

Y'all may be glad to know that a similar series of compatibility fixes has been rolled into the most recent release of FeedWordPress, v. 2012.1212, released today and now available at:

http://wordpress.org/extend/plugins/feedwordpress/

Hope this helps!

@zcytunoy, thanks for supplying the explanation and work-around fix on this issue.

Y'all may be glad to know that a similar series of compatibility fixes has been rolled into the most recent release of FeedWordPress, v. 2012.1212, released today and now available at:

http://wordpress.org/extend/plugins/feedwordpress/

Hope this helps!

As promised: I pushed out a quick release today that wraps up a compatibility fix for WordPress 3.5 with a number of other incremental improvements that have been added over the past several months. Now available as version 2012.1212, here:

http://wordpress.org/extend/plugins/feedwordpress/

Let me know if this fixes the problem you were seeing.

is installing VirtualBox, in order to be able to test FeedWordPress against PHP 5.4. Wee-ha.

Hi Morgan,

Thanks for writing about this. This behavior is deliberate.

The reason why FeedWordPress does this is because of an unfortunate feature of the Visual Editor -- even though it is capable of understanding posts in full, ready-to-display HTML, it actually strips out a great deal of HTML when you save posts in it -- on the assumption that paragraph breaks will be restored by WordPress's built-in formatting filters. However, since FeedWordPress stores syndicated posts in full, ready-to-display HTML, and deliberately bypasses WordPress's formatting filters for syndicated posts, this causes an issue where any syndicated posts that are edited in the Visual Editor will usually show up with all their line-breaks and paragraph breaks seemingly stripped out. This was frequently reported as a bug by FWP users in earlier releases, so in order to avoid the possible bad interaction, I simply disabled the Visual Editor for syndicated posts (since it deals so poorly with them in general).

If it's important to you to get the Visual Editor back, I think I can actually work out a quick compromise solution, which will enable the Visual Editor for syndicated posts if and only if you have FeedWordPress set up to expose syndicated posts to formatting filters, rather than bypassing formatting filters as it normally does. If you have that setting turned on, then the effects that Visual Editor has on syndicated posts' HTML should not cause the harmful results that were seen when it is turned off. Does that sound like something that would work better for you? If so, let me know, and I'd be happy to drop a note onto this thread when the compromise fix is ready.

Cheers,
-C