[Plugin: WP Super Cache] i just cant get it to work

I allready found it.

You must also set de Cache folder in de content folder writable.

one question.:
It now says:

Rewrite rules must be updated

The rewrite rules required by this plugin have changed or are missing. Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.

And when i click that button, my site will give an error, and no one can get on it anymore.

Is this nessasary to set this Rules must be updated?

Hi

If you are using “rewrite caching” then indeed you need to update the rules.

Are you running rewrite caching?

Bob

No i,m not running rewrite caching, cause when i eneble this, the site crashes.

But what does this “rewrite chaching” do?

Hi

The only time I see the stuff about rewrite rules is when I check the top box on the advanced setup menu. That’s the one that enables rewrite caching instead of php caching.

The cache can either work by feeding back information at the php level (the code) or by re-writing the request (the server level). Doing it at the server level is slightly faster according to the docs. rewrites are also a bit more complex to set up.

Did you have another cache set up before you installed Super Cache?

Bob

runningplus, were you able to work this out?

I also get

Rewrite rules must be updated

The rewrite rules required by this plugin have changed or are missing. Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.

Notice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.

Scrolling down I see no button, but another note

Mod Rewrite Rules

Mod Rewrite rules cannot be updated!

You must have BEGIN and END markers in /.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:

# BEGIN WordPress
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
Refresh this page when you have updated your .htaccess file.

My host says we can do mod-rewrite. I do have

# BEGIN WordPress
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

in my .htaccess already…

I don’t know what is going on…

Bob,
Should I click to “use PHP” instead of “use mod rewrite”?? (I don’t really what that means…)

Would anyone please give me an advice??

Thank you.

Hi

I found that I had to copy the “example” .htaccess stuff directly from the Super Cache admin page into the .htaccess in the wordpress root directory to get it to recognize that it was there. Maybe I had a typo, who knows.

Once the correct stuff was in .htaccess It then brought up more stuff on the Super Cache page to allow it to try the .htaccess rule add. The file needed to be writable by the server in order for that to work.

Again, I only saw this stuff after I checked “use mod_rewrite” instead of “use PHP”. Getting the “use PHP” up and running was very simple.

Bob

Hi Bob,
Thank you for your info.
I already had .htaccess in my file.
But a support person suggested me to add another, totally new, different .htaccess in the file “wp-content/cache/”.
Now I have one .htaccess in the main file and have another one… the file “wp-content/cache/.htaccess”.

I already had copied

# BEGIN supercache
<IfModule mod_mime.c>
<FilesMatch “\.html\.gz$”>
ForceType text/html
FileETag None
</FilesMatch>
AddEncoding gzip .gz
AddType text/html .gz
</IfModule>
<IfModule mod_deflate.c>
SetEnvIfNoCase Request_URI \.gz$ no-gzip
</IfModule>
<IfModule mod_headers.c>
Header set Cache-Control ‘max-age=300, must-revalidate’
</IfModule>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType text/html A300
</IfModule>

# END supercache

in my newly created wp-content/cache/.htaccess

Did I follow a wrong advice? Should I have copied this into the .htaccess I had already?

I see this in my page source.

<!– Dynamic page generated in 3.292 seconds. –>
<!– Cached page generated by WP-Super-Cache on 2010-11-02 15:24:32 –>
<!– super cache –>

Does that mean the plugin is working even though the wp super cache plugin page still says

Mod Rewrite rules cannot be updated!

Any help would be appreciated.
Thank you.

Hi

There are two .htaccess files involved here. One is in “/” and the other one is in “/wp-content/cache”. The one that needs the # Begin stuff is the one in “/” . The “Rules cannot be updated” is complaining about the “/.htaccess” file and not about the “/wp-content/cache/.htaccess” file.

Bob

Hi Bob,
Does that mean I should delete the file “wp-content/cache/.htaccess” and add

# BEGIN supercache
<IfModule mod_mime.c>
<FilesMatch “\.html\.gz$”>
ForceType text/html
FileETag None
</FilesMatch>
AddEncoding gzip .gz
AddType text/html .gz
</IfModule>
<IfModule mod_deflate.c>
SetEnvIfNoCase Request_URI \.gz$ no-gzip
</IfModule>
<IfModule mod_headers.c>
Header set Cache-Control ‘max-age=300, must-revalidate’
</IfModule>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType text/html A300
</IfModule>

# END supercache

# BEGIN WordPress
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

in the “/.htaccess”?
Is the order right?

Do I need to add the lines

RewriteEngine On
RewriteBase /

somewhere?

Thank you.

If i put that code in mt htacces file, my site is failing…

Oh, no, runningplus. That’s not good…
Did you ever find the solution? I hope someone would help us!!

Hi

No, the “BEGIN WordPress” stuff does not go in /wp-content/cache/.htaccess.

The stuff you have shown between # BEGIN supercache and # END supercache is correct for /wp-content/cache/.htaccess.

Completely different rules go into /.htaccess once it is set up with the # BEGIN WordPress and # END WordPress tags. The only thing you need to do manualy is add those tags to /.htaccess if they are not there already. Everything else you need is done for you by the magic of the Super Cache admin page.

If you are having all this trouble why are you using rewrite caching? Just click the box for php caching and all these issues will go away.

Bob

Hi

One other point, you do not want the goop between the tags in the /.htaccess file. What you add looks like this:

# BEGIN WordPress
# END WordPress

and not like this:

# BEGIN WordPress
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

That all *assumes* you have a blank /.htaccess file with nothing in it. If there’s stuff in there already you would do this:

# BEGIN WordPress
everything that's in there now goes here
# END WordPress

That assumes that WordPress put the stuff in the /.htaccess file. If not you will have to figure out where the file came from.

Bob

Thank you, Bob.
I am learning a lot.

Hi

Mod_rewite is a fine thing. It’s recomended mainly because it adds a slight bit more performance. The setup is much more involved. I suspect it’s more likely to have strange interactions with other stuff. I have benchmarked both mod_rewrite and php on my site and found little differance in static tests. Static testing is *never* perfect, so in the real world there may be a greater differance.

Bob