Leaderboard

If a client upgrades or downgrades their service / configuration options it would be cool to have a email (optional) to alert staff / customers that it's gone through .

What would we offer bounties for exactly?

Do you have a ticket open? If so, what is the ticket #? After you had a failed import, did you restore your database back to a fresh install of Blesta before running the import again? The error about a duplicate entry could be a result of not doing so. The import can only be run once because it will try to import everything again. We recommend making a backup of your Blesta before attempting to do the import. If you didn't do that, you could empty your database and remove your /config/blesta.php config file (You should have a blesta-new.php file in there) and run the installer again. Then make a backup, and try the importer again. If it fails, you can restore your database backup. Any errors you get would be helpful, but it must be from a failed import on a fresh Blesta install.

The new look is a minor part of the major code update to 4.0 which increases the minimum requirements for Blesta and allows things like domain management to happen. When we began development for 4.0, we announced that 4.1 would be dedicated to domain management. The new whmcs is mostly a new look, and they borrowed a lot of ideas from us. I understand you want better domain support yesterday, but it's scheduled for 4.1. The most constructive way to proceed is to give us feedback on what features of domain management you value most.

My point is simple, because there is no domain management, the product is defective for the majority of hosting providers. Even the large domain resellers are now focusing on WHMCS and have given up on blesta, until we have some form of domain management this will only get worse. Since you are a blesta reseller, you have an extreme bias towards it. I have lifetime owned licenses for WHMCS/Blesta/Clientexec/AWBS. Besides the domain management, blesta is a fantastic product. As of right now the best WHMCS alternative is clientexec, which is sad. If blesta lacks the resources, they need to hire more developers and expand, and/or offer bounties.

hey ginner159 from lowendtalk I could make you one for free and just distribute it out for free for everyone else to benefit off of as well.

Settings > Company > Billing/Payment > Invoice Customization. Add it to "Terms".

You can put it in the notes section on the invoices.

my point of view . the probleme is not the DNS management, as the actual modules can handle the DNS management , it need just a couple of lines code to add the DNS management as a new tab . my request or let say feature request in the new refactor , is to make the DNS/EMAIL forwarding/web forwarding as extention/plugins of module manager , why ? let say i have domain with logicbox or enom or ... , and i want to manage the DNS with other platform like (cPanel & cPanel DNSOnly ,DynDNS , SimpleDNS , PowerDNS ...ect ) , so i want a system that allow me to add the DNS MANAGEMENT to any registrar i want to use is with it or use the default dns manager included with the registrar . i hope the idea is clear .

Is there a way to use the Blesta's built in cache for plugins?

maybe another bug found : blesta always fetch the cached page even if we have not initialed the startcahing() function the controller . $this->startCaching(Configure::get("Blesta.cache_length"));

Template files can be cached automatically by specifying so, e.g. class MyController extends AppController { public function myPage() { $this->startCaching(Configure::get("Blesta.cache_length")); ... } }

+1 for this question . what i can help from the basic code, , the cache system is already enabled by default in blesta Configure::set("Caching.on", true) . a sample code like this can work , but not tested . $cache = Cache::fetchcache('your_plugin_controller_pdt_file', $this->company_id . DS . 'plugins' . DS ); // if a copy of cache existe if ($cache) { // here you should return the cached file return unserialize(base64_decode($cache)); } // no cache existe , return output and create cached file else { $pdt_file = $this->view->fetch("your_plugin_controller_pdt_file"); // get the pdt file // create cached file if cache system enabled if ( (Configure::get('Caching.on') && is_writable(CACHEDIR)) ) { Cache::writecache('your_plugin_controller_pdt_file', base64_encode(serialize($pdt_file)), strtotime( Configure::get('Blesta.cache_length') ) - time( ), $this->company_id . DS . 'plugins' . DS ); } }

...and ICANN require us to display a list of our current tld pricing. Why this list doesn't show up in Blesta, in order to help us to comply with the ICANN terms and conditions? I think ICANN policies should be followed the same as you would follow security best practices while programming : we can't live without.

Yup : it's true. It's hard to manage domains, and customers are all completely lost in the product list, should they have more than (let's say) 10 domains / services. It's all mixed together, and hard to separate domains and the other products using the existing functions. Also, the industry require different pricing for registration, renewal and transfer. I understand we can use a coupon code, but what if we want our regular price to be lower at registration? It must allow us to invoice the way we want