matia

I ‘m having trouble with WP multisite today (I kinda miss the Mu days) and it couldnt get a db connection because after enabling multisite WP thought it was a good idea to look for tables with “_1” in the middle of the table names. So I’ve changed the table names from phpmyadmin and then it relaxed with the database connection.

But now I have a problem with the permalinks too
It adds a silly index.php in all permalinks and doesn’t want to let me remove it >: (

oops ??

so I should somehow recreate edit.php as edit-sortedByViews.php if I understand correctly. Do you have any suggestions on which path should I choose?

Thank you very much!

ps I was talking about the posts list in edit.php

I was really convinced because I tried it on two different machines, one with apache and the other with nginx. Thank you for checking it yourself, I ‘l have to “dig” deeper into my setup I guess :”)

I think that the .htaccess rules that SuperCache suggest needs some modifications to work the way we both wish.

I’m trying to point out that both in apache and nginx the web server’s rewrites are overriden by php.

But the rewrites don’t work as supposed to and you can test and check that by chmoddin 0 the index.php on a WP installation.

I’ve tried nginx and got the same problem

Just read

https://techblog.evo.pl/en/2009/03/21/how-to-boost-speed-up-your-typo3-website-with-nginx/

let me quote a phrase

“in order to read cache, one has to invoke a php process, read and parse the cached data, and then send the information to the browser.”

anyone?

My other idea is to move myblog.domain.com (WP) to myblog2.domain.com
have a copy of all the supercached files in myblog (which is known to google) and have a .htaccess that would redirect a 404 error to myblog2 (which would be running my WP)

really static has a similar concept but 1) I don’t want to ftp all my posts etc and 2) it doesn’t want to co-operate with any ftp server I’ve tried

I think however there must be a neat .htaccess way to do show the super cached file even if index.php of WP is chmoded 0.

my .htaccess

# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
AddDefaultCharset UTF-8
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP_USER_AGENT} !^.*(Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|hiptop|IEMobile|iPhone|iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|Playstation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows\ CE|WinWAP).*
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_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP_USER_AGENT} !^.*(Android|2.0\ MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|hiptop|IEMobile|iPhone|iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|Playstation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows\ CE|WinWAP).*
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

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Could my “problem” be in the WP part of the .htaccess and not in the WPSuperCache rules?

First of all thank you very much for replying ??

I already have SuperCache running with it’s own .htaccess rules (copy pasted from the plugin options) and it does serve super cached files

(from a file’s source code:
<!– Dynamic page generated in 0.406 seconds. –>
<!– Cached page generated by WP-Super-Cache on 2009-10-17 12:26:19 –>
<!– Compression = gzip –>
)

But if index.php has 0000 perms, then a super cached file cannot be served. So I’m guessing that index.php is in the way (well in a way that doesn’t help me ;P )