Ever since the folks at aMember did my installation, my site has been messed up. Now, when someone tries to get to my home page, they are sent to my protected folder instead! I have found the help to be good, but certainly not within 24 hours. I am going to uninstall aMember and ask for -- and hopefully get -- a refund, tho the link for requesting a refund takes you conveniently to a 404 page. Is there anything I need to know before simply pulling the files off my server? Thanks and good luck!
The problem with the incorrect redirect is very likely caused by wrong statement(s) in the .htaccess file in your root website directory. If you want, post its content here (nothing really secret there...) and I will try to find the problem statement. Other than that, to remove aMember from your server completely, simply delete the /amember directory (or whatever you named it) and then also get rid of the associated MySQL database. Tomas
Why would file change on its own? Thanks for the answer, tomfra. I will look at file, but why would it change? Actually, the link has worked intermittently all aft. I have gotten no support fr the aMember folks, and I am not technologically savvy enough to fight these battles. I need to spend time on content and marketing, not fighting recalcitrant support folks. If htaccess looks interesting, I'll post. If not, I'll just simply delete and hope my links and pages work again (whole site's a mess!). Thanks again.!
newdesign, 1) when you say "log into homepage of site" are you referring to logging into your aMember installation using a test account? 2) when you are taken to a "protected HTML page" is this a content page that is a part of your membership or a "access denied" kind of page? Two things come to mind: 1) Each product has a Product URL defined. if a member is only subscribed to one product they will go to that URL when the log in. -or- 2) You accidentally protected a folder that should not have been protected. Browse to that folder in your FTP client and rename .htaccess to something else and see if that corrects the issue.newdesign, 1) when you say "log into homepage of site" are you referring to logging into your aMember installation using a test account? 2) when you are taken to a "protected HTML page" is this a content page that is a part of your membership or a "access denied" kind of page? Two things come to mind: 1) Each product has a Product URL defined. if a member is only subscribed to one product they will go to that URL when the log in. -or- 2) You accidentally protected a folder that should not have been protected. Browse to that folder in your FTP client and rename .htaccess to something else and see if that corrects the issue.
Probs Thanks skippybosco: what I mean is when I click on a link on another page of mine that had been dropping people off correctly at my home page, instead I would go straight to the page (the only one) that was supposedly behind the green curtain, if you will, i.e., past the login page. The thing is I had made no changes to anything. Last night it worked, today, sites a mess. And since I am getting no "support," I am giving up and trying for a refund, which I am passimistic about, since refund link takes you to a 404. There must be a simpler solution for my small site -- heck PayPal alone is prolly enough for me -- and am tired of dealing with it all. Your mileage obviously has varied! Thanks again. I am going to take a look at htaccess for the fun of it....
tomfra: htaccess ########### AMEMBER START ##################### AuthType Basic AuthName "Members Only" AuthUserFile /homepages/1/d240340376/htdocs/nds/amember/data/.htpasswd AuthGroupFile /homepages/1/d240340376/htdocs/nds/amember/data/.htgroup Require group PRODUCT_1 ########### AMEMBER FINISH ####################
Changes could be a result of a server reboot, server side software update from hosting, etc. Amember protects folders and all files/subfolders underneath them. In your case it looks like you are protecting via .htaccess. Assuming you are not using a CMS of some kind, the content that you want folks to land on needs to live in a directory that is NOT protected by aMember (nor is it's parent directory) -OR- you have to have a explicit exception defined in your .htaccess file to allow access to it.
newsdesign: If that .htaccess file is in your website "root" directory - i.e. in the same directory as your home page, it's no wonder you are experiencing problems. That .htaccess file has to be in the directory where your protected content is located and nowhere else. If you want to get rid of aMember completely, simply remove or rename it and everything will work again. Tomas
Thanks File was in protcted folder, I believe. This is not for me. I have removed it and am seeking refund. Take care, /b
if for whatever reason you do check back.. move the file out of the protected folder.. any files in that directory will be prompted for login if the user is not signed in or authorized (hence "protected")
skippybosco: I am not sure if by "the file" you meant the .htaccess file, that one should indeed be in the protected folder - this is completely OK. It's possible to place it above the protected folder (one or more levels), or merge it with another .htaccess file above the folder, but it would have to be somewhat modified and that would cause unnecessary complications. .htaccess is a special control file. It's read and parsed by the Apache server as the very first thing when someone attempts to access a directory containing it. In this case, this is the file that decides whether login is necessary. Tomas
Tomas, Was referring to the landing page file that they were dropping users off. By their description it was sounding like it could have been a few things: 1) redirection based on .htaccess (which when they posted their .htaccess did not suggest as such. 2) their landing page was behind a .htaccess protected folder to be honest, it was not quite clear what was going on .. just grasping at straws
@newdesign I agree. The support has been poor and the product has so many caveats you must know in order to make it work. I am at 4 days now trying to get it to work to no avail.. I will try for a refund and see what they say..