I've been running aMember for over a year on my existing server but am now migrating to a new hosting company and have run into a problem with aMember. Specifically, when I click the 'Protect Another Folder' link, nothing happens; i.e. aMember seems to freeze and renders the rest of the control panel inoperable. The only way I can re-access it is to log out using a different browser. I've run tester.php, and it reports the following: Code: Testing whether your system has ionCube Loader in php.ini...OK Testing results: No additional configuration required and aMember will work on your hosting using the following loading method: ionCube Loader installed Additional information: PHP version 5.1.6 (apache2handler) OS Linux 179703-www1.chromasia.com 2.6.18-92.1.6.el5 #1 SMP Fri Jun 20 02:36:06 EDT 2008 x86_64 safe_mode Disabled enable_dl Enabled extension_dir /usr/lib64/php/modules PHP Extensions libxml, xml, wddx, sysvshm, sysvsem, sysvmsg, SimpleXML, sockets, SPL, shmop, Reflection, pspell, posix, mime_magic, iconv, hash, gmp, gettext, ftp, exif, date, curl, ctype, calendar, bz2, zlib, openssl, apache2handler, dbase, dom, gd, imap, mbstring, mysql, mysqli, PDO, pdo_mysql, pdo_sqlite, SQLite, xmlreader, xmlwriter, xsl, ionCube Loader CURL binary /usr/bin/curl Also, there are no errors in either the aMember logs or my server logs. I've raised a ticket, and am waiting to hear back, but in the meanwhile I wondered if anyone else had experienced the same problem or could suggest anything I could try to fix this? I suspect that I could generate the .htaccess files manually for new products, but am worried about activating my new server when I know there's a problem with this installation. Best wishes, Dave
Sounds like an issue with one of the protection plugins or an issue with the root folder setting of Amember. For troubleshooting purposes: 1) in Amember Admin -> Setup -> Plugins... make note of which protection plugins are enabled and then disable all of them 2) Try to go to protect folders 3) Enable the one at a time (starting with .htaccess), going to protect folder after each until the problem returns.