Skip to content

Latest commit

 

History

History
21 lines (14 loc) · 1.35 KB

UPGRADE.md

File metadata and controls

21 lines (14 loc) · 1.35 KB
Raw

Migration from Mailtrain v1 to Mailtrain v2

The migration should happen almost automatically. There are however the following caveats:

  1. Structure of config files (under config) has changed at many places. Revisit the default config (config/default.toml) and update your configs accordingly.

  2. Images uploaded in a template editor (Mosaico, Grapesjs, etc.) need to be manually moved to a new destination (under client). For Mosaico, this means to move folders named by a number from public/mosaico to client/static/mosaico.

  3. Directory for custom Mosaico templates has changed from public/mosaico/templates to client/static/mosaico/templates.

  4. Imports are not migrated. If you have any pending imports, complete them before migration to v2.

  5. Zone MTA configuration endpoint (webhooks/zone-mta/sender-config) has changed. The send-configuration CID has to be part of the URL - e.g. webhooks/zone-mta/sender-config/system.

  6. If there are lists that contain birthday or date fields that were created before commit bc73a0df0cab9943d726bd12fc1c6f2ff1279aa7 (on Jan 3, 2018), they still have TIMESTAMP data type in DB instead of DATETIME. The problem was that that commit did not introduce migration from TIMESTAMP to DATETIME. Mailtrain v2 does this migration, however in some corner cases, this may shift the date by a day back or forth.