Redirection Issue – 2 installs on a domain – 1 is a buddypress

There could be a misconfiguration on your .htaccess which leads to the broken links. You may want to input the below code to your .htaccess.

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

Thanks CrazyDeals ..

I deleted both .htaccess on the root (buddypress) and /blog/ (blog) and replaced the blog with the above (after modified RewriteBase /blog line)

That worked and allowed me to save permalinks again, and then I went into wp-super-cache settings and revised .htaccess again .. and now both sites permalinks works

> until next time.

Do you have any recommendations about caching?

IT seems that the buddypress (root) and W3 Total Cache someone mentioned to NOT cache .htaccess … and it seems like wp-super-cache- in the blog (/blog/) installation the .htaccess pops up in the always cache “even if they match one of the rejected substring”.

I wish wp-super-cache worked in buddypress for the activity .. it will cache the blog posts but, that’s not buddypress. That w3-total-cache is confusing to me.

HART

I can imagine the number of odd conflicts… Why aren’t they both running off the same site with w3 total? I mean, having two installs like that is counter the idea of multisite…

ipstenu ..

This is the site: https://PetLvr.com/blog/ – i’ve had it over 5 years now and almost 4000 posts and everything that goes with it .. images, store, etc

This month I wanted a community separate from the blog and installed it on the root https://PetLvr.com

I suppose this would be nice if I can figure a way how to get the blog on the root and still have a community on the root and still save all the data and everything else. I have a multi-site on https://PetLvr-Blogs.com allowing registration and wouldn’t want people to register blogs on the same database as the existing blog

Any suggestions? How would I merge a blog or meld into a multisite where the “subdomain” /blog/ exists before the root domain?

HART

I had to think about this for a while.

https://PetLvr.com/blog/ actually should already be conflicting with the main site at https://PetLvr.com/ because the default folder name for the main site’s blog is … blog. And that’s probably why things go pear shaped now and then!

I can see two options

1) Move https://PetLvr.com/blog/ to https://PetLvr.com/ and upgrade it to 3.0 multisite, making it your ‘main’ site, and spawn the community off of that. By default, all your posts will show up in https://PetLvr.com/blog/ (https://PetLvr.com/blog/postname for example), but the ‘main’ page would be

2) Deallocate the /blog folder and then export/import https://PetLvr.com/blog/

To deallocate,
* Login to your admin site for https://PetLvr.com/
* Go to: Super Admin > Sites > Edit
* Edit the site for your MAIN blog (normally site #1)
* Scroll down to “Permalink Structure” and change the “/blog” part to something else. “news” maybe, but anything BUT blog!
* Save

Then you go into https://PetLvr.com/blog/ and export the posts. Rename the blog folder to ‘old-blog’ or such to disable it. Make a new subsite in https://PetLvr.com/ and call it blog. Import the posts.

Which one you do depeneds on what you want your blog to look like at the end of the day. If you want to keep the /blog/ folder or not, etc etc. it’s not an easy answer :/ it’s a reorg and you have to pick the way you like it best.

Ipstenu’s 1st option will allow you to keep SEO juice for blog which has been out there for a while already. Just back up /blog/ database and server files (don’t forget htaccess), then export XML file from /blog/ and then delete /blog/ site.