DraganK Posted January 13, 2021 Share Posted January 13, 2021 (edited) Hello! I'm just start to prepare my first Prestashop e-shop, and this upgrade is my first Prestashop upgrade. It's 1.7.7.0 instalation from scratch. No modification. Classic Theme, for the moment... I'm using CentOS 7 with MariaDB 5.5.68 and PHP 7.3.26 After upgrade (with "1-click-upgrade" module ) from 1.7.7.0 to 1.7.7.1, I have recevied following error: [INTERNAL] /var/www/vhosts/bal****.com/httpdocs/vendor/composer/autoload_real.php line 25 - require(): Failed opening required '/var/www/vhosts/bal****.com/httpdocs/vendor/composer/platform_check.php' (include_path='.:/opt/plesk/php/7.3/share/pear') And after Rollback to 1.7.7.0. , I have received sql error for following sql line: CREATE TABLE `ps_access` ( `id_profile` int(10) unsigned NOT NULL, `id_authorization_role` int(10) unsigned NOT NULL, PRIMARY KEY (`id_profile`,`id_authorization_role`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 - Table 'ps_access' already exists And after sql error, I have received another error: [INTERNAL] /var/www/vhosts/bal****.com/httpdocs/config/config.inc.php line 122 - Error: Call to a member function getName() on null #0 /var/www/vhosts/bal****.com/httpdocs/modules/autoupgrade/classes/UpgradeContainer.php(550): require_once() #1 /var/www/vhosts/bal****.com/httpdocs/modules/autoupgrade/classes/TaskRunner/AbstractTask.php(120): PrestaShop\Module\AutoUpgrade\UpgradeContainer->initPrestaShopCore() #2 /var/www/vhosts/bal****.com/httpdocs/admin030c07uzv/autoupgrade/ajax-upgradetab.php(52): PrestaShop\Module\AutoUpgrade\TaskRunner\AbstractTask->init() #3 {main} Any idea how to solve the problem? Recover server backup? And after that, how to upgrade? Also, I'm little scared... If Prestashop has this kind of problem for minor upgrade, what will happened with next minor or major upgrade after I put the web on production mode? Best regards Edited January 13, 2021 by DraganK (see edit history) Link to comment Share on other sites More sharing options...
DraganK Posted January 13, 2021 Author Share Posted January 13, 2021 I did recovery of whole server I have tried one more time to do upgrade And result is, more or less, the same First error is the same as the first time Second error is different than first time!!!! Here is the screenshots of upgrade.... And here is the screenshot after ther Rollback: Link to comment Share on other sites More sharing options...
Ortez Posted January 14, 2021 Share Posted January 14, 2021 Same problem here. I think this is a problem related to the wrong PHP settings on the dedicated server on plesk. Link to comment Share on other sites More sharing options...
DraganK Posted January 14, 2021 Author Share Posted January 14, 2021 Hi Ortez! Any idea what PHP setting(s)? Link to comment Share on other sites More sharing options...
Ortez Posted February 10, 2021 Share Posted February 10, 2021 No sorry, i cant find any solution for that problem. Link to comment Share on other sites More sharing options...
musicmaster Posted February 10, 2021 Share Posted February 10, 2021 Prestashop upgrades are tricky. They have been so for a long time. So the general advice is not to upgrade unless you see a new feature that you want or a bug fix that concerns something you care about. Link to comment Share on other sites More sharing options...
DraganK Posted February 14, 2021 Author Share Posted February 14, 2021 Thank you so much both of you! @Ortez I find out that turning off all type of cache can help sometimes... Yesterday, I found out that, problem appears also if you want to translate something. Then I discovery that before save a translation, problem disappeared if I clean web browser cache and “CLEAN CACHE” on Configuration / Advance Parameter / Performance. After that, it accepts to save a translation. Try by yourself and let me know if it works for you! Link to comment Share on other sites More sharing options...
ssekazinga Posted March 7, 2021 Share Posted March 7, 2021 I had the same issue when i was upgrading to 1.772 when it failed. Go to /public_html/vendor/composer/autoload_real.php and comment out //require __DIR__ . '/platform_check.php'; on line 25 AM not what the platform_check is used - site looks to be working fine Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now