I'm having some trouble protecting the wordpress section of my membership. So far I have my membership setup as follows: I protected this folder... Domain.com/members within that folder I have a wp installation and a phpbb3 installation. Domain.com/members/wordpress and Domain.com/members/forum I also have a page setup at domain.com/members/product.html, this simply links out to the forum and wordpress sections so my members can find them (this is the product page for the subscription). The product subscription page and the forum are both being protected like they are supposed to be, but for some reason my wordpress section is still unprotected. any ideas as to what the problem might be? Thanks in advance -Derek
Hi dhales, If you are looking to protect Wordpress such that only members can access it, you need to use aMember to protect your wordpress folder with new_rewrite. This should work for you if you have only 1 product/subscription. Lee
Have you placed the blog in a protected directory (walled garden) or are you trying to protect posts allowing teaser text (magazine model)? David
I'm trying to go with the walled garden approach. I've protected the top level directory of domain.com/members. In which I placed a folder for my wordpress installation (domain.com/members/wordpress) and a folder for my phpbb3 installation (domain.com/members/forum). The forum is being protected, but wordpress is still open. I'm using the new_rewrite protection method.
Not sure if this helps or not, but when I try to protect only the wordpress folder (domain.com/members/wordpress) I get the following 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. "
Hi dhales, The error message is because you have pretty Permalinks activated for Wordpress. You need to deactivate it first before you protect the Wordpress folder using aMember (choose the default links option, where /?p=123, save and try protecting the folder again. Delete the .htaccess file in the WP folder if you need to.) The downside here is you can't have both "walled garden" concept and pretty permalinks. There are many aMember users who want to give a better customer experience when delivering content, which is logical considering that the most of the interaction between you and your customer is in the membership area and your CMS. If you would also like to have both "walled garden" and pretty permalinks, I have a plugin that can give you the best of both worlds. Lee