
Wordpress MU
When I was making the move to wordpress mu one of the strangess things that i encountered was a problem with pages and looking at full page articles. When every I click on the links I would get an 500 internal server error returned. Since the way that wordpress mu works it has to rewrite the url quite abit to understand what pages to actually get under the covers, for example:
http://phoenix.adamcoulthard.co.uk/blogs/2009/12/08/wordpress-page-hit-internal-server-error
is not an actual page on the server it gets rewritten to something that the server can handle under the covers. I think alot of the problems were occuring because of the way that I had installed wordpress mu (at least this is what I think). I had installed wordpress mu into a directory on the webserver rather than putting it into the root directory. So when it created the .htaccess file with file rewrite information it added a base rewrite of that directory. So if I installed it into wordpressmu/ then its rewrite base would have been /wordpressmu/ in the htaccess file.
After alot of googling with very little luck and attempting to use the write logging again with no luck, I started to think about what that rewrite base would mean to the system. So I had a cPanel setup of *.adamcoulthard.co.uk pointing at /html/wordpressmu/ meaning that all the sites had to go to the wordpressmu folder straight away. So if the rewrite base was adding on /wordpressmu/ then it would mean that it was going to be trying to navigate to /wordpressmu/wordpressmu/…. leading to the internal server error (I would have expected a 404 not found but nevermind).
So what I did was set the base to being just / and that solved the problems of loading the articles.
0 Comments until now.
Comment!
You must be logged in to post a comment.