Cannot unburn feeds

Can you try the latest 6.x-1.x version?

Yes, I meant the 6.x-1.x-dev version. RIght now it's the latest stable version, so you can give it a try and let me know if it works for you. Could you also post a screenshot of the admin/build/feedburner page on your site? I'll look into this problem on my end.

I just experienced the same problem - a bunch of new blog feeds showed up in the feedburner block that I couldn't delete from the feedburner admin section. It happened immediately after I deleted a number of users (they were spam users who registered but didn't respond to their automated email). Upon deletion, each of these users was automatically given an "undeletable" feed. Finally, I deleted them from the "feedburner" table. Not pretty, but it worked.

I also noted the following error repeatedly in the apache logs:

PHP Notice: Undefined index: HTTP_USER_AGENT in /usr/local/www/drupal6/sites/all/modules/feedburner/feedburner.module on line 293

So, looks like deleting users suddenly gives them "permanent" feeds.

version 6-1.0 beta3, drupal 6.10

I take another look at this tonight, but everyone please make sure you are using the latest 6.x-1.x-dev version of feedburner.

So I just tried all the following:

1. Creating new user
2. Adding feedburner for user's blog in the user/x/edit form
3. Deleted user
Results: Blog feed was removed from database, as expected

1. Manually ran INSERT INTO {feedburner} (path, feedburner) VALUES ('blog/1/feed', '');
2. Went to user/1/edit, and just pressed 'Save'
Results: Blog feed was removed from database, as expected

I'm adding test cases to feedburner.test just in-case for user deletion, but I cannot confirm this bug on the latest 6.x-1.x-dev. Please download the latest and report back here. For now, I'm keeping this issue as needs more info.

Don't change the status. I still need more info because I am not able to duplicate this.

At this point to get this fixed, I'm going to ask if someone can create an account on their website for me with the 'administer feedburner' permission. Additionally, if you are able to grant some kind of temporary FTP access to the server as well so I can make adjustments in the feedburner.module code, that would be great. If someone is willing to do this, I can probably find out what is going wrong and get this fixed.

Please do not post server details here, instead use my contact form.

Again, I'm using the latest CVS version that gets packaged into the dev releases. I'm able to unburn feeds using the same circumstances as you. I can't duplicate this on my own install or any of my remote websites, so I'll need to be able to debug on the servers where other people are having this problem.

I only use the CVS version on my local development site. I actually use the drupal.org packaged versions on my remote websites, and they all work fine too, so I know it's not a corruption issue. :/

Just wanted to let everyone know that I was finally able to replicate this on one of my production sites, so I'm on the case and will get this figured out by tomorrow.

Fixed. Give the packaging script about 12 hours to rebuild the 6.x-1.x-dev download, then you can use it.

It was a stupid logic error in the 'unburn' form code that would simply redirect the user back to admin/build/feedburner if the FeedBurner url for a feed path was 'empty'. :/ Upon investigating more of the 6.x-1.0-beta3 code, I found a few more similar errors, but luckily they have all been fixed before they've become a problem.

I still have this issue - I cannot unburn a feed. I first installed 6.x-1.0-beta4, then read this issue and upgraded to dev - but still had this problem. In admin/build/feedburner the "unburn" link is "admin/build/feedburner/unburn/roger-saner/feed" - I've clicked on that and I'm simply returned to the admin/build/feedburner page.

Luckily my trusty debugger tells me that line 178 in feedburner.admin.inc is incorrect:
$path = _feedburner_get_path_segment(5);

It should be:
$path = _feedburner_get_path_segment(4);

Then it works nicely!

Thanks burningdog. I went and double checked through every call to _fb_get_path_segment() and discovered that they were all off by one. :/ Not sure where that got changed, but I fixed them all now. See http://drupal.org/cvs?commit=210920 for the commit.