Search the Community

Hi, I'd like to upgrade from Blesta version 3.1.1 to 3.2.2. Do I need to do incremental upgrades, or can I do one upgrade? I'm not sure what steps to take to upgrade in the first place. I read something about using FileZilla to replace certain folders. Is that right? Thank you!!!! Clare

I've been working over the last few days to establish Australian English as the default language by taking the en_us language files, duplicating them to en_au and making various changes to spelling and localising terminology. I currently have both languages active and in various locations I now see two tabs -- one for English, US and one for English, AU. However when I go to edit a template under Settings > Emails > Email Templates, I only see the English, US tab. I also tried changing the language in the database from en_us to en_au for each of the templates but then the list of e-mails disappears completely. Perhaps the template list may be hard-coded to en_us rather than looking for the Default Language defined in Settings > General > Localization?

Version 3.1.1 is now available. You can download it in the Client Area. This is a patch release that corrects issues with 3.1.0. Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes - Blesta Core - Version 3.1.1 ## Version 3.1.1 2014-02-12 ** Bug * [CORE-990] - Email parser syntax error with PHP < 5.3 * [CORE-997] - Removing package pricing that is in use causes the service to disappear * [CORE-1012] - Interworx: Remove check for domain name when creating a reseller account * [CORE-1013] - Appending a service to an existing invoice does not include tax for that service's line items * [CORE-1023] - VPS.NET: Undefined property r1soft_backups_enabled * [CORE-1026] - Support Manager: Missing loop back check for ticket notifications * [CORE-1030] - Nonmerchant transactions are listed as Other when editing. * [CORE-1032] - Adding a service with addons causes error attempting to pass a parameter by reference * [CORE-1040] - Cron task time format does not treat optional seconds as optional * [CORE-1045] - Security: Staff permission escalation through crafted URLs ---