doog

I’ve gotten it to work but there are def some minor wrinkles. I’d pay real $ to help this get fixed…

On the left sidebar under ‘Plugins’
http://codex.ww.wp.xz.cn/File:plugins.png

Assuming you backed up your database before you upgraded as per the installation instructions, you should be able to simply delete the core files (keeping, of course, your theme and wp-content/uploads/ folders and any plugin customizations) install the previous version you desire after downloading it from here:

http://ww.wp.xz.cn/download/release-archive/

and import your database to restore your site.

As for anyone ‘telling you to upgrade,’ I honestly don’t recall anyone ever -telling- ME to upgrade… it just seemed like a good idea to get the latest version of a wonderful, feature-rich and oh-by-the-way FREE tool supported (again for FREE) by a great community of intelligent, passionate and committed developers and users.

I’ve built several sites using 2.7 and wouldn’t say any of them are ‘impossible to use’ now – quite the opposite in fact.

What ‘the crap’ is going on here?

I could hazard a guess but it might just upset you more.

Here’s a suggestion: ask polite questions. You’ll get better results.

I hope my response was helpful.

I doubt you’re an idiot. 😀 More likely have what I suffer from: “Transient IQ Failure” induced by lethal caffeine overdose. LOL

Donncha, here’s what my htaccess file looked like while the error was occurring, if it’s any help:
—
# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
AddDefaultCharset UTF-8
RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]
</IfModule>

# END WPSuperCache

Donncha, first, thank you for your outstanding work on SuperCache, it IS a lifesaver for shared-hosting users (like anyone on BlueHost!).

Second – I’m running the latest WP (2.7), did the plugin update and started getting two lines of errors (sorry, didn’t catch them, our content managers immediately started howling in pain and I had to scramble to get it settled down) but I definitely remember seeing a reference to PEAR.

Turned the plugin off (deactivated) and ONLY the errors came up. I removed the supercache code from the htaccess file and got the site running again, but am now concerned (terrified? my heart is still fluttering) that the plugin may not work right.

Any suggestions? Aside from a nice break and a cold towel on the forehead?

WHEW. Fun morning!

dd32 commenting out those lines instantly solved the problem.

THANK YOU for your suggestion/solution! I am in your debt.

So, since this is a core file I’m editing I suspect the issue will (may?) return with the next new codeset?

I’d like to reiterate that I have always received prompt and polite assistance from the WordPress team.

I’m always amazed at the quality of the software they’ve produced and their committment to excellence.

Thanks folks.

I’m with Otto, I like the 2.7 admin interface. I tried the Ozh Admin plugin – not sure why, but it buswrecked* my site, which is the short route to permanent plugin limbo for me. (* as in scrambled my options table, lucky I had a backup). Maybe the next step is themes for the admin panel? Then users could get their OWN appearance ‘inside’ as well as ‘out’ – I’d vote for that!