How To Update Prestashop 1.6 To 1.7

How to upgrade PrestaShop

Important

Do not get further if yous haven't made a backup of your shop.

Rollback will be the only mode to go back if something does non become well, and this requires a fill-in.

Learn how to fill-in your shop

This affiliate describes several ways to complete an upgrade of PrestaShop.

Manual upgrade – Process details

This guide gives you the full control on the procedure. This one has been applied by PrestaShop for several major versions, and thus can be applied on very old shops.

Release download

The start stride is to download the latest version on https://world wide web.prestashop.com/.

If you upgrade to another version of PrestaShop one.6, the release files tin can be constitute in a dedicated archives list.

Download can likewise exist done in command line, as done here with the version 1.7.7.five:

            wget -O prestashop-upgrade.zippo https://www.prestashop.com/download/quondam/prestashop_1.vii.7.v.zip                      

Extract the files from the annal with a tool similar 7zip

Note starting from PrestaShop 1.7.0.0, the release package contains a zip file itself, which must exist extracted likewise.

On a Linux terminal, you tin can use the command `unzip`:

            unzip prestashop-upgrade.cypher              &&              unzip prestashop.zip                      

One time yous take the folders like classes/, modules/, themes/, etc. you lot may go on the adjacent step.

Sample files cleanup

Avoid overwrite the production resources (images, conf …) with the default data. These folders can be removed from the new release:

• img/
• override/

All the other files present in the new release will overwrite the existing files. All changes you made on the original source lawmaking volition be lost (by the way, this is not recommended, y'all should never modify the cadre files).

Too, rename the "admin" folder to match your shop's admin folder proper noun. This will prevent an unwanted duplication of the administration content.

Turning on maintenance mode

The shop will now be modified. As it may cause unexpected beliefs for y'all and your customers during the upgrade, nosotros highly recommend you to plow on maintenance fashion during the upgrade.

This can be done in your administration panel:

• On PrestaShop 1.seven, in Store parameters > Full general > Maintenance tab
• On PrestaShop 1.6, in Shop parameters > Maintenance

Calculation your IP address volition allow you to admission your shop while information technology'southward in maintenance mode. That way, you tin can make sure everything is working right before allowing your customers to access information technology again.

File copy

In this step, we "upgrade" the PrestaShop files past copying the new release content in the existing shop.

Disable cache

You lot may have activated a caching organisation (eg. memcache) on your store. In that case, make sure to disable it in "Avant-garde Parameters" > "Functioning". You tin can enable information technology again once the upgrade procedure is done.

Note about vendor binder: Previous upgrades of PrestaShop 1.vii showed that conflicts may occur when merging the new vendor/ folder with the onetime one. To avoid this problem, we recommend to delete this folder in the existing shop earlier copying the new one.

On Windows, copy the new binder content and paste it in your shop folder. You will become warnings that files already exists in the destination binder. Choose "overwrite" to keep.

On linux, the copy can be done in your last:

            cp -R <path_to_the_new_release>/* <path_to_the_current_shop>/                      

Example:

            cp -R ~/Downloads/prestashop/* /var/www/html/                      

Database upgrade

Once the files have been copied, your shop database is prepare to be upgraded.

Some web hosting providers gives you two user accounts to access your database. One with full privileges the other for using in scripts with limited rights. To be able to apply this Database upgrade script you have to use the account with total privileges.

All the changes to utilise have been defined in the install folder, running them tin exist done with a specific PHP script.

When you're prepare, run the file install/upgrade/upgrade.php.

This can exist done with a browser, past reaching the accost http://<shop_domain>/install/upgrade/upgrade.php, or from your server's control line:

            php install/upgrade/upgrade.php                      

In both cases, an XML log will be displayed. The result can exist found in the attribute result of the first tag <activeness>:

• ok if updates have been found and executed
• error if something went wrong
• info for next deportment, displaying the details on the procedure

Execution log

When the upgrade script found some upgrades to apply, the SQL queries run will be listed forth their respective consequence.

                          <?xml version="1.0" encoding="UTF-8"?>              <action              result=              "ok"              id=              ""              >              <action              result=              "info"              id=              "1.7.0.5"              >              <![CDATA[[OK] PHP 1.7.0.5 : /* PHP:ps_update_tabs(); */]]>              </action>              <action              result=              "info"              id=              "1.vii.0.5"              >              <![CDATA[[OK] SQL 1.7.0.5 : Change Table `ps_currency` Modify `name` varchar(64) NOT Naught]]>              </activity>              <action              event=              "info"              id=              "1.7.i.0"              >              <![CDATA[[OK] SQL ane.vii.1.0 : Gear up SESSION sql_mode = '']]>              </action>              <activeness              outcome=              "info"              id=              "i.seven.1.0"              >              <![CDATA[[OK] SQL 1.vii.1.0 : Set NAMES 'utf8']]>              </action>              [...]                      

