Leaderboard

I never recommend CloudFlare it causes more problems than it resolves, but feel free to edit: /components/modules/cpanel/views/default/client_service_info.pdt

Thanks a lot @BlestaStore, works perfect.

A new CentOS Web Panel (CWP) alpha module is available. To install, download the attached centoswebpanel.zip and unzip the file. Upload the centoswebpanel directory to ~/components/modules/ and go to Settings > Company > Modules to install it. Per http://wiki.centos-webpanel.com/cwp-account-api You must set an API Key on your CentOS Web Panel server in: /usr/local/cwp/.conf/api_key.conf You must add your Blesta server's IP address on your CentOS Web Panel server in: /usr/local/cwp/.conf/api_allowed.conf Any comments or suggestions, please post them below. centoswebpanel.zip

Hello The community LAST UPDATE : 23-08-2014 First i dont know if this is the correct forum to post ! another time we are happy to announce the release of the first professional Template for blesta called admin LTE , this Template is based in the adminLTE , is bootsrap of course (3.1.x) . to not talk so much i will let you with some screenshoot . Login Page Client Dashboard Client Other Pages when we get more time we will word in the admin side , but we need to add ability to select template for admin side like client side . any BUG/SUGGESTION port it in this thread . you can download it from github https://github.com/Blesta-Addons/adminlte just upload the folder adminlte inside the folder "app/views/client/" and select the template from admin area . THE BONUS : the color theme can be changed from admin side in look and feel , client section . if you like our work , thanks or donate

Blesta doesn't have a Blesta 3.x+ to 3.x+ only a 2.5 to 3.0+. If you want to migrate another installation to your current one you would need to either use a CSV importer or hire someone to make you your own importer. It's quiet hard to do from what I know unless you are importing to a company B. If you are moving your installation to another server just copy the files and DB and move them over.

Exactly I will need @Paul 's help in order to migrate clients and their services @gosuhostThat I already knew read several times the tutorial I need a solution to be able to do the migration, if you can already migrate from WHMCS to blesta because you can not from blesta to blesta in versions 3+ - 4+

I can confirm this works. Thanks again Tyson and Paul.

I'm adding Tyson's solution to this thread in case it comes up for anyone else. Nobody should do this unless they rely on snake_case and are having the same issue as @barryf CamelCase should be used going forward.

As Mike mentioned, you need a mapping file. All this does is map the whmcs fields to the blesta fields for Virtualizor. The mapping file would go in ~/plugins/import_manager/components/migrators/whmcs/5.2/config/. Point the Virtualizor folks to this directory and the existing mapping files (like cpanel.php, directadmin.php, etc) as an example. Once you have the mapping file and have uploaded it to that directory you'll need to run the importer again (from a fresh Blesta install).

4.0 was a major release, which included an upgrade to the framework minPHP, PHP 7 support, and a lot more. Major releases can have backwards incompatible changes. Any custom extensions should be tested with a major release in a dev environment before deploying live.

for me, if they pay i don't matter if is sub-domain or domain or nonexistent domain . they need just to respect our terms and don't abuse our system .

Anyone that has a large number of invoices should run the upgrade via CLI. The data in the table is required to reliably process renewals through a module. Not many modules support renewals, so for some people it might not be a big deal to skip populating the table (would require a modification to the migrator). If the table isn't populated though, and you have say a domain name for an invoice that was generated before the upgrade, then paid after the upgrade, it would not be renewed through the module. Hopefully this doesn't turn into a big issue. It may have been better for the cron to handle initial population.

The error handler doesn't stop php execution over notices so the cron wouldn't fail to complete if no output buffer exists to flush. There's something else going on that's causing the cron to hang (e.g. waiting for a callback from a module request). Does the cron complete adding all of its services every time?

then talk to the developers of swiftmailer directly then? or use a cc processor that doesn't require you to use tls v1.2? as I usually only use paypal gateway since it handles both and each is handled off on paypal's site so I don't have to deal with no pci compliance which is why I am guessing you are enforcing tls v1.2 only on your mail system.

Indeed. Thank you. But such a feature would be useful for customers also. I think there are some attack techniques which could exploit this as a vulnerability.

Version 4.1.1 is now available. Please see the announcement. This is a patch release that corrects issues with 4.1.0. Be sure to run /admin/upgrade after uploading the patch or full versions. NOTE! If you have a large number of invoices, it may be necessary to run the upgrade via CLI as the upgrade process can take some time while a new table is populated. To upgrade via CLI, from your Blesta directory run: php ./index.php admin/upgrade Patching Blesta See Patching Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.1.1. See all Change Logs.