
                    For ecommerce-framework, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Hi @photinia73 @StraitsKapitan
Do not rename the column active Status: Tech investigation still need to be done
I have encountered an issue with the upgrade of Prestashop 1.7.7 from both 1.7.6.9 and from 1.7.6.5
I have upgraded two of my shops

PrestaShop The left menu in BO disappeared after upgrade to 1.7.7.0

Hi @TedEriksson
Checking out the diff for 1.7.6 in the payment module I use (mobilpay) 

PrestaShop 500 error: Kernel Container is not available

The following fixed it for me:

shutdown artisan
cd storage/app/
unlink public
startup artisan

When running php artisan storage:link 

bagisto Impossible to create the root directory "".

As discussed today we're going to enable PS to work php7.3 on develop (milestone 1.7.7) branch 

PrestaShop PrestaShop must be compatible with PHP 7.3

I did not check all the tables but I compared where the new system use null or not So this is not the full list 

PrestaShop Error on display details of order OrderCustomerForViewing (... must be of the type string null given ...) GetOrderForViewingHandler

Hi @khouloudbelguith  I recommend this issue be re-opened Google Search Console rightly complains about all product listing pages that in some way incorporate themes/classic/templates/catalog/_partials/miniatures/product.tpl

PrestaShop classic theme template catalog/_partials/miniatures/product.tpl incorrectly specifies schema.org/Product

This issue is not resolved with the PR #15906  Please reopen Currently the installation fails on Windows I tested latest .zip release cloned source from git 

PrestaShop Template \account.html.twig is not defined   (it's a bug ?)

OK I think I have the reason right here: angular/angular#41193 (comment)

Packages must be compiled and ran using the exact same version of Angular; any other combination is not supported and likely to break in subtle ways