Skip to content

Upgrade V1 to V2 [EN]

Thomasfds edited this page Apr 22, 2021 · 4 revisions

Upgrade Guide Translated by Google Translate.

1 - Backing up your data

First of all, it is essential to save all the files of the old version of the CMS, we will reuse the images and information that some files contain.

Back up** your database** as well.

2 - Download

Download the latest release package available here: https://github.com/Thomasfds/intersect-cms-unleashed/releases/tag/2.0.0

3 - Installation

Delete all of the existing web files from the folder that contained the old version. Then download the new CMS files.

Once everything is finished, open the .env.local.php file

The "DATABASE_URL" line replaces the following information:

mysql://[email protected]:3306/otda?serverVersion=5.7

by the good ones, respecting the following format:

mysql://username:[email protected]:3306/database_name?serverVersion=5.7

Once the data, save, go to your MYSQL database manager (PhpMyAdmin in 99% of cases), select your database (which was saved during step 1), click on import, search the upgrade.sql in the package file that you downloaded above, and validate the import.

If no error is displayed on your screen, go to the file manager and empty the cache (see tips 1).

On the "MAILER_DNS" line, modify while respecting the following format: smtp://usernameEmail:password@yourmtp:theport

Now, we are putting the resources necessary for your site back online, all will happen in the "public / assets /" folder in a first old cms having the same file configuration, uploaded the images and others in the same folders ( Example: public / assets / general / news for your images on the front page of your articles).

Also remember to write in your database the name of each item in the store item, otherwise an error will occur.

4 - Try the new version

Now everything is ready to prepare your new version, if you have any problems contact me through the Intersect forum, Discord or start an issue on Github.

TIPS 1: Clear the cache

Go to the file manager, in the folder containing the CMS, go to the var / cache folder and delete the "prod" folder.