• luky-from-pixelization

    (@luky-from-pixelization)


    I tried to upgrade to the new WordPress 3.1, however had your plugin active at the same time. This resulted in a 500 error, but when I deleted the file for the plugin it disappeared.

    I realize that this may be something that you cannot help or solve, however, if so you should put this information somewhere in the readme file or on the website. Otherwise, the plugin should not do this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • I’ve encountered the same issue. With WP 3.1 running, once I activate this plug-in THEN try to work in the back-end as an administrator, I get the 500 error.

    I’m not sure while file @luky-from-pixelization deleted to solve his/her problem. I’m guessing simply removing the entire plug-in directory from under wp-content but I’m going to look around on the web some more before taking that action — just in case removing it makes my situation worse.

    Well, thanks to some advice from @james in his response to a similar issues on a different thread, I discovered one of his suggestions on how to another issue who pointed me off to some instructions on how to manually resetting your plugins

    I did a variation of it by FTP’ing to my host, going to the wp-content/plugins/maintenance-mode folder then copying the maintenance-mode.php file to my system. I edited it to remove everything EXCEPT the header info then restored it back onto my server. I was then able to get back to the Dashboard where I promptly went to deactivate this plug-in.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: Maintenance Mode] Broke site when upgrading’ is closed to new replies.