BudPR
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Cannot log inThanks for all of your help. I FTPed into my site and renamed the twitter plugins and I was then able to log into my WP Admin area and restore the site without the twitter plugins.
It looks like this is the bad plugin
Widget Twitter VJCK
Bud
Forum: Fixing WordPress
In reply to: Cannot log inI can’t to the Admin panel or anywhere else at this point. When I log in I get this
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-login.php on line 368
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-login.php on line 380
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 680
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 681
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 682
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 876
Forum: Fixing WordPress
In reply to: Cannot log inMy ISP reset something so that I was able to get to my site. There were several upgrades – one to WP and one to my twitter link and the last was to help with addins. I didn’t note the name down but when I did the upgrade I get the following when I try to log into WP and I can’t get to the admin panel to delete or reverse the upgrade(note, this also pushes the right hand column in the blog page down to the bottom of the page and it does not show my twitter feed.
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-login.php on line 368
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-login.php on line 380
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 680
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 681
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 682
Warning: Cannot modify header information – headers already sent by (output started at /usr/home/ermsco/www/htdocs/wordpress/wp-content/plugins/twitter/widget_twitter_vjck.php:171) in /usr/home/ermsco/www/htdocs/wordpress/wp-includes/pluggable.php on line 876
Forum: Fixing WordPress
In reply to: Cannot log inI am on hold right now waiting to ask if they are blocking wp.login.php as suggested elsewhere. Is that the right question?