Can't get aMember to work with Wordpress

Hello,

I just installed aMember on my site and have protected one of my directories with htpassword.

I've got a Wordpress installation set up in the root directory of my site that I do not require people to register to see. Open access.

When I try to access the blog at the root / main site, (www.bimrg.com)I'm presented with the log in box for the protected directory.

After reading some posts on this type of issue over the weekend, I understood the way to resolve it was to edit the .htaccess file in both the root (the one being used by the WP installation) as well as the .htaccess file in the protected directory.

I added the contents of the .htaccess file in the protected directory to the bottom of the content in the WP .htaccess file. I also added the contents of the WP .htaccess file to the to the top of the .htaccess file in the protected directory.

After I did this, I got a message that the file can't be found when I try to access the protected directory. (404 Error: Not Found!) The only way I can access the protected directory AND the WP installation is to remove the .htaccess file in the protected directory.

Any ideas of how I can get both the free (& no registration required) root directory WP installation to work with my aMember installation?

Here are the contents of the .htaccess file I'm using in both the root directory and the protected directory:

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

########### AMEMBER START #####################

AuthType Basic

AuthName "Members Only"

AuthUserFile /home/bimrgco/public_html/amember/data/.htpasswd

AuthGroupFile /home/bimrgco/public_html/amember/data/.htgroup

Require group PRODUCT_1

########### AMEMBER FINISH ####################

Thanks

Warren

Hi Warren,

You might have incidentally protected the wrong directory. You need to recheck on your settings.

If you still need help resolving your issues, email me codeispoetry [at] amemberincremental.com

Lee

Need A simple code change

I had this problem too. I am using a blog for both the free side and a protected blog for the members only. I found an easy solution on the wordpress site.
The easiest way to fix this is to make the following change, which I found at the following link: http://codex.wordpress.org/Installing_Multiple_Blogs

"By default, WordPress assigns the table prefix wp_ to its MySQL database tables, but this prefix can be anything you choose. By using more than one, you create unique identifiers for each blog in your database. For example, let's say you have three blogs to set up, with the names Main, Projects and Test. You want to substitute the prefix wp_ for each blog's wp-config.php:

Main blog:

$table_prefix = 'main_';

Projects blog:

$table_prefix = 'projects_';

Test blog:

$table_prefix = 'test_';

As noted, you may use a prefix of your own making. Those provided here are for example purposes only.

Upload each wp-config.php file to its specific root/installation directory, and run the installation.

You simply open each wp-config.php file in each blog installation, and change the table prefix to a different label as shown above. It worked like a charm.