Upgrading notes for AppMail 1.x to AppMail 2.x

Upgrading notes for AppMail 1.x to AppMail 2.x

When upgrading from AppMail  1.x to AppMail  2.x there are a few things you need to do before starting the upgrade process.

#1. It is very important you backup your application, be it on your own or by using the Backup Manager.

#2. You need to disable all the extensions and themes you have added to the application. Please note that we're not talking about core application extensions but extensions you have bought or developed and added into the application.
You can do this from Backend > Extend > Extensions and Backend > Extend > Themes.

#3. If you are using a language pack other than english, you need to set your application default language to english. You can do this from Backend > Extend > Translations.
For best results, if your user (not customer) account is using a different language than english, edit it and make sure it also uses english.

Possible problems during/after the upgrade process:

#1. You started the upgrade process without disabling the extensions and now you cannot access your backend dashboard to do so. In this case, login via FTP and navigate to the apps/ folder and find the extensions folder and rename it to something else, say extensions-disabled. This should allow you to continue the upgrade process. Once the upgrade is done, rename the extensions-disabled folder back to extensions BUT not before you upgrade all your extensions, so they are compatible with AppMail  2.0.

#3. You started the upgrade process and you're using other language than english and now you're getting an error related to translations and/or missing translation database tables. You will have to login via FTP and open the file apps/common/config/main.php and locate this piece of code:

'messages' => [
    'class'                  => 'CDbMessageSource',
    'cachingDuration'        => 3600,
    'sourceMessageTable'     => '{{translation_source_message}}',
    'translatedMessageTable' => '{{translation_message}}',
],

and delete it. Simply remove it and save the file.
This should allow you to continue with the upgrade process. Once the upgrade process is done, simply undo your changes to this file, put back the code you just deleted, and save the file.

    • Related Articles

    • Nginx server basic configuration for AppMail

      Please note that the below configuration is going to use php-fpm for what is worth. /etc/nginx/nginx.conf # For more information on configuration, see: # * Official English Documentation: https://nginx.org/en/docs/ # * Official Russian Documentation: ...

    • Guide to follow while creating your AppMail extensions

      The naming convention of the extension folder and extension init file for the extension remains the same, if your extension folder is called amazon-s3 your extension init file must be called AmazonS3Ext.php and must contain the class AmazonS3Ext ...

    • Extend AppMail

      AppMail is highly extensible and flexible. You can extend it using a high number of extensions for payments, backup, email validation and so on, you can alter the look of it by either using customisations or custom themes and you can translate it in ...

    • How can I tell AppMail how to use or not to use php’s Tidy extension?

      Please note that the setting from the code also works and has more weight than the one from the web interface, therefore if Tidy is enabled from the code but disabled from the web interface, then it will be disabled, but if it is disabled from the ...

    • Use 2FA in AppMail

      Two-factor authentication (2FA), sometimes referred to as two-step verification or dual-factor authentication, is a security process in which users provide two different authentication factors to verify themselves. This process is done to better ...