Leaderboard

Version 3.5.3 is now available. You can download it in the Client Area. This is a patch release that corrects issues with 3.5.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 3.5.3. See all Change Logs.

Upgraded and only 7 issues in this patch well done guys roll on 3.6.0

I am starting to like systemd and getting use to running systemctl, it's logical. I just have many many years doing it the old way so that's what wants to flow out of my finger tips.

I disagree, systemd is a drop-in replacement for SysV. You can use your SysV scripts with systemd as long as they don't declare incomplete dependencies in your LSB block. You can't please everyone, people complain when you stay the same and don't innovate, people complain when you change. Damned if you do, damned if you don't. I happen to like the clean syntax for systemd much more than SysV.

Yep, we were able to automatically upgrade extensions as well during a normal /admin/upgrade. It's not a bad idea to check these post-upgrade, but this feature eliminated some issues, as you can imagine.

I believe from 3.3.x the plugins, etc try to upgrade themselves, if they fail you will get the old way of upgrading.

Interesting issue. I'm not aware of there have ever being a fix for such a problem, and I haven't experienced that myself or heard of anyone else having that issue. My concern would be that possibly your fields have the same name. You could inspect the element in your browser and compare the field names to each other. They should all be unique.

the answer is clear , wthe notification ned to read from the callback url a output of json .

Updated

@PauloV have you tried with this case . http://www.blesta.com/forums/index.php?/topic/3562-initiate-blesta-core-in-external-location/

because the token is valid for the curent session , so when you fetch it via curl is a session different from the client sessions public function getCsrfToken($key = null) { $session_id = session_id(); if ($key == null) $key = $this->csrf_token_key; // Prefer computing CSRF using HMAC if (function_exists("hash_hmac")) return hash_hmac("sha256", $session_id, $key); // Sha256 hash is the next best thing if (function_exists("hash")) return hash("sha256", $key . $session_id); // Regretably, fallback to md5 return md5($key . $session_id); }

We recommend setting your packages for SSL to "cancel at end of term", and they can reorder if they want to renew the certificate. As they have to provide information in order to renew, auto renew could be problematic. Mention Blesta if you sign up with either GoGetSSL or TheSSLStore and they may be able to offer better pricing.