Comments Elsewhere

Hey Morgan,

No problem. It didn't get into the 2012.1212 release because I needed to move quickly on a couple of other issues, but it will be in the next iterative release, which should hopefully happen over the weekend or the beginning of next week.

In the meantime, while you are waiting on that fix, here is a quick fix that should forcibly override what FWP is trying to do, if you are able to edit the files in your WordPress Theme. Open up your functions.php file in an editor, and add the following code near the top, somewhere underneath the opening <?php prefix but before much of anything else happens in the script:

add_filter(
'user_can_richedit',
'user_can_too_richedit_feedwordpress',
1001, // After FWP
1
);
function user_can_too_richedit_feedwordpress ($rich_edit) {
return true; // Override FWP's override
}

If you try this out, let me know whether it works for you. If not, I'll do a few tests to try to troubleshoot. If so, then great; you should only need to leave it in functions.php for a few days until the new FWP release supplies a better fix.

Hey Morgan,

No problem. It didn't get into the 2012.1212 release because I needed to move quickly on a couple of other issues, but it will be in the next iterative release, which should hopefully happen over the weekend or the beginning of next week.

In the meantime, while you are waiting on that fix, here is a quick fix that should forcibly override what FWP is trying to do, if you are able to edit the files in your WordPress Theme. Open up your functions.php file in an editor, and add the following code near the top, somewhere underneath the opening <?php prefix but before much of anything else happens in the script:

add_filter(
'user_can_richedit',
'user_can_too_richedit_feedwordpress',
1001, // After FWP
1
);
function user_can_too_richedit_feedwordpress ($rich_edit) {
return true; // Override FWP's override
}

If you try this out, let me know whether it works for you. If not, I'll do a few tests to try to troubleshoot. If so, then great; you should only need to leave it in functions.php for a few days until the new FWP release supplies a better fix.

@Old Cow, @kbunt, and @Purusothaman,

Thanks for posting about this. The behavior is actually deliberate -- it's kind of a crappy attempt to deal with a crappy situation caused by the interaction between the Visual Editor's assumption that all posts edited in it will be run through WP formatting filters, and FeedWordPress's assumption that syndicated posts arrive in ready-to-display full HTML, without needing to go through formatting filters. I received enough bug reports resulting from this bad interaction that I decided to cut off the Visual Editor for posts syndicated through FWP. (If your Visual Editor is disabled also for posts you create locally -- e.g. by using Post --> Add New -- let me know ASAP; that'd be a bug.) Anyway, the reasons for this, a quick workaround fix for those who need it, and an upcoming solution, are all discussed in this thread here: http://wordpress.org/support/topic/feedwordpress-and-wysiwyg

HTH,
-C

@Old Cow, @kbunt, and @Purusothaman,

Thanks for posting about this. The behavior is actually deliberate -- it's kind of a crappy attempt to deal with a crappy situation caused by the interaction between the Visual Editor's assumption that all posts edited in it will be run through WP formatting filters, and FeedWordPress's assumption that syndicated posts arrive in ready-to-display full HTML, without needing to go through formatting filters. I received enough bug reports resulting from this bad interaction that I decided to cut off the Visual Editor for posts syndicated through FWP. (If your Visual Editor is disabled also for posts you create locally -- e.g. by using Post --> Add New -- let me know ASAP; that'd be a bug.) Anyway, the reasons for this, a quick workaround fix for those who need it, and an upcoming solution, are all discussed in this thread here: http://wordpress.org/support/topic/feedwordpress-and-wysiwyg

HTH,
-C

Hey all,

So, for reference, this issue should be definitively 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,

So, for reference, this issue should be definitively 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

Yes, definitely; I'll check in in the morning to see if I can reproduce the issue that you're having.

You say that you get a fatal error; could you post the error message you're getting to this thread?

Thanks,
-C

Thanks for the heads-up. I'll take a look at this in the morning. Will post here if I need any further information.