Recenly, i upgrade Amember Pro to version 4.6 After this updgrade, when my costumers tried to acces to any protect content and the put the credentials, the site has a infinte loop that causes 302 error on customers browsers "Too Many Redirects" Any body has a solution to this problem. Thanks
What version did you upgrade from? Test with one of the products and rename the .htaccess file in the directory (or back it up and delete it) and then reprotect the folder.
I'm using 4.2.6 I'm using wordpress plugin w/new_rewrite where i can find .htaccess file? Thank you for your response.
1. What version were you using previous to 4.26? 2. What version of Wordpress are you using? I assume this protection worked before without the looping? .htaccess is for file/folder protection, so not a consideration for your Wordpress setup, but same logic applies. I assume non-protected pages are not experiencing this issue? Trying protecting a new page and see if the problem occurs or if it is just related to pages that were protected on your previous version of aMember.
Previously Amember was 1.4.15 My wordpres version is 3.4.1 Yes, the proctection and redirects works good befores upgrade to 4.2.6 The, non-protected pages/post, are functioning without problem. Thanks skippybisco, i'm triying to fix this, because my site is live, and no customer can view protected pages.
1. If you protect a new page does the looping occur? 2. If you unprotect a page does the looping stop? (Does it start again when you re-protect it?) 3. I notice you are running the latest version of Wordpress. Did you upgrade aMember and Wordpress at the same time or is the looping only a result of the aMember upgrade?
1.- Yes. When i proctect a new page the loop occurs. 2.- No. When desactive proctection, posts are displaying without problem. 3.- I updgrede both at the same time. Thanks
In the future you should upgrade and test your scripts independent from each other to help isolate any issues that occur. That being said, if you have not already, open an aMember support tickets as I'm not sure there is much more to do without actually checking out your site and configuration and figuring out if the issue is with aMember or with Wordpress.