Leaderboard

for my point of view, the pricing system need only a simple adjustement, the pricing already has price, setup fee price and cancel price , if we add another fields called renew price and transfer price we can achieve the multi pricing case, in renew services and the renew price isn't filled then use the default price . This can impact some other areas but it can be achieved, i think this is the simple and the effective way to do. Regarding domain management, really i cant see the need to create a new way to handle domains but rather if we can make a good order form that is enough , the actual modules need some addition to add more tabs to manage forwarding and dns if available with the registrar . DO not make it complicated for you guys and for us, the simple is the best always.

we have already talked about the renew_date in blesta, and i want to re-open again this subject . blesta update the renew date every time the invoice was generated . this leading a big problems for us and our clients. Firstly some client claim that the renew date showed is in the future and normally it should show the real renew date !! for example, a service that is renewed in 31-7-2017, when a invoice generated, the renew date will become 31-8-2018 . this behavior also impacting the observium plugin that we have made for billing calculation between two dates, so if a service has a renew date 31-7-2017 normally the plugin in 31-7-2017 should create invoice for the extra usage from 30-6-2017 to 31-7-2017, when blesta generate invoice, the renew date change to +1 term, the plugin ignore the service because it has a a future renew date and will not included in the billing calculation. we need a way that the we be sure that the actual service is from X date to Y date, and when the invoice is paid then the renew date can be updated . the only solution we found is to push all observium users to make the package use prorate for 1st of month, and then we update the plugin to make a calcul in the 1st of the month for the previous month, this way will impact some users that they didn't use prorate and they don't want use it .

We have a new importer for Clientexec 5.5. To install, download the attached clientexec.zip and unzip the file. Upload the clientexec directory to ~/plugins/import_manager/components/migrators/ and go to Settings > Company > Plugins to install it the Import Manager. Then, manage the plugin and click on the Clientexec 5.5 link to start. Be sure to import into a fresh Blesta install. clientexec.zip What's imported? If you want to import user passwords, it's necessary to make a couple changes: Edit ~/app/models/users.php around line 715, add a new case statement: case 'clientexec-sha256': $temp = explode(':', $stored_hash); $algo = isset($temp[0]) ? $temp[0] : 'sha256'; $iterations = isset($temp[1]) ? $temp[1] : 1000; $salt = isset($temp[2]) ? $temp[2] : null; $hash = isset($temp[3]) ? $temp[3] : null; $new_hash = hash_pbkdf2($algo, $password, $salt, $iterations, 0, true); return substr(base64_encode($new_hash), 0, 32) == $hash; Edit ~/config/blesta.php and change: // Set to true to enable support for legacy passwords (plain md5). Set to false for improved security Configure::set("Blesta.auth_legacy_passwords", false); // The legacy password algorithm to use if legacy passwords are enabled Configure::set("Blesta.auth_legacy_passwords_algo", "md5"); to: // Set to true to enable support for legacy passwords (plain md5). Set to false for improved security Configure::set("Blesta.auth_legacy_passwords", true); // The legacy password algorithm to use if legacy passwords are enabled Configure::set("Blesta.auth_legacy_passwords_algo", "clientexec-sha256"); Then, continue with the import. If you don't care about user passwords, you can import anyway and users can reset their passwords using the password reset feature in Blesta. Did you give the importer a try? Let us know what you think below.

Hello, We literally just finished our development of the Cerb helpdesk plugin that would allow Blesta clients to use Cerb instead of the default helpdesk with Blesta. Now we noticed that v4 is out (congratulations). Is there a write up somewhere, for developers, on what changed when creating a custom plugin? What functions depreciated? New features added? etc. We have not tried our new plugin on a v4 system yet, but I suspect we will start that process soon. Thanks, -Adam P.S. For those wondering, we plan on releasing the Cerb plugin, free of charge, to the rest of the Blesta community. No ETA yet.

Get the trial and test .

another issue to fix with the graph in blesta, i have posted a fix there

In some cases, the staff can change the invoice due date to a future date, so is not a reliable solution. and sometime we need to change the service renew date manually, then is not useful using the invoice due date . the perfect solution is to update the renew_date when it should be updated (payment only). is not possible to add another date field to play with it? and how others scripts handle this?

@Paul can you let me know how the widget loads the scripts and where in the code it does this and renders the graphs; we use nvd3 for graphs/charts in alot of our projects and haven't come across this issue so would be more than happy to look into this and see if we can get a fix for this

Yes it is. I wanted to bring it up again to keep it on the radar.

Hello I'm currently trialing blesta on directadmin and notice if the user enters a directadmin username with uppercase characters in it the service is set to pending in blesta after changing the username to all lowercase so directadmin accepts it the service is then created is there a way around this?