Jono

Hello blestars
My 2 cents on this mater  
We are ditching cPanel for good, mass migrations servers to Virtualmin, the Virtualmin handle 100% cPanel Backups restore witout any issues and so we only need to point the DNS's to the new servers

We only made a few changes on Virtualmin. On Webmin, we add ports 2096/2097 to redirect to Usermin port 2000 and 2086/2087/2082/2083 ports to Virtualmin port 10000

We also pré-installed on the hostname phpMyAdmin and RoundCube with the Mobile Theme (https://github.com/messagerie-melanie2/Roundcube-Plugin-Mobile) to all users have normal acess to a known Webmail and MariaDB Database managment  (Virtualmin alredy bring there own DataBase Managmente and Webmail software). and add a Link on Usermin Painel to open RoundCube Webmail
Finally we add CSF Firewall like so:
cd /usr/src rm -fv csf.tgz wget https://download.configserver.com/csf.tgz tar -xzf csf.tgz cd csf sh install.sh - Install the csf webmin module in:
Webmin > Webmin Configuration > Webmin Modules > From local file > /etc/csf/csfwebmin.tgz > Install Module (sometimes because the webmin cache we have to make this step twice)
After you install the module, you can simply log in to Virtualmin, chick on Webmin (top left) and then: System > ConfigServer Security & Firewall
Also we add PHP verions 5.4, 5.6, 7.2 (now by default virtualmin alredy brings php 5.4 and 7.2) 
#we install remi repository to add more php versions and modules yum install http://rpms.remirepo.net/enterprise/remi-release-7.rpm yum install php56 php56-php-bcmath php56-php-cli php56-php-devel php56-php-fpm php56-php-gd php56-php-mbstring php56-php-mysqlnd php56-php-opcache php56-php-pdo php56-php-pspell php56-php-xmlrpc php56-php-memcached php56-php-iconv php56-php-zlib php56-php-mcrypt php56-php-simplexml #you cann add/remove extensions abose :)  
We also add ioncube like so:
cd /usr/local wget https://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.zip unzip ioncube_loaders_lin_x86-64.zip rm ioncube_loaders_lin_x86-64.zip And add to php.ini on Virtualmin the line for exemple for php7.2
zend_extension = /usr/local/ioncube/ioncube_loader_lin_7.2.so To start migrate you can do it on Virtualmin GUI or on CLI, on CLI (https://www.virtualmin.com/documentation/id%2Cvirtualmin_for_cpanel_users) you can make a batch file with mass import in a very easy way like so:
virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file.tar.gz --user cpanel_username_here --pass 'cpanel_username_password_here' --webmin #for multiple just add a .sh file with a somethin like this: virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file1.tar.gz --user cpanel_username1_here --pass 'cpanel_username_password1_here' --webmin virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file2.tar.gz --user cpanel_username2_here --pass 'cpanel_username_password2_here' --webmin virtualmin migrate-domain --type cpanel --source /home/cpanel_username_backup_file3.tar.gz --user cpanel_username3_here --pass 'cpanel_username_password3_here' --webmin #and so on... Its more easy and less troblen then DirectAdmin, Plesk or even Interworx
Common problems after migration:
#Error 500
.htacess file with the directive "Options +FollowSymlinks" just comment that line
#Rong php version (client can change PHP on Virtualmin painel)
#Some notes for anyonw that never try Virtualmin/Webmin
Virtualmin/Webmin (port 10000) Root = WHM (so many features that in the first time we "lost" inside, but the more time we spent the more you will likeit, its a lot better and more mature then cPanel)
Virtulmin/Webmin User (port 10000) = cPanel (A lot more options than cPanel)
Usermin = Webmail (but with a loit more option like POP/IMAP external emails sincronizing and SPAM filters more advanced than cPanel)
The only thing is that dosent support CloudLinux (its not a downside) and dosent support Softaculous (Virtualmin has is own Software inside that you can add toyr own scripts or buy the Pro License that is 200$ per year with unlimited accounts)
The GPL verion dosent support Reseller accounts, but you can bypass this if you dont want to spend now any money, just creat on Webmin New users with permissions to only acess there clients accounts, is like a Reseller accouny but witout any limit on creating, or do it like us and create for each reseller a VPS or CLOUD server for that reseller maybe is cheper than buy a Virtualmin Pro license, on this critical fase  
Any problems or any douths you can ask me and I will try to fill in  

P.S- We are migrating more than 5k clients from cPanel to Virtualmin and we have tested a lot Virtualmin since last year iin migrations and compability (we have several CLOUD on production with dozens of clients with CentoS 7 + Virtualmin), because of our new CLOUD platform that we have created. 

Yea this module was built a couple years ago.  I believe at that time they were still in the process of developing their current API.  You can see that the endpoint structure is completely different between the examples, so the module must be working off of an old API.  I'll go ahead and create a task to look into updating the module to use the new API.  CORE-3217

We've created CORE-3206 to do just that

Both the white space (CORE-3181) and the tooltips remaining open (CORE-3201) are resolved in the final release of 4.6.  They should now remain open for 2/10 of a second unless you hover over the body of the tooltip in which case it will remain open until you mouse off.

so you may thank me by pressing the like button...

You have the system_hash key in config/blesta.php
but break that and your encryptions are all gone.

Edit:
HAHAHAHAHAH the password from a hash? Erm it's done with Bcrypt which is irreversible like Beav said. There's NO way you can reverse that unless you use a competitor who doesn't use it correctly.

CORE-2964

2Checkout payment gateway is now recording payments after i used Secret Word.

Nice!
Looks like you may have another typo in the success message.  It says 'you can how submit a support ticket'.

Nice!
Looks like you may have another typo in the success message.  It says 'you can how submit a support ticket'.

After a long and great time building the CMS we wanted to change our way we do business to help others get the best out of Blesta and we can grow a bigger community with Blesta.
The BlestaCMS is now open-code and the "base" is free to everyone. That's currently 1.2.7. We will fix bugs and patch the version when needed for free but to upgrade to a new version let's say 1.3.0, you will need a license. We're still working on this to make sure the updates are safe and secure. You'll also need a license if you wish to get support from us with active support and updates.
If you do need support you can go to our support ticket page, click on BlestaCMS Support and then enter your license key. This will allow you to submit a ticket.
You can download the latest version of the BlestaCMS Base here: https://blesta.store/client/plugin/download_manager/client_main/download/26/CMS-1.2.7.zip
Support:

Valid:

Suspended:

PS: We've fixed the spelling on complimentary, sorry for the error on the screenshot.
Cancelled:

 
---
BlestaCMS previews: https://blesta.store/cms
Share / View the code / Modify / fork freedom on Github: https://github.com/atlanical/BlestaCMS-Community-Edition

Well I kinds depends.  If you are looking to do it through the API then you should first call SupportManagerTickets::add() like this
$ticket_data = [ 'vars' => [ 'department_id' => 1, 'staff_id' => 1, // This field is optional 'service_id' => 1, // This field is optional 'client_id' => 1, // This field is optional 'email' => 'firsttes@mailinator.com', // This field is optional 'summary' => 'Something is terribly wrong', 'priority' => 'critical', 'status' => 'open' ] ] $ticket = $api->post("support_manager.support_manager_tickets", "add", $ticket_data); On the other hand, if you are within Blesta you should be able to use the loader to access the model even though it's from a plugin.  In a controller that would look like this
$ticket_data = [ 'department_id' => 1, 'staff_id' => 1, // This field is optional 'service_id' => 1, // This field is optional 'client_id' => 1, // This field is optional 'email' => 'firsttes@mailinator.com', // This field is optional 'summary' => 'Something is terribly wrong', 'priority' => 'critical', 'status' => 'open' ]; $this->uses(['SupportManager.SupportManagerTickets']); $ticket = $this->SupportManagerTickets->add($ticket_data);

Well I kinds depends.  If you are looking to do it through the API then you should first call SupportManagerTickets::add() like this
$ticket_data = [ 'vars' => [ 'department_id' => 1, 'staff_id' => 1, // This field is optional 'service_id' => 1, // This field is optional 'client_id' => 1, // This field is optional 'email' => 'firsttes@mailinator.com', // This field is optional 'summary' => 'Something is terribly wrong', 'priority' => 'critical', 'status' => 'open' ] ] $ticket = $api->post("support_manager.support_manager_tickets", "add", $ticket_data); On the other hand, if you are within Blesta you should be able to use the loader to access the model even though it's from a plugin.  In a controller that would look like this
$ticket_data = [ 'department_id' => 1, 'staff_id' => 1, // This field is optional 'service_id' => 1, // This field is optional 'client_id' => 1, // This field is optional 'email' => 'firsttes@mailinator.com', // This field is optional 'summary' => 'Something is terribly wrong', 'priority' => 'critical', 'status' => 'open' ]; $this->uses(['SupportManager.SupportManagerTickets']); $ticket = $this->SupportManagerTickets->add($ticket_data);

@Jono
We now have a basic blueprint of API documentation https://cyberpanel.docs.apiary.io/
Let me know if you need any specific function, you can use this call to get user information https://cyberpanel.docs.apiary.io/#reference/user-functions/get-user-information

Turns out it is an issue with permission for fetching the modal.  To fix you can alter app/client_controller.php starting at line 17 from
// Allow states to be fetched without login if ($class_name == 'ClientMain' && (in_array(strtolower($this->action), ['getstates', 'setlanguage']))) { return; } to
// Allow states and dialog to be fetched without login if ($class_name == 'ClientMain' && (in_array(strtolower($this->action), ['getstates', 'setlanguage'])) || $class_name == 'ClientDialog' ) { return; } This fix will be included in v4.4.  See CORE-2850

Turns out it is an issue with permission for fetching the modal.  To fix you can alter app/client_controller.php starting at line 17 from
// Allow states to be fetched without login if ($class_name == 'ClientMain' && (in_array(strtolower($this->action), ['getstates', 'setlanguage']))) { return; } to
// Allow states and dialog to be fetched without login if ($class_name == 'ClientMain' && (in_array(strtolower($this->action), ['getstates', 'setlanguage'])) || $class_name == 'ClientDialog' ) { return; } This fix will be included in v4.4.  See CORE-2850

感谢兄弟，成功了

感谢兄弟成功开启了域名注册功能了。

Ah, I've found it

It works . Thanks.

Can't be done without modifying the files for the support manager plugin.
In {blesta_dir}/plugins/support_manager/models/support_manager_tickets.php you can change lines 1230 - 1239 from
public function getPriorities() { return [ 'emergency' => $this->_('SupportManagerTickets.priority.emergency'), 'critical' => $this->_('SupportManagerTickets.priority.critical'), 'high' => $this->_('SupportManagerTickets.priority.high'), 'medium' => $this->_('SupportManagerTickets.priority.medium'), 'low' => $this->_('SupportManagerTickets.priority.low') ]; } to
public function getPriorities() { return [ 'high' => $this->_('SupportManagerTickets.priority.high'), 'medium' => $this->_('SupportManagerTickets.priority.medium'), 'low' => $this->_('SupportManagerTickets.priority.low') ]; }  

Can't be done without modifying the files for the support manager plugin.
In {blesta_dir}/plugins/support_manager/models/support_manager_tickets.php you can change lines 1230 - 1239 from
public function getPriorities() { return [ 'emergency' => $this->_('SupportManagerTickets.priority.emergency'), 'critical' => $this->_('SupportManagerTickets.priority.critical'), 'high' => $this->_('SupportManagerTickets.priority.high'), 'medium' => $this->_('SupportManagerTickets.priority.medium'), 'low' => $this->_('SupportManagerTickets.priority.low') ]; } to
public function getPriorities() { return [ 'high' => $this->_('SupportManagerTickets.priority.high'), 'medium' => $this->_('SupportManagerTickets.priority.medium'), 'low' => $this->_('SupportManagerTickets.priority.low') ]; }  

Requires a little JS
<?php $this->Javascript->setInline(" $(document).ready(function() { $('#content').ckeditor(function() {}, {language: '" . substr(Configure::get('Blesta.language'), 0, 2) . "'}); }); "); ?>  

Just a note, CORE-2600 is scheduled to be in the 4.4.0 release.

Not sure you could do that if you wanted to keep the client and simply make them inactive.  A client without a contact seems problematic.
If you are looking for relations on the client_id then there are some others.
module_client_meta - Blesta Core client_notes - Blesta Core client_packages - Blesta Core client_settings - Blesta Core client_values - Blesta Core reseller_pricing_clients - Reseller Pricing support_tickets - Support Manager You should also be concerned with tables related on the contact_id
accounts_cc, accounts_ach - Blesta Core contact_numbers - Blesta Core contact_permissions - Blesta Core log_contacts - Blesta Core support_replies - Support Manager download_logs - Download Manager mass_mailer_tasks - Mass Mailer I think that covers everything you missed.