• Hello everyone,

    I have a wordpress 3.01 site that I upgraded today to 3.01 multisite because I had the plan to install a few users blogs beneath the main site as subdirectories.

    In the original single user site I had permalinks installed as /%category%/%postname%/ however it seems that any custom structure forwards me to a blank page. I can access the original site content under the ‘ugly’ http://www.mysite.com/?p=118 style of link.

    Unlike many users who dislike the /blog/ structure I’d be satisfied with it if I could have my permalinks back.

    My guess is that my .htaccess has an issue somewhere. I’m including a copy below in case any other wordpress users have seen the same thing happen with their upgrade to mu.

    I appreciate any help that can be given.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    RewriteCond %{REQUEST_FILENAME} !-f [OR]
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^ – [L]
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

Viewing 9 replies - 1 through 9 (of 9 total)
  • At a glance it looks right… tho a white page usually means a php-based error.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    I can access the original site content under the ‘ugly’ http://www.mysite.com/?p=118 style of link.

    That’s just weird. Go in and reset your pretty permalinks? I mean, just go in and hit save. See what happens?

    Also, since you’re using suibdirectories, try this:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    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).*) $2 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]
    </IfModule>
    # END WordPress

    I don’t think it’ll matter, but the htaccess code you gave is what showed up on my subdomain site, and not my subdirectory one.

    Thread Starter CJWolff

    (@cjwolff)

    @ipstenu

    Thank you for providing the .htaccess code for subdirectories. I copy-pasted that into my .htaccess code, changed the permalinks back to %category%/%post% and all seems to be well again.

    This is my first major wordpress site and I’m making it for a group of senior citizens…my usual CMS is drupal however I didn’t think the seniors could understand the backend. So you’ve all been very helpful. Thanks!

    Christopher

    Gah, I need to comb over the differences… I read too fast.

    I’m having the same problem with permalink structure – it works fine with default, but generates a 404 error with any pretty structure.

    It’s a new localhost install of 3.0.1 on OS x with multisite enabled. I changed the httpd.conf file allowOverride to ‘All.’ It seems from what I’ve read that it must be an .htaccess issue, but the code above that worked for CJWolff didn’t solve it. Could it be a permissions problem? What should I be looking for?

    I’m having the same problem with permalink structure – it works fine with default, but generates a 404 error with any pretty structure.

    It’s a new localhost install of 3.0.1 on OS x with multisite enabled. I changed the httpd.conf file allowOverride to ‘All.’ It seems from what I’ve read that it must be an .htaccess issue, but the code above that worked for CJWolff didn’t solve it. Could it be a permissions problem? What should I be looking for?

    I changed the httpd.conf file allowOverride to ‘All.’

    look in that same file for mod_rewrite. If it has a # in front of it, it’s disabled, so remove the #.

    Thanks, Andrea. No, the lines in httpd.conf weren’t commented out, but I found the solution here:

    http://blog.401consulting.com/2010/06/enabling-pretty-permalinks-in-wordpress-on-osx-10-6/

    In my case, the suspect .conf file wasn’t private/etc/apache2/sites/sitename.conf, it was ..apache2/users/username.conf. The allowOverride needs to be set to ‘All’ in this file instead of (or in addition to?) the main .conf directly under ../apache2

    I didn’t come across anything in the codex that warned about other possible .conf files that require editing. Maybe it’s only the case when there is more than one user on a mac?

    or because it’s on a mac? 😀

    Apache on Linux boxes usually only deals with the one file. unless Plesk is involve,d which is also different.

    So… OSes matter, is my point. I think But hey! you found it. allowOverride was my next tip.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Changed site to network, lost prettypermalinks’ is closed to new replies.