Mass pay not working in 6.3

[Chris74]

Customer pays all open invoices but some of them remain unpaid and services don't get renewed. Seen this half a dozen times since upgrading.

 

Anyone else having this problem?

[web2008]

Yes, I opened a ticket on 2nd April for this problem and WHMCS answered the following:

 

There haven't been any problems reported with mass pay in 6.3 at this time.

[WHMCS John]

Hi,

This behaviour indicates that a fatal PHP error is occurring at the time of payment which prevents all the original invoices being marked paid.

 

This is not how I would expect a stock WHMCS installation to behave. Could you please ensure there are no customisations present on your installation as these can often change the way WHMCS operates.

These are typically located in the /includes/hooks and /modules/addons directory (and maybe also /modules/admin if it's an old customisation)

 

Once the issue is resolved you can add them back one-by-one until the problem begins again - at which point you have identified the troublesome customisation and can contact the vendor directly for assistance resolving the problem in their code.

 

If the problem persists after that I'd recommend adjusting your PHP configuration to log errors to a file. Next time the problem occurs, you can refer to the log file at the time of payment to see the cause.

[Chris74]

Just wanted to add that I'm also getting invoices paid by credit for multiple domains where the domains are not getting renewed at all. I have a client that pays everything by credit and sets his domains to auto renew. He just pointed out two invoices, each automatically generated with more than 5 domains where none of them were renewed. The invoice shows credits being added with no balance to pay. When I started this thread, I seem to remember that credits might be a common factor with the invoices where items didn't renew.

 

Web2008 - are you seeing this only happen when the client pays (or partially pays) by credit?

 

 

There doesn't seem to be any error checking in WHMCS that lets you know when a domain was not renewed successfully. I see plenty of notifications for domains that did renew - but none for any that didn't.

 

How am I supposed to know when this happens?

 

Looking at the client log, it shows the invoice being paid and then the domain renewals being run on payment - then it shows individual entries for the first three domains in the invoice showing them as being renewed and then emails being sent to the client accordingly - but then no other log entries for items on that invoice, despite there being another half dozen domains in the invoice that needed renewing. There is no log entry to show that any of the remaining domains failed renewal, or even that the renewal was attempted.

 

There are no notifications sent to the admin to show that the process failed.

 

Sorry to be blunt, but that really sucks! It should at least let us know if there was a problem renewing one or more of the items.

Edited May 4, 2016 by Chris74

[brian!]

Chris,

 

are you still using v6.3.0 or have you upgraded to v6.3.1 ?

 

I ask because there was a renewal bug in v6.3.0 that has, supposedly, been fixed in v6.3.1

 

http://forum.whmcs.com/showthread.php?113870-Auto-Renew-on-Payment-Issues&p=461722#post461722

[Chris74]

I just want to add that the way WHMCS renews products and services on the fly is a really bad idea. If a client pays for the renewal of, lets say 10 domains, they have to sit there at the checkout while WHMCS processes those jobs to each relevant registrar. Even with a super fast server, this can cause quite a delay for the page to refresh.

 

What you need is a "job queue" that runs via cron every few minutes so that any renewals or API calls that need processing are not done while the client waits for those processes to complete. This was one really good (possibly the only good) thing about AWBS. When an order was placed, or approved, the relevant tasks, such as setting up the hosting or registering / renewing a domain were queued and you could view the job queue to see what was ready to process , run individual jobs and importantly, see which ones failed.

 

This complete lack of logging is really scary. Surely every attempted task should be logged somewhere?

 

- - - Updated - - -

 

Chris,

 

are you still using v6.3.0 or have you upgraded to v6.3.1 ?

 

I ask because there was a renewal bug in v6.3.0 that has, supposedly, been fixed in v6.3.1

 

http://forum.whmcs.com/showthread.php?113870-Auto-Renew-on-Payment-Issues&p=461722#post461722

 

Thanks Brian - I'm on 6.3.1 and applied a fix before that.

 

- - - Updated - - -

 

Ahh - I've just realised that the invoice dates on the ones that failed are around the 10th of April. I think 6.3.1 was released on the 14th.

 

I will keep an eye on things and see if this happens again. it could be that 6.3.1 has resolved this issue.