Remove Version 3.5.5

Hi,

You can deactivate the plugin, then delete it from you install. This will run a clean up script. Then you can install the latest version.

Please let me know how it goes.

Thanks,

Gerroald

I just installed a clone of our site on a local test server and did the uninstall. As far as I can see it all went well. The plugin was deactivated and deleted with no ill effects.

We will proceed with the live site soon – no news will be good news.

Thanks for your help

OK – live site broke after deleting. Our site is working, it is the login to admin is the problem.

I deactivated and deleted the plugin. As a test I went to another browser WHILE leaving the site open in admin. In the new browser when I go to wp-admin I get this:

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/4419894/html/wp-config.php:88) in /home/content/94/4419894/html/wp-login.php on line 425

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/4419894/html/wp-config.php:88) in /home/content/94/4419894/html/wp-login.php on line 438

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/4419894/html/wp-config.php:88) in /home/content/94/4419894/html/wp-includes/pluggable.php on line 925

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/4419894/html/wp-config.php:88) in /home/content/94/4419894/html/wp-includes/pluggable.php on line 926

Warning: Cannot modify header information – headers already sent by (output started at /home/content/94/4419894/html/wp-config.php:88) in /home/content/94/4419894/html/wp-includes/pluggable.php on line 927
-
then at the log-in input:

ERROR: Cookies are blocked due to unexpected output. For help, please see this documentation or try the support forums.

My plan was to get my WordPress install updated. What if I went ahead and updated WordPress – since I’m still in the admin?

I think it’s fixed —

lot’s of searching and most results referenced white extra spaces in .php files, my problem was in wp-config after the last after a closing ?> tag

@bydesigndm

As far as I’ve seen the wp-config.php file by default does not contain any php closing tag (?>).

Have a look at the wp-config-sample.php file …

Without a php closing tag in the wp-config.php file the chance of running into your issue is greatly reduced.

dwinden