Port of Feedburner to D6

Any news??

subscribe

???
Does this mean it is working on Drupal 6?

subscribe

Can you make a support for FeedBurner's MyBrand feature in Drupal 6 release? The curent one doesn't allow me to use links like: feeds.mysupersite.com/mysupersite instead of feeds.feedburner.com/mysupersite

subscribe

I've got a new site up and running using Drupal 6 and have feedburner working, sort of. From other threads I've since gleaned this piece of .htaccess redirects re - feeds. I'm half assuming that is how this module works, Put this code in the .htaccess file at the Drupal root and before the Drupal RewriteRules take effect - well, that's how it was explained to me.

I'm still unsure about the above code as it's very hard for me to determine if the re-direct occurs. Clicking on my Drupal generated feed http://prime357.org/rss.xml opens up my Google Reader Page directly and there is no reference in the address bar referring to the Feedburner link. What should happen, if no defaults on systems occur, is that a Feedburner page opens - giving the user a choice of which reader to subscribe to. On my Windows system, for the life of me, I can't find where to turn-off automatically directing all feeds to Google Reader - for checking purposes.

So I'm wondering if the above code is valid (if it is, I won't know until a few days have lapsed until results start showing at Feedburner). If it is valid then at least it's a simple hack/fix until the Version 6 module is released.

Ok, answering my own question after scouring heaps of sites and finally the following piece of RewriteRules is working.

I'm now a little confused. My feed is re-directed to FeedBurner and when users subscribe, they are subscribing to the FeedBurner feed. I thought the whole process was in order to retain our feeds and not rely totally on Feedburner. If after a year I pull the plug on Feedburner, I effectively pull the plug on all my subscribers.

superjacent,

Your questions really are not relevant to this thread (the drupal 6 port of the Feedburner module). However to answer your question, yes the standard way that Feedburner works is to handle all your feeds, including your traffic. Feedburner does now offer a server for free called "My Brand". (http://www.feedburner.com/fb/a/publishers/mybrand) It allows you to point a CNAME (ie: feeds.mydomain.com) to a Feedburner server thereby maintaining your own domain name and control of your RSS feeds. If at any time you choose to take them out of the picture, you can then repoint your domain name to your own server and you have all your traffic back. Additionally, Feedburner will put a forward in for your existing feeds if you remove or move them and want them to go to another address.

Hope that helps.

Brent

Ok sorry about the lack of updates. Between my work obligations, crappy laptop development environment and feeling like I ws taking the wrong approach to new features, I got stalled on development of my official 1.0 version of the 5.x FeedBurner module. I wanted to finish the 1.0 version before porting to 6.x. I've resumed work and I feel like I'm making progress. I'll try and commit to CVS when I feel like it's ready for testing again, and I'll make sure to keep everyone updated.

Also to answer a few questions:
ProRunner: Yes it will support MyBrand custom domains in the 6.x version of the module.
superjacent: This is essentially what the FeedBurner module does, so just wait for the 6.x version of the module for easy administration interfaces and no more messing with .htaccess.

Thanks for the update Dave. Version 6 coupled also with MyBrand (if desired) should make for a pretty decent module.

can't wait for the port to 6 :)

I've half ported this module to Drupal 6. I'm using it with my personal blog (http://onedd.net). As now, I changed my feed target in feedburner setting page to http://onedd.net/rss.xml??no_feed_redirect .
The attachment is the patch against 5.x-0.5

Attachment	Size
feedburner_203733_13.zip	1.77 KB

Adjusting name to be consistent with similar issues in various other modules like CCK and Views. Hopefully it will help everyone find and keep up with what's going on a bit more quickly.

Thanks for the patch Wiennat. :-)

Thought I'd keep everyone updated. I'm making major progress and I'm actually getting into new features now that I wanted to get in 1.0 Just maybe another week or so until final 1.0 version, then I can start porting to 6.x

Thanks Wiennat for the patch! Between that and the coder module helping me, it shouldn't be too long to get everything ported once I'm ready to start.

fabulous :-) Thanks for the update.

