Page History

...

Checking the integrity of your System Key and Encrypted Data

The /config/blesta.php file contains a very important Blesta.system_key. This key is generated during installation and must match the original database. If the key is changed, all encrypted data will be irrecoverable and your installation will be permanently broken.

...

Disable Human Verification (CAPTCHA)

If you enable a captcha Human Verification / CAPTCHA's for staff logins, and are then unable to login and must disable the captcha, you may run this disable Human Verification for the company using the following query. Please note that this will disable Human Verification / CAPTCHAs for the entire company. If you are using multi-company and the issue affects a company ID other than 1, update the query to replace the company ID with the desired company ID.

UPDATE `company_settings` SET `value` = 'a:0:{}' WHERE `company_settings`.`key` = 'captcha_enabled_forms' AND `company_settings`.`company_id` = 1;

ThenAfter running this query, login to Blesta and visit Settings > Company > General > Human Verification, and adjust . Adjust your settings and re-enable Human Verification / CAPTCHA's for the desired forms.

Regain Staff Access to Settings

...

INSERT INTO client_settings (client_settings.key, client_settings.client_id, client_settings.value) SELECT 'autodebit', `clients`.`id`, 'true' FROM `clients` LEFT JOIN `services` ON `services`.`client_id` = `clients`.`id` AND `services`.`status` = 'active' LEFT JOIN `client_settings` ON `client_settings`.`client_id` = `clients`.`id` AND `client_settings`.`key` = 'autodebit'  WHERE `services`.`id` IS NULL AND `client_settings`.`key` IS NULL;

How do I prevent a domain or service from being renewed via the module when an invoice is paid?

Sometimes, particularly with domains the domain could be renewed outside of Blesta. We recommend that you let Blesta handle these renewals automatically. If for some reason you need to prevent that from happening you will need to remove the relevant record from the service_invoices table where invoice_id=your invoice id, and service_id=your service id.

Fetch the Collation of Tables

...

#!/bin/bash
# Upgrade MariaDB to 10.2

# ------- REPLACE MARIADB -------
# Set up MariaDB 10.2 repo
cat >/etc/yum.repos.d/MariaDB10.repo <<EOL
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.2/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
EOL

# Stop MariaDB
systemctl stop mariadb

# Remove old MariaDB
yum -y remove mariadb-server mariadb mariadb-libs
yum clean all

# Install MariaDB 10.2
yum -y install MariaDB-server MariaDB-client
# UNCOMMENT IF YOUR PHP MYSQL PACKAGE IS php-mysql
#yum -y install php-mysql
systemctl enable mariadb
systemctl start mariadb
mysql_upgrade

# Re-install postfix!
# UNCOMMENT IF RUNNING VIRTUALMIN OR POSTFIX
#yum install postfix -y
#systemctl enable postfix
#systemctl start postfix

Manually Resetting Staff Password

There are a couple ways to reset your staff password, from simplest to most complex. Follow these steps in order until your password has been successfully reset:

1. To reset the staff password visit /admin/login and click the "Reset My Password" link. Enter your username, and click the "Reset Password" button. You should get an email with a password reset link within a few minutes.
2. If you don't get an email, ensure that your username is correct. In phpMyAdmin or other MySQL database utility, look in the users table. Your username should appear in the "username" column, typically where id equals 1, as the primary staff account is the first user to be created. Try using the password reset option above with the correct username.
3. If that still doesn't work, you will need to temporarily enable legacy passwords.
   1. Please see Encryption in the user manual, specifically Blesta.auth_legacy_passwords and set it to true.
   2. Then, in the users table for your username, update the password field to: 5f4dcc3b5aa765d61d8327deb882cf99
   3. Then, try logging in with your username and the password password. Reset your password.
   4. Then, change Blesta.auth_legacy_passwords back to false.

Renaming a Module

In some rare cases it may be necessary to rename a 3rd party module. For example, if you are using a third party module named TestModule, and we release an official module called TestModule, you may wish to rename third party module so that it is not overwritten by the official module.

The first step is to rename the module directory and primary module file

• /components/modules/testmodule becomes /components/modules/testmoduleold
• Rename /components/modules/testmodule/testmodule.php to /components/modules/testmodule/testmoduleold.php

The second step is to  update the class name in testmoduleold.php from:

class Testmodule extends Module

to

class Testmoduleold extends Module

The third step is to update the modules database table.

UPDATE `modules` SET `class` = 'testmoduleold' WHERE `class` = 'testmodule';

The fourth step is to change view context statements from:

$this->view->setDefaultView('components' . DS . 'modules' . DS . 'testmodule' . DS)

to

$this->view->setDefaultView('components' . DS . 'modules' . DS . 'testmoduleold' . DS)