Tanel

Tyson, I am in software development business and we had a web based application for data insertion that included version management. The data also needed to be translated to many languages. So, for some people the logical approach was to also implement translation editing into our web application. After 50k€ or so investment, we have basically ditched the custom translation editor (included history, fuzzy matching, etc) because we always needed to update some parts of it or implement something additional, and are now happily using an external process with professional tools that have existed for decades. If only we had not tried to reinvent the wheel and used translation export/import in the first place. Concentrate on Blesta itself and let us use available tools to modify the phrases. I would be more than happy to volunteer some of my time to make this happen.

I think in the perfect world, this should be customizable and implemented as a widget.

Does anyone know if Blesta team is actually planning to implement this and any of the other language support related tasks in the next two releases? I am not sure if they actually understand that lack of language support makes Blesta pointless for half of the countries in Europe due to multiple languages or large minority ethnic groups (with their own languages) in the countries. In addition to this, I am sure I am not the only one who wants to target at least the local languages + English for international customers.

Why don't you put the translation editor code to github and let the community help out. This way you can concentrate on the core of Blesta and we can worry about the translation editor.

+1

+1

+1

IMHO, this should be more generic. Ideally the client should be able to select the language for the whole UI, not just for the order forms.

This is an essential feature. +1

Is it really so that the client cannot change the language in the order forms? I am using the ajax forms.

I am not sure if everything is working normally or not, just fooling around with 3.2.0 at this time. Looks OK.

When looking at modules, I only have the cPanel module installed and the Universal Module. Both of these were installed manually. Plugins side has more items installed, I have not modified these myself: Billing at a glance, Feed reader, Order system, Portal, System overview, System status.

I have a fresh installation of blesta 3.2.0 (installed via CLI). When logged in to the admin side of Blesta and checking the installed modules page, there seem to be no modules installed (not sure if this is normal). Went into "Available" modules page and clicked on the install button for the "Universal module" and got the following: Oh noes! SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-universal_module' for key 'company_id' on line 124 in /home/ordersibn/public_html/lib/model.php Printing Stack Trace: #0 /home/ordersibn/public_html/lib/model.php(124): PDOStatement->execute(Array) #1 /home/ordersibn/public_html/components/record/record.php(216): Model->query('INSERT INTO `mo...', Array) #2 /home/ordersibn/public_html/app/models/module_manager.php(332): Record->insert('modules', Array, Array) #3 /home/ordersibn/public_html/app/controllers/admin_company_modules.php(96): ModuleManager->add(Array) #4 /home/ordersibn/public_html/lib/dispatcher.php(111): AdminCompanyModules->install() #5 /home/ordersibn/public_html/index.php(21): Dispatcher::dispatch('/admin/settings...') #6 {main} After going back to the installed modules section, the module is now shown as installed. Universal module version is 1.2.0 Blesta 3.2.0, PHP 5.4.22, MySQL 5.0.10.

From business point of view I would prefer getting money first and worry about the details (CSR) later.

There is a ssh2 extension for PHP which you can use to make the actual connection and execute commands, see http://www.php.net/manual/en/book.ssh2.php .

Using SSH to connect to the remote server from your module is a bad idea. If you really want to go that route, set up key based authentication. I would suggest making your own VestaCP module to provide this API interface for the functionality you need, perhaps implement the REST interface - there are lots of examples around.

Is it safe to assume that 3.1 will not see daylight before 2014?

I also agree with all points listed by nsc. My personal priority list is (highest priority first): 7. Auto-action after reply? for example after answering tickets, it would be nice if it would go to "awaiting reply" or different status. Most of the time ticket has to go to the same status after reply, why it needs to be changed manually ? 8. Auto-action after user reply? I answered to user, changed to "Awaiting reply" status, when user replied, it still was in "Awaiting reply". You should consider to add feature, automatically would change Status to for example "In progress" after user replies. 1. Adding + to one of existing requests: Custom ticket statuses with different colors in priorities (being able to change colors would be nice). So I'd love to have that feature also. Colors helps to notice more important tickets in a bunch of them. Custom statuses would help to personalize ticket system. 6. Ability to add/remove columns in "Tickets" part. For example i would like to see client name and assigned stuff in there. Now I need to go to the exact ticket to see that information (yes, i know that it is written in "last reply" part when someone replies, but what if I replied those?) What if there are more than 20tickets at that time? view all of them ? I'm not a robot, i can't remember what status I saw some time ago, or what my colleague set in it by ticket numbers. 3. Ability to add signature per staff user. I think no need to explain why this is needed. 4. Ability to change client in ticket. This is needed when You have some report, or problem in Your mail, but not in ticketing system. So You are able then just forward it to blesta, change ticket client to the real one, and give replies normally having all conversation with him. For example i have a cron that sends to blesta mails, that i sometimes need to write info to client, so creating new ticket and copy pasting all info to it takes unneeded time resources. Also might be that user went out for holidays or got fired, and that same job with all info should be done by having conversation with different person. 5. Ability to forward ticket. When You need to get info from 3'rd party, it would be nice, that You could write to him from the same ticket, and when he would reply, it would be in one ticket, not in separate ones. 2. Ability to quote messages, when doing reply. Having ability to choose quoting bellow answer or on top of my answer would be nice (i prefer quote bellow my answer). When client writes not one ticket, but few at once, quoting makes easier not to get lost for him between obtained answers. 10. Ability to delete tickets 9. Ability to merge tickets