In the last month or so, I have been experiencing several recurring problems that are really causing major issues for my customers. I have a help ticket in and I have been trying to troubleshoot this for several days now. But with 24 hrs between responses and little explanation, I am left wondering what is actually happening and if I need to look for another membership software solution. Problem 1: On a regular basis, I log into aMemberCP and see that all of my active users are actually listed as Expired. If I go into their accounts, the dates of all their accounts are valid, yet for some reason they are listed as expired and they can't log in. Problem 2: At about the same time as problem 1, my user count jumped up about 200. It lists no expired accounts (which I know is not true), and seems to include the expired accounts in with the active accounts total. Problem 3: Users are receiving multiple (anywhere from 9 to 20) expiration notifications. I have it set up to deliver one email 20 days before expiration, and another just one day before expiration. I have found that rebuilding the database does temporarily fix Problem 1. But should I have to do this every other day?!?! And it does nothing to help with Problems 2 and 3. Anton recommended setting up a CronJob, but I haven't received explanation on what this CronJob does to prevent all the problems I am experiencing. As you can imagine, this is incredibly frustrating for me and my 650 paying members. Any advice or shared experiences would be welcome.
Sounds like a major problem- keep on tech support to provide a solution. I haven't seen this before. You shouldnt need to use a cronjob to rebuild the database daily, this is pretty sloppy. Keep bugging them till this gets fixed- it shouldnt be happening. David
I should also add that I am using the Wordpress integration plugin and SimplePress forum. Not sure if that plays into it or not. I am wondering if the best thing to do at this point is a complete reinstall. I will be doing some major overhauls to my site theme in the coming weeks. That would be a good time to do it. But it frustrates me that I really don't know what the problem is and how to prevent it from happening again. We are going on 2 years of aMember use so this is quite unexpected. I will definitely keep on the tech support (as much as they will let me).
I would do a 2nd install just for testing- put it on a subdirectory with a new database. Set it all up and then test out some memberships. David
Thanks David. I will have to give that a shot. I am sure a fresh install with a new database will fix it. But without any information on the nature of the problem and what's actually causing it, I fear I will just end up in the same place in another few months. I have had good support from CGI in the past but this time, when the stuff is really hitting the fan, they are falling short. Makes it tough to grow a business if you can't depend on the software that makes it possible. I don't mean to direct my frustration at you.....but you are the only one to respond so far so you are the lucky recipient.
thewoodwhisperer, I took your ticket personally and sent my Skype ID and request for additional info in the ticket. Will handle this asap.
Same Problem I have just logged in today and discovered exactly the same problem. I'm currently running version Stupidly, I haven't backed up for a while. When I login I see only 20 members instead of around 1000, everyone else is shown as expired. It seems as though only the aMemeber database tables are affected on my website database. Still investigating. I'll let you know what I find.
Forgot to mention the version I am running is: 3.1.8PRO. When I do a rebuild the result is the same so the slave database also seems to be affected.
This is weird. My maximum payment term is 3 months so I did a search on payments after 3rd May and show only completed payments. First 60 entries are ok but after that no product is shown and all periods go to 03/05/2010 - 06/05/2010. Also, when I do a check on the database the am_members table is completely empty. The am_members_backup table has 2299 records. Hmmmm... should I replace the members table with the backup table?
Ok, I have decided to ask my host if they can restore the affected database table and then take it from there. I'll post the results here when it happens.