endgamepr

Update: I’ve noticed something additional. I published our latest daily post today, and found that one of the “missing” posts was suddenly showing up in the main Posts list. Then, I wrote a post that’s not due to publish until next week (saved as draft) and *another* one of the “missing” posts showed up. But, the two new ones written today aren’t showing up unless I click on the category view.

Weird, huh?

Actually, my initial upgrade WAS manual. I upgraded the site from a much earlier version of WP. When I tried the re-install option, I did it through WP with the automatic installer.

Laura — It despise IE as well. Try Chrome. I’m using it to edit a client site right now, and it works just fine.

PS – I’m using the latest public release of FF, version 3.6.13

Ipstenu — Tried clearing my Firefox cache … didn’t make any difference.

Funny you should mention previous versions of Firefox breaking TinyMCE. That’s how I figured out to try IE8. In my research of the problem, I came across some old troubleshooting posts about a problem in WP 2.7 that was very, very similar to this one.

I’ve also tested Chrome, and it works just fine. It’s obviously a Firefox issue. Pain in the rear to switch browsers just for WordPress usage, but at least I know there is a workaround.

Laura — What browser are you using? I normally use Firefox, but I just powered up my version of IE8. When I log in using IE8, everything seems to work normally. I haven’t checked Chrome or Safari, but this might be a temporary work-around until the bug is squashed or someone finds a fix.

I just did a reinstall of WordPress (using the automatic updater within WordPress) and that didn’t fix it either. Sometimes I can see the Visual Editor view, but even then only SOME of the TinyMCE buttons work … but not all of them. The link creation button doesn’t work, for example. If I go into HTML view, it works just fine. I wonder if this is all related to the upgrades to the intra-site linking?

I’m having this same problem and haven’t been able to figure it out. I’ve done a little research and it seems to be a problem that a lot of people are dealing with, unfortunately. Any fixes would be fantastic.

Bingo. That was what I needed. Thanks!

Disabling Gears seems to have solved it for me too. Thanks, Teratoma! Very strange on my part as well. I’ve had Gears installed for a long time, but this problem just cropped up yesterday. I wonder if Google updated the plugin? I would think I would be notified of that, though. Or, rather, I would *hope* I’d be notified…

I’m having a similar problem. If I click any of the uploader buttons, it starts to bring up the uploader screen, and then Firefox crashes. I can upload via FTP, insert manually, and then bring up the size/layout screen to adjust things. It just started happening yesterday and I can’t come up with anything I did to cause it.

Something that could potentially help whoever might be looking into this — I seem to be having this problem on multiple WordPress installations that are on different servers. Also, the problem is happening on multiple *computers*, as I’ve had the crash happen on my office and living room computers. The computers are on the same network, but I doubt that’s the issue. It seems to be some way that WP is interacting with Firefox.

Interestingly, the uploader appears to work in IE7. I can use that as a workaround if necessary, but it’s a pain in the rear.

This doesn’t appear to be a plugin issue with me, by the way. I disabled all plugins in one of my WP installations and it still crashed. I also have closed browsers, deleted histories, and restarted computers … no luck.

Anyone? If I delete every WordPress file and then try to install in a different directory, will it screw things up?

Thanks. It’s good to hear I’m not the only one experiencing this problem. It sounds like none of the suggested solutions fix the problem 100% of the time.

Otto — you rule. That’s the solution to all of these problems. I didn’t realize that when GoDaddy did the initial installation of WordPress for me that it set the non-www URL as the address of the blog. I switched it to the www version, which I have been using to log in, and everything appears to work great!

Probably was. I looked at the code in that post and it was mess. I copied it over from an online news release I’d distributed and didn’t realize how sloppy the code was. Regardless, it’s fixed.