probablynot
Forum Replies Created
-
@designsimply with that line in place, the code no longer errors.
For a temporary fix, if you don’t want to roll back to 2.2.2 and you are comfortable editing the plugin. At the end of the jetpack.php file, comment out the following lines:
if ( function_exists( 'bbpress' ) ) $_jetpack_rest_api_compat_includes = dirname( __FILE__ ) . '/class.jetpack-bbpress-json-api-compat.php';and that will get rid of the error if bbpress if your only issue.
You can comment out the foreach loop at the end as well if you are getting other problems.Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] 2.2.3 warningIf you comment out the lines:
if ( function_exists( 'bbpress' ) ) $_jetpack_rest_api_compat_includes = dirname( __FILE__ ) . '/class.jetpack-bbpress-json-api-compat.php';it also works.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] 2.2.3 warning@jason102178 I noticed that both Fabrizio and I have bbpress on our sites. Do you as well? This could be the problem as there is a bit of code right before that foreach() specific to bbpress.
Forum: Fixing WordPress
In reply to: Incoming links error message?Apparently this issue is affecting all of WordPress.com
http://en.forums.wordpress.com/topic/incoming-links-suddenly-stopped… since last year.
Forum: Fixing WordPress
In reply to: Incoming links error message?So it seems we have two issues.
1) If your feed is empty (i.e. Google doesn’t believe anyone links to you) it should just say it’s empty but is instead throwing an error (first post).
2) If your feed isn’t empty but contains certain html characters, Google appears to be replacing them with invalid characters and an error is being thrown (second post).
Forum: Fixing WordPress
In reply to: Incoming links error message?From my feed:
The item from http://eatingbees.brokentoys.org has invalid characters. However, if you validate the individual feed for that site directly (http://eatingbees.brokentoys.org/feed) it doesn’t have the invalid characters. So it appears that google search feed is actually replacing valid characters with invalid characters.Forum: Fixing WordPress
In reply to: Incoming links error message?The odd part is that in the validation for my feed, the invalid characters marked in red are coming from WordPress blogs – some of which are on WordPress.com. So either those people are using feed making plugins that are altering html codes to the invalid characters, or WordPress itself is generating the invalid characters in their feeds.
Forum: Fixing WordPress
In reply to: Incoming links error message?I’ve been with the same host for several years (Dreamhost) and I know it has worked in the past, so if anything it had to be within the last 2 or 3 updates that it stopped, but a while back I shifted my dashboard around and the incoming links got moved to the bottom where I don’t see if I don’t scroll down, and I don’t often scroll down on the dashboard.
Forum: Fixing WordPress
In reply to: Incoming links error message?I only noticed it after the 3.4 update, but it could have been there before. I don’t know for certain.
Forum: Fixing WordPress
In reply to: Incoming links error message?I’m getting that exact same error on my blog:
RSS Error: A feed could not be found at http://blogsearch.google.com/blogsearch_feeds?hl=en&scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://weblog.probablynot.com/. A feed with an invalid mime type may fall victim to this error, or SimplePie was unable to auto-discover it.. Use force_feed() if you are certain this URL is a real feed.If I go to that feed, it exists and has items. Where exactly would I go to use force_feed()?
I’m in the same boat… love the plug in, but it is disabled due to the truncation issue. Hope it gets fixed soon.