jaimetout

@damjang If true, then bingo. My host is lame, and refuses to update its version of PHP. Is this truly the issue?

@illustrata My upgrades definitely aren’t finishing, no matter how long I wait. All that happens is I get a “Unpacking the core update” message, and then nothing happens. When I check my wp-content folder, there is a zip file (of the expected size) containing the update in there, but it never gets unpacked.

Every time I try to update the core, things seem to be working, and then the upgrade stops after “Unpacking the core update.”

Yes, I know three people will just tell me to update manually. But that hardly seems like a valid fix for this issue.

@rosecitysister No plugins related to either of the editing modes, so I’m not sure why my experience would be unusual. Weird.

I’m not encountering the situations described above, but the visual editor is clearly not quite ready for primetime.

I normally write everything in html view because I like to be in control and don’t mind hand-coding. I just wrote a big, long post, though, at one point during which I switched over to the visual editor just to have a peek. When I went back to the html editor, maybe 100 (yes, 100) double- and triple-nested <em> tags had been inserted out of nowhere. It took me twenty or thirty minutes to delete all of them.

I’ve noticed that the options pages for Stray Random Quotes are partially missing; I can tweak general options, but the page allowing the addition of new quotes has gone AWOL.

I think these kinds of things were hanging on hooks which are no longer there. We’ll probably just have to wait for updated plug-ins.

Compatibility in general seems to be surprisingly good, by the way…at least in my experience.

This is happening to me too–my most recent tweet isn’t being displayed by the plug-in. However, I checked my Twitter feed and it does contain the tweet in question.

Anybody know what might be going on here?

I was having the same problem as sailboatvn, and it was driving me crazy. I dropped the wp_footer call in there, and bingo, problem solved.

Thanks.

That was indeed a very fast fix. Thanks.

Same problem here, and I just read another thread in which a few others were having the same trouble. Sounds like a bug to me.