ozbigben

That was the way I was editing them (download – edit – upload). Thanks for letting me know it worked for someone else too.

One extra twist I had on one site was that after editing wp-config.php I had to uninstall and reinstall TinyMCE Adv.

I’ve had a similar problem and have possibly found one solution. I’d love to hear if anyone else can reproduce this…

Check the wp-config.php file and see if there are any blank lines at the end of the file. If there are, delete everything after the last character of code, clear your browser cache and try again.

It doesn’t sound like the sort of thing that would cause problems but it’s fixed 4 of my sites so far with various problems disappearing after this fix. The common symptoms I had with all sites were that a) TinyMCE Advanced was present and enabled but not displaying in the edit page and b) The default visual editor only shows html code

Same symptoms different server. Also had an issue with the NAVT plugin. I could view the manage NAVT screen but there was no functionality.

Checked the wp-config.php and there was one empty line after the close of the php code. Edited the file directly on the server this time and removed everything after the last character of code and everything works again. Truly weird but it seems to work.

Had one error pointing to line 47 in wp-config.php and line 807 of wp-includes/classes.php in the edit post page.

Also had an error pointing to line 770 in wp-includes/pluggable.php every time I deactivated plugin and had to reload the page to view the plugin list.

Looking at wp-config.php the php code actually ends at line 45. Deleted the empty lines and all of these errors disappeared and TinyMCE Advanced is now working. ??

I’ve had a similar problem on a few sites and it appears to be related to an upgrade issue. On sites where I haven’t had the problem I’ve installed 2.5.1 and upgraded to 2.6. On sites where I’ve had the problem they have been older sites, upgrading progresively from 2.3.3 through to 2.6.

It’s not a server issue as the sites are on the same server.

Tried many of the solutions on this forum to no avail.

One solution in particular made things worse. Setting WPLANG to “en” in wp-config.php broke the default visual editor completely, leaving it stuck in code view. Changing the setting back did not undo this problem.

Tempted to do a db backup and reinstall

Oops… yes it is scriptloader.php ??

The only difference I can think of in my case is that I had made some mistakes editing the template for the site which resulted in some sql errors. Whether this is significant or not I don’t know, but the problem arose after the errors only on the subdomain that had the sql errors and not on the other sites… and my WP configuration is now back to it’s original settings and it’s working again (still).

I have to admint this is a weird one. I have a server with multiple virtual hosts all running similar installs of WP2.3.3. All are installed and updated the same way, apart from some minor variations in plugins. The visual editor broke on one site, while it was still working on others.

A couple of things worked for me and in the end I went for Octav’s solution of commenting out

Scriptaculous.load();

in /wp-includes/js/scriptaculous/wp-scriptaculous.js.

The other solution that also worked for me was opening /wp-includes/scriptloader.js and replacing “tiny_mce_gzip.php” with “tiny_mce.js”

… and then I entered the twilight zone… Checking through the files, I found that I had actually edited the wp-scriptaculous.js file for the site that worked! The file on the site that had the problem was back to its original state. In between changes I had refreshed an edit window from both sites. Checked the access/error logs but nothing unusual there. I’ve now undone all changes and the editor is still working! ???

Linux FC6, Apache 2.2.6.1, php 5.1.6-3.7, mysql 5.0.27-1