Details
Improvement
Major
Description
Some modules are capable of handling a sync of the registration date. In cases where the module is not able to provide the registration date, it appears that we sync it to match the service creation date. The problem with this is that someone may manually update the registration date to the correct registration date as with the registrar, and then the sync updates it again to match the service creation date.
As a result, I think the best solution is: When running a Domain Synchronization automation task, if the registrar does not provide the date AND the registration date is not equal to the service creation date, then do not update the registration date, skip it.
NOTE: This may need to be updated in ~/components/modules/module.php From Jono: The modules inherit it if they don't implement the method themselves.
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Paul Phillips
made changes -
| Rank | Ranked lower |
Paul Phillips
made changes -
| Description |
Some modules are capable of handling a sync of the registration date. In cases where the module is not able to provide the registration date, it appears that we sync it to match the service creation date. The problem with this is that someone may manually update the registration date to the correct registration date as with the registrar, and then the sync updates it again to match the service creation date.
As a result, I think the best solution is: When running a Domain Synchronization automation task, if the registrar does not provide the date AND the registration date is not equal to the service creation date, then do not update the registration date, skip it. |
Some modules are capable of handling a sync of the registration date. In cases where the module is not able to provide the registration date, it appears that we sync it to match the service creation date. The problem with this is that someone may manually update the registration date to the correct registration date as with the registrar, and then the sync updates it again to match the service creation date.
As a result, I think the best solution is: When running a Domain Synchronization automation task, if the registrar does not provide the date AND the registration date is not equal to the service creation date, then do not update the registration date, skip it. *NOTE: This may need to be updated in ~/components/modules/module.php From Jono: The modules inherit it if they don't implement the method themselves.* |