I learned also alot Bob,
Thanx for you,re time!!
Hi
This stuff could be a lot easier than it is. Of course you are doing some *very* complex things with these plugins. Not simple at all…
Bob
Hi,
As Bob said, I unchecked the Mod_Rewrite and checked PHP. And there was no more “warning” sign.
Now I am a bit curious (or ambitious), my webhost support person thinks I can do mod-rewrite, but my .htaccess is not writable. They want me to copy what the installation instruction says (below) and paste it instead. They asked me to ask the plugin author where exactly I am supposed to paste this in my .htaccess before I do anything.
—————–.htaccess—————–
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240×320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).*
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_METHOD} !=POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{QUERY_STRING} !.*attachment_id=.*
RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240×320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).*
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
—————–.htaccess—————–
I read Bob’s comment, and it sounded like Bob pasted his as well (?)
So, are these lines supposed to go before or after or in the middle of the following in my .htaccess??
#BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
#END WordPress
Could Donncha or automattic verify this? so I can go back to my web host support person and let them know this worked?
Thank you.
Hi
You do *not* want to post what comes after
#BEGIN WordPress
and before
#BEGIN WordPress
The only reason to paste any of the “WordPress” tags is to enable the automatic stuff to work.
The stuff you *do* want to paste is between the Super Cache begin and end tags.
Again, if there’s something else already in the /.htaccess file, be carefull you don’t mess it up. (as in don’t erase it).
If you have the WordPress tags in your /.htaccess then put the Super Cache stuff *before* the WordPress stuff. The same would be true if your /.htaccess had WordPress generated lines that did not have the tags on them. The SuperCache stuff would go before that as well.
Bob
Don’t bother using mod_rewrite mode if you’re having problems with it. PHP mode will be almost as fast and you honestly won’t notice a difference. It’s much easier to get working too!
Thank you, Bob.
Thank you, Doncha.
Doncha,
I didn’t see either of your messages, and I actually left mod_write clicked all day and all night.
My .htaccess was the same (nothing added), and the wp super cache plugin setting page still says mod_rewrite is not being updated, but the page source keeps logs… like the one example below;
<!– Dynamic page generated in 0.208 seconds. –>
<!– Cached page generated by WP-Super-Cache on 2010-11-04 09:12:39 –>
So, I contacted my webhost support, and the tech person says he can see that it is saving cached files. He thinks it’s caching (except amazon and other ads… is the wp super cache supposed to cache ads?) for the server’s end.
So now, I am confused.
Should I keep this setting or should I go back and unclick mod_rewrite and goes back to PHP setting?
Thank you.
Hi
If Super Cache finds the rewrite rules in your /.htaccess file, it will use mod_rewrite caching. The “php caching” setting will be overridden.
Don’t ask how I know this … it’s in the same file as, “gee if wp-cron stops working right all sorts of things break in odd ways (including Super Cache) …”.
Bob
Hi Bob,
I am not sure I get it.
Even though my .htaccess don’t look anything like the one in the instruction, should I leave it like that and keep mod_write?
Or.. since this is strange, I should go back to PHP?
Hi
Super Cache looks for the tags:
# BEGIN SuperCache
# END SuperCache
(that may not be the right capitalization and it does matter)
if it finds them it decides to use mod_rewrite. If it does not find them it decides the rules aren’t loaded acts accordingly.
If you simply comment out the rules (and don’t delete the tags) super cache gets *very* confused.
If you are going to use mod_rewrite, the super cache rules need to be pretty much exactly as shown in the plugin. If they are not, Super Cache will likely mess up in one way or the other.
The rest of the rules in the /.htaccess file also need to be right. That’s not just for Super Cache, that’s true for WordPress in general. If the rules are not right, odd things will break here and there.
Bob
ninjazen – yes, go back to PHP caching. You won’t notice a difference and it’s easier to get working. That’s why it’s on the “simple setup” page 🙂
