Domains > Next Due Date

[DJFireCFH]

How can you change the next Due date Manually?

 

The invoice was paid for 2 domains, However, the next due date refuses to change. It should have changed to 02/01/2017 & 02/04/2017, but it's still on 02/01/2016 & 02/04/2016.

 

By looking at the expire dates, they are set fine and show 2017, however the due date is still on 2016 and all invoices are paid in full for both the domains. So the next due date should have changed, right?

 

Is there a way to change them manually? Because changing the date, and then saving, just reverts back to the same date. How can I change to date to show what it's suppose to be?

[WHMCS John]

Hi,

You can certainly change the Next Due Date manually.

 

If the date did not increment forward automatically this suggests a problem at the time of payment. What entries do you see under Utilities > Logs > Activity Log at the time of invoice payment?

[DJFireCFH]

Just says:

 

02/01/2016 01:09 Email Sent to (Name removed for privacy) (Invoice Payment Confirmation) - User ID: ###

 

02/01/2016 01:09 Invoice Marked Paid - Invoice ID: ######

 

02/01/2016 01:08 Added Invoice Payment - Invoice ID: ######

 

 

There's no log that shows any kind of action for the domain due date other than when I tried to do it manually, which was around 02/01/2016 09:34.

 

But the due date wouldn't change.

 

I tried setting the date for 02/01/2017 and the other one 02/04/2017, then when I save the changes, it reverts back to 02/01/2016 and 02/04/2016.

[brian!]

do you have the correct mysql permissions assigned to the database?

 

if you manually edit something else (pricing?), do those changes stick?

[WHMCS John]

Hi,

That all looks to be in order. Do you see any fatal errors in your PHP errors logs from the time of payment?

[DJFireCFH]

do you have the correct mysql permissions assigned to the database?

 

if you manually edit something else (pricing?), do those changes stick?

 

All permissions are fine, everything else can be edited with no issues..

 

 

Hi,

That all looks to be in order. Do you see any fatal errors in your PHP errors logs from the time of payment?

 

 

There are no errors present for that.

 

- - - Updated - - -

 

I just made it simple, and just went through phpmyadmin, and changed the dated for both of them to 2017.... I guess that was the easiest way to resolve it.

[ScottN]

Doesn't that date also get set when the domainsync cron runs?

 

- Scott