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.)
Hi there, I was wondering
Hi there, I was wondering whether you offered any advertising possibilities on your website? I have a friend who is looking to promote his new website.You can prepare for your project management exam by spending weeks reading books, or you can simply get the PM PrepCast. This training course was created by a project management expert who has had several years of experience in the field of project management and PMP training.
tip
Great info. I got a few applicable tips. Thanks.
Great site. Very informative
Great site. Very informative and a big help for me. Thanks!
Thanks for solution at
Thanks for solution at feedburner i had same issues.
No teme
Hello from Russia!
Can I quote a post in your blog with the link to you?
reply
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
Sorry to hear about your
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.
I found the problem, and it's me
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.
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". : /
Post new comment