I'm using Drupal Acquia 6 with the Millennium OPAC Module.
I'm ultimately trying to make it possible for our site visitors to subscribe via email to an RSS view I've created (yes - I know emailing RSS feeds is anachronistic, but this is what the client wants). So I am trying to burn my feed to google feedburner so I can leverage their email subscription and statistics tools (but if anyone knows of a better/pure Drupal solution, I would love to hear about it. Please note: the solution has to allow unauthenticated users to subscribe).
I have finally got the RSS feed for my Millennium new books list to look like I want it to (well, close enough): http://libraries.cca.edu/newbooks/feed
But when I burnt it to feedburner (http://feeds.feedburner.com/cca/newbooks), it includes data that isn't visible on my feed (e.g., authors) and it strips the one piece of data that is essential ("Link to Original Record").
When I view the source for http://libraries.cca.edu/newbooks/feed, I do see all the invisible data like authors, so I guess this is why feedburner is displaying this data. But this doesn't explain why feedburner isn't displaying my "Link to Original Record."
In order to get the bare-bones data displaying like it is on http://libraries.cca.edu/newbooks/feed, I had to resort to tweaking line 188 of sites/all/modules/millennium/millennium.theme.inc. I stripped the teaser mode of everything but 'url' which is what is responsible for "Link to Original Record." The node title and image are coming from views-view-row-rss.tpl.php.
How do I get this extra data like authors to not display in the source of the generated html? What mechanism is hiding it from displaying in the browser? Is there any way to fix this on the Drupal side or overcome it on the feedburner side?
My forehead hurts from pounding it against my desk!
Anne
Comments
Feedburner limits on customization
We ran into the same issue with Feedburner not displaying a critical piece of information from the feed (in our case, the author of a blog post in a multi-author blog). In addition, we found it unsuitable for delivering New Items RSS feeds to email, because some of our lists had over a hundred items on them, and Feedburner unceremoniously dropped half of them from the email it sent.
As a free service, Feedburner has its limits. Since we were trying to push it beyond its capabilities, we went with a paid service, MailChimp. This allows endless customization of the email format and content and does not balk at sending out RSS-to-email messages where the RSS feed contains hundreds of individual items.
We have been extremely happy with MailChimp and find that the cost is actually quite tiny for our low volume of email -- in fact, the free level of MailChimp may be all you need.
Thanks!
Thanks, ge! Great tip!