take a feed with title: "managing news" drupal - Google Blog Search"
http://blogsearch.google.at/blogsearch_feeds?hl=en&client=news&um=1&q=%2...

add the feed to managing news, you get: "managing news" drupal - Google Blog Search

just a minor bug, but a great product ;)
jo/sef

Comments

dasjo’s picture

well ... you get the following without the spaces: & quot ; managing news & quot ; drupal - Google Blog Search

lennart’s picture

Priority: Minor » Normal

Yes. The equal signs (=) are transformed into something else so the URL is no longer valid. This is also true on content aggregated from Google News.

Since many people will want to aggregate from google I do think it is a concern.

haisam’s picture

I just tagged my issue (http://drupal.org/node/612236) as duplicate because I just found this one.

I think this should be critical.

haisam’s picture

Priority: Normal » Critical
alex_b’s picture

Project: Managing News » Feeds
Version: 6.x-1.0-beta5 » 6.x-1.x-dev

This is a Feeds issue. Pushing to the right place. We should address this with the next Feeds release. Hence priority is fine.

whurleyvision’s picture

Hey guys, forgive me if I seem out of place here but I think this is a google issue. I am pulling feeds from several other searches and they work correctly. As fas as I can tell, Google seems to be taking the referring website, and if it's not *.google.com then they redirect you to that error page. i.e. Google is free to take your feed, but if you try to take theirs, no dice.

I did a little research and found that Google does block several RSS aggregation tools such as Yahoo! Pipes. So, I'm curious as to how this is an issue with the feeds module. Please correct me if I'm wrong, I am new to both Drupal and RSS aggregation.

alex_b’s picture

Title: Character escaping » Output double encoded

Reading dasjo's original issue and trying the steps myself I understand now what this is about: *not* the URL gets encoded, but the rendered title (or other text) gets double encoded on output.

This most likely happens because the source feed contains HTML encoded characters (it shouldn't) and Feeds stores these HTML encoded characters without decoding them (it should). On output, we encode everything (we must: for security reasons) and voilà: la misère.

mrfelton’s picture

I have the same problem (I think this is the same problem) when trying to parse and display drupal.org's own feeds. Take the cvs commit feed for this project for example:
http://drupal.org/project/issues/rss/feeds

The description contains escaped html.

When feeds loads this into my data table, it is stored as is (as escaped html). When I then try to create a view to display this feed on my site, the description field gets printed as escaped html, rather than parsed as html.

alex_b’s picture

Priority: Critical » Normal
Status: Active » Closed (duplicate)

This issue has been fixed with #637580: SimplePie: Decode HTML entities