Leaderboard

An attempt at modifying the sign-up form to add VAT number and e-mail address verification. Asks the user if he is a private individual or company Hides company name input field if private individual (to prevent the user entering things like "-" or "NA", which can cause problems with domain registrations.) If the user is an European company, he can enter his VAT number and press "validate", the system will then verify the number and fill in the company name and address information (if available) automatically. If a valid EU VAT number is entered, and the customer is in a different country than you, he will not be charged VAT (reverse charge procedure) The e-mail address is verified by sending an 8 character verification code to it, that must be entered by the user to proof the address is correct. Requires PHP SOAP extension (to communicate with the European Union's VIES VAT number validation service), and that the default country in the Blesta settings is set to your own company location. Diff (file changes): http://www2.noc-ps.com/dl/blesta-3.1-signup-form.diff SQL (extra e-mail template): http://www2.noc-ps.com/dl/blesta-3.1-signup-form.sql

Yeah, the diff is not that human readable, due to me moving the input fields on the sign-up form around (the "country", "tax_id" and "company" fields were moved to the top of the form) Generally it is not necessary to edit the files manually though. patch is your friend. $ cd blesta-3.1.0 $ patch -p1 < blesta-3.1-signup-form.diff patching file blesta/components/invoice_templates/default_invoice/default_invoice_pdf.php patching file blesta/components/invoice_templates/default_invoice/language/en_us/default_invoice.php patching file blesta/plugins/order/controllers/main.php patching file blesta/plugins/order/language/en_us/main.php patching file blesta/plugins/order/views/templates/standard/language/en_us/main.php patching file blesta/plugins/order/views/templates/standard/main_signup.pdt

We discussed this in a ticket, but it did result in CORE-1066. Adding that here, for future reference, it adds an option to staff service management to add and edit recurring coupons.

Multiple domain registrars can be used, with different TLDs going to different registrars. This is all set up on the package level. When you add a package, you select the module and what TLDs the package applies to. Then, you add your domain packages to a package group. During checkout, all TLDs valid across all packages within the group are available for order. The order system determines which package to use for the TLD being registered, which in turn determines the module. Just to add -- in the future, when we release the registrar plugin, a pricing matrix will be available. That will simplify the current method of having to have a new package for virtually each TLD (Or at least TLDs where the pricing needs to be different).

Thanks for the answers I thought as much regarding the multiple registrars. One radio for NZ and the other for gTLDs could work. I might see if I could develop a page where you can add each domain and select which registrar would be used for each like boxbilling has. Ok, that seems fine That would probably be alright as well Regarding all those modules/plugins I mentioned, I would be developing them myself (won't get all of them done before I start). I do similar stuff as an OpenCart dev. I'll have a look at the SSL stores mentioned.

Services are provisioned and managed through Modules, so it's simply a matter of using the correct module to interface with the service you're wishing to provide.