Leaderboard

When a client orders an addon, you don't get a email just a payment received. I think there should be a email per addon so you know there's an order placed and for what. Who thinks so too .

Hi, i think that Blesta is a far cry from a "multi-language" system. I must add to your items: Settings > Company > Invoice Customization > "Terms" is not multi-language; Email signatures are not multi-language; Settings > Company > General > Localization: “Calendar Start Day”, “Date Format” and “Date Time Format” are not multi-language (now i can only select a date format not correct for some users); Package description is not multi-language (also name should be multi-language to); Support Department name and description are not multi-language; "Responses" in Support Manager ara not multi-language; Knowledge base "category"'s name and description are not multi-language; ... In this list, there are some items with "low priority" because we can fix these with simple tricks. e.g.: 1. we have created a custom invoice template and we use for "terms" a variable that we set in language file; 2. isn't very critical (for us), because we use only one signature with more languages; 6. very low priority, we solve it simply with naming with language code in title, e.g. "IT - Chiusura ticket" and "EN - Ticket closed". Others that i think so hard to solve (or not?), e.g. the item 3. Others that i consider "high priority", e.g. 4 (the first! how i can sell in multi-language if my products and its description aren't multi-language?), 5 e 7. On this theme, i want also suggest to uniform UI: in a form with multi-language fields, please use tabs without reloading page (as is in staff/packages/add)! Try for example to edit email template!!! At the end, always about multi-language,... sorry for my bad english! Regards

A user MUST be able to upgrade from version 3.0.0 to any future version. Any upgrade could completely change the database schema. So having the code expect one database schema but have a different one actually running is unstable. It's impossible to ensure backwards compatibility with a previous version's database schema, especially with EVERY previous version, as you imply with this authentication requirement. So we have no intention of even trying that. It's a waste of time.

For addons ordered for existing services within the client area? Please see CORE-1228 and CORE-1229 including my recent comments on each task.

Since this is the intended result of this feature, I've moved to feature requests. A few things to note: Don't upload files until after you've already made a backup. The upgrade can not proceed unless the files uploaded are for a different version than the one currently installed. If you've done step 1, it doesn't matter who processes the upgrade. If we were to allow only 'authenticated upgrades' it would mean either: Upgrades can only be processed through CLI, OR Blesta would need to automatically handle the upgrade (download files/process upgrade) It's way too risky to force someone to be authenticated in order to process an upgrade when the system is in an unstable state (i.e. the files are for a different version than the database).

This is the first question than can anyone has a non English business ask . Blesta is Multi-Language ? the answer is Yes , but as now "v 3.3.2" is not totally multi language , so why yes , and why is not totally multi language . 1 - if you want to run blesta in only one other language rather than English , so is "yes" , you need to disable "Client may set Language" . 2 - if you want to run blesta in multiple languages , the answer here is not totally multi language . so my analyses will get based in the second case . A - the first big obstacle is the Portal CMS plugin , is a unique language , we can't make entry for a multiple languages . B - the navigation link , exempt the core one "dashboard,account,contact" , are not in multi-language , so if you install the plugin with admin area in English , the navigation will remain in English even if the client has a French language in their profile , for me this a "no professional company" that offer a their clients a merged languages in their navigation links , this issue i have already posted in the forums and it was not answered . C - no languages selection in the system for visitors - not logged clients - , and this has no sense with multiple languages installed . D - the widgets name, the search options tag , is not multi languages . after blesta is supporting this issue we can say blesta is a true multi-language system .

Hey guys- New user here- I discovered Blesta on Friday and quickly signed up after about a month of debating on how I am going to manage my growing client's hosting. We primarily focus on fully-managed solutions and optimized hosting solutions and I have been looking for a highly configurable, but usable out of the box solution, that really doesn't automate everything (as we're a hands on web dev company) but had the capability, and this is it! I spent the weekend plugging in my clients, linking my Stripe account, building service plans, etc, and best of all, personalizing the client dashboard and login screen (I've modded the admin a bit, but really not necessary). I am a front-end developer with a lot of CSS experience and basic PHP experience... enough to tweak and move stuff around comfortably, but I don't program. Here is the result of my personal integration for my clients. Basically- I widened the template, removed all of border radius' and shadows, removed the chunky top sections, modified the client_main_myinfo to incorporate a photo (which is static for now, my programmer will make that account specific, set by the admin, in the weeks to come) and rearranged some of the functions, and basically changed the font and colors on everything. This is just a start- We're going to run client account info down the left as part of main_myinfo, and tweak it a bit more. We'll eventually modify the package order forms before we roll out the ability to sign up from our website. We also do graphic/print work, so we may modify the support system to allow for requests that include text fields and drop downs for graphic type products (ie. asking the client what type of product, what size, what amount, etc) I am not happy with my CSS mods of the login page, it will likely change. It looks nice, but it's not perfect. I've really enjoyed modifying Blesta- the php and css is very clean and easy to work with! See attached. Feedback greatly appreciated! Craig

+++1 for fully support multilanguage Blesta now as it is, is only 60% multilanguage

Open a ticket and I'll issue a dev license to your account. If you have an owned license, it'll be permanent, if monthly, then it'll expire after 6 months but can be extended.

I am not sure why you wouldn't be able to authenticate the user in this case still? You are most likely never changing the username/email and password fields in the database for users which means running a query against that shouldn't be much of an issue. On top of that you control the upgrade script, that means you know that schema version (not sure if you track this or not as I haven't checked) which means you should be able to craft a query for any version of the users/groups/permissions tables if they did change. I am most likely missing something though and probably should just look at the code at this point (which is my favorite thing about Blesta).

I'm talking about the people who already store credit cards. Also, it would just be an option for those who want it.

I may create a CSS-Only version of the theme where it will re-skin the the dashboard but not change the functionality but I'd need to purchase a second license to the software as I'd rather apply the changes to a fresh installation. I've started to re-skin the admin dashboard to match as well. Essentially, I'd just create a drop-in css folder to replace the existing folder (although i'd suggest saving the original). To re-skin the login I'd create a second CSS folder to modify and make one link rel change to the login screen's .pdt, as right now the login and dashboard itself share some of the same CSS elements. I prefer to control both screen's styles independent of each other, so we just need to have the login call do different css files. If I can get some time over the next few weeks, I will work on this, as i'd like to have it myself Right now I haven't worked much with this so I need to get in there and make this system work for me!

Human error is possible, you may have backed up the files but not the database. You read the note that said make sure you have a backup so you go to backup the database and it gets ran in that time. Again there isn't much that can really go wrong but why not make it safe? Are you telling me that isn't a security hole though regardless if it is a staff account or not. If one of my support peoples accounts was compromised they normally wouldn't have been able to do much damage unless they took advantage of the bug. Overall Blesta is proactive is protecting people who use their software, they can't be expected to do everything for you but making minor changes that could help people that aren't a lot of work don't seem like a bad move to me. Either way I trust the developers decision will be what is in Blesta's best interest.

I will +1 this. They tell you to take a backup before you upgrade just in case anything goes wrong. If someone comes by and upgrades, it botches itself, I now have no recovery option past my last backup (assuming you are doing them). cli update. If you have access to the server you may as well let them upgrade it There is no such thing as perfect software, as much as anyone would like there to be. Security holes will pop up here and there no matter how hard to try to prevent them. Blesta is great at addressing issues quickly. An example would be CORE-1045. That was a security hole, but they patched it very quickly. Mainly what I am getting at is saying "Blesta doesn't doesn't [sic] do holes" is not putting forth a proactive feeling toward security. Showing that they do have issues but treat them seriously and fix them in a reasonable amount of time shows they do care about security and do their best to keep things secure which is what the majority of people expect. .

Yeah 1+ , i think that is necessary, and also i think the placed orders should be shown in the client area, because it might be confusing if the order is set to in review status, the service won't be even shown as pending in the client area, therefore, a client might think that the order has not been placed successfully and then submit a duplicate order.

the feature is already exist , it need just a message to show

/plugins/support_manager/views/default/knowledgebase.pdt or /plugins/support_managerpro/views/default/knowledgebase.pdt

i have found the source of the probleme . i will fix it next week , to use the admin tools just uncheck the "Block Access To Uninstalled Plugins Via Direct URL" in security tab of admin tools .

What if you're not logged in, and now you can't login because of a MySQL error?

css I prefer it as it is, but I saw it in development and alpha. I just overwrite css with my own file in structure, but you can just use the css toolkit by Naja7host.

looking good any chance to get that theme?

Future release without ETA is something that make me lost Maybe this is the major request for multi-language , note this is not my request , this what i think about a complete multi-language blesta . to no , i heat a phrase like "This is not currently possible" , "this is impossible now" ... it send a bad signal . this is something related to the action table . the search option event . i have a found 2 temporary solutions for the "Multi-Language in Navigation Links from Plugins" , the first one is a modification in the navigation.php model , te second one is a plugin with jquery cpde to search/replace , that is working for me, but i have not yet tested in other installation .