williscreative

I deactivated Jetpack and installed Google Analytics (using Google Analytics for WordPress 4.2.4 ), code inserted in the header. Many of the same problems result – the only difference is that part of the footer appears, part does not.

Yes, I deactivated/reactivated all plugins. That process isolated JetPack as the limiting factor.

bh_WP_fan,

Where is “sticky about the gooooogle hack”, as you say above?

yokima – thanks for additional advice after my post 2 days ago. I ended up copying vars.php from one of my other sites, also WP 2.6.1 All edit/publish functions working smoothly now.

whooami – my host is Bluehost

I do plan to upgrade WP to 2.8.2. I’ve dragged my feet because I prefer dashboard with horizontal nav bar as in WP 2.6. Can anyone recommend a good plugin for customizing the dashboard?

Yokima,

I followed the process you described above, retrieving the 2.6 version of vars.php and saving it over the hacked file.

Then I tried save a Test file and got this:

Warning: Cannot modify header information – headers already sent by (output started at /home/blindfla/public_html/wp-includes/vars.php:73) in /home/blindfla/public_html/wp-includes/pluggable.php on line 770

I used the back button to return to the Edit Post page, then went to Manage Posts, and found that the post was saved despite the warning. I then tried editing and publishing a draft post following the same process. I got the warning again, but the post published.

So I seem to be halfway there. I’m not getting the obnoxious pop-up anymore. What action do you suggest about the warning?

Thanks so much for your trouble-shooting due diligence, Yokima. You rock!

I’m having the same problem, which first appeared about 16 hours ago. See description and screenshot. So far, it’s appeared only on one of my WP sites, all hosted by Bluehost. I’m using WordPress version 2.6.1 with these plugins:

Akismet
creative commons license widget 0.5
Sidebar Page (and other) Sections
Twitter Tools
Viper’s Video Quicktags 5.4.4
WordPress.com Stats 1.1.1

I haven’t added or updated a plugin in several months. After I breathe into a paper bag, I’ll try the initial trouble-shooting steps discussed here. I look forward to further suggestions/solutions.