Details
New Feature
Major
Description
The NameSilo module should be adapted to Blesta:
https://github.com/knownhost/Blesta-Namesilo
It should be forked into the Blesta repository on github, then this feature can be integrated.
This feature should:
- Allow packages to be created from the module
- A set of TLDs can be selected, and a package created for each TLD
- Pricing will come from the NameSilo API for each TLD, and can be marked up by a percentage
- Probably should store the TLD, the TLD old price from NameSilo, the adjusted price we are setting it to, and the value of the markup we are applying (e.g. 15%)
- Allow packages to be updated from the module
- Pricing may be updated for specific packages (based on TLD) when manually set to do so
- We can list the current data we have on record, i.e. The TLD, the old TLD price from NameSilo, the price of the current package (in each currency), and the prices that the package will be updated to if we apply a change to the markup (e.g. 20%). This will allow us to compare the old price vs the new price and make it easier for staff to know what prices have changed in NameSilo vs Blesta that they may want to update.
Activity
Moved it from 4.9 to 4.10.
Paul Phillips
added a comment - Moved it from 4.9 to 4.10. 
I think we should show the price for each TLD that will be used as a result of the markup %, however allow that to be changed before the packages are created if desired.
So we'll show the cost from Namesilo, we'll show the price in a text field that is calculated based on the % supplied, and the admin can change it if they want prior to running the import. Maybe the price comes out to $14.93 and they want to just round it up to $15 or something.
This should work for renewals also, so a % markup for new and a % markup for renew can be set. As above, this would result in the price being shown for new and renew
Only question I have is are we doing 1 year for each, or should we allow 1-10 year prices to be created? That may add some complexity. Investigating.