How to fix White Page bug after Prestashop migration ?

Welcome to the intervention specialist on Prestashop.
Web2007 is at your entire disposal for ALL your Prestashop needs.

The answer in detail: cause of the blank page bug following Prestashop migration

The first step is to enable debug mode to see if there is a problem (show the error message if so). If no message is displayed on the back of the desktop or on the homepage, it may be due to a cache problem. You must empty the caches created by Prestashop by hand, in the following FTP folders: /app/cache/dev/. Then remove Debug mode and the site should appear. Since version 1.7 of the software, these folders are no longer available. It is therefore essential to create a new manipulation of these: Make sure that you are using the latest version of PHP (at 7.2). Disable debug mode. If there is still a blank page. The problem is not related to the migration itself, but rather comes from elsewhere (database or module). ...), the possibilities are many, the debug mode could be beneficial in this scenario !
Migrate Prestashop to Woocommerce, , err_too_many_redirects Prestashop SSL, , Prestashop antivirus, , Prestashop boost speed, , Prestashop POS

To join Web2007:

Contact form

What are the problems that arise when changing Prestashop and what are the possible solutions ?

Many online retailers built on Prestashop would like to migrate to version 1.7; however, it's not easy, and sometimes it's better to start from scratch rather than trying to move on. First of all, let's say it again: there is almost an integrated update from Prestashop 1.6.x to Prestashop 1.7. 1.) You need to create a second one if there is none (sandbox) and then "re-create the store". 2.) Then, we will modify the 1.7 store to the 1.6 store: it is possible to automate the configuration via the development of an application (this automation is essential to ensure the transition). 3.) You will need to transfer information from 1.6 to 1.7 (customer orders, customer catalog category pages for cms, ...). The import process is done using copies of tables, database files (with mills to enter data from 1.6 into 1.7). It is crucial to realize that the Prestashop 1.7 database structure differs from the database structure that were previously available in Prestashop so don't think it will be a simple export data import. 4.) Now is the time to install the modules with the latest version at 1.7 or to modify or even replace them. It is a lot of is necessary before the migration to determine which modules will be modified or expanded. Some modules have disappeared in Prestashop 1.7 and are not updated, while others are free or paid (GDPR module, for example) Do not forget that the import script must import in 1.7 the data of the modules listed in 1.6. And, some modules have an impact on the database, so it is essential to understand the modules well before launching. 5) Eternal problem... the design. If we are using the same template, but it is not available in Prestashop 1.7, we need to change the theme. The most effective way to do this is to start with the basic Prestashop 1.7 theme and then modify it if you want to keep the original design.
Prestashop integrator, , Prestashop project quote, , Create Prestashop online store, , Prestashop consultant, , Prestashop Webmaster

The know-how

+

19 Certificates !

+

+15 years of experience

+

What is the solution to the Prestashop migration error the product thumbnails are no longer displayed ?

Before you jump into the concrete implementation of your solutions, here is a checklist that could save you some time. These few questions helped me: 1. Are the thumbnails of your products visible in the back-office? When you connect to the file, you verify that the images you created appear. 2. Are the CMS images displayed correctly in the front office? Image management for products and the CMS are not managed exactly the same way on Prestashop. For CMS images, there is no URL change. Images are saved in the /img/cms directory. 3. Do you have the SSL connections correctly configured? If the answer is "yes" to these three points, here's how you could do it. Have you taken your tests but still haven't found anything? Here is what you can do: Accomplish: Clean prestashop cache. This is the very first step to take. This is the very first step to take. The cache of Prestashop is very powerful and to ensure that there are no residues, you must put the store in maintenance and not work with the cache. In the back office, go to Advanced Settings > Performance. Cache should be set to "no" + save and clear cache. Refresh the Front Office of the store. Do you see an improvement? Refresh the images. Depending on what you've done to your store, such as a template migration or update... You may need to create the images again. This is a process that requires server resources. The best advice is to keep the server in maintenance mode. In the desktop, go to Appearance > Pictures. At the end of the page, you can select the images at the bottom of the page. Depending on the size of your business, it may be advantageous to work in stages. Reset the Htacces file. Product thumbnail urls are managed by the url-rewriting mechanism. If you change domain or server, it may not work anymore. Re-create your htaccess file
Prestashop Specialist, , Prestashop expert, , Referencing Prestashop site on Google, , Prestashop SEO Agency, , Freelancer Prestashop

The answer in detail: correction problem migration Prestashop passwords no longer work

Locate the configuration file needed to make it work. You have successfully transferred the Prestashop 1.6 store to the 1.7 version, and that is why you are importing the databases (manually because the tables do not have identical fields!) on your new Prestashop 1.7 installation. Everything seems to work Except the passwords which are not recognized. Do not worry, it's normal. The coded "key" changes with each installation. You must therefore find your old key to add it to your Prestashop 1.7. On your 1.6 installation, find the file config/settings.inc.php Copy the line that contains: define('_COOKIE_KEY_', 'xxx'); On version 1.7, the location of the configuration file has changed, these parameters are in the app/config/parameters.php file that you open, to replace the line. Clean the cache. Your passwords from the past work! You will be able to take full advantage of the advantages of the Prestashop store! If your problem is not solved, do not hesitate to contact our agency.
Prestashop 1.7 bug, , Prestashop Fatal Error, , Prestashop product image not showing, , Prestashop blank page, , Facebook Prestashop conversion pixel

Other benefits at WEB2007:

Best report
price quality

Fast intervention !
(subject to availability)

Available evenings and weekends
(except holidays and vacations)