New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<type 'exceptions.AttributeError'> while adding a feed #23
Comments
Yep, I also had this but while clicking the "save" button at the bottom of the page. <type 'exceptions.AttributeError'> Python 2.7.3rc2: /usr/bin/python A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred. <type 'exceptions.AttributeError'>: 'list' object has no attribute 'strip' |
I think I may have found the cause of this and did a quick fix. Pull request submitted - let's hope it works for you! |
Closed, thanks to Aleta's 3289266 patch. |
Reopening this, requires more testing to make sure it didn't create another issue. Lizzard reported an error on line 162. Tested to see if it's due to her attempting to add the same feed as she added previously when she encountered the error, but it still dies at Line 162 when adding a completely different feed. |
I tried again with http://fredjoiner.wordpress.com/feed/atom/
|
That's very helpful! Thanks for this info, I'll keep working on it. On Mar 29, 2013, at 8:23 PM, Ken Stailey wrote:
|
Form HTML contains: <label for="Pass">Password:</label><input type="password" size="25" name="Pass" id="Pass" value=""> Parse goes: good_field(Form.getvalue('name%d' % feed_count, '').strip()), but Anyhow, it shouldn't try to do |
I'm now experiencing this issue as well with the WFS planet; same traceback as @nutznboltz when he added the fredjoiner blog (above). @nutznboltz, thanks for your attention to this. I apologize for having dropped the ball, life has been a bit crazy lately! A rewrite of the admin.py file is in the plans in the next month or two, but I'd like to at least do a short-term fix for this issue so that those who are prevented from using the admin page. I'm afraid I am not going to be able to take a look at it for a couple weeks still, would you be interested in taking on this issue? |
I've found the culprit! Comparing the three planets that I know have experienced this issue (wfs, feministhackers, allarounddc), it seems all of them first experienced the issue when making a change AFTER having added a feed with an apostrophe in the name. The apostrophe was being interpreted to signify the end of the string, which was throwing a wrench in things. I've made a small change so that it escapes the apostrophes in the Name field with b4cb5f9. This prevents the issue from happening with feeds added moving forward, however this does not fix the existing feed names in the database with unescaped apostrophes. I'm leaving this bug open until that's addressed, since those planets which are affected are still broken (cannot add any new feeds). |
Upon further testing, it seems no changes to the database are needed. In my local install, I can now update planets that previously got errors. Closing this bug! |
Feed URL: http://fredjoiner.wordpress.com/feed/atom/
Error
The text was updated successfully, but these errors were encountered: