While entering in feeds, I forgot that I was using my WYSIWG editor, and it added some < p > HTML tags to the feeds. This results in my getting an error:
"Fatal error: Call to a member function get_date() on a non-object in /sites/all/modules/simpleblogroll/simpleblogroll.module on line 14"
And I see this error when I navigate elsewhere in Drupal:
"The URL < p >http://feeds.feedburner.com/xxxxxxxxxxxx< /p > is invalid. Please enter a fully-qualified URL, such as http://www.example.com/feed.xml."
Unfortunately I can't get back to the configuration file to remove the < p > tags. I just keep getting this error. Completely removing the module and installing a fresh copy doesn't help, so I'm guessing the config data is stored in the database? In any case, it would be excellent to have some sort of "Reset to Default Configuration" feature.
Thanks!
-Lurple
lurple@lurple.com
Comments
Comment #1
filiptc commentedI'm not sure you mean uninstalling (admin/build/modules/uninstall) when you say 'completely removing'. If you tried uninstalling the module after disabling it, all the db information stored by simpleblogroll should be removed. If this doesn't solve the issue (though there is no reason I can think of for it not to), you can access the db (through e.g. phpmyadmin) and drop the row 'simpleblogroll_feeds' inside the 'variables' table.
As a matter of fact, there is a 'Reset to defaults' button but it's on the module's config page which, if I understood correctly, you cannot access.
Please try these solutions and post back.
Your issue seems reasonable and I will probably make an input check, to strip all html tags to leave the text plain. You'll see that in version 6.x-1.3 somewhen next weekend.
Comment #2
Lurple commentedYou're correct, I cannot get to the module's config page. For whatever reason the information for simpleblogroll wasn't removed from the db when I removed it. I tried dropping the table manually through phpmyadmin, and that did clear up the "The URL < p >http://feeds.feedburner.com/xxxxxxxxxxxx< /p > is invalid. Please enter a fully-qualified URL, such as http://www.example.com/feed.xml." error. I'm still getting the other error, however.
I'll try the new 6.x-1.3 version when you roll it out and let you know if I still have a problem; thanks for the quick response.
Comment #3
filiptc commentedAgain, did you uninstall the module or just deactivate it and remove 'simpleblogroll' from the modules folder? Drupal offers uninstall functionality to all modules which simpleblogroll makes use of. You need to go to example.com/admin/build/modules/uninstall (which is not a folder anywhere) and follow steps there. Only previously disabled modules (at example.com/admin/build/modules) will appear in the uninstall list.
Sorry if I'm underestimating your drupal capabilities, I just want to make sure I'm not speaking gibberish here.
What the uninstall thing does, is it unsets all 'simpleblogroll_xxxxxx' rows from 'variables' and drops the 'simpleblogroll' table completely. If you want to try that manually (after disabling the module) there's no way you should get any errors from the module anymore.
Comment #4
Lurple commentedEven after using the Uninstall function in Drupal and then setting the module back up, I'm still having issues. I was able to get back to the configuration page, but after I added a feed to it (without any HTML tags), I started getting the Fatal error again:
Call to a member function get_date() on a non-object in /sites/all/modules/simpleblogroll/simpleblogroll.module on line 14
Not sure what's causing that. The problem with the incorrect feed configuration is fixed though, so the bug I was initially talking about can indeed be resolved by using the Uninstall function or by manually dropping the table with that entry.
Comment #5
filiptc commentedOk, I'll look into it, but the line should not be called unless you enter some feeds. And if the feed isn't a valid one, that line shouldn't be called either. Very strange. Have you made sure the 'simplepie' module is correctly installed (and its necessary simplepie.php too)?
Comment #6
filiptc commentedPlease download the latest version (1.3) and report back whether your issue has been fixed.
Comment #7
filiptc commentedAfter over 1 day, I assume issue is fixed. If not, please feel free to reopen this thread.
Comment #8
filiptc commentedJust in case it doesn't, I stumbled across a similar issue doing some debugging for a new feature and it might just fix what may have been left of yours. You can download the latest code with the 6.x-1.x-dev snapshot, which should be ready for downloading once D.O goes through cron. Just make sure you have the simpleblogroll.module v1.1.2.11.