I did go over this in the sticky.
The htaccess is not, in fact, being read properly.
Also you may as well just share your .htaccess 🙂 It may look right to you, but a second pair of googly eyes can help.
My .htaccess:
# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) includes/ms-files.php?file=$2 [L]
# add a trailing slash to /admin
RewriteRule ^([_0-9a-zA-Z-]+/)?admin$ $1admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
I looked at your sticky Andrea and I contacted my webspace provider however they said that everything is running correctly and that it is calling the .htaccess file. I have not really played much with .htaccess files much in the past so I’m not enlightened on how to double check these things.
There’s at least one typo under add a trailing slash to /admin so try this:
# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress
it LOOKS like all the wp- prefixes to your locations got stripped somehow o.O
Ya I removed them because I changed the name of my wp-admin folder.
Since I have renamed the wp-admin I am just calling it admin for now-so no it isn’t a typo.
Ya I removed them because I changed the name of my wp-admin folder.
Since I have renamed the wp-admin I am just calling it admin for now-so no it isn’t a typo.
Ugh. Seriously there’s NO need to do this, and it’s going to cause hassles. It doesn’t make your site any safer (the SQL injections still exist) and people can easily suss out what your admin side is with a big of bot-attacking. You gain nothing except headaches. Also? You screwed up your .htaccess by just removing ALL the wp-‘s. LIke the ones for wp-content (where your stylesheet is) and wp-includes (where other needed files are).
If you MUST keep it, try this, but I have no idea if it’ll really work. It’s a theory.
# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
# Also for /admin - just in case something else needs redirecting
RewriteRule ^([_0-9a-zA-Z-]+/)?admin$ $1admin/ [R=301,L]
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
# END WordPress
BTW, when you make support posts, you should be upfront with stuff like that 🙂 It makes it easier to debug if we know what YOU did.
Not to be a jerk ipsten but “I do however wish to note that my wp-admin directory is not labelled wp-admin” – 3rd paragraph.
Thanks for the attempt at helping me it’s greatly appreciated but I just got around to trying your fix out and it didnt help =\……So I dunno I guess I’ll keep searching google for solutions.
I also did notice you took the admin out of one of your rewrite rules can you explain why(the one that has includes|etc)?
sorry, I did miss that. Probably tried to pretend it was like the cake (I.e. A lie… Bad joke!)
I was thinking that since you’re not using wp-admin, you don’t need that part of the redirect, but I could be wrong. Still, if adding that in again doesn’t help, then go back to wp-admin and the bog standard htaccess and try again.
I was just curious – when you install multisite what files does it affect? ie. Does it automatically add in a few lines of code here and there to other files?
It adds database tables and then you add more lines to wp-config and .htaccess, which tell it to call other files.
I reviewed my .htaccess and started making some headway – got the main image appearing now –
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
As you see I bolded the spot that needed fixing – I’m assuming this is a pre-pend for where it is looking for the content, admin, and includes……So now I just need to get the css to display.
CSS should have been picked up by that (as it’s in wp-content).
You didn’t rename wp-content, did you?
No I didn’t – I used firebug and I can see that it is pulling the css from test/wp-content/themes/twentyten/.
What I am not understanding as of right now is why it isn’t loading the css-I’m a completely newbie to wp multisite but after reading the sticky that Andrea posted saying that basically there is no static files created for sub-sites I cannot wrap my head around how I can even begin troubleshooting where the disconnect exists between the web browser(s) (since I use ie and firefox) and the files themselves.
Typically if they were static files you’d think that the browser would be looking for the css files under:
wp-content/themes/twentyten/
being that that is my root directory where the theme physically exists but since I am not sure how wp dynamically grabs the theme from the root directory to make it:
test/wp-content/themes/twentyten/
Now this all leads me to believe that whatever file is calling the wp-content/themes/twentyten/ folders on the test site is not calling the files correctly if you know what I mean.
Now this all leads me to believe that whatever file is calling the wp-content/themes/twentyten/ folders on the test site is not calling the files correctly if you know what I mean.
That file is .htaccess – specifically this line
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
It means ‘/anything/wp-content/anything’ gets redirected to ‘/wp-content/anything’ but the URL does NOT change.
So /test/wp-content/twentyten/style.css is transparently redirected to /wp-content/twentyten/style.css
BTW, http://www.pixelatedkarma.com/test/ looks fine to me now. Flush your browser caches?
The .htaccess file. 🙂 The magic happens all in there. Some users have reported unstyled thems, can’t login to the admin area – it’s all the same issue. the htaccess file.
Sometimes the web server has to be forced to read it.
