|
afqam_webmaster
|
September 18, 2019 at 6:24 am
I have an instance where an attendee registered and paid via “Invoice”. They received a confirmation email as well as their invoice back in July at the time of registration. Their accounting person is attempting to pay, but unfortunately I cannot find any record of the registration. The issue seems similar to the topic thread here. I tried to locate the registration looking and searching every way possible. I searched registrations for the event as well as all registrations for that registration number. I tried looking through the event registrations and there are none on the date that this person registered. The “pay now” link the invoice they received returns an error that says the registration information can’t be found in the database.
Any ideas what might have occurred here? I assume that even though the system clearly generated this registration record, there’s no way to recover it from wherever it went…
I have the original invoice and the original email notification. Am happy to provide some temporary login credentials for you to look at our site, if that’s helpful.
|
|
Josh
|
September 18, 2019 at 6:57 am
Hi,
In the other topic you linked to, it was found that the site had some caching activated. So what was happening is the registration did not get properly written to the database.
One thing you could check is if you have a database backup that was taken on or shortly after the date of registration in July, you could compare that data with the current database of the site.
If you’re not already taking daily or at least weekly backups of your site’s database, today is the best day to start.
|
|
afqam_webmaster
|
September 20, 2019 at 12:43 pm
We do make daily backups of our site. In this case, it wasn’t worth going back that far and trying to recover the record, I just recreated it. I don’t believe the issues is terribly systemic as we just completed a busy registration period and this is the only dropped record (that I know of). We will continue to monitor the problem, and put in another ticket if necessary.
|
