Brandonm

@WHMCS Alex faster than an actual support ticket. Thanks that worked!

Same issue here but when I try the resolution I get: MySQL said: Documentation 1067 - Invalid default value for 'termination_date' Any suggestions?

Thanks @brian!, apparently my sortby file had a line that was causing an error. Updated with the file you posted and it's working again. Cheers!

The @sortby modifier is no longer working with WHMCS 7.6 and PHP 7.2. Does anyone have a way to sort existing Smarty arrays or know how to make @sortby modifier work with the latest version?

Had the same issue, here are things to check: 1. Make sure the "Server" on the Products page is set to the server you setup in WHMCS. 2. Make sure the "Reseller/Owner" in WHM is the same as the username you used in WHMCS when setting up the server.

Also experiencing this error with 5.2.13, it happens when a subscription is canceled.

We have these enabled and it seems to catch 99% of the fraud signups: Reject Country Mismatch Reject Anonymous Proxy Reject High Risk Country MaxMind Fraud Risk Score: 5 Use New Risk Score Never used the telephone verification.

What about a fraud protection module?

You could use an action hook to do this based on the product id after signup or activation and change the service id billing cycle to annually.

Do you use one of the fraud protection modules? For the Paypal Gateway Module do you have "Client Address Matching" enabled?

Do you care if the # of results is accurate? Edit: supportticketslist.tpl Add the lines in red. This will hide all tickets with the status 'Closed'.

Why not use eNom nameservers and enable DNS Management?

What I am proposing is to be able to charge only the difference between the two plans. In either scenario the customer should get charged the difference between the two plans rather than paying a lesser pro-rated amount. Scenario 1 the difference should be $5.00 so the customer pays the full monthly amount of the upgraded plan which is $10.00. Scenario 2 the difference should be $100.00 so the customer pays the full monthly amount of the upgrade plan which is $200.00. I'm asking, how do others handle these upgrades? Manually? Overages? Not at all? Just let them pay less?

In Scenario 1 the pro-rated amount charged is $2.50 so the total the customer paid for the month is $7.50. In Scenario 2 the pro-rated amount charged is $50.00 so the total the customer paid for the month is $150.00.

How do you handle upgrading to more bandwidth mid-cycle? Scenario 1: Customer is 13 days into a one month billing cycle on Shared Hosting Plan 1 ($5.00/mo) and running out of bandwidth. So customer wants to upgrade to Plan 2 ($10.00/mo). Right now the system will pro-rate the difference instead of charging the full amount of $10.00 for the entire month. So the customer ends up paying only about $7.50 for the month instead of the full $10.00 it should have cost. That's only a small example but is the same difference on a larger scale (ex. for vps or dedicated). Another example would be: Scenario 2: Customer is 13 days into a one month billing cycle on Dedi Plan 1 ($100/mo for 5000GB bandwidth). So customer wants to upgrade to Dedi Plan 2 ($200/mo for 10000GB bandwidth). The pro-rated amount is only about $50 so the customer pays only $150 for the month and gets 10000GB when it should have cost $200/mo. If you have upgrade/downgrade enabled in WHMCS how do you regulate this and charge the full amount difference?