I don't know what this is related to...does anyone have any idea?
On my dashboard, under "incoming links" there is this message:
RSS Error: A feed could not be found at http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://savvyhomeschoolmoms.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.
[closed] Incoming links error message? (71 posts)
-
Tina
Posted 1 year ago #
-
probablynot
Posted 1 year ago #
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()?
-
Rev. Voodoo
Posted 1 year ago #
I"ve actually had that same erro for a while myself, but forgot to try to do anything about it... If I figure anything out, I'll report back
-
The error is correct. That feed does not validate.
How long has this been an issue? Was it pre-WordPress 3.4?
-
Posted 1 year ago #
I only noticed it after the 3.4 update, but it could have been there before. I don't know for certain.
-
It's working fine on all of my live sites. I wonder if this could be hosts or server specific?
-
Posted 1 year ago #
Mine was definitely pre-3.4
It's all sites, including bare bones testing site.
All on the same host - bluehost (for comparison)
Unfortunatley I didn't notice it immediately, so I can't be sure if it happened upon a certain update.
But I do know that it worked at for a while after transferring to that host
-
Posted 1 year ago #
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.
-
Josh (Ult. Tinymce)
Posted 1 year ago #
Add me to the list. Not sure what's going on with this. I will do some digging and see what's going on.
I just noticed this after the wordpress 3.4 update. But I can't be sure that was the cause.
It is happening on three of my sites, all using different themes, widgets, etc. Two are with HostGator and one with GreenGeeks.
-
Could a few of you validate these feeds and post links to the validator results? Let's see if they are all failing for the same reason.
-
Posted 1 year ago #
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.
-
Posted 1 year ago #
So mine's failing whether or not I have incoming... (1 and 3 have no incoming, 2 has em)
-
Feed url?
-
@Rev: Two of your feeds (the first and the 3rd) are valid - which makes sense since they're empty. so it looks like it's down to the content within the feed (ie other people's content). Looks like most of the problems are related to invalid characters in the content. If any of that was coming from wordpress.com sites, it would need looking into. But if it's all coming from self-hosted sites, there's not a lot that core can do about it. We've all seen how the wrong plugin in a WPORG site can wreck outgoing content, yes?
Not sure if the force_feed() is going to help in these cases. I'll have a look into it.
-
OK - that was quick.
Use force_feed() if you are certain this URL is a real feed.
is coming directly from SimplePie (which is built into core). So it's part of core but not part of core IYKWIM. Not sure if there's any hooks or filters in core that can help but I'll try asking around.
-
Posted 1 year ago #
Hmm... my first and third feeds are coming up as the feed error though (as is the second), rather than just empty.
We used to get that fancy message that said something like - no content has been found, don't worry...blah blah....
-
Posted 1 year ago #
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. -
Posted 1 year ago #
Validator results:
http://www.joshlobe.com - Results | Feed
http://www.plugins.joshlobe.com - Results | Feed -
So it appears that google search feed is actually replacing valid characters with invalid characters.
That wouldn't surprise me in the slightest. :-(
@Josh: They're your site's feeds - not the Incoming links feed. :-)
-
Posted 1 year ago #
That was my fault. Comment has been updated.
-
Posted 1 year ago #
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).
-
@Josh: Both feeds are valid although they do have a couple of minor errors. Are you seeing the force_feed message too? I've sent out an email on this asking if there is any way that force_feed() can be used.
-
Posted 1 year ago #
@esmi, I believe that @Josh has the same issue I do, we get the error message (referencing force_feed) thrown up in that panel regardless of a valid feed, invalid feed, empty feed
-
Posted 1 year ago #
@esmi,
Yes I do. On all three sites. The message is the same (except the url):
RSS Error: A feed could not be found at http://www.google.com/search? ie=utf-8&partner=wordpress&q=link:http://joshlobe.com/ &tbm=blg&tbs=sbd:1&output=rss. 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. -
Hmmm... I guess SimplePie, as utilised in WP, is a lot fussier than I thought. If I don't get a response in a few hours, I'll try poking some people.
-
Posted 1 year ago #
Poke away, Diva Mod!!
Thank you, kindly.
I'll post back if I find anything in the meantime.
-
Samuel Wood (Otto)
Posted 1 year ago #
The invalidness of the feed won't cause that error, I think. But having something blocking your site from retrieving that feed URL will cause it.
Maybe your site is firewalled, somehow?
-
Posted 1 year ago #
I know we've got about 4 different hosts listed in the thread now, on which we are experiencing the issues....
Mine happened probably a month (ish) after being on bluehost... I wasn't informed of any changes on my host, but that doesn't mean a whole lot.
-
Posted 1 year ago #
Could it perhaps be a plugin? I use BulletProof Security plugin. I hate to deactivate with all the hackers on standby...
But I'll give that a try and see.
@Rev. VooDoo,
Are you by chance also using this plugin?
-
Posted 1 year ago #
Nope, no plugin of that sort
Actually on my test site, its bare, no themes, no plugins, no nothing
Topic Closed
This topic has been closed to new replies.
