Leaderboard

cpanel working well , but in a big companies the actual cpanel plugin need some tweaks . actually, the module create account in the server selected in package , or if module groups created , the cpanel module use "first" methode free server to provision the account in it . so no options for staff to choose wish server to host the account . so , what i suggest a option to choose wish server to host the account , if not choosed then use the default method to host account . when thinking in this request make in consideration a park of 5 or 30 servers dedicated to host website . and some times we need to make a manual activation for account in some servers . another time v2, was this option

The forums have been upgraded. One thing to note is that you need to log in with your Display Name. On the old version, it was possible to have a username that was different than your display name. If you are having trouble logging in, login with your name as it appeared when you posted.

Same questions on my mind. Thanks for this post. It helps a lot.

the code is no longer working after upgrade to 3.6.2 ... nos sure why , but the fallowing code will work . if (isset($vars->module_group) && $vars->module_group == "") { if (isset($vars->module_row) && $vars->module_row > 0) { $rows = $this->getModuleRow($vars->module_row); } else { $rows = $this->getModuleRows(); } } else // Fetch the 1st server from the list of servers in the selected group $rows = $this->getModuleRows($vars->module_group);

I am using piping But I don't want to have 12 google apps accounts. I want 1. Along with 12 aliases on it. admin@domain.com is the main account. info@, sales@, whatever@ are the aliases. I forward the aliases to the blesta domain. Alias1@google-apps.com forwards to alias1@blesta-install.com, alias2 forwards to alias 2 and so on However, if I sent an email to alias1@google-apps.com, it forwards the email to blesta, my server has logs of it. However, Blesta doesn't pipe in the ticket. It sends the "Ticket Bounce" error message template. So it actually reaches Blesta, but Blesta rejects creating a ticket for it. Departments are set to accept all emails, not just customers. However, if i email alias1@blesta-install.com directly, the ticket is piped in just fine. That's what I want to know. What's going on in Blesta to refuse creating a ticket the first way.

Piping is instant. You can forward email to another domain that accepts mail on your server and use piping instead.

Only reason is SLA's. Up to 5 minutes before a ticket is seen equals up to 50% of the reaction time for certain SLA segments in my case. Piping only takes about 30 seconds to a minute, so that helps a lot when it comes to response and reaction times. If only it were so simple to use IMAP in my case

Instead of piping, try using IMAP, and set up your Gmail rules like the following: department1@example.com gets put into a folder called DEPARTMENT1 department2@example.com gets put into a folder called DEPARTMENT2 etc.... Then, in the Blesta install, just change the IMAP folder for each department from INBOX to the department's folder. What are the benefits of piping compared to IMAP for you? Currently, we have it set up this way, and no complaints.

Im Lovin it

Version 3.6.2 is now available. More information on this advisory and direct download links can be found at http://www.blesta.com/2016/08/02/security-advisory/

What does the error say? If it is generic, you can edit /config/blesta.php and set this back to true: Configure::set("System.debug"), true); Then you should get a stack trace with more information about the issue. The more information you can provide the better.

I like the idea of making more data available, but this is something we'll need to discuss internally first.

I do miss this feature from v2.5. It's good for staff to be able to specify which server to use when manually provisioning. See CORE-2156