benzilla

@esmi – Thanks again for all the advice. The problem is corrected now. I tried so many things in quick succession that I really can’t say definitively what fixed it, but I think it probably was the result of some aggressive browser cache clearing. I’m thinking there must have been some cached file/code from the previous visual editor version lingering around.

@esmi – Yeah, absolutely. Only a small subset of people seem to be having this issue. I just wish I could figure out what we all have in common. I’m going to monkey around with it more before giving up and downgrading. My hunch is that there’s something going on with caching

@esmi – I can get my hosting company to roll back the database if I need to. I guess that’s what I’ll do since there doesn’t seem to be any solution to this. There’s two or three pages of results when you search the forum for “3.8.1 editor”–and no definite resolution to this issue.

@esmi – I just tried that… and it didn’t solve the problem. FWIW, here’s the page source:

https://pastebin.com/bcuT0t9v

Any idea if I could just roll back the files to pre-update? Will that cause conflicts with the database now?

For what it’s worth, the issue was on the hosting/server end of things. Thanks!

Thanks again! I’m going to get my hosting folks to migrate my site to a different shared server and see if that has any effect. My other Twitter-related plug-in seems to be experiencing problems as well and I’m wondering if the IP has been blacklisted by Twitter.

Thanks for the reply, Aaron. I’m wondering about the diagnosis, though. It seems incredibly abrupt. The thing stopped pulling Tweets all of a sudden and hasn’t pulled through a single new one since. It seems like, even if there were some other site on the same IP sending requests to Twitter, I’d squeeze through one every once in a while. I’ll keep fiddling with things…

This has happened to me as well… and curiously, my blog reverted to the fresh install screen as well. I’ve repaired and changed password (which was already pretty strong: non-dictionary, letters and numbers, non-alphanumeric stuff, 12 characters). I really don’t know what to make of it.

The slow typing issue has pretty much rendered WordPress useless to me. I’m on a 2.4 Ghz machine and the typing is so lagged that it’s pretty much impossible to type coherently. I’ve never tried to downgrade WP, but unless there’s some way to clear up the typing issue, I guess I’m gonna give it a try.

Maybe there’s some way to disable the “word count” feature if that’s indeed the culprit?

There’s a fix/workaround posted on the developer’s forum here. Worked for me!

Yes, this seems to be a problem a lot of folks are having. See this thread (which for some reason is listed as “resolved”).

Yes, I also just upgraded to 2.6.3 and am also getting that same error:

Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'media_admin_css' was given in /home/****/***/***/wp-includes/plugin.php on line 311

Disabling Flexible Upload solves it. On the bright side, all it seems to do is throw the error and mess up some of the page formatting on the upload screen; it still appears to function OK.

There’s an entry on this problem in the codex here:

https://codex.www.ads-software.com/Converting_Database_Character_Sets

Unfortunately, of the items in the “Conversion Scripts and Plugins” section, the former is a link to a now-404 page, and the latter plugin fails on WP 2.3.3. (It truncates all the old posts to about 60 characters.)

I got the same deal as zern got trying to use this plugin to convert a 2.3.3 WP: all the old posts truncated at 60 words or so. Oh well…

Simon – Thanks for the input. Regarding your questions:

1- What version did you upgrade from

I’ve been regularly upgrading as each new release is out. But, this seems to be a known issue that folks are experiencing when upgrading from whatever to 2.2

2- If you look at your html source, what do you see in the meta values of the header ?

Yes, my content meta tags are fine, and exactly as you pasted above. This seems to be a known issue that has to do with a switch in 2.2 in the way WP handles the MySQL database character set preferences. You can Google up a fair amount of info about this, but no real definitive fix. (See also the forum posts linked to in my initial post.)

For this “in action,” here’s a pre-2.2 post, now displaying in WP 2.3.3:

https://www.benzilla.com/?p=828

In this case, double spaces and hyphens are appearing as question marks, but in some cases quotation marks, special characters, and other things are affected.