Can you access your site by using the file manager provided in your host’s control panel. Popular file managers: cPanel, DirectAdmin, Plesk or by using an FTP client like Filezilla?
Halo 🙂
Thank you for your really quick answere.
Yes, I can reach my site by a FTP client, Filezilla.
Ok. Via FTP navigate to the wp-contents folder (directory).Rename the folder “plugins” to “plugins.hold”,
Now you should be able to login to your WordPress administration menus (/wp-admin). Let us know if it worked. It might be also caused by a theme so you will have to rename the active theme folder.
Yes it works – but how can I get the page to functions again? 😉
THank you so much for your time! I really appreciate it!
Is there some way to get to the 3.6. again? Then everything was ok …
WP 3.6.1. fixes some security issues so i would suggest to always stick to the latest version. Instead of reverting back, you should locate the plugin that is causing the problem.
Via FTP rename “plugins.hold” back to “plugins”. Turn on plugins one by one to check which one is causing the problem.When you find it, delete it and find another plugin that will get the work done instead.
ok – if that is the only way 🙁
It was the gravityform from woocommerse it seems like…
ok – if that is the only way 🙁
The best way I have found to deal with WordPress core upgrades is to first deactivate *all* plugins (and maybe even temporarily rename the plugins folder to plugouts for the duration) and then activate a default WordPress theme such as Twenty Twelve prior to doing the upgrade…and then (and after restoring the plugins folder name, if necessary) re-activate my plugins (but not all at once). By doing that, WordPress does not have to try to step over or around anything some plugin might be doing or trying to do during the upgrade and there is not such a rush at the door while plugins are re-activating after the upgrade…and I have yet to ever have any trouble either during or after a core upgrade.
doing the upgrade…and then (and after restoring the plugins folder name, if necessary)
Oops, I goofed. Temporarily renaming the plugins folder will *completely* deactivate even the plugins that do not fully disengage even when deactivated, but then that folder needs to be renamed back to plugins *before* the core upgrade to be sure the upgrade does not complain like when adding or upgrading “Dolly”, for example.
