Wouter

Officially, you'd need an unbranded license to do that. Reason being is that we could get a lot of requests for what would be acceptable to change it to with a branded license. So with a branded license, officially, it should be unchanged. With that said, if you do change it to that, it's not likely anyone is going to complain.

Today I started developing our custom code for Blesta, because we're coming from WHMCS where we created much custom code for. Now, I see this "bad" (when I compare it to WHMCS) domain management, I can't continue to switch to Blesta because of this.   

I hope a better domain management will being implemented in the near future. I don't think you'll need to do this per module, which will get very messy over time (all different way's of handling things).
 
My ideas for the domain management, which you may consider while implementing this:
- Centralized WHOIS information over multiple registries, with ability to "override" this for a specific domain by the customer.
- Centralized nameservers over multiple registries, with ability to "override" this for a specific domain by the customer.
- Proper transfer handling (including a cron).
- TLD syncing with automated price updates
- WHOIS through the preferred registry for a TLD
- Some TLD's have different requirements (e.g. a domain needs to be renewed x days before expiry).
 
Thanks! 

We're using this status on a daily basis, together with "In Progress". Love to see these in Blesta (without the really need for custom ones).

I think one big disadvantage of Blesta is domains in general. WHMCS isn't great in it either, but Blesta simple sucks in it. The additional requirements you've listed there is just 1% of the features that needs to be build it, to let Blesta rock with domains. 
 
And, the WHMCS support indeed sucks, but I haven't heard great noises about Blesta either (although, I didn't experience this - yet, just becuase I didn't but anything yet).

I'm currently developing a gateway for SEPA direct debit with batch support and the ability to export to XML. Let me know if you're interested in this gateway, it should be ready soon (~3 weeks).

I'm currently developing a gateway for SEPA direct debit with batch support and the ability to export to XML. Let me know if you're interested in this gateway, it should be ready soon (~3 weeks).

Today I started developing our custom code for Blesta, because we're coming from WHMCS where we created much custom code for. Now, I see this "bad" (when I compare it to WHMCS) domain management, I can't continue to switch to Blesta because of this.   

I hope a better domain management will being implemented in the near future. I don't think you'll need to do this per module, which will get very messy over time (all different way's of handling things).
 
My ideas for the domain management, which you may consider while implementing this:
- Centralized WHOIS information over multiple registries, with ability to "override" this for a specific domain by the customer.
- Centralized nameservers over multiple registries, with ability to "override" this for a specific domain by the customer.
- Proper transfer handling (including a cron).
- TLD syncing with automated price updates
- WHOIS through the preferred registry for a TLD
- Some TLD's have different requirements (e.g. a domain needs to be renewed x days before expiry).
 
Thanks! 

i'm  working for a new Gateway , but i have some confusion about this urls , when used and what they are ?
 
 
return_url , $options['return_url'] ?
cancel_url , ??
notify_url , callback_url ?
 
and which url should be called in a successful operation , and wish for denied operation , and wish one for canceled operation by client click ? 

Today I started developing our custom code for Blesta, because we're coming from WHMCS where we created much custom code for. Now, I see this "bad" (when I compare it to WHMCS) domain management, I can't continue to switch to Blesta because of this.   

I hope a better domain management will being implemented in the near future. I don't think you'll need to do this per module, which will get very messy over time (all different way's of handling things).
 
My ideas for the domain management, which you may consider while implementing this:
- Centralized WHOIS information over multiple registries, with ability to "override" this for a specific domain by the customer.
- Centralized nameservers over multiple registries, with ability to "override" this for a specific domain by the customer.
- Proper transfer handling (including a cron).
- TLD syncing with automated price updates
- WHOIS through the preferred registry for a TLD
- Some TLD's have different requirements (e.g. a domain needs to be renewed x days before expiry).
 
Thanks! 

Lets face the fact Blesta's domain management is TOTAL CRAP.. WHMCS and Clientexec do it way better in every way.
 
Blesta does NOT have a proper domain offering, period. seems to be that its just not a priority.
 
Domains are totally unique to generic products and should be treaded as such.
 
For webhosters, domains are part of hosting, the most important part.
  The enom module for Blesta is 10 years behind that of WHMCS..currently we have the bare minimal basics.
  What if one wants to only sell a domain ? Does not appear blesta support domain only products.  
Domain Transfers ?
 
Renew pricing ? Allot of domain renewals cost more than the initial registration fee
 
Name spinning ?
 
Importing and sync of prices from enom & namecheap ?
 
Importing and sync of TLD's and new TLD's from enom & namecheap ?
 
What about .co.uk that requires a 90day before expire renew ?
 
Direct managment of the domain hosted on the registrars nameserver ?
 
Proper whois lookup or usage of dig to check if non api domains are registered/available ?
 
A domain email module, where domain orders are emailed, still does whois checking for availability. Some tld's are still stuck in 1970.
 
Domain availability widget ?
 
^^ BLESTA FAILS FOR ALL OF THE ABOVE
 
---
 
I challenge Blesta to make a billing brawl using domain management and include enom's module...
   
btw if you want a reseller enom account, or access to the enom api sandbox , contact me and ill sort you out with an account.

Today I started developing our custom code for Blesta, because we're coming from WHMCS where we created much custom code for. Now, I see this "bad" (when I compare it to WHMCS) domain management, I can't continue to switch to Blesta because of this.   

I hope a better domain management will being implemented in the near future. I don't think you'll need to do this per module, which will get very messy over time (all different way's of handling things).
 
My ideas for the domain management, which you may consider while implementing this:
- Centralized WHOIS information over multiple registries, with ability to "override" this for a specific domain by the customer.
- Centralized nameservers over multiple registries, with ability to "override" this for a specific domain by the customer.
- Proper transfer handling (including a cron).
- TLD syncing with automated price updates
- WHOIS through the preferred registry for a TLD
- Some TLD's have different requirements (e.g. a domain needs to be renewed x days before expiry).
 
Thanks!