Wordpress 2.9 killed my site, please help me bring it back
December 26, 2009 9:51 AM Subscribe
Wordpress 2.9 upgrade borked my site. Please help me figure out where to go under the hood to do the necessary surgery.
So, just did the automatic upgrade to 2.9. Previous automatic upgrades have gone flawlessly, but this one appears to have a big problem with a plugin called WeatherIcon. Get the following message on the site:
Warning: require_once(/home/mysite/public_html/wp-includes/streams.php) [function.require-once]: failed to open stream: No such file or directory in /home/mysite/public_html/wp-content/plugins/WeatherIcon/WeatherIcon.php on line 58
The file WeatherIcon.php is indeed still there. There is no file withinwp-includes called streams.php, so I can't see where that reference is coming from.
I tried going into my sidebar PHP file to just remove the offending call to the plugin, but it references a dynamic sidebar, and I don't know where that hides.
So ... with the site totally borked and I can't get any access to the dashboard or any other admin page, how I do I remove the offending plugin?
On pins and needles waiting for ideas on this ... thanks in advance.
So, just did the automatic upgrade to 2.9. Previous automatic upgrades have gone flawlessly, but this one appears to have a big problem with a plugin called WeatherIcon. Get the following message on the site:
Warning: require_once(/home/mysite/public_html/wp-includes/streams.php) [function.require-once]: failed to open stream: No such file or directory in /home/mysite/public_html/wp-content/plugins/WeatherIcon/WeatherIcon.php on line 58
The file WeatherIcon.php is indeed still there. There is no file withinwp-includes called streams.php, so I can't see where that reference is coming from.
I tried going into my sidebar PHP file to just remove the offending call to the plugin, but it references a dynamic sidebar, and I don't know where that hides.
So ... with the site totally borked and I can't get any access to the dashboard or any other admin page, how I do I remove the offending plugin?
On pins and needles waiting for ideas on this ... thanks in advance.
Seconding manually disabling all plugins. Alternatively, install 2.8 over 2.9 and restore your database backup. Which... you did, right?
posted by squorch at 10:13 AM on December 26, 2009
posted by squorch at 10:13 AM on December 26, 2009
Response by poster: OK, I've got PHPMyAdmin access ... browsing the tables ... the plugin table is empty. Any idea where the plugin names live?
posted by jbickers at 10:13 AM on December 26, 2009
posted by jbickers at 10:13 AM on December 26, 2009
You could try to use FTP (or the GUI provided by your web host for moving files around) and just go in to the plugins folder and remove the offending plugin that way.
So: wordpress/wp-content/plugins/ and delete the folder for the Weather Icon plugin.
posted by gemmy at 10:15 AM on December 26, 2009 [1 favorite]
So: wordpress/wp-content/plugins/ and delete the folder for the Weather Icon plugin.
posted by gemmy at 10:15 AM on December 26, 2009 [1 favorite]
Response by poster: OK, so renaming the plugin folder via FTP got us back up and running. But my time spent poking around in PHPMyAdmin left me feeling very unsettled - I can't see where anything is in there. We've got something like 60,000 posts, but there's not a single table with a record count anywhere near that high. Is there good documentation anywhere for how Wordpress stores data? Couldn't find a thing in there.
posted by jbickers at 10:27 AM on December 26, 2009
posted by jbickers at 10:27 AM on December 26, 2009
Delete the plugin folder, clear your cache and try loading the site again. It looks like the plugin isn't compatible with 2.9 because it's calling for a file that no longer exists.
posted by Solomon at 11:50 AM on December 26, 2009
posted by Solomon at 11:50 AM on December 26, 2009
Sorry, I should read more.
When you're inside phpMyAdmin, it's not always obvious how deep into it you have to go. First into the database, then the table (probably wp_posts). Click on browse, and then you'll see the posts appear.
For what it's worth, if you're going to poke around in the database, it's best to learn what you're doing before you poke too much. It's easy to mess things up if you don't know what you're doing.
posted by Solomon at 11:55 AM on December 26, 2009
When you're inside phpMyAdmin, it's not always obvious how deep into it you have to go. First into the database, then the table (probably wp_posts). Click on browse, and then you'll see the posts appear.
For what it's worth, if you're going to poke around in the database, it's best to learn what you're doing before you poke too much. It's easy to mess things up if you don't know what you're doing.
posted by Solomon at 11:55 AM on December 26, 2009
A bit of help understanding that error, now that you're making progress:
The file WeatherIcon.php is indeed still there. There is no file withinwp-includes called streams.php, so I can't see where that reference is coming from.
The error is saying that a problem occurred while running WeatherIcon.php, and that the problem was that it couldn't find streams.php. So presumably WeatherIcon.php includes streams.php (maybe because it's not compatible with this version of Wordpress).
posted by mendel at 8:50 AM on December 27, 2009
The file WeatherIcon.php is indeed still there. There is no file withinwp-includes called streams.php, so I can't see where that reference is coming from.
The error is saying that a problem occurred while running WeatherIcon.php, and that the problem was that it couldn't find streams.php. So presumably WeatherIcon.php includes streams.php (maybe because it's not compatible with this version of Wordpress).
posted by mendel at 8:50 AM on December 27, 2009
« Older Does this exist for iPhone? If not, port it... | Besides making juice and smoothies, what else can... Newer »
This thread is closed to new comments.
i don't want to make you feel worse, but this is why you're supposed to disable every plugin before doing an upgrade. i also learned this the hard way. you have to be able to get into the db.
posted by micawber at 10:05 AM on December 26, 2009