Leaderboard

The premadekb articles are a pretty good starting place. For $50 is saved me a ton of time as all I had to do was read each one to make sure it sounded right and looked correct to me. It will give you most of the cpanel kb articles you need as well as instructions for updating name servers at many of the popular registrars. They have Softaculous articles as well which is helpful. They didn't cover any of the items that cloud linux uses if you use that but it was quite easy to add a couple more articles for those items.

Glad I could help!

Agreed, if the articles will save you time it's worth the money. Before I got married and had kids, I had a lot of time so writing the articles myself would have been no big deal.. but now I'm happy to pay for things that save me time.

The module enforces an 8 character username limit as described in the docs. You may be able to support up to 16 character usernames if 'database prefixes are disabled'. You can update the module to increase the character limit to 16 if you'd like. Open /components/modules/cpanel/cpanel.php and find: 'rule' => array("betweenLength", 1, 8), Change it to 'rule' => array("betweenLength", 1, 16), and try adding the service in Blesta again.

The module always logs a success result for requests (Input). Responses from cPanel (Output) may not result in success. If you don't receive a response, then you may have a log with an Input value but no corresponding Output. The error check you removed from the module appears to be accurate. Blesta is unable to communicate with the server, or the credentials are incorrect. Make sure that the server Blesta is installed on meets the system requirements. If no outbound connections are being attempted, make sure you have curl available to php. If you're still not able to find out where the problem lies, you can check if the module is throwing an exception. You will need to add a line of code to the module. Open /components/modules/cpanel/cpanel.php and find: $this->log($module_row->meta->host_name . "|listpkgs", null, "input", true); Just below that is a catch statement: catch (Exception $e) { // API request failed } Update it to log the exception message: catch (Exception $e) { // API request failed $this->log($module_row->meta->host_name, $e->getMessage() . " \n\n" . $e->getTraceAsString(), "output", false); } Then go to add/edit a cPanel package in Blesta. A request will be made to fetch the packages from cPanel. If an exception is thrown by the module, the module will now log an entry into the Module Logs table under [Tools] -> [Logs] that should give more insight into the problem.

I've added a language to the translator for Taiwan that you can use for translating Chinese Traditional.

Really not sure how you could get that. You should only get the unknown status if the local license data can not be decrypted. When you receive the unknown status, what do you have stored for the license data on the client side? It should be the same data both before and after the client changes location before the next call home.

So you need just KB articles related to cPanel. - How to set-up a email address - How to log into cPanel from Blesta - How to make a database and username - How to install Wordpress with Softaculous or manually (depending if you have Softaculous) - How to make a backup and download it - How to change the cPanel theme - How to change your password - How to log into PHPmyAdmin - How to access Webmail - How to scan for malware with clamav Stuff like that is from the top of my head as I don't like cPanel

Yeah ive got them working on something, they seem pretty keen on blesta! There a great bunch over there

Thanks I hadn't seen that! Still open to other suggestions too

Have you checked this mate: http://www.blesta.com/forums/index.php?/topic/3910-premadekbcom-blesta-ready-made-cpanel-knowledgebase-articles-images/

I see the issue. In some cases LicenseManager::decryptData can't decrypt the data, so it returns null. When null is unserialized it returns boolean false. Added CORE-1643. We'll work on a fix. Thanks!

The expired status will only be provided if the last call-home is date is more than $ttl seconds past. Where $ttl is passed into LicenseManager::validate(). You'll only receive a suspended status if the service for the license is suspended in Blesta, and the client makes a call-home to fetch this update. This is one reason why you should perform at least a daily call-home. The invalid_location status is given if the IP, path, or domain of the client no longer matches the value stored in the encrypted license data stored on the client.

I think you are referring to LicenseManager::validate() on line 155 of license_manager.php. That method only returns a status of unknown if no license data is given, or the license data signature is invalid.

That is the desired behavior of the License Module. The license_module_status field will only contain "reissue" if the license is in a reissue state. If not in a reissue state, then it contains no data.