Home

Primary links

  • top o the deck
  • Drupal for Beginners
  • about
  • links
  • give me some sugar

Drupal stuff

  • EDAM
  • STARDOM
  • Question Bank
  • Drupal musings
  • Drupal tips
Home Blogs Drupalace's blog

Key stuff on this site

Easy Drupal Admin Manual (EDAM)

SEO, Traffic and Revenue: Drupalace's Online Manual (STARDOM)

Drupal for Beginners

Subscribe to posts by RSS or email

Subscribe to Drupal Ace by RSS feed RSS feed 

Subscribe to Drupal Ace by Email

Donate towards my web hosting bill! Get a great host!

Share and save

Share/Save

Random piece of content

Maintenance and Construction Notices

Manuals on this site

  • Easy Drupal Admin Manual (EDAM)
    • Welcome to Your Site
    • First Steps: Please Read!
      • Understanding These Instructions
      • Important Terminology!
      • Best Practices for Site Admins
    • Super Quick Guide (for the experienced and the brave)
    • Logging In
    • Your Administrator Tools
    • Setting Site Basics
      • Setting Site Information
      • Configuring Your Theme
    • Creating Content
      • Node Types
      • Create a Page Node
      • Create a Story Node
      • Create a Blog Entry Node
      • Making Images and Other Files Available
      • Using Text and Image Editors
    • Organizing Your Content
      • Terms, Vocabularies, and Taxonomy: "Tagging" Your Content
        • Taxonomy Suggestions
      • Menus, Links, and Paths: Navigating the Site
        • Content Paths and URLs
        • Creating Links
        • Working with Menus: Administration Form (Drupal 6)
        • Working with Menus: Administration Form (Drupal 5)
        • Creating Menu Items on the Fly
        • Placing Menus on Your Pages
      • Placing Content on pages
        • Creating a page from a Single Node
        • Creating a page from a List of Nodes
        • Setting the Front Page
      • Working with Blocks
    • Maintenance Stuff
      • Maintenance and Construction Notices
    • Other Fun Things
      • Changing Color of Garland Theme
      • Free Aliases!
  • SEO, Traffic and Revenue: Drupalace's Online Manual (STARDOM)
    • Set a Clear Goal
    • Make a Good Site
      • Put out the Welcome Mat
      • Make Great Content
      • Build a Great Brand
      • Make Navigation Easy
      • Tune Site Performance
    • Drive Traffic
      • Promote your Site
      • Get Found with SEO
    • Build a Community
      • Build an Offsite Community
    • Monitor and Improve
    • One-Page Checklist
    • Drupal and the Blogging Starter Checklist
      • Drupal and the Blogging Starter Checklist, Part 1
      • Drupal and the Blogging Starter Checklist, Part 2
      • Drupal and the Blogging Starter Checklist, Part 3
      • Drupal and the Blogging Starter Checklist, Part 4
      • Drupal and the Blogging Starter Checklist, Part 5
      • Drupal and the Blogging Starter Checklist, Part 6
      • Drupal and the Blogging Starter Checklist, Part 7

Recent comments

  • Deleting cookies

    Good point; thanks! Deleting cookies and/or caches, depending on the problem at hand, is a part...

  • It worked

    adding $GLOBALS['tempUser'] = $user; worked but I find it worth noting that I had to delete...

  • very good document...

    very good documentation for beginners!!!!!! thanks!!

  • del penitential 62

    strike out abject
    eliminate penitent 5

  • Chat

    Thank you a lot about very beneficial to my work was very useful thank you

more

Drupal and Feedburner

Submitted by Drupalace on Mon, 2009-07-06 12:36
  • blogging
  • Drupal 6
Drupal and Feedburner

Feedburner seems to be working now. You can subscribe to Drupal Ace by RSS feed or subscribe to Drupal Ace by Email, either of which gets handled by Feedburner. 

What was the problem? As I mentioned last time, it was working fine when I set it up a few months ago, but later stopped. First culprit: Somewhere along the way, my setup at admin/build/feedburner lost the correct feed URL. How that happened I don't know, but obviously the wrong feed info makes for a Feedburner extinguisher.  

There was also a problem in the subscription process. I had been using the following Feedburner-provided code for the subscription block, which displayed an email input field and a "subscribe" button:

<form style="border:1px solid #ccc;padding:3px;text-align:center;" action="http://feedburner.google.com/fb/a/mailverify" method="post" target="popupwindow" onsubmit="window.open('http://feedburner.google.com/fb/a/mailverify?uri=DrupalAce', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true"><p>Enter your email address:</p><p><input type="text" style="width:140px" name="email"/></p><input type="hidden" value="DrupalAce" name="uri"/><input type="hidden" name="loc" value="en_US"/><input type="submit" value="Subscribe" /><p>Delivered by <a href="http://feedburner.google.com" target="_blank">FeedBurner</a></p></form>

However, this code was breaking – parts of it just disappearing – very time I made any edit to the block. That means I was forgetting to use the proper input format, right? No; I checked and rechecked until I was silly, and was correctly using an unfiltered HTML format, which has worked fine in many similar tasks.

With one other exception: I had the same problem earlier with Google-provided search code. There, too, the code would break if I edited the block for any reason, despite use of an unfiltered HTML input format.

