Sync Domain Name Expiry Date

[TheHostingHeroes]

Hi

 

I am glad to see in 3.6.1. "Tick this box if you want the expiry date sync script to update the expiry and next due dates (cron must be configured)"

 

is the cron the usual cron that does the usual billing, or is there another cron i need to setup?

[CSNM-Carl]

http://wiki.whmcs.com/Enom

 

Take a look at "Expiry Date Syncronisation"

[TheHostingHeroes]

Cheers Carl!

[Redsign]

Hi

"Tick this box if you want the expiry date sync script to update the expiry and next due dates (cron must be configured)"

 

Does there need to be a tick box when you also need to run the cron?

 

Surely there is no point in having to tick the box as well.

 

Ben

[9DollarDomains]

A) Good point Redsign.... why both a tickbox and a cron? Not a problem, but just currious what the tickbox is doing then?

 

B) This is my actual question - when I run the sync manually, I see it checking every domain, but I have a couple 'Error for somedomain.com: Domain name not found'.

 

The question is - is there a report somewhere, or an option to remove those domains from my WHMCS database?

[Matt]

The tick box is for if you want to update the next due date also - by default the "Domain EXPIRY Sync Script" will only update the expiry date field.

 

The file is designed to run as a cron, and outputs the results to the screen, so you would set your server to email you the cron output so you have a record of what was done and can take action on the domains which no longer exist in your Enom account.

 

Matt

[9DollarDomains]

Perfect, thanx.

[dexus]

This is really great and useful script but I just have a question and suggestion about it...

 

This script in it's output is showing for every domain "Updated domain.ext expiry to XX/XX/200X". Does this script really update every expiration date field in the database for every domain? Why is it showing "Updated..." for every domain? I would suggest this to be changed so script can first just compare dates, and if date is the same just to skip that domain and does not output anything about it, because this output is useless this way if you have few thousand domains, and also there is no reason to update all expiration dates in the database. So it would be nice to output really only what was different and what is changed, and of course any errors - domains that does not exist or that are in redemption period etc.

[Ben-iNetFx]

That's a good idea - also to have the script email you instead of needing to Pipe the results yourself, this allows customers who just have http cron access to get their report too.

[cyberneticos]

Good work Matt Saved me to have to write up a copy Expiry to Next Due Date script

 

Cheers

[rldev]

How do I only sync changes in expiry date. I know this is an option in the command, I just forgot and can't find it.

[disgruntled]

This is really great and useful script but I just have a question and suggestion about it...

 

This script in it's output is showing for every domain "Updated domain.ext expiry to XX/XX/200X". Does this script really update every expiration date field in the database for every domain? Why is it showing "Updated..." for every domain? I would suggest this to be changed so script can first just compare dates, and if date is the same just to skip that domain and does not output anything about it, because this output is useless this way if you have few thousand domains, and also there is no reason to update all expiration dates in the database. So it would be nice to output really only what was different and what is changed, and of course any errors - domains that does not exist or that are in redemption period etc.

 

 

We dont know how it operates, we cant see the source, however i think its likely to prevent further output checks it just states all as updated, but probably does not actually update each and every entry. After all

 

if value1 !== value2 would be fast enough and simple enough to omit an update.