After struggling with my upgrade for a couple of hours last night, I realized that the Super-Cache plugin, once reactivated, writes to the .htaccess file (as it usually does with a clean install), and if there are any other custom rules existing (there were a few in mine) then it causes a lot of the problems I've been reading about here, like insanely slow load times, disappearing TinyMCE, lots of javascript errors. It took me awhile to figure it out because simply deactivating the plugin does NOT resolve the problem. I managed to fix it with the following steps:
1. Disabled all plugins, especially Super-Cache
2. From my root directory (I'm using WP as a CMS for my entire site, if your blog homepage is down a level or in a subdomain look for it there), I downloaded the current .htaccess file to my local machine then DELETED it from the server entirely. This step restored Coltrane to semi-full functionality.
3. After much trial and error, I was forced to simply delete all rules in the .htaccess file except the original WP rules:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>
# END WordPress
4. I then re-uploaded the .htaccess file, reactivated my plugins, configured super-cache, and things are working smoothly. 2.7 is pretty sweet once you've got it running.
Messing with the .htaccess file is a dark art, and I've got no real suggestions just yet on how to get Super Cache to play nice with any custom rules you might need to include. I'm still working on it, but taking these steps are a good place to start. A few problems with the syntax in that file causes some weird, weird problems with WP 2.7. Hope this helps! -Matt
ml kay
thisisedie
nickjordan
oppodeldoc
tubalreversal
Ellion
Jemmie
dr.arief
smacklemore