oooooh subscribe. Can't wait, Dave! :D

subscribe

I'm looking forward to the Drupal 6 version.

In the meantime, I implemented the tip in post #8 with 2 changes. Since all of my feed links start with www, I had to change
RewriteCond %{HTTP_HOST} ^domain\.org$ [NC]
to
RewriteCond %{HTTP_HOST} ^www\.domain\.org$ [NC]

And because I am using Pathauto module to make SEO friendly URL aliases, all my individual blog feeds ended with /feed based on my custom settings (ie - www.domain.com/blog/username/feed).
So I added a second rewrite rule as such that wildcard matches any url ending with /feed:
RewriteRule ^(.*)/feed$ http://feeds.feedburner.org/myfeedname [L,R=temp]

So the entire bit of code looks like this:

## START: FeedBurner redirects
RewriteCond %{HTTP_HOST} ^www\.domain\.org$ [NC]
RewriteCond %{HTTP_USER_AGENT} !FeedBurner.*
RewriteRule ^rss.xml$ http://feeds.feedburner.com/myfeedname [L,R=temp]
RewriteRule ^(.*)/feed$ http://feeds.feedburner.com/myfeedname [L,R=temp]
## END: FeedBurner redirects

subscribe

subscribe

subscribe

I’m looking forward to 1.0 as well as a Drupal 6 version.

Hi Dave,

What is the development status on this the feedburner module for Drupal 6?

Thanks,

Dennis

Whoops I should have paid more attention to this issue. I just did a straight port of feedburner 5.x-0.5 to drupal, and I see there was already a very similar patch in this issue.

My port can be seen here:

http://hg.davidherron.com/index.cgi/drupalv6/rev/3b2c4bbda77f

That diff also contains removal of the diggthis module.. whoops.

Direct access to viewing the source:
http://hg.davidherron.com/index.cgi/drupalv6/file/3b2c4bbda77f/sites/all...

Any update on this module, if this depends on this module releasing its 1.0 version, does anyone know if there is an issue for the 1.0 version so people can help testing that?

subscribe

Every time there's a new post, I get my hopes up and fear those two dreaded syllables...

sub-scribe.

gah.

Please try out the 6.x-1.0-alpha version! Please report any new bugs or issues as separate issues please.

Sweet, looks like it's working pretty well. Although Feedflare is just saying "Feedflare!" in place of where the ff should actually be. Am I missing something?

Edit: The module doesn't show up either. It's there, it's configured, but not showing up.

tf5_bassist can you clarify what is "not showing up"? The menus? As for the FeedFlare...oops...left some debugging stuff in there. :)

The block itself. When I activate the block, configured it and gave it a title, and put it in my sidebar, it's just not there. Like it was never activated.

As far as the feedflare, the jscript is there (as was documented in a previous 5.x thread). And I just activated the Adsense portion of Feedburner on the FB site, and oddly enough, just below where it says "FEEDFLARE!", I have my configured Adsense ad. Go figure. So something isn't pulling the actual feedflare items in properly.

But they are showing up in my burned feed at http://feeds.feedburner.com/slappop ... So they're configured and up and running, there's just something in the code that's not showing it on the teaser or full node display.

Anything else I can do to help with this issue?

Ah. I have the block configured internally to show only on node pages. But you'd like it to show up on all pages (front page, etc)?

Oh hey, you're right. hah. So didn't notice that. Yeah, I'd like to have the flexibility to have it show up wherever I would like to put it. Is there a downside to having it on the frontpage or somewhere else other than node pages?

and it's also showing "FEEDFLARE!" there as well.

Yeah that was a debugging info to show me when the JavaScript was inserting. I've enabled the 6.x-1.x development build that will have the latest code available. It should be available shortly.

Alright, I installed the dev version. the "FEEDFLARE!" placeholder is gone, but there's still no feedflare being embedded in either the teaser or full node view. Feedflare is turned on on my FB account (it shows in the rss page), but nothing on-site. Is there anything here I'm missing? Any steps I may have missed in installing/setting this up?

Automatically closed -- issue fixed for two weeks with no activity.