People are losing the toolbar in the post and page editor after upgrading to WordPress 3.3. It could happen because of a problem with your computer, or a problem with your WordPress files.
edit: There was also a report of a malfunctioning toolbar that #3 and #4 solved.
Although this doesn’t officially solve the problem, using compatibility mode in Internet Explorer 9 did rectify the problem for at least one person.
If that can carry you through until the official fix comes through, I’d recommending only trying the first two solutions and stopping there.
edit: I changed the order of the last 2 steps below – what you see is the updated advice. Step 2 is only a 50/50 proposition, but you can’t go doing things like 3 and 4 without clearing your cache first. It’s just good WordPress (and computer) policy!
(1) First, check to see if you have an ad blocker extension installed in your browser. Disable it and see if that works. If that works, then just add your WordPress site as an exception.
(2) Second is to deal with the cache: some people refreshing the screen a few times got the toolbar to eventually appear. Holding down SHIFT while you click reload/refresh is supposed to force a full refresh of the page. You’d want to do that a few times. If there’s no relief there, try clearing the cache. The cache in Chrome is persistent, so at this point you’ve got to confirm the exact same problem in another browser.
(3) Try the 0.8 hotfix from WordPress, it’s the link labeled “Development Version”.
edit: if (3) didn’t solve your problem, I’d be surprised.
(4) Install the plugin Use Google Libraries. It seems to solve the problem without clearing the cache, but if it doesn’t immediately clear your problem, then you’d want to clear the cache just to be sure. (I’ll follow up to see if we’re expected to keep this permanently, I would think we can uninstall it after a fix for this problem comes through.)
If the Google Libraries plugin solves your problem, then it was recommended to manually copy the files from a manual download to the /wp-includes/ directory .
More than one person has reported that downgrading didn’t solve their problem.