For any of you, like myself, who are using version 3 of aMember and have recently upgraded to WordPress 3.4.2 and are using the WordPress plug-in, you are likely experiencing Page Not Found errors on any pages in your WordPress site protected by aMember. As I was experiencing these problems, Alex just got onto my site tonight and discovered that recent versions of WordPress have changed their core functionality in terms of how redirects are handled. These core changes cause the WordPress plug-in to not work correctly. He was able to quickly correct the plug-in and fix the issue, so the solution is not very far away. Presumably he will be either posting a sticky thread in this forum or providing a new download for the plug-in on the website somewhere or both. Though there is a thread for this in the version 4 section of the forum, I thought I would post this here just to let all you legacy aMember users know.