Amember not writing to .htgroup or password

Discussion in 'Troubleshooting' started by dreemr13, Feb 10, 2011.

  1. dreemr13

    dreemr13 New Member

    Joined:
    Jul 13, 2009
    Messages:
    4
    Not sure when it happened but Amember is not updating the , htgroup or passwords files in the data folder. It's not writing new members and not deleting expired.

    data folder is set to 777 and both the .htgroup and .htpasswd has permissions set to 666.

    I have a VPS so can manage anything on my server. Perhaps maybe something in php.ini or server config?


    Suggestions?



    I have Amember Pro but can't afford the support $80 US upgrade for a year right now. Too bad the 6 months option went away.

    Would be nice to have a monthly subscription via PayPal. $8 a month isn't that big of a deal and it would probably encourage more customers to continue for update support. I first bought Amember in 2003 and only got the $40 support when something went wrong.
  2. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Check aMember CP -> Setup -> Plugins. Do you have htpasswd plugin enabled?
  3. dreemr13

    dreemr13 New Member

    Joined:
    Jul 13, 2009
    Messages:
    4
    That was it. No sure why it was off. Hope you consider the monthly upgrades subscription :)
  4. dblack6047

    dblack6047 aMember Pro Customer

    Joined:
    Feb 7, 2009
    Messages:
    5
    Same Problem - aMember not writing to .htgroup or .htpasswd

    Alexander,

    I just ran into the same problem today when a new member subscribed to a paid membership subscription using the 2Checkout. New member notified me immediately that they could not log into a URL requiring their name and password. I looked at .htgroup and .htpasswd and noticed the member name was not added. All other previous authorized member names were present but just not the new member today.

    I checked aMemberCP > Plugins > htpasswd and it was properly selected as required.

    I have had members subscribing over the past several months using PayPal and have not had any member problems.

    The last 2Checkout member subscription prior to today was back in November 2010 and it appeared to work fine. I have not touched any settings with aMember 3.2.3 Pro since your team had remotely fixed another bug I had back in November so I am not sure if it is related or not.

    Any suggestions?

    David
  5. skippybosco

    skippybosco CGI-Central Partner Staff Member

    Joined:
    Aug 22, 2006
    Messages:
    2,526
    Did you check the users record in aMember? Does it show the new payment?

    Is this the only user having the problem?
  6. dblack6047

    dblack6047 aMember Pro Customer

    Joined:
    Feb 7, 2009
    Messages:
    5
    Yes, the payment was processed and received successfully from 2Checkout. Everything looks accurate in regards to the new member's account and paid subscription details within aMember.

    This is the very first incident or anomaly involving aMember not writing to the .htgroup and .htpasswd files directly after the new member signed up and payed via 2Checkout.

    I do not get subscriptions via 2Checkout that often thus I won't be able to see the anomaly again until someone purchases a similar subscription via 2Checkout. Primarily my members pay with PayPal which seems to be a trend more often.

    Is there a log that shows what aMember does to a member's account during and after the payment transaction?
  7. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Please contact us in helpdesk, provide access info and example of such users that were not updated in htpasswd files we will check what can be wrong
  8. dblack6047

    dblack6047 aMember Pro Customer

    Joined:
    Feb 7, 2009
    Messages:
    5
    Alexander,

    If it does not appear that other users of aMember are suffering from the same anomaly then I will just wait for now until my next 2Checkout customer subscribes to my website to see if the same anomaly occurs again.

    If it does happen again I will contact your helpdesk as you prescribed.

    Thank You,

    David

Share This Page