WordPress .htaccess & amember .htaccess

Discussion in 'Setting-up protection' started by lauren, Aug 12, 2008.

  1. lauren

    lauren New Member

    Joined:
    Aug 11, 2008
    Messages:
    10
    New user alert! (and I'm 0 for 2 so far today....)

    I'm protecting a Word Press blog in a /members directory. I read the posts here and it was suggested that I delete my Word Press .htaccess file and let aMember put its own in -- which I did. And it worked.

    Here's the problem:

    Now when I click on any page inside my blog, they are all redirecting to my home page of my site. "www.sitename.com". Not good!

    I know this must have to do with taking out the Word Press .htaccess file, and evidently, I need this!

    Suggestions anyone? Grrr. Stuck again!

    How do I get Word Press to still operate like Word Press. I guess these .htaccess's do not play nice with each other?

    Lauren
  2. davidm1

    davidm1 aMember User & Partner

    Joined:
    May 16, 2006
    Messages:
    4,437
    Create a new product in amember called admin, and give it admin privileges in wordpress. Then add a new user in amember and assign this product to them.

    This should let you in and give you a user account in wordpress to post articles etc..


    David

    Edit- just reread, ah, sounds like you have some sort of SEO plugin? Try turning this off?
  3. lauren

    lauren New Member

    Joined:
    Aug 11, 2008
    Messages:
    10
    Hi David,

    Wow, you're super helpful! You're 2 for 2 helping me today! :)

    My WP blog is Semiologic Pro v.5.5 RC-3. It comes with a ton of plug-ins already enabled, but there is one called Semiologic SEO. I deactivated it, but the site is still redirecting all blog pages to the root url (not the membership site, but the main page of my public site).

    I'm at a loss. Any help is appreciated.

    Lauren

    Edit:
    I thought this might be helpful. The Word Press .htaccess contained this:


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

    # END WordPress
    AuthUserFile "/home/sitename/.htpasswds/public_html/members/passwd"

    I deleted that one one and replaced with Amember's automatic one that contains this:

    ########### AMEMBER START #####################
    Options +FollowSymLinks
    RewriteEngine On

    ## allow access for any active subscription
    RewriteCond %{HTTP_COOKIE} amember_nr=([a-zA-Z0-9]+)
    RewriteCond /home/sitename/public_html/amember/data/new_rewrite/%1 -f
    RewriteRule ^(.*)$ - [L]

    ## if user is not authorized, redirect to login page
    # BrowserMatch "MSIE" force-no-vary
    RewriteCond %{QUERY_STRING} (.+)
    RewriteRule ^(.*)$ http://www.sitename.com/amember/plugins/protect/new_rewrite/login.php?v=-any&url=%{REQUEST_URI}?%{QUERY_STRING} [L,R]
    RewriteRule ^(.*)$ http://www.sitename.com/amember/plugins/protect/new_rewrite/login.php?v=-any&url=%{REQUEST_URI} [L,R]
    ########### AMEMBER FINISH ####################

Share This Page