You tin double check that each action is marked as "OK". If not, boosted details will be shown subsequently the request, which tin help yous fix the consequence and re-execute the request manually on your database. In some cases, you may need to restore your database fill-in and start over.

Error codes

An error code tin can also be displayed. Each code is related to a message described hither:

• Error #27: The shop is running a newer version than the content provided by the install folder.
• Error #28: The shop is already at the version y'all try to upgrade to.
• Error #29: Could not observe the current version. Bank check your database parameters file and the database connection.
• Error #31: Unable to notice upgrade directory in the installation path, does the folder install/upgrade/sql exist and is not empty?
• Error #32: No upgrade needs to be applied.
• Error #33: Error while loading a SQL upgrade file. Check your permissions of the folder install/upgrade/sql.
• Error #twoscore: The version provided in the file install/install_version.php is invalid.
• Error #43: Fault while upgrading database schema using doctrine.
• Mistake #44: Error while updating translations.
• Error #45: Error while enabling theme.

Cleanup

Before going further, a few things should now exist cleaned.

• The install folder, used to run the database upgrades, is not needed anymore and can exist safely deleted.
• When opening your store (in the front or back office) on your browser, you may see some visual issues. This can be due to your old assets being still served by a cache. Reload them by forcefulness-refreshing the page (printing ctrl+R on Windows / Linux or cmd+R on Mac OS) or clearing your browser's enshroud.

Modules upgrade

Your modules files have been upgraded during the file copy, however many of them may require additional changes on the database. Please check the module page in your Dorsum Office to run across if upgrades are waiting to exist run.

Get to your administration console and login. You volition notice the version displayed has changed on the login page. Then in the menu, click on the module page to reach your itemize.

On PrestaShop ane.6, this page can exist found in "Module & Services". Click on "Update all" at the top of the page to run all bachelor upgrades:

On PrestaShop 1.7, the same feature tin be plant in the Amend >> Modules page, under the tab "Notifications":

1-click upgrade module

If the manual procedure seems too dull, other solutions exist to complete an upgrade.

PrestaShop provides the module 1-click upgrade for free on the marketplace and your shop administration panel. It executes the previously given procedure automatically, and is bachelor for nearly all versions of PrestaShop.

Y'all tin read more about it here.

Support service

Doing an upgrade by yourself can be risky. If you feel uncomfortable with doing it on your own, you tin leave it to our support team who will handle the fill-in and the upgrade to the terminal minor version for you (one.half dozen → one.6, 1.vii → 1.7 etc.).

Basically, the procedure and the result will be the same. The existing data on the shop volition be kept, equally well every bit your module and your current theme.

You lot tin subscribe for the upgrade service on the marketplace.

Many agencies and freelancers in your area may likewise provide this kind of service.

Source: https://devdocs.prestashop.com/1.7/basics/keeping-up-to-date/upgrade/

Posted by: langfordcounce.blogspot.com

Share this post