Help with Fixing Permalinks after Network setup

  • Preeminent

    (@preeminent)


    13 years ago

    I know there are a bunch of threads all over about Permalink issues, but I really haven’t found a solution that works for me. I have been using 3.1 with no problems. Tonight I decided I wanted to try out two blogs on one server. I followed all instructions. As you can imagine, now none of my custom permalinks work because of the added /blog that is added in. My .htaccess file has been updated with:

    # BEGIN WordPress
    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]
    # END WordPress

    I’ve updated my config.php file with what I was told to do.

    I’ve tried the plugin that fixes permalinks and it just redirect you to the home page when a post link is clicked on.

    I’ve deactivated all plugins.

    The only way they work is if I choose the “default” option.

    I’m on a 1and1 shared server.

    I’ve seen a few mention that they edit a line out of their “functions.php” file. I have been looking all throughout mine and cannot find the $wp_rewrite->flush_rules();
    area anywhere. Can anyone give me a general idea of where it’s at? Towards top, middle, bottom etc

    I read that it was going to mess up my permalinks before I went through with this, but I did it anyway! Stupid! If I go back, will everything be all screwy still?

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Bookewla

    (@bookewla)

    13 years ago

    Exact same issue with /blog/ – i’ll go see some other threads but will watch here too for a solution.

    Bookewla

    (@bookewla)

    13 years ago

    i didn’t know it would mess up my permalinks or I’d probably not have done it 🙁

    Andrea Rennick

    (@andrea_r)

    13 years ago

    Change your install to subdomain format.

    http://wpmututorials.com/hacks/forcing-subfolder-blogs/

    Same instructions, but do the reverse. That’ll fix the permalink.

    Then if you want to remove multisite:

    http://wpmututorials.com/how-to/how-to-disable-multisite/

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Thanks for your reply Andrea! I was under the assumption that I did do the subdomain install?! I will check the link you provide as soon as I get home tonight. But yes, if I can fix the permalinks I want to use this network feature.

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Hmm, well here is what is going on. My main blog is located at http://www.mysite.com/blog separate from my main http://www.mysite.com.
    I now plan on using the multisite network feature to have another blog and theme located at http://www.store.mysite.com does that make sense? Is this going to be possible while keeping all old blog posts from mysite.com/blog intact, as far as permalinks go?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    13 years ago

    Where is WOrdpress installed?

    if it’s physically in the folder /public_html/blog you CANNOT do subdomains. Period. Don’t work.

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Ok well what if I just create another folder for it. For example:
    http://Www.mysite.com/store and have that be my 2nd wordpress blog in addition to the http://www.mysite.com/blog which currently has the broken permalinks.
    Does this make sense? I hope I’m explaining myself clearly. Basically i would like my original blog to stay the same without broken permalinks, but setup my install with another wordpress theme as my store. I appreciate the replies!

    Andrea Rennick

    (@andrea_r)

    13 years ago

    – the /blog is only inserted in subfolder installs.

    – if you only ever want one more blog… multisite is probably overkill.

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Ok, now I’m just lost, sorry! You say that multisite is probably overkill, but how else can I have basically a separate blog and theme on the same server/database/domain and still be part of my main site like my http://www.mysite.com/blog is? I guess what I need to know is what is the best way for me to keep my http://www.mysite.com/blog and also start a http://www.mysite.com/store portion of my site. But have the /store be a separate blog and theme? All without messing up my current /blog permalinks?

    And to maybe help more: when I added the multisite feature, I ended up with http://www.mysite.com/blog/blog/category/postname when I click on any post title link, and that extra /blog is screwing things up.

    I originally was going to do a http://www.store.mysite.com subdomain, but I can’t do it that way. Can I just create a new /store directory and have that new blog and theme be pointed to that directory?
    Again, I feel like i’m making things harder to understand, but I want to make sure I explain what I’m trying to do. I really thank you for any direction you can give!

    Andrea Rennick

    (@andrea_r)

    13 years ago

    make a folder called /store, install another copy of wordpress in it.

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Ok, well now that I’ve gone and screwed things up for nothing! I’ve got another problem! I changed everything back to what it was before trying to go multisite. (edited wp-config and my .htaccess files back to what they were) During that whole process of trying to fix broken permalinks, I reset my blog back to default permalinks, because that was the only option that worked. I probably know the answer, but is there anyway to get my blog back to the /%category&/%postname%/ permalinks that I had? If I now try to change them from default to that, all hell breaks loose and I’m taken back to the LOGIN screen (which won’t let me login) and if I try to access my blog’s url, nothing happens. If I delete my .htaccess file from the server and then reupload, I can get things back up but with only default permalinks.

    Here is the .htaccess file I’m using:

    AddType x-mapp-php5 .php
    AddHandler x-mapp-php5 .php

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

    Should I change something?
    I can’t believe I did this! For some reason, I had it set in my brain that I had to go the multisite route to get another blog going. Geez!

    Andrea Rennick

    (@andrea_r)

    13 years ago

    http://wpmututorials.com/how-to/how-to-disable-multisite/

    Gianfranco

    (@gian-ava)

    13 years ago

    Preeminent, are you installing WP Multisite only to have a logial permalink structure?
    Like defing secttions for your website: Blog, Store, …

    If so, looks like you are suffering from this WP limitation problem:
    http://wordpress.org/support/topic/permalinks-infinite-frustration-a-huge-wp-limitation-problem

    Or am I wrong?

    Thread Starter Preeminent

    (@preeminent)

    13 years ago

    Thanks Andrea, I’ve used that link and dropped those items from the database.
    I still can’t get my permalinks back to /%category&/%postname%/ every time I set it back to this, I get sent to the admin login page and it won’t let me log back in.
    If I take my .htaccess file off my server, I can go back and login. If I upload the .htaccess file back up, every thing still works fine, except if I try and change the permalink structure back to/%category&/%postname%/ Does it seem like I’m stuck with default permalinks now?

    Andrea Rennick

    (@andrea_r)

    13 years ago

    I have no idea without going an looking, which I can’t really do.

    Could be some leftover stuff in the db. that is where I’d start.

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • The topic ‘Help with Fixing Permalinks after Network setup’ is closed to new replies.