WordPress.org

Support

Support » How-To and Troubleshooting » Upgrade to V3.2 and my site is f**ked

Upgrade to V3.2 and my site is f**ked

Viewing 15 replies - 1 through 15 (of 38 total)
  • esmi

    @esmi

    Forum Moderator

    We’ need more details than that (and please don’t swear).

    What error are you getting?

    Can you share a link?

    Did you disable all your plugins?

    the error is a blank page at the site end and admin site.

    the reason is because I used the automatic update facility in the dash board.

    http://weddingphotographersinsheffield.com/wp-admin/index.php

    http://weddingphotographersinsheffield.com/

    I’m swearing because the prospect of losing all my hard word isn’t turning me on!

    We all understand your anger, but being polite is … polite. 🙂 The volunteers here don’t take kindly to insults.

    A blank page is a php error. However. I get an error 500, which is a little different

    HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

    Internal server errors are sometimes described in more detail in the server error log. If you have access to your server error log, check your server error log for anything useful.

    Also, did you read http://wordpress.org/support/topic/troubleshooting-wordpress-32-master-list and follow the directions for how to disable plugins when you can’t login? You need to try that too.

    If you WON’T try any thing in there, we CANNOT help you. Seriously. Go try disabling your plugins. Go read your error log.

    Don’t take this the wrong way but if you have the time to be so altruistic, spend more of it testing the updates before hapless morons like myself end up walking the plank.

    I don’t know php, that’s why I installed wordpress Get it?

    I can’t try anything because despite what you’re getting, I HAVE A BLANK SCREEN!

    How do I log into a blank screen?

    I can’t check the logs because I don’t know what they are or where they are or how to interpret them when I eventually find them.

    As for disabling plugins. I CAN’T LOG IN!

    Hope this helps.

    Do you have that out of your system?

    Did you read http://wordpress.org/support/topic/troubleshooting-wordpress-32-master-list and follow the directions for how to disable plugins when you can’t login?

    Seriously. I’m even going to quote the section you need. And bold the part YOU need to read.

    – deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). Don’t forget the ones in mu-plugins. If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    Okay?

    Go read. Follow the directions. If you can’t do that, there’s nothing we can do to help you.

    Are you mentally ill?

    Do you have that out of your system? Can you elaborate because this sentence doesn’t make sense.

    Secondly, stop putting seriously in front of everything.

    Thirdly (please read this bit carefully) how do I deactivate plugins if I can’t get into the back end of my site?

    I GET A BLANK SCREEN – A SCREEN THAT IS BLANK – DEVOID OF ANY INFORMATION.

    Seriously, do you get it?

    PS if you think I’m going fishing around in the database, you desperately over estimate my understanding of php and as for buggering about with pluggins via http://ftp...

    Mate, you need to talk to the people that write this stuff.

    Thirdly (please read this bit carefully) how do I deactivate plugins if I can’t get into the back end of my site?

    If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F

    FYI – If you think that ‘buggering around with plugins via FTP’ is too complicated, then there’s nothing at all we can do here to help you.

    You’re going to need to use FTP (or SSH if unix command line is more appealing to you) or a file manager tool from your web host, and go in and rename the plugins folder. if you don’t know how to do that, pick up the phone and ask your webhost for help, but only someone with access to the server that RUNS your site can do anything at this point.

    Thirdly (please read this bit carefully) how do I deactivate plugins if I can’t get into the back end of my site?

    If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    I refer you to the answer I gave some moments ago…

    PS if you think I’m going fishing around in the database, you desperately over estimate my understanding of php and as for buggering about with pluggins via http://ftp

    Mate, you need to talk to the people that write this stuff.

    I think the best thing you can do is leave this alone and I’ll wait for someone else to come along with something more helpful than reset my folder.

    Cheers all the same. Seriously.

    You’re American aren’t you.

    You don’t need to keep putting FYI – I know it’s for my attention. I’m reading it.

    Serious, FYI, give up mate.

    You’ve got more chance of winning in Afghanistan than talking me through this.

    I’ll restore to sunday and wait for the next update.

    @bwoose

    Way to be an absolute [redacted]. Well done.

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    I think the best thing you can do is leave this alone and I’ll wait for someone else to come along with something more helpful than reset my folder.

    That’s the official answer. Find the plugins folder via your webhost control panel or via ftp. Rename it to plugins-old. That tuns off all the plguisn – including ones that probably are not 3.2 compatible.

    If you’re restoring your site to Sunday, then how are you doing that?

    3.2 has been testing for months. not all plguins are. Buddypress, for example, has already announced it is not 3.2 compatible and users shoudl wait until the next BP version comes up.

Viewing 15 replies - 1 through 15 (of 38 total)
  • The topic ‘Upgrade to V3.2 and my site is f**ked’ is closed to new replies.
Skip to toolbar