Wordpress Folder Protection Error

Hi,

I installed wordpress on my server at ...com/members and my amember
at ...com/amember. I'm trying to protect my wordpress folder /members
with the "new_rewrite", but it gives me this error:

File exists and contains non-aMember code unmodifiable
by aMember. If you don't need this file, delete it and aMember will
automatically create a new aMember compatible .htaccess file to
replace it.

I also installed the wordpress plugin and activated it.

Any ideas?

Your wordpress directory already has a .htaccess file that amember does not want to write over. You can change it to htaccess.txt and try the protection again in amember and should be ok.

David

Backup original .htaccess file

zimsolve,

I just faced a similar challenge. Luckily backed up my original .htaccess file first to .htaccess_orig Good thing I did, because once amember wrote it's own .htaccess file I was only able to log in to the protected blog directory and get it to format correctly. When I clicked on any of my page links, or blog entry titles (to go directly to the blog's unique page / file), I got a WordPress error message stating the page didn't exist.

Now... that could also be unique to me because I have 2 WordPress blogs running on the same server. Each has it's own SQL database and install, but the fact that they both exist on the same server may be interacting oddly with the amember files/ setup. So... after I did a few tests, I realized all I had to do was open the .htaccess_orig file containing the WordPress security info, copy the few lines of text therein, open the .htaccess created by amember, paste the .htaccess_orig code at the top (above the existing code) and save. All is working fine now.

Best,
Barbara

I still can't get this to work...

The .htaccess I have on my wp-blog is:

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

# 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

Any idea on how to get this to work?

If you rename the .htaccess file what happens?
Do you have it set for SEO? If you are using amember to protect the directory, then SEO isn't needed since the spiders can't get in.

David

This also worked for me. The WordPress part needs to be at the TOP of the file, as noted. I put it at the bottom first and it failed.

This is with folder protection on the WordPress directory, not the WordPress Plugin.

You would think this could be in the manual...