Leaderboard

NameSilo Domain Module This module is a complete solution for domain registrations and transfers through NameSilo. This module builds upon and continues the work by @NETLINK. He and I will be jointly contributing to this project and we welcome any other contributions on GitHub. An old thread related to this plugin was at https://www.blesta.com/forums/index.php?/topic/3399-namesilo-plugin Features Domain registrations Domain transfers Supports all NameSilo-supported TLDs by dynamically listing the available ones to package creation Proper .us/.ca support with necessary fields on order forms NameSilo audits Sync service's renewal date with domain expiration date Register/manage nameservers/hosts Set/change nameservers Update WHOIS details Lock/unlock domain Retrieve EPP code DNSSEC management Check email validation & resend validation email if needed Toggle WHOIS privacy Manually extend registration Transfer status tracking Screenshots Coming soon Installation https://github.com/knownhost/Blesta-Namesilo/blob/master/README.md Upgrading Nothing special is required except when updating from <1.8.0. In this case see the "Other" section below. Known Issues A domain transfer can be ordered for more than 1 year. NameSilo's API does not allow a transfer to extend more than one year so the extra years would be lost if not manually corrected. I'm unsure of how we'll solve this at this point. Future Plans Update for Blesta's new domain management system when release. This will be the v2.0 milestone and will likely be mostly a rewrite of the module. Clean code and remove unnecessary code. Manually extending as an admin should support invoicing/queuing to post-payment. We should be able to do this with the proration logic. DNSSEC management Implemented! Source This module is fully open source and can be found on GitHub. Two repos are kept fully updated with releases currently being built on the second: https://github.com/knownhost/Blesta-Namesilo https://github.com/NETLINK/Blesta-Namesilo Download I will make every effort to maintain the listing in the marketplace at https://marketplace.blesta.com/#/extensions/80-NameSilo Module GitHub will always definitely be up-to-date: https://github.com/NETLINK/Blesta-Namesilo/releases Other The version 1.8.0 release is a major update building upon @NETLINK's work. The new auditing features will not work properly until you "manage" and save your NameSilo account settings. Everything else should be fully backwards-compatible.

might we can say in a future release a new fields in contacts for age(birthday) and gender ? some companies need this two data for some interne stats, and i really see this a nice new fields to add, it mandatory of course, but we can force client to fill them .

There is no hard limit, but we do not recommend a very large number. Multi-company is intended for a single organization that operates multiple brands/companies. It's not meant for companies to offer addon companies to their customers/resellers. If you're thinking of offering Blesta to your customers/resellers as addon companies, I'd highly recommend becoming a reseller and setting them up with their own installations instead. See https://www.blesta.com/resellers/ It takes time to process automation tasks the more data and companies you have. Depending on hardware, number of addon companies, and data stored, automation tasks could take a significant amount of time to run.

You must check "everything".

Thank you Tyson. I completed as complete as possible the EER_Diagram on MySQL Workbench, but do have +/- 10 relationships I am not sure about. Should I attach the wbs, sql, pdf copy of the layout with the questions here, or should I rather email these files first that we upload them here when done, or make them part of the documentation? I think if I had something like this, I would have been on the road to success long ago. I'm not complaining, Thank you very much for the current documentation it helped me very much, as well as this forum. ?

Thanks Blesta Addons, I'll keep in touch.

As far as I know they link to this github project from https://www.namesilo.com/Support/Reseller-Options

+5 I had a custom date of birth but nice to get it as default.

We have added to our cms PRO a function to list the domains, a proof of example are in live production here https://nh.ma/en/domains admin side for the page

In order to understand recursion, one must first understand recursion.

We are still waiting the staff answer if what we have put are enough or exist something else we have not included ? it great if you can do something and always i'm ready to help you finish the work .

I have also created CORE-2593 to address the issue brought up in this thread, per Tyson's suggestion.

The current logic exists to prevent customers from receiving the service for free for a period of time. The cutoff for voiding the invoice is when it is past due since that is the point we can reasonably assume the customer is entirely liable to pay the invoice for services rendered. If a customer has a service, but does not pay the invoice for it, it will become canceled after a period of time. During that time, they have received the service for free, but you are still due the amount of the invoice for having rendered the service to the customer. If, instead, you void the invoice at that point, you accept that you are letting the customer have the service for free for that period. This behavior can be taken advantage of by customers to repeatedly receive free services for a length of time. For example, they can purchase a service, not pay for the renewal, and get the service for free until it's canceled and the invoice is voided. Then they can re-purchase it and repeat the process to get some time for free without worrying about paying an open invoice. If you would like to offer free service time to customers in such cases, that sounds like it would be a business decision on your part, and we could add a new option to allow past due invoices to be voided upon cancellation, e.g. Open Invoices that are X Days Past Due Will be Voided Options: - Any - (always void a past due invoice on cancellation) 0 Days (default, current behavior) 1 Day 2 Days 3 Days ... 60 Days