Why does this happen? I don't know. I expect that with an unfiltered input format, code should go into a block - and stay there - untouched. Yet for the two examples above, re-opening the block for editing would always reveal the code to have been stripped down to something shorter (and broken). Go figure.

Solution? I found shorter code that opens a subscription window, instead of a ready-to-go email input field and "Submit" button. It too does the job – see it in action toward the top of this page! – and doesn't fall apart when I re-open the block.

So. Once again, it's an unsatisfying ending of "I'm not sure what happened, but things are working again". That's not so bad – but if you have any insight into the breaking-block-code matter, please speak up. (Or if you see something else laughably wrong with this site's Feedburner setup.)

Share/Save
  • Drupalace's blog
  • Printer-friendly version
  • Quote
XspyZ's picture

Thanks for solution at

Submitted by XspyZ (not verified) on Mon, 2010-05-31 17:27.

Thanks for solution at feedburner i  had same issues.

  • reply
  • quote
Polprav's picture

No teme

Submitted by Polprav (not verified) on Tue, 2009-10-20 21:50.

Hello from Russia!
Can I quote a post in your blog with the link to you?

  • reply
  • quote
drupal video tutorials's picture

reply

Submitted by drupal video tutorials (not verified) on Sat, 2009-07-11 00:36.

a lot of subscribers ask us on how to insert the feed burner code and here its nice , tis will be quoted as an important source for  drupal users

  • reply
  • quote
Dave's picture

Sorry to hear about your

Submitted by Dave (not verified) on Tue, 2009-07-07 06:04.

Sorry to hear about your FeedBurner problems! That's really odd about the module losing it's settings since they're stored in the database. You didn't happen to encounter any related errors did you?

If you were using the 'Full HTML' input format, I believe it will still strip some tags that could cause XSS (form tags, JavaScript, etc). You would need to create a new input format (what I call 'Raw HTML') without any filters applied to it.

  • reply
  • quote
Drupalace's picture

I found the problem, and it's me

Submitted by Drupalace on Tue, 2009-07-07 12:59.

It is odd that the settings were lost. One possibility is that they weren't set up correctly from the start - though why FeedBurner was initially working then becomes a mystery. 

The other, more likely, possibility is that while trying to troubleshoot the issue of my broken subscription block, I munged the FeedBurner settings. In fact, it's quite likely:

At admin/build/feedburner, I can see my Drupalace feed all set up and ready. But say I want to check its settings to troubleshoot a problem, so I click that feed's "edit" link. There I see the fields for specifying the local feed URL and the FeedBurner feed URL – but instead of displaying the previously-entered values, the form shows the fields as empty! If I take care to click "Cancel" or just close the page, all will be well, but if I carelessly click "Save" just to exit the form, I'll have erased my settings.

It's a usability flaw in the form, and I'll bet it's where I broke things by not paying attention. 

Dave wrote:

If you were using the 'Full HTML' input format, I believe it will still strip some tags that could cause XSS (form tags, JavaScript, etc). You would need to create a new input format (what I call 'Raw HTML') without any filters applied to it.

That advice is spot-on, and I'm happy to report that I was using a custom input format just like yours, which I label "Unfiltered HTML"... except – ack! – it wasn't so unfiltered after all.

Thinking I'd better check one more time before pleading "huh, I'm sure I did this right", I looked at my Unfiltered HTML filter settings just now... and "HTML corrector" is checked. It should not be! 

This HTML corrector hasn't messed up most of the HTML code I paste into blocks, but I'll bet it's precisely what mangled the more complex Google search and FeedBurner codes I had trouble with. Let's check:

Disable "HTML corrector" in "Unfiltered HTML"... Create new test block using that troublesome FeedBurner code... Save block... Edit block... 

And this time, the code is impeccably intact. No more mangling! Looks like I just found the should-have-been-obvious source of the problem.

So how in the world did I make this mistake? I thought for sure I'd confirmed that the input format was kosher; I must have done so for another site. 

At least it's good to see that so many problems can be traced to a single cause: one big doofus user. I hereby proclaim that the "ACE" in this site's name stands for "A Comedy of Errors". : /

  • reply
  • quote

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><br><p>
  • You may quote other posts using [quote] tags.
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options


Relevant Content

The Drupal Ace logo has dealt these content suggestions from the deck.

  • Drupal New Site Setup Checklist
  • How to stop Drupal from logging error messages to screen?
  • Things theme different...
  • Changing download method from Private to Public: Image problems solved (somehow)
  • More EDAM updates!
  • Flexible WYSIWYG editing for Drupal
  • Review: Drupal 6 Ultimate Community Site Guide

Learn Drupal, hands-on

Get the beginner-friendly ebook that teaches community site building via a live case study.

Drupal 6 Ultimate Community Site Guide

Read the review

Drupal mini tip

The Book module creates "Printer-friendly version" at the bottom of Book pages. If you hit that link from a page with child pages, Drupal creates a printer-friendly page from that page and its child pages. If you hit the link from the Book's top page, you get the whole book in a single page!

It's a deal!

Dreamhost dealsDrupal Ace presides over his domain, proudly ensconced in his DreamHost eyrie. Won't you join me?

Promo code deal!

Just enter the code 49ER when you register for an account, and save $49 off the already-low price. No strings!

Read my hosting service review

Powered by Drupal, an open source content management system

Copyright 2007 and forever after. Made with Drupal, of course. On OS X, of course. Served up by DreamHost. DreamHost

RoopleTheme