Redirection Issue - 2 installs on a domain - 1 is a buddypress (7 posts)

  1. PetLvr
    Posted 5 years ago #

    This is frustrating for me.

    I have the latest wp in both.

    domain.com/blog - is a separate installation and the main blog
    domain.com - is a separate installation with buddypress

    domain.com/blog - is using Wp-Super-Cache for caching posts etc
    domain.com - is using W3 Total Cache excluding pages for caching activity

    Every day one or the other site's permalinks do NOT work, and I have to re-save the Options/Permalinks ... I usually just do both - then the permalink posts work fine.

    I'm in the process of setting up the buddypress site and tweaking stage . yet, according to my WHM since I've done that my CPU resources jumped from 49% to 74% ... This week I did the same thing to another domain and setup a buddypress site - but in a folder, not the root - and the permalinks work fine. The CPU Resources jumped from 74% to 89% and fluctuates now between 70-90% all the time. There are not many people on my site at a time .. maybe 9? 10? 35 at most?

    Is there any recommendation for getting this caching under control and redirection? I can't even access my blog right now because of it .... http://PetLvr.com/blog/


  2. crazydeals
    Posted 5 years ago #

    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]
    # END WordPress
  3. PetLvr
    Posted 5 years ago #

    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.


  4. 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...

  5. PetLvr
    Posted 5 years ago #

    ipstenu ..

    This is the site: http://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 http://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 http://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?


  6. I had to think about this for a while.

    http://PetLvr.com/blog/ actually should already be conflicting with the main site at http://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 http://PetLvr.com/blog/ to http://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 http://PetLvr.com/blog/ (http://PetLvr.com/blog/postname for example), but the 'main' page would be

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

    To deallocate,
    * Login to your admin site for http://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 http://PetLvr.com/blog/ and export the posts. Rename the blog folder to 'old-blog' or such to disable it. Make a new subsite in http://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.

  7. @mercime
    Volunteer Moderator
    Posted 5 years ago #

    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.

Topic Closed

This topic has been closed to new replies.

About this Topic