After updating the module to the latest version v5.0.2, the following error appears. How to solve this problem? Regards

PrestaShop\Module\AutoUpgrade\UpgradeSelfCheck::__construct(): Argument #2 ($prestashopConfiguration) must be of type PrestaShop\Module\AutoUpgrade\PrestashopConfiguration, string given, called in /.../modules/autoupgrade/AdminSelfUpgrade.php on line 497

[TypeError 0]

Prestashop version : 8.2.1
PHP 8.3.30

I would like to update to prestashop 8.2.4.
I have downloaded :

• prestashop_8.2.4.xml
• prestashop_8.2.4.zip

from https://github.com/PrestaShop/PrestaShop/releases/tag/8.2.4

I have put these two files in /var/www/prestashop/adminxxxxxxx/autoupgrade/download/
I have installed module Update Assistant v7.5.1 - by PrestaShop.

When I use it to do the upgrade : I have the following errors

1. It is not possible to write in the following folders. Give write access to the user running PHP with the appropriate authorizations and permissions : /var/cache
2. Your current PHP version is not compatible with PrestaShop 8.2.4. (attended : 7.2.5 - 8.1 | current : 8.3.30)

For #1 here are the permissions on /var/www/prestashop/cache
drwxr-xr-x 8 prestashop prestashop 4096 24 févr. 22:16 cache

What about these errors ?

Best regards

 After a failed update to version 1.7.6.1, I reinstalled the files I had previously backed up.

I now have this message:

 (1/1) FatalErrorException

Compile Error: Symfony\Component\Debug\DebugClassLoader::loadClass(): Failed opening required '/home/brth4338/public_html/vendor/composer/../symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php' (include_path='/home/brth4338/public_html/vendor/pear/pear_exception:/home/brth4338/public_html/vendor/pear/console_getopt:/home/brth4338/public_html/vendor/pear/pear-core-minimal/src:/home/brth4338/public_html/vendor/pear/archive_tar:.:/opt/alt/php71/usr/share/pear')

in DebugClassLoader.php line 156 

Can you help me? 

How can I fix this?

Fatal error: Uncaught PrestaShop\PrestaShop\Core\Exception\ContainerNotFoundException: Kernel Container is not available in /home/silvesyx/test.silvestricamerashop.it/silvesyx/src/Adapter/ContainerFinder.php:77 Stack trace: #0 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/module/Module.php(1702): PrestaShop\PrestaShop\Adapter\ContainerFinder->getContainer() #1 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/module/Module.php(1691): ModuleCore::getModuleRepository() #2 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/Hook.php(884): ModuleCore::getNativeModuleList() #3 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/Dispatcher.php(606): HookCore::exec('moduleRoutes', Array, NULL, true, false) #4 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/Dispatcher.php(243): DispatcherCore->loadRoutes() #5 /home/silvesyx/test.silvestricamerashop.it/silvesyx/classes/Dispatcher.php(201): DispatcherCore->__construct(Object(Symfony\Component\HttpFoundation\Request)) #6 /home/silvesyx/test.silvestricamerashop.it/silvesyx/index.php(28): DispatcherCore::getInstance() #7 {main} thrown in /home/silvesyx/test.silvestricamerashop.it/silvesyx/src/Adapter/ContainerFinder.php on line 77

Overraid desabled, cache cleared from BO, manually and on Chrome.

Any suggestion, please?

after cleaning up the cache, removing ps_mbo etc. I am still stuck getting the following error during the upgrade step 4:

[...] Declaration of PrestaShop\Module\PsEditionBasic\Controller\AdminPsEditionBasicController::get($serviceName) must be compatible with PrestaShopBundle\Controller\Admin\FrameworkBundleAdminController::get(string $id): object

I checked and found a suggestion to edit /modules/ps_edition_basic/src/Controller/AdminPsEditionBasicController.php

from: public function get($serviceName)

to: public function get(string $serviceName): object

I see how that might work around the crash - but is that a good idea? I'd rather find the root cause. Any suggestions what might cause the crash?

Thanks in advance!

BJF

I've tried a great number of times to upgrade from 8.2.1 to 9 and it never fully works. First main issues were during the upgrade process itself it was failing half way through and ending in an error 500, but always related to a module from the theme I'm using. So I updated the theme to an apparent version 9 compatible version, but that made no difference.

I then removed the theme totally and every module associated with it, the upgrade then for the first time completed, but now in the admin if I click on the Module tab and Module Manager I just get a blank white page, so there's still something wrong.

Why is it so difficult to ever upgrade this software without some major issues?

I have updated Prestashop from 8 to 9, everything is working fine, the site looks good, but when you access the administrator (backend) it shows an error.

An exception has been thrown during the rendering of a template ("PrestaShop\PrestaShop\Core\Context\CurrencyContext::__construct(): Argument #9 ($precision) must be of type int, string given, called in /public_html/src/Core/Context/CurrencyContextBuilder.php on line 62").

TypeError 

PrestaShop\PrestaShop\Core\Context\CurrencyContext::__construct(): Argument #9 ($precision) must be of type int, string given, called in /public_html/src/Core/Context/CurrencyContextBuilder.php on line 62  

Anyone who can guide me to find the solution? 

Thank you

PHP: 8.1 to 8.4
PS: 9.0.1

I am using PHP 8.4 and v7.4.3 of the upgrade assistant. I have tried this with 3rd party modules and overrides enabled and disabled,

The file and database updates completed correctly, but I get this error when trying to install assets.

INFO - CoreUpgrader - Database update OK
[2025-10-21 12:35:03] INFO - CoreUpgrader - Installing assets
[2025-10-21 12:35:03] CRITICAL - ErrorHandler - /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/UpgradeTools/CoreConsoleExecutable.php line 74 - Symfony\Component\ErrorHandler\Error\UndefinedFunctionError: Attempted to call function "exec" from namespace "PrestaShop\Module\AutoUpgrade\UpgradeTools".
#0 /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/UpgradeTools/CoreConsoleExecutable.php(45): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreConsoleExecutable->getBaseCommand()
#1 /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(890): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreConsoleExecutable->callCommand('assets:install ...')
#2 /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(124): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->installAssets()
#3 /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/Task/Update/UpdateDatabase.php(73): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->finalizeCoreUpdate()
#4 /home/sites/testsites/domains/testnv/modules/autoupgrade/classes/Task/Runner/ChainedTasks.php(66): PrestaShop\Module\AutoUpgrade\Task\Update\UpdateDatabase->run()
#5 /home/sites/testsites/domains/testnv/**admin_folder**/autoupgrade/ajax-upgradetab.php(58): PrestaShop\Module\AutoUpgrade\Task\Runner\ChainedTasks->run()
#6 {main}

If I refresh the screen or reopen the update assistant, the screen tells me that v9.0.1 has been installed correctly.

Any ideas?

I'm currently on 1.7.6.5 with Warehouse Theme and some customization and wondering how much effort/cost it would be to upgrade to a later standard and which to chose?

//Hans

i try upgrade the version 8.2.3 to 9.0.1-1.0 and give error 500 

any solution?

best regards

Jorge

I'm trying to apply the v9 update since it's published without any success. The autoupdater does not works at all, it hang for ever at the requirement check.

That's something I've seen since we started to use Prestashop, so in the past I've just downloaded the upgrade archive and XML from Github to apply it.

But I cannot find them for v9, where are they?

We migrated from Prestashop 1.3 to Prestashop 8.

We discovered that we cannot manage the add or edit of categories to products.

What we saw is that in the 1.3 database, category 1 is (HOME) and (root).

In the Prestashop 8 database, category 2 is (HOME) and (root).

In the database of 8 after the migrate, category 1 is (root) and category 2 is (HOME)

Also, category 1 has id_parent (582), a category created during migration that did not exist in 1.3 and is not processed in the Prestashop back end (The object cannot be loaded (or found).

First of all, I would like to ask if it is possible to migrate from Prestashop 1.3 to 8 and if there is a solution to the above problem.

Thank you.

Main reason for upgrade is spam problem

* Upgrade PS version

* check that modules are working properly

* check that template is working propely

Any ideas on hot to fix this or what module is actually not found. Debug mode shows nothing

Below is the log when I submit the login form:

request.CRITICAL: Uncaught PHP Exception Doctrine\ORM\NonUniqueResultException: "More than one result was found for query although one row or none was expected." at AbstractQuery.php line 973 

The error was as follows:

The solution was to delete old, additional records for my user from the table ps_employee.

I hope this helps someone else!

By default the database structure and field definitions of the new shop are used. However, the are options to copy (part of) the structure of the old shop. 

You can use Copy_shopdata for fixing broken shops and for upgrading. It will adapt the data to the requirements of the new version. The minimum version of the old shop is 1.5.0.10.

Copy_shopdata should be installed in the same directory as Prestools as it uses Prestools for authorization. It should be installed in the new shop, after which you fill in the database credentials of the old shop in copy_shopsdata's config file.

With the added file copy_shopdata_imghub.php you can copy images from one installation on a server to another. It works even when the files are on a different server.

The added file Copy_shopdata_fix copies all database tables to the database of a new shop of the same version that is on the same server and applies a few fixes. After that you can assign the new database to the shop.

This is mainly meant for shops that used to work but had a bad upgrade. It can be applied very quickly.

Documentation is in the pdf files.

PS. Nearly any shop can be repaired and/or updated this way. If you are afraid to do it yourself you can hire me to do it for you.

PS-2: For upgrading older Prestashop versions up to version 1.6.1.24 you can also try UpgradeHub. That offers an interactive way of executing the Prestashop upgrade process that offers you a way to see and correct the error messages.

You can download from the Prestools website:

/xxxx/httpdocs/modules/autoupgrade/classes/Task/Update/UpdateFiles.php line 166 - is_file(): open_basedir restriction in effect. File(/phpstan-disallowed-calls.neon) is not within the allowed path(s): (xxxxx/:/tmp/:/usr/share/php/:/var/www/vhosts/system/xxxxxx/opcache/)

Zend OPCACHE is active on the server.

After several errors like this:

/xxxxx/httpdocs/modules/autoupgrade/classes/UpgradeTools/CoreConsoleExecutable.php line 74 - Symfony\Component\ErrorHandler\Error\UndefinedFunctionError: Attempted to call function "exec" from namespace "PrestaShop\Module\AutoUpgrade\UpgradeTools".
#1 /xxxxxx/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(890): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreConsoleExecutable->callCommand('assets:install ...')

Up to six errors like this.

I restored the backup and waited a few days.

Today I noticed some module updates:
Update Assistant v7.4.1 to v7.4.2
PrestaShop Checkout v9.5.0.4 to v9.5.0.5
PrestaShop Marketplace in your Back Office v5.1.0 to v5.2.0

I mean, now it's mine. I'll try again...

Same result. Unable to update. After consulting with the hosting service, they say everything is fine. It doesn't seem like a server issue. Although a 500 error (server) also appears in the Update Assistant error report.

i faced this problem after upgrading from 8 to 9 , please see attached screenshot

/var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/dependency-injection/Compiler/DecoratorServicePass.php line 91 - Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "ets_seo.form.type.seo_type" has a dependency on a non-existent service "form.type.sell.product.seo.seo_type". #0 /var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/dependency-injection/Compiler/Compiler.php(80): Symfony\Component\DependencyInjection\Compiler\DecoratorServicePass->process(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #1 /var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/dependency-injection/ContainerBuilder.php(767): Symfony\Component\DependencyInjection\Compiler\Compiler->compile(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #2 /var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/http-kernel/Kernel.php(507): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #3 /var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/http-kernel/Kernel.php(772): Symfony\Component\HttpKernel\Kernel->initializeContainer() #4 /var/www/fastuser/data/www/smokerschoice.ru/vendor/symfony/http-kernel/Kernel.php(126): Symfony\Component\HttpKernel\Kernel->preBoot() #5 /var/www/fastuser/data/www/smokerschoice.ru/app/AppKernel.php(96): Symfony\Component\HttpKernel\Kernel->boot() #6 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(61): AppKernel->boot() #7 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(39): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initKernel() #8 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(110): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #9 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/Task/Update/UpdateDatabase.php(142): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->setupUpdateEnvironment() #10 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/Task/Update/UpdateDatabase.php(49): PrestaShop\Module\AutoUpgrade\Task\Update\UpdateDatabase->warmUp() #11 /var/www/fastuser/data/www/smokerschoice.ru/modules/autoupgrade/classes/Task/Runner/ChainedTasks.php(66): PrestaShop\Module\AutoUpgrade\Task\Update\UpdateDatabase->run() #12 /var/www/fastuser/data/www/smokerschoice.ru/**admin_folder**/autoupgrade/ajax-upgradetab.php(58): PrestaShop\Module\AutoUpgrade\Task\Runner\ChainedTasks->run() #13 {main}

Tried:
Uninstalled/installed theme modules
Deleted var/cache prod and dev
Cleared cache
Manually copied theme overrides to correct Presta overrides directories.
Only theme modules enabled
Only theme and Presta core modules enabled
Switched to Classic theme - still the same

Frontend only shows header and footer with modules enabled on them stacked together with no content in-between. If I use the search, the results are loaded and looks correct but a 500 error is thrown when any product is clicked:

Notice: Trying to get property 'id_category_default' of non-object in /var/www/html/......./controllers/front/ProductController.php on line 1344

Notice: Trying to get property 'name' of non-object in /var/www/html/......./controllers/front/ProductController.php on line 1364

[PrestaShopException]

Invalid product vars
at line 173 in file classes/Link.php
 

Backoffice works OK but the theme's overrides module can only be enabled via uninstall/install otherwise Presta throws:

The override file /var/www/html/......./modules/stoverride/override/controllers/front/AuthController.php conflicts with an existing override in /var/www/html/......./override/controllers/front/AuthController.php.

The override file /var/www/html/......./modules/stoverride/override/classes/controller/FrontController.php conflicts with an existing override in /var/www/html/......./override/classes/controller/FrontController.php.

The override file /var/www/html/......./modules/stoverride/override/classes/ProductAssembler.php conflicts with an existing override in /var/www/html/......./override/classes/ProductAssembler.php.

The upgrade to 8.2 works and frontend works like it should when the overrides and modules options is disabled during the Upgrade Assistant wizard using an old backup.

Database is on its own server but wasn’t backed up again before the upgrade.

The server with Prestashop www files was backed up prior to the upgrade.

Absolute cannot afford to recover using the old database backup.

This seems like a Presta config issue handling the modules during the upgrade.

Please help!

So in prestashop 1.7.4.2 under the SMTP configuration the store is unable to send test email to any address that is not from a domain of the store. If I try to send the 'test email' to an email addres with a domain that store is set up on (or the same that is in the SMTP configuration) then it goes - there is an success message and in my inbox there is a new e-mail.

But any other domain, like gmail, gmx etc. is not working. Prestashop claims "Check your configuration". I know some servers are configured to not send emails to other domains. But mine is not. I know this, as I have prestashop 1.7.3.2 installed on the same server, with the same settings (the same SMTP settings) and it can send all the emails.

So the problem is that the store can not: send password reset email, order status change email, test email... I'v seen some people saying it is an translation error. But how can it be translation error if the testing e-mail is sent in english to my store domain, and can not be sent to my gmail? This is clearly prestashop bug, but how can I fix it?

edit: not sure if this matters but the store that doesn't work is on subdomain, the store that it works on is on domain. Server provider claims it's no difference for the server. So it has to be prestashop bug.

Fatal error: Uncaught Error: Call to undefined method Tools::displayPrice() in /home/testsites/testnewversion/modules/opayo/opayo.php:519 Stack trace: #0 /home/testsites/testnewversion/classes/Hook.php(1251): Opayo->hookPaymentReturn(Array) #1 /home/testsites/testnewversion/classes/Hook.php(462): HookCore::coreCallHook(Object(Opayo), 'hookPaymentRetu...', Array) #2 /home/testsites/testnewversion/classes/Hook.php(1143): HookCore::callHookOn(Object(Opayo), 'paymentReturn', Array) #3 /home/testsites/testnewversion/controllers/front/OrderConfirmationController.php(255): HookCore::exec('displayPaymentR...', Array, 130) #4 /home/testsites/testnewversion/controllers/front/OrderConfirmationController.php(232): OrderConfirmationControllerCore->displayPaymentReturn(Object(Order)) #5 /home/testsites/testnewversion/classes/controller/Controller.php(330): OrderConfirmationControllerCore->initContent() #6 /home/testsites/testnewversion/classes/Dispatcher.php(487): ControllerCore->run() #7 /home/testsites/testnewversion/index.php(78): DispatcherCore->dispatch() #8 {main} thrown in /home/testsites/testnewversion/modules/opayo/opayo.php on line 519

The order is processed, the payment is taken and order confirmation emails are sent. THe probelm is just in the display of this page.

I can't find where I bought this module from. The module is 'Opayo (Formerly Sagepay) v4.0.0 - by Nethues Technology Pvt Ltd'

The problem code is:

 if ($this->ps_below_7) {
            $total_to_pay = Tools::displayPrice($params['total_to_pay'], $params['currencyObj'], false);
            $order = $params['objOrder'];
        } else {
            $total_to_pay = Tools::displayPrice(
                $params['order']->getOrdersTotalPaid(),
                new Currency($params['order']->id_currency),
                false
            );
            $order = $params['order'];
        }

Tools::displayPrice() has been deprecated in v9.0

Is there a simple workaround to this?

The following error is displayed when a payment returns to the order confirmation page. This happens regardless of my payment method, whether it is Opayo, PayPal or Bank Transfer.

The order appears in the Prestashop back office and a payment is taken by the PSP. The order confirmation emails are also produced.

Any ideas what I need to do for this page to display correctly?

Fatal error: Uncaught PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'action' in 'INSERT INTO' in /public_html/classes/db/DbPDO.php:149 Stack trace: #0 /public_html/classes/db/DbPDO.php(149): PDO->query('INSERT INTO `ps...') #1 /public_html/classes/db/Db.php(381): DbPDOCore->_query('INSERT INTO `ps...') #2 /public_html/modules/ps_eventbus/src/Repository/IncrementalSyncRepository.php(98): DbCore->query('INSERT INTO `ps...') #3 /public_html/modules/ps_eventbus/src/Service/SynchronizationService.php(340): PrestaShop\Module\PsEventbus\Repository\IncrementalSyncRepository->insertIncrementalObject(Array) #4 /public_html/modules/ps_eventbus/src/Traits/Hooks/UseOrderHooks.php(53): PrestaShop\Module\PsEventbus\Service\SynchronizationService->insertContentIntoIncremental(Array, 'upsert', '2025-09-08T12:5...', 1, false) #5 /public_html/classes/Hook.php(1251): Ps_eventbus->hookActionObjectOrderAddAfter(Array) #6 /public_html/classes/Hook.php(462): HookCore::coreCallHook(Object(Ps_eventbus), 'hookActionObjec...', Array) #7 /public_html/classes/Hook.php(1142): HookCore::callHookOn(Object(Ps_eventbus), 'actionObjectOrd...', Array) #8 /public_html/classes/ObjectModel.php(595): HookCore::exec('actionObjectOrd...', Array) #9 /public_html/classes/order/Order.php(327): ObjectModelCore->add(true, true) #10 /public_html/classes/PaymentModule.php(1077): OrderCore->add() #11 /public_html/classes/PaymentModule.php(351): PaymentModuleCore->createOrderFromCart(Object(Cart), Object(Currency), Array, 494, Object(Context), 'QFJDOKITQ', '59fc1b5aca43464...', 'Opayo (Formerly...', 'opayo', false, 109.99, 0, 109.99, false, Object(OrderState), 2, 73) #12 /public_html/modules/opayo/controllers/front/validation.php(82): PaymentModuleCore->validateOrder(24206, 2, 109.99, 'Opayo (Formerly...', NULL, Array, NULL, false, '59fc1b5aca43464...') #13 /public_html/classes/controller/Controller.php(319): OpayoValidationModuleFrontController->postProcess() #14 /public_html/classes/Dispatcher.php(487): ControllerCore->run() #15 /public_html/index.php(78): DispatcherCore->dispatch() #16 {main} Next PrestaShopException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'action' in 'INSERT INTO' in /public_html/classes/db/DbPDO.php:151 Stack trace: #0 /public_html/classes/db/Db.php(381): DbPDOCore->_query('INSERT INTO `ps...') #1 /public_html/modules/ps_eventbus/src/Repository/IncrementalSyncRepository.php(98): DbCore->query('INSERT INTO `ps...') #2 /public_html/modules/ps_eventbus/src/Service/SynchronizationService.php(340): PrestaShop\Module\PsEventbus\Repository\IncrementalSyncRepository->insertIncrementalObject(Array) #3 /public_html/modules/ps_eventbus/src/Traits/Hooks/UseOrderHooks.php(53): PrestaShop\Module\PsEventbus\Service\SynchronizationService->insertContentIntoIncremental(Array, 'upsert', '2025-09-08T12:5...', 1, false) #4 /public_html/classes/Hook.php(1251): Ps_eventbus->hookActionObjectOrderAddAfter(Array) #5 /public_html/classes/Hook.php(462): HookCore::coreCallHook(Object(Ps_eventbus), 'hookActionObjec...', Array) #6 /public_html/classes/Hook.php(1142): HookCore::callHookOn(Object(Ps_eventbus), 'actionObjectOrd...', Array) #7 /public_html/classes/ObjectModel.php(595): HookCore::exec('actionObjectOrd...', Array) #8 /public_html/classes/order/Order.php(327): ObjectModelCore->add(true, true) #9 /public_html/classes/PaymentModule.php(1077): OrderCore->add() #10 /public_html/classes/PaymentModule.php(351): PaymentModuleCore->createOrderFromCart(Object(Cart), Object(Currency), Array, 494, Object(Context), 'QFJDOKITQ', '59fc1b5aca43464...', 'Opayo (Formerly...', 'opayo', false, 109.99, 0, 109.99, false, Object(OrderState), 2, 73) #11 /public_html/modules/opayo/controllers/front/validation.php(82): PaymentModuleCore->validateOrder(24206, 2, 109.99, 'Opayo (Formerly...', NULL, Array, NULL, false, '59fc1b5aca43464...') #12 /public_html/classes/controller/Controller.php(319): OpayoValidationModuleFrontController->postProcess() #13 /public_html/classes/Dispatcher.php(487): ControllerCore->run() #14 /public_html/index.php(78): DispatcherCore->dispatch() #15 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'action' in 'INSERT INTO' in /public_html/classes/Hook.php:484 Stack trace: #0 /public_html/classes/Hook.php(1142): HookCore::callHookOn(Object(Ps_eventbus), 'actionObjectOrd...', Array) #1 /public_html/classes/ObjectModel.php(595): HookCore::exec('actionObjectOrd...', Array) #2 /public_html/classes/order/Order.php(327): ObjectModelCore->add(true, true) #3 /public_html/classes/PaymentModule.php(1077): OrderCore->add() #4 /public_html/classes/PaymentModule.php(351): PaymentModuleCore->createOrderFromCart(Object(Cart), Object(Currency), Array, 494, Object(Context), 'QFJDOKITQ', '59fc1b5aca43464...', 'Opayo (Formerly...', 'opayo', false, 109.99, 0, 109.99, false, Object(OrderState), 2, 73) #5 /public_html/modules/opayo/controllers/front/validation.php(82): PaymentModuleCore->validateOrder(24206, 2, 109.99, 'Opayo (Formerly...', NULL, Array, NULL, false, '59fc1b5aca43464...') #6 /public_html/classes/controller/Controller.php(319): OpayoValidationModuleFrontController->postProcess() #7 /public_html/classes/Dispatcher.php(487): ControllerCore->run() #8 /public_html/index.php(78): DispatcherCore->dispatch() #9 {main} thrown in /public_html/classes/Hook.php on line 484

The back office product page displays the following error, but it doesn't seem to affect the functionality of the page

Loading...
Failed to load plugin url: https://domain.com/js/tiny_mce/langs/gb.js
×Failed to load plugin url: https://domain.com/js/tiny_mce/langs/gb.js
Failed to load plugin url: https://domain.com/js/tiny_mce/langs/gb.js

Any ideas what this is?

Our update failed after upgrading files and before updating the database and modules.  We ran a test update on our test site which ran smoothly, but when attempting our live site we got the following:

2025-09-04 13:28:13] INFO - UpdateFiles - All files updated. Now updating database...
[2025-09-04 13:28:14] INFO - UpdateDatabase - Cleaning file cache
[2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory "/app/cache/" does not exist and cannot be emptied.
[2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/cache/ emptied
[2025-09-04 13:28:14] DEBUG - CacheCleaner - Directory /home2/xxxxxxx/public_html/cache/smarty/compile/ emptied
[2025-09-04 13:28:14] CRITICAL - ErrorHandler - /home2/xxxxxxx/public_html/modules/autoupgrade/vendor/symfony/filesystem/Filesystem.php line 180 - Symfony\Component\Filesystem\Exception\IOException: Failed to remove directory "/home2/xxxxxx/public_html/var/cache/prod": rmdir(/home2/xxxxxxx/public_html/var/cache/prod): Directory not empty

Now.. we removed the cache manually and our shop seems fine... updated to 8.2.3 when we log into our back office and everything in the front office seems to work as well.

Our question is should we be concerned that the database didn't seem to be updated?  Is there a way we can run just the database update scripts?  It won't allow us to re-apply the 8.2.3 upgrade and we didn't make a backup since the test site upgrade went smoothly and it was just a minor version.   We're not concerned about the modules as we always kept them up to date anyway.  

Also... why did this fail?  Lol

my module "Update assistant" (version 7.3.0) does not show any possibility to upgrade to PS 8.2.2.

I can only upgrade to PS 9 (which I won't until 1. the modules that we use are upgraded to PS 9 compatibility 2. the errors I get when trying PS 9 on local server can be solved)

Some people say we have to wait an update of "Update assistant" module. But some websites show that they already can upgrade to PS 8.2.2 using "Update assistant". For instance Upgrade to PS 8.2.2 (the pictures show 8.2.2 available)

Did someone manage to get PS 8.2.2 and how?

Do we need to go back to old times of manual updates through file copies, etc.????

Thank you!

My config

PS 8.2.1

PHP 8.1

What I found is that in 1.7.60 there is no PEAR.php file in the classes folder, there is only a PEAR.php file in the vendor/pear folder

So how do one fix this?

Error!
Exception thrown by module psaddonsconnect on upgrade. Warning: include_once(/var/www/vhosts/4x4direct.co.za/httpdocs/classes/../tools/pear/PEAR.php): failed to open stream: No such file or directory

I'm trying to install version 9.0 of prestashop starting from 8.2.1 but I'm encountering many difficulties. 

All the files are downloaded but before the database update starts it stops and gives me errors on a series of plugins even if they are deactivated.

Then if I empty the modules folder and the execution continues and also updates the database and ends the installation.

But then when I try to go into the backoffice I get a whole bunch of errors.

Disabling the extra modules. Uninstalling all other modules than standard.

Uninstalling the extra modules did work to update to 9.0, but then the new errors start again.

Compile Error:
 

FatalError

HTTP 500 Internal Server Error

Compile Error: Declaration of Ups::get($serviceName) must be compatible with ModuleCore::get(string $serviceName): ?object


in modules/ups/ups.php (line 847)

/**

* Override of native function to always retrieve Symfony container instead of legacy admin container on legacy context.

*

* {@inheritdoc}

*/

public function get($serviceName)

{

if (null === $this->container) {

$this->container = SymfonyContainer::getInstance();

}

So I believe this happened with my UPS module.

That is why I uninstalled this module before updating.

But after the update worked, the Module Manager, and other pages in the Back Office didn't work anymore.

That's where I got the Compile error.

The only thing I didn't do, was delete the folders of the modules after uninstallation.

Maybe that's the last thing I can try when updating.

But the stupid thing is that I already tried it now 8 times already.

Is there a difference in Updating through Update Assistant or updating through DirectAdmin?

Before uninstalling the module, I disabled the module. Then I got some error logs that I added below.

2025-07-08-120350-update.txt 2025-07-08-131255-update.txt

after updating Prestashop from 8.0.4 to 8.1 with 1-click update, backoffice is still "old".

How do I update the look of the backoffice also?

Update with 1-click went well. No errors. All good. Except backoffice is still looking as it was before.

EDIT: After doing some investigation I noticed that in my test store with new look, this line is included in <head>

<link href="https://unpkg.com/@prestashopcorp/edition-reskin@latest/dist/back.min.css" rel="stylesheet" type="text/css"/>

This seems to do the job. But where do I put it, in which source file of the store, that still has old look? Any ideas?

EDIT 2: After more digging I managed to figure this out. I was missing module called "ps_edition_basic". I copied it from the test store to the live store, activated it and now backend is "new".

Symfony\Component\Debug\Exception\ContextErrorException:
Notice: Array to string conversion

  at vendor/symfony/symfony/src/Symfony/Component/Form/ChoiceList/ArrayChoiceList.php:73
  at Symfony\Component\Form\ChoiceList\ArrayChoiceList->Symfony\Component\Form\ChoiceList\{closure}(array(false))
  at call_user_func(object(Closure), array(false))
     (vendor/symfony/symfony/src/Symfony/Component/Form/ChoiceList/ArrayChoiceList.php:158)
  at Symfony\Component\Form\ChoiceList\ArrayChoiceList->getValuesForChoices(array(array(false)))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Extension/Core/DataTransformer/ChoiceToValueTransformer.php:32)
  at Symfony\Component\Form\Extension\Core\DataTransformer\ChoiceToValueTransformer->transform(array(false))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Form.php:1100)
  at Symfony\Component\Form\Form->normToView(array(false))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Form.php:352)
  at Symfony\Component\Form\Form->setData(array(false))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Extension/Core/DataMapper/PropertyPathMapper.php:49)
  at Symfony\Component\Form\Extension\Core\DataMapper\PropertyPathMapper->mapDataToForms(array('enable_shop' => array(false), 'maintenance_ip' => array(''), 'maintenance_text' => 'We are currently updating our shop and will be back really soon.<br>Thanks for your patience.'), object(RecursiveIteratorIterator))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Form.php:379)
  at Symfony\Component\Form\Form->setData(array('enable_shop' => array(false), 'maintenance_ip' => array(''), 'maintenance_text' => 'We are currently updating our shop and will be back really soon.<br>Thanks for your patience.'))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Extension/Core/DataMapper/PropertyPathMapper.php:49)
  at Symfony\Component\Form\Extension\Core\DataMapper\PropertyPathMapper->mapDataToForms(array('general' => array('enable_shop' => array(false), 'maintenance_ip' => array(''), 'maintenance_text' => 'We are currently updating our shop and will be back really soon.<br>Thanks for your patience.')), object(RecursiveIteratorIterator))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Form.php:379)
  at Symfony\Component\Form\Form->setData(array('general' => array('enable_shop' => array(false), 'maintenance_ip' => array(''), 'maintenance_text' => 'We are currently updating our shop and will be back really soon.<br>Thanks for your patience.')))
     (vendor/symfony/symfony/src/Symfony/Component/Form/Form.php:483)
  at Symfony\Component\Form\Form->initialize()
     (vendor/symfony/symfony/src/Symfony/Component/Form/FormBuilder.php:226)
  at Symfony\Component\Form\FormBuilder->getForm()
     (src/Core/Form/FormHandler.php:114)
  at PrestaShop\PrestaShop\Core\Form\FormHandler->getForm()
     (src/PrestaShopBundle/Controller/Admin/Configure/ShopParameters/MaintenanceController.php:53)
  at PrestaShopBundle\Controller\Admin\Configure\ShopParameters\MaintenanceController->indexAction(object(Request), null)
  at call_user_func_array(array(object(MaintenanceController), 'indexAction'), array(object(Request), null))
     (var/cache/dev/classes.php:4571)
  at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1)
     (var/cache/dev/classes.php:4526)
  at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, false)
     (vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php:200)
  at Symfony\Component\HttpKernel\Kernel->handle(object(Request), 1, false)
     (admin-1549586535/index.php:88)

(1/1) FatalErrorException

Error: Class PrestaShopBundle\Form\Admin\Extension\ModifyAllShopsExtension contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Symfony\Component\Form\FormTypeExtensionInterface::getExtendedType)

in ModifyAllShopsExtension.php line 49

-----

Please help me solve this problem

I have a Prestashop 8.1.7 instance running in a Kubernetes environnement.

I would like to upgrade to Prestashop 8.2.1.

If I start a Prestashop 8.2.1 against a 8.1.7 database, I will have issues.

Before starting the 8.2.1 instance, can I run a command to update the database schema ?

Does this command update schema for modules ?

Thanks.

David.

I have been using prestashop for a very long time now (ab out 7+ years). However I hardly upgrade the version because 1. I am not a developer, 2 I am afraid something might break and i will have to spend a long time to try to fix the issue.

The result of this is I am still running 1.7.8.4 version. The website works okayish mostly as a user or guest. I used to work fine as admin also and the last time I logged into the admin panel was about 3-4 months back. Today when i tried to login, the login was successful but instead of the dashboard page loading, I only see the prestashop logo and the version number displayed. (screenshot attached).

The website is hosted on Godaddy server and the current PHP version is 7.4 on which the web site is running. This PHP version has upgrade available to 8.1.

Please help...

1. Do I upgrade the PHP version to 8.1?

2. How do i see the admin panel dashboard so that I can use the one-click upgrade for prestashop

I installed 1-Click Upgrade, and when I tried to run the update, I encountered a 500 error and can’t do anything from that point on.

Do you have any idea what might be causing this?

Thank you in advance.

This time i use the newest version of the update plugin with the new design. There are just 2 boxes to check - update your store or rollback. I check update. But the button "get started" just doesnt work. Thats it. I downloaded php page that checks if all requirements met - they do meet the requirements. I dont have much hope in this post or in prestashop in general, but maybe i get lucky? I dont get it, i've worked with a lot of various CMS but i've never met someting such stubborn to upgrade. Its dedicated server, php version - tried every version that 1.7.5 supports. But what can a man do with a broken button and broken hopes...

I don't know how to progress from there, so I did a whole of host backup the other day for safety's sake and have downloaded for safekeeping.

When I go over to Update Assistant, I select the one option available to me 8.2.1 and click through to backup from there. That all progresses for quite a while, then I get a couple of failures- see below. 

I am normally reluctant to progress the upgrade without backup, but perhaps too much is busted...
What does the hive mind think?

I'm kind of stuck. Suggestions and advice appreciated.

Alan

I'm pretty sure I'm not the only one experiencing this issue.

Thank you in advance for any help !

J-M

https://shop.musikundwein.ch/admin123

Unable to generate a URL for the named route "admin_module_catalog" as such route does not exist.

I tried already disabling the non-standard modules by renaming the folders, clearing chache and switching PHP-versions.
I still get the error message.

Please help!

I am testing (on a cloned site) the upgrade from 8.0.2 to 8.2.1 on a hosting server which timed out during the test upgrade of a rather big site.

Upgrade launched in GUI from the backoffice which left a crashed site I had to restore manually.
Now trying if things would be smoother in CLI. I followed instructions from https://devdocs.prestashop-project.org/8/basics/keeping-up-to-date/update/update-from-the-cli/, for the "Update Assistant module" in fact now called autoupgrade ?
Also read the nice post at Feedback from that post

however on my site :

php modules/autoupgrade/cli-upgrade.php --dir=admin123

(with the correct and checked many times name of the actual dir) just says :

"No admin directory provided (dir). Update assistant cannot proceed.

Any idea why ? I'd like to use CLI as I believe it may be more efficient than the graphical BO?

Thanks.

I'm an absolute newbie to PrestaShop.

My website (www.farmyummies.co.za)  was on PrestaShop 1.7.4.0 before with no issues until one day when I couldn't log in with a 504 Gateway timeout error.  Turns out that disabling the Gamification module fixed this error.

I attempted to upgrade to PrestaShop 1.7.4.4 but had issues with 1Click, so my hosting provider wiped everything and installed 1.7.4.4 from scratch.  

Now, everything's there, except that the product images aren't showing, as follows:

I tried to delete one product image on the backend and re-uploading it but it's still not showing.  But I do have all the images in the backend, as follows:

What can I do to fix this without messing with code, etc?

Quite urgent as I have a meeting with the big bosses this afternoon and the site needs to be functional by then ..... ?

Thank you

i get messages like 

The controller HOME is missing or invalid.

The controller AdminPsxDesignParentTab is missing or invalid.

The controller AdminPsMboTheme is missing or invalid.

I tried to look at /usr/local/www/our_shop/var/logs 

*ERROR*     v8.1.6    2025/04/01 - 09:02:40: SQLSTATE[42S02]: Base table or view not found: 1146 Table &#039;asprestashop.ps_configuration&#039; doesn&#039;t exist at line 151 in file classes/db/DbPDO.php
 

It seems something is / are missing.  With the previous HTTP Error 500 i could at least login to the Backoffice, but now it is totally horrible. The Server ist responding for ping check and apache24 is running. 

Is there any way to overcome or solve this error? Thanks! 
 

Sorry for my bad english...

After lots of trials to upgrade my prestashop from 1.7.8.11 to 8.2.0. I found successfull way. I hope this will be usefull for others.

There is some minor display issues remaining (see below).

Here is the different steps for a successuful upgrade. I didn't manage to use One-click upgrade module for this upgrade. I used CLI-command upgrade.

Step 1 : deactivate cash, smarty cache and delete var/cache/* (and Prestashop prerequists for upgrade)

Step 2 : upgrade to 8.0.4

Quote

 

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.0.4/prestashop_8.0.4.zip -o admin5667jgngm/autoupgrade/download/prestashop.zip

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.0.4/prestashop_8.0.4.xml -o admin5667jgngm/autoupgrade/download/prestashop.xml

echo "{\"channel\":\"archive\",\"archive_prestashop\":\"prestashop.zip\",\"archive_num\":\"8.0.4\", \"archive_xml\":\"prestashop.xml\", \"PS_AUTOUP_CHANGE_DEFAULT_THEME\":0, \"skip_backup\": 1}" > modules/autoupgrade/config.json

php modules/autoupgrade/cli-updateconfig.php --from=modules/autoupgrade/config.json --dir=admin5667jgngm

rm -rf var/cache/*

php modules/autoupgrade/cli-upgrade.php --dir=admin5667jgngm

 

After these steps, there were 2 warnings :

Quote

 

WARNING - [WARNING] Migration failed while running the file upgrade-2.3.1.php. Module ps_emailalerts disabled.

WARNING - [WARNING] Migration failed while running the file upgrade-0.3.php. Module blockwishlist disabled.

 

And module manager tab on backoffice was broken.

Let's continue.

Step 3 : upgrade from 8.0.4 to 8.1.7

Quote

 

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.7/prestashop_8.1.7.zip -o admin5667jgngm/autoupgrade/download/prestashop.zip

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.7/prestashop_8.1.7.xml -o admin5667jgngm/autoupgrade/download/prestashop.xml

echo "{\"channel\":\"archive\",\"archive_prestashop\":\"prestashop.zip\",\"archive_num\":\"8.1.7\", \"archive_xml\":\"prestashop.xml\", \"PS_AUTOUP_CHANGE_DEFAULT_THEME\":0, \"skip_backup\": 1}" > modules/autoupgrade/config.json

php modules/autoupgrade/cli-updateconfig.php --from=modules/autoupgrade/config.json --dir=admin5667jgngm

rm -rf var/cache/*

php modules/autoupgrade/cli-upgrade.php --dir=admin5667jgngm

 

All right after that but do not access to BO.

Step 4 : upgrade from 8.1.7 to 8.2.0

Quote

 

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.2.0/prestashop_8.2.0.zip -o admin5667jgngm/autoupgrade/download/prestashop.zip

curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.2.0/prestashop_8.2.0.xml -o admin5667jgngm/autoupgrade/download/prestashop.xml

echo "{\"channel\":\"archive\",\"archive_prestashop\":\"prestashop.zip\",\"archive_num\":\"8.2.0\", \"archive_xml\":\"prestashop.xml\", \"PS_AUTOUP_CHANGE_DEFAULT_THEME\":0, \"skip_backup\": 1}" > modules/autoupgrade/config.json

php modules/autoupgrade/cli-updateconfig.php --from=modules/autoupgrade/config.json --dir=admin5667jgngm

rm -rf var/cache/*

php modules/autoupgrade/cli-upgrade.php --dir=admin5667jgngm

 

After that, the file upgrade didn't work.

--> reload the last CLI command :

Quote

php modules/autoupgrade/cli-upgrade.php --dir=admin5667jgngm

Step 5 :

Access to BO, activate tiers modules, enjoy 8.2 version of Prestashop.

Minor display issues :

There is some minor display issues remaining (see attached pictures) :

- with profil icons on the top right only in some sheets (for example, not in dashboard page but in order page or module manager page)

- with order indicator on order page

If anybody have an idea, keep me informed ?

Have a nice day.

Namely, I can no longer upgrade the existing Prestashop modules that are in BO and there is no longer a notification at the top that an upgrade is ready and I can no longer upload new modules. 

If you then click on "upload a module", the screen will open and when you select a module, the module will not be searched for. 

Also, the connection with addons in the top right corner will not disconnect  when you click on it, the screen does open and you are then asked if you want to disconnect the connection, but it is ultimately not disconnected. 

It seems like there has been a problem with the module page... 

Now I haven't changed anything just upgraded to 1.7.8.11. The only thing that has remained is in the 1Click-upgrade module which gives a red cross - that the database does not match the Prestashop version - 

I have adjusted that in MyPhP Configuration / PS_VERSION_DB and PS-INSTALL both set to 1.7.8.11, but unfortunately this has not solved or changed the problems. 

I also tried these problems with ChatGPT but it redirects me to a forum, well here I am ?

Henny,

I have a shop with version 1.6.1.23 and I'd like to upgrade to 8.2. For my tests I've set-up a local installation of 8.2. My plan was to get a DB from old shop and import it to a new one, copy stuff from /img. I have only 3 external modules so they are not a problem. I have already a new theme which is 8.2 ready.

However importing a db to new 8.2 with phpmyadmin is not that easy, it seems that a lot of has changed in db structure. Which way should I go with the migration, how to approach it? Looks like I should use modules and upgrade 1.6 -> 1.7 -> 8.2?

Thanks!

I updated prestashop with 1-Click Upgrade module to version 1.8.

Once I updated, all the graphics made with the Creative Elements module disappeared.

So, naively, I rolled back, but now it gives me error 500.

I activated debug mode, it gives me the following error... What can I do? Unfortunately I don't have a backup of the site...

Just upgraded my PrestaShop from 1.7 to 8.2 and doesn't find themes settings in my back office.

i tried to change theme in database and config.php/config.yml, but it doesn't work. There is way to change theme? 

Symfony\Component\ErrorHandler\Error\
UndefinedMethodError

in modules/pkamp/classes/Amp.php (line 52)
 

 $confOrdered = [];

        // get module config from file

        if ($f = @fopen(\Pkamp::CONFIG_FILE, 'r')) {

            $json_config = fread($f, filesize(\Pkamp::CONFIG_FILE));

            if ($configObj = \Tools::jsonDecode($json_config)) {

                $fileConfig = (array)$configObj;

            }

        }

        // get module config from DB

_________________________________

Please any help will be very thankful... is ohmyicons.com

Thanks!

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

This problem can sometimes be caused by disabling or refusing to accept cookies.

The F.O is showing the Maintenance page but no access to B.O at all.

Any idea on how to get back into B.O

I have deleted the VAR folder so that has been rebuilt

How can I fix this ?

I have spent a considerable amount of time making changes to the translations of our store - especially the email content.

I have not yet tried the one-click upgrade, but I am worried that if I do use this to upgrade to the lastest version, that all of the modified translations will be lost. Can anybody confirm that this is/or is not the case?

Thanks

Wondering if anyone can help me in the right direction..

I have upgraded from 1.6.X.X to 1.7.5.0, everything seemed to be ok, now all of a sudden I have this error! when I say all of a sudden, I mean that the upgrade was made a month ago and the error is about 2 days old

I would be really happy if you could help me with my problem. I'm trying to update my prestashop, from 1.7.1.0 to 1.7.2.4 with the 1-click module.

I've downloaded everything manually, extracted them into the autoupdate/latest and started updating. (updating normally gave an internal server error at decompressing the archive, which I could not solve with changing the timeout and memory value in the php.ini)

The manual update works fine, till updating the vendor/symfony/src/Symfony/Component/Yaml/inline.php. Before, it says 696 files left to upgrade. There I get the error: [Ajax / Server Error for action upgradeFiles] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "  Screenshot see attached.

I've tried to update the shop several times, changing the php.ini memory and timeout limit, also changing the prestashop switch for non-native modules. The update always gets stuck at the very same file. Do you have an idea how can I solve this problem? I would really appreciate your help!

Thank you.

Best Regards,

Marcell

 ├------[FATAL ERROR]-->
Array
(
    [type] => 16384
    [message] => Not specifying the optional ShopConstraint parameter is deprecated since version 1.7.8.0
    [file] => /var/www/computercentrale/src/Adapter/Configuration.php
    [line] => 418
)

The script fails on the last line:

        require_once('../config/config.inc.php');
        require_once("lib/images.inc.php");
        define("ID_SHOP", 1 );
        define("ID_SHOP_GROUP", 1 );
        require_once("lib/ps/Prestashop15.class.php");

without any other information. In this last function it does not execute anything, it fails allready in the function __construct()

I have other scripts working fine.

Does anyone have the same issue, and how to resolve this. What exactly do you need to specify and where?

Any help is much appreciated!

/home/bolchant/www/var/cache/dev/smarty/compile/classiclayouts_layout_left_column_tpl/42/f8/02/42f80221c9bf89dc5f7d63c793bbadd5ed7b59b8_2.file.stylesheets.tpl.php on line 50

Warning: Attempt to read property "value" on null in /home/bolchant/www/var/cache/dev/smarty/compile/classiclayouts_layout_left_column_tpl/42/f8/02/42f80221c9bf89dc5f7d63c793bbadd5ed7b59b8_2.file.stylesheets.tpl.php on line 50
" /> /home/bolchant/www/var/cache/dev/smarty/compile/classiclayouts_layout_left_column_tpl/42/f8/02/42f80221c9bf89dc5f7d63c793bbadd5ed7b59b8_2.file.stylesheets.tpl.php on line 52

Warning: Attempt to read property "value" on null in /home/bolchant/www/var/cache/dev/smarty/compile/classiclayouts_layout_left_column_tpl/42/f8/02/42f80221c9bf89dc5f7d63c793bbadd5ed7b59b8_2.file.stylesheets.tpl.php on line 52
" />

[INTERNAL] /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php line 54 - Symfony\Component\DependencyInjection\Exception\RuntimeException: You have requested a non-existent parameter "api_private_key". #0 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(83): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue() #1 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php(32): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #2 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(47): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue() #3 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php(94): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->process() #4 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php(762): Symfony\Component\DependencyInjection\Compiler\Compiler->compile() #5 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(594): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #6 /home/platne/serwer146135/public_html/nowa/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #7 /home/platne/serwer146135/public_html/nowa/app/AppKernel.php(96): Symfony\Component\HttpKernel\Kernel->boot() #8 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(67): AppKernel->boot() #9 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initKernel() #10 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(102): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #11 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(49): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #12 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/Task/Upgrade/UpgradeDb.php(49): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #13 /home/platne/serwer146135/public_html/nowa/modules/autoupgrade/classes/Task/Runner/ChainedTasks.php(61): PrestaShop\Module\AutoUpgrade\Task\Upgrade\UpgradeDb->run() #14 /home/platne/serwer146135/public_html/nowa/adminpuM7nu/autoupgrade/ajax-upgradetab.php(54): PrestaShop\Module\AutoUpgrade\Task\Runner\ChainedTasks->run() #15 {main}

I’m reaching out for assistance with a challenging migration issue I’ve been facing for the past month and a half. I’ve been trying to update my client’s PrestaShop store from version 1.7 to 8.2. Since the store has a large number of products and orders, I decided to copy the website files and database to a test host to ensure everything works smoothly before making the switch.

Unfortunately, the direct update from 1.7 to 8.2 failed, and I’m unsure why. As an alternative, I decided to export all the data (products, clients, orders, etc.) from the 1.7 version using the "Export + Import + Update of Products Catalog" plugin by Smart Presta. I then created a fresh PrestaShop 8.2 installation and attempted to import the data using the same plugin.

While the import process seemed to go smoothly, I encountered two major issues:

Product images were not imported – None of the product images were transferred to the new store.

Incomplete data import – Out of 800 products, only 600 were imported, and out of 4000 clients, only 2500 were imported.

To troubleshoot, I split the import files into smaller chunks (4 files) and reattempted the import, but the results were exactly the same.

After this setback, I explored another solution: the PrestaShop Manager by EmagicOne. This desktop application offers import/export functionality and a 14-day trial. I installed it and attempted to export and import the data again, but I faced the same issues with the same numbers.

At this point, I’m exhausted and frustrated after spending so much time on this problem without success. I’m reaching out to the community for guidance. Has anyone experienced similar issues during a PrestaShop migration? Are there any recommended tools, plugins, or methods to ensure a complete and successful data transfer, including product images?

Any advice, suggestions, or solutions would be greatly appreciated. Thank you in advance for your help!

Best regards,

I am trying to upgrade prestashop from 1.7.8.11 to latest 8.2 with 1click upgrade and i get this error:

[INTERNAL] /home/r47431gdsh/public_html/xxxx.xx/vendor/composer/autoload_real.php line 45 - require(): Failed opening required '/home/r47431gdsh/public_html/xxxx.xx/vendor/composer/../react/promise/src/functions_include.php' (include_path='/home/r47431gdsh/public_html/xxxx.xx/vendor/pear/pear_exception:/home/r47431gdsh/public_html/xxxx.xx/vendor/pear/console_getopt:/home/r47431gdsh/public_html/xxxx.xx/vendor/pear/pear-core-minimal/src:/home/r47431gdsh/public_html/xxxx.xx/vendor/pear/archive_tar:.:/opt/cpanel/ea-php74/root/usr/share/pear')

(xxxx.xx is the domain)

Both BO and FO error 500.

I tried:

deleting all directories from /var/cache before upgrade.

Switching to default theme before upgrade and with option in autoupgrde module

disabled all non native modules(manual disabled in BO before upgrade and checbox in autoupgrade module) and override.

Upgrade stops at database upgrade with this error.

Changed PHP version from 7.4 to 8.x after upgrade.

Please Help.

I am out of ideas.

Thanks in advance.

Have had prestashop for a long time but now all of a sudden it is completely impossible to login from any browser to back office.
So is there a way of upgrading without being loged in?

I am NOT a programmer so I will not even consider sit and try to find out what is wrong and why I cannot login.
My server agent says there is something wrong with the PHP actions, and sure the error list is long in the logfile but still. I have been able to login before despite those logs. But now nothing works.

I have cleared the cache, cookies in browers, tried different browsers, deleted webshop chache file and so on but still all I get is a whote page or a 500 message, depending on what browser I use.

Can I solve such an image by changing from Apache to Windows setup at my server location?
I don't know what that means but it says when I log in that it should be Apache if I use PHP and whould be Windows if I use ASP.

Does someone have any clue why my problems occur?
I have posted in general Prestashop archive as well, no answers there, mayby I am invisible there I don't now.
Have been trying this now for two weeks and soon I will ned o remove my entire shop, with several hundreds of products and rebuild everything including product databases, and that is a big no go for me. It will take months to put everything up and running again with so many products.

Any suggestions are welcome and I will try anything.

Thank you fellows.

I have been using Prestashop for several years and performing the upgrade process by using the 1-Click-Upgrade module.  Currently, Prestashop 8.1.6 is running on a FreeBSD 13.3-RELEASE-p1 amd64 and PHP Version is 8.1.28   .  I wanted to upgrade to Prestashop 8.2.0, which is the recommende stable version. I did following usual necessary steps to upgrade the shop,

0. Activate the maintance mode
1. Make the shop folder on server writable with "chmod -R 777 ./<shop folder name>" 
2. Deactivate the Payment method

My 1-Click-Upgrade module is the latest version v 6.2.0  and showed all Prestashop requirements for an Upgrade are fulfilled, as shown below (in German).

The istalled version of PHP is 8.1.28, which is also recommended version. I think the PHP Version should not be the problem. However, when I click to upgrade the refresh symbol (or processing symbol) was displayed for ca. 2 seconds (I showed it with an arrow), 

then stopped without any message, no error, nothing. Just stopped. This is weird.  I searched the entire internet, but couldn't  find any clue about this. 

I am looking for a hint and advice from your guys.

Thank you! 


 

Recently downloaded the following module:
https://addons.prestashop.com/en/data-migration-backup/5496-1-click-upgrade.html

When I went to the modules and services tab and pressed "add a new module" the form to upload my module showed up and thus I selected the zip file I downloaded previously. After I got a confirmation pop-up message, to my surprise I couldn't find the module displayed anywhere.

I've went over the server using an FPT server and noticed the module exists in there it's simply not showing on the module tab.

I downloaded the version 6.2.0v since my prestashop version is the 1.7.x version.

Thanks in advance for any help you guys might provide.

Prestashop upgraded my site to 8.2 and also upgraded the server php to 8.1.30

WebService was working 100% for several years on the old setup.

After the upgrade everything was fine until the first sync between Accounting Software and Presta.
All our products' names, short and long descriptions were deleted.

All the data is still in the accounting software, Smart-It , but when I sync it does not write the data back to Prestashop and Webservice.

My server support tried hard to help but says everything is fine on their side.

For some reason it cannot write to Prestashop.
Anyone encountered this before?

Do you know what this is, was also one of the errors?

connect() to unix:/var/www/vhosts/system/4x4direct.co.za/php-fpm.sock failed (2: No such file or directory) while connecting to upstream, client

what is php-fpn.sock ?

These are some of the errors and do not worry I changed the key.

I've increased the max_children to 80.
In terms of server capabilities, GET, POST, PUT, PATCH, DELETE and HEAD are supported.

The 40 max_children was reached. There is also a PHP error seen in the PHP error log:

[27-Nov-2024 20:00:44] WARNING: [pool 4x4direct.co.za] server reached max_children setting (40), consider raising it
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "PHP message: PHP Fatal error:  Uncaught Error: Call to undefined method Attribute::getAttributes() in /var/www/vhosts/4x4direct.co.za/httpdocs/override/classes/WebserviceSpecificManagementSi.php:198"
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "Stack trace:"
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "#0 /var/www/vhosts/4x4direct.co.za/httpdocs/classes/webservice/WebserviceRequest.php(622): WebserviceSpecificManagementSiCore->manage()"
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "#1 /var/www/vhosts/4x4direct.co.za/httpdocs/webservice/dispatcher.php(98): WebserviceRequestCore->fetch()"
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "#2 {main}"
[27-Nov-2024 20:00:53] WARNING: [pool 4x4direct.co.za] child 29725 said into stderr: "  thrown in /var/www/vhosts/4x4direct.co.za/httpdocs/override/classes/WebserviceSpecificManagementSi.php on line 198"

proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:41:58 +0200] "PUT /api/stock_availables/682 HTTP/1.1" 200 640 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:41:59 +0200] "PUT /api/stock_availables/232 HTTP/1.1" 200 640 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:41:59 +0200] "PUT /api/stock_availables/864 HTTP/1.1" 200 640 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:41:59 +0200] "PUT /api/stock_availables/1570 HTTP/1.1" 200 643 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:41:59 +0200] "PUT /api/stock_availables/1272 HTTP/1.1" 200 643 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:42:00 +0200] "PUT /api/stock_availables/1122 HTTP/1.1" 200 643 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:42:00 +0200] "PUT /api/stock_availables/1499 HTTP/1.1" 200 643 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:42:01 +0200] "PUT /api/stock_availables/1071 HTTP/1.1" 200 641 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:42:01 +0200] "PUT /api/stock_availables/1523 HTTP/1.1" 200 643 "-" "-"
proxy_access_ssl_log:41.***.***.101 - EAE1AIMIZ46UGA6IT3H431PHKEGTEZJ1 [27/Nov/2024:17:42:01 +0200] "PUT /api/stock_availables/279 HTTP/1.1" 200 640 "-" "-"

proxy_access_ssl_log:41.***.***.101 - R91TH6YKB6V2F8US4Q82SVMBY2FQGBEN [27/Nov/2024:14:08:48 +0200] "DELETE /api/categories/1069 HTTP/1.1" 404 238 "-" "-"
proxy_access_ssl_log:41.***.***.101 - R91TH6YKB6V2F8US4Q82SVMBY2FQGBEN [27/Nov/2024:14:08:48 +0200] "DELETE /api/categories/1070 HTTP/1.1" 200 5 "-" "-"
proxy_access_ssl_log:41.***.***.101 - R91TH6YKB6V2F8US4Q82SVMBY2FQGBEN [27/Nov/2024:14:08:48 +0200] "DELETE /api/categories/1111 HTTP/1.1" 200 5 "-" "-"
proxy_access_ssl_log:41.***.***.101 - R91TH6YKB6V2F8US4Q82SVMBY2FQGBEN [27/Nov/2024:14:08:49 +0200] "DELETE /api/categories/1181 HTTP/1.1" 404 238 "-" "-"
proxy_access_ssl_log:41.***.***.101 - R91TH6YKB6V2F8US4Q82SVMBY2FQGBEN [27/Nov/2024:14:08:49 +0200] "DELETE /api/categories/1182 HTTP/1.1" 404 238 "-" "-"

My website www.mediterraneansupermarket.com seems to only display the home page and CMS pages, When I click on any of the product categories or products  it goes to a blank page. I have enable error reporting to display the issues with the website. Attached is a screen shot of the errors, I cannot access the admin area of the website either.

This happened after the website was upgraded from Prestashop v.7 to v.8.

Any ideas how I can solve this?

Many thanks,

Leilah

Aparently the issue has a few months but ntil now I recieve the call.

Given this I think a clean install of PS latest version ld be the better choice, however the '1 click upgrade module' requires me to have admin privileges to upgrade the database structure, but my hosting provider doesn't allow them and recommended switching into a VPS which is about 4x as expensive and the customer is not comfortable with it.

That being said, any methods involving CLI are discarded now.

Any workarounds on this scenario?

For the bulk delete fix I've unsuccesfully tried:

- Debugging the install

- Disabling custom modules and themes

- Clearing database cache

- Repairing he database through phpMyAdmin

I am currently running:

PS 1.7.8.11

And hese are my serve configs

Any tips on how to address this?

The error log entries are as follows:

2024-11-20 18:02:27.277122 [NOTICE] [11898] [T0] [96.63.158.143:52935:HTTP2-119#APVH_thunderbirdmodels.com:443] [STDERR] PHP Notice:  Trying to get property 'theme_name' of non-object in /home/thunder3/public_html/test_site/var/cache/prod/ContainerUGuOxCa/appAppKernelProdContainer.php on line 3376\n
2024-11-20 18:01:40.649150 [NOTICE] [11898] [T0] [96.63.158.143:52935:HTTP2-99#APVH_thunderbirdmodels.com:443] [STDERR] PHP Notice:  Trying to get property 'theme_name' of non-object in /home/thunder3/public_html/test_site/var/cache/prod/ContainerHDHVzYL/appAppKernelProdContainer.php on line 2911\n
2024-11-20 17:58:40.253155 [NOTICE] [11898] [T0] [96.63.158.143:52935:HTTP2-41#APVH_thunderbirdmodels.com:443] [STDERR] PHP Notice:  Trying to get property 'theme_name' of non-object in /home/thunder3/public_html/test_site/var/cache/prod/ContainerBFkNWEE/appAppKernelProdContainer.php on line 3376\n
2024-11-20 17:57:46.169190 [NOTICE] [11898] [T0] [96.63.158.143:52935:HTTP2-23#APVH_thunderbirdmodels.com:443] [STDERR] PHP Notice:  Trying to get property 'theme_name' of non-object in /home/thunder3/public_html/test_site/var/cache/prod/ContainerGqxJggE/appAppKernelProdContainer.php on line 2911\n
2024-11-20 17:53:06.187748 [NOTICE] [11898] [T0] [96.63.158.143:52892:HTTP2-43#APVH_thunderbirdmodels.com:443] [STDERR] PHP Notice:  Trying to get property 'theme_name' of non-object in /home/thunder3/public_html/test_site/var/cache/prod/ContainerFzGJDS7/appAppKernelProdContainer.php on line 3548\n
 

Can anyone shed any light on this please?

Tried clearing cache, Friendly URL off/on, VAR cache and theme switch to classic and back to the them, nothing helped, the other stores seem to be fine. Any solution will be appreciated.

When turn the debug mode on  and tried to open the homepage of one of the stores I get this error

Thanks in advance.

Fatal error: Uncaught PrestaShop\PrestaShop\Core\Exception\ContainerNotFoundException: Kernel Container is not available in /home/sundarinnovation/public_html/NewVersionStaging/src/Adapter/ContainerFinder.php:77 Stack trace: #0 /home/sundarinnovation/public_html/NewVersionStaging/classes/module/Module.php(1674): PrestaShop\PrestaShop\Adapter\ContainerFinder->getContainer() #1 /home/sundarinnovation/public_html/NewVersionStaging/classes/module/Module.php(1663): ModuleCore::getModuleRepository() #2 /home/sundarinnovation/public_html/NewVersionStaging/classes/Hook.php(878): ModuleCore::getNativeModuleList() #3 /home/sundarinnovation/public_html/NewVersionStaging/classes/Dispatcher.php(606): HookCore::exec('moduleRoutes', Array, NULL, true, false) #4 /home/sundarinnovation/public_html/NewVersionStaging/classes/Dispatcher.php(243): DispatcherCore->loadRoutes() #5 /home/sundarinnovation/public_html/NewVersionStaging/classes/Dispatcher.php(201): DispatcherCore->__construct(Object(Symfony\Component\HttpFoundation\Request)) #6 /ho in /home/sundarinnovation/public_html/NewVersionStaging/src/Adapter/ContainerFinder.php on line 77

Unknown locale code: es-AR

[PrestaShop\PrestaShop\Core\Localization\Exception\LocalizationException 0]

I'll leave you what I see in the DB, if you need anything to help me, please let me know

mysql> SELECT * FROM ps_currency_lang;
+-------------+---------+-----------------------+--------+---------+
| id_currency | id_lang | name                  | symbol | pattern |
+-------------+---------+-----------------------+--------+---------+
|           1 |       3 | Euro                  | €      | NULL    |
|           1 |       5 | Peso Argentino        | ARS    | NULL    |
|           2 |       3 | US Dollar             | $      | NULL    |
|           3 |       3 | peso argentino        | $      | NULL    |
|           3 |       5 | peso argentino        | ARS    | NULL    |
|           7 |       3 | dólar estadounidense  | $      | NULL    |
|           7 |       5 | Dólar estadounidense  | $      | NULL    |
+-------------+---------+-----------------------+--------+---------+
7 rows in set (0.00 sec)

mysql> SELECT * FROM ps_lang;
+---------+----------------------+--------+----------+---------------+--------+------------------+------------------+--------+
| id_lang | name                 | active | iso_code | language_code | locale | date_format_lite | date_format_full | is_rtl |
+---------+----------------------+--------+----------+---------------+--------+------------------+------------------+--------+
|       3 | Español (Spanish)    |      0 | es       | es-es         | es-ES  | d/m/Y            | d/m/Y H:i:s      |      0 |
|       5 | Español (Argentina)  |      1 | es       | es            | es-AR  |                  |                  |      0 |
+---------+----------------------+--------+----------+---------------+--------+------------------+------------------+--------+
2 rows in set (0.00 sec)

I upgraded my shop from 1.7.8.8 to 1.7.8.11. The process went smoothly, but after further inspection, I discovered some issues. I’m unable to log into customer accounts created before the update, and when I enable debug mode to investigate, an error message appears (see attached picture).

Any help would be greatly appreciated. Thank you in advance!

As a note, I have no experience with Presta Shop, but I do with servers and web development, but the website has been backed up.

Thank you for your time.

<a href="{$product.url}" target="_blank">{$product['name']}</a>

in version 1.7.7.5 most recent available version it does not work.

Can anyone assist with this?

I upgraded my store with the 1 click upgrade and it was going well so far. At the end of the installation I closed my backoffice webpage to log again and now I am not able to connect anymore, of course I am 100% sure that my ID's are correct. When I log in it say that my account does not exist. If I try to reset my password it will say that there is an error processing the reset of my password. You can see the screenshot bellow. 

I would be grateful if you can help me. 

contact
dashtrends
marketplace
welcome

url rewrite & the robots text file, have dogged me, a couple times for an hour or so.
then the damn panda theme wants to be an absolute pain in the arse

It makes me wonder what all the tricks are to reach my journey
is prestools and copyshop_data the solution again? it did get me from 1.6x to 1.7 but I have forgotten how now.
it shouldn't be this hard. I started this site back in the the 1.3.1 days. I will not give up

I am experience an issue trying to update from prestashop 1.7.6.8 to 1.7.8.8 using 1-Click upgrade module

The 1-Click upgrade module won't run because the checklist is not complete "Enable maintenance mode and add your maintenance IP " is not checked even though the ship is Maintenance mode. 

I tried installing previous versions of the model and they all "see" the shop is in maintenance mode but can't update because a newer version of the module exists. Once I update the module I get the "Enable maintenance mode" error again. 

I tried uninstalling and reinstalling the 1-Click upgrade module several times. Cleared cache for  Performance/Clear Cache, deleted cache from var/cache folder.

Module version is v4.15.0

Any ideas of what is wrong? 

Long time i didn't post maybe few years i was away from Prestashop and here i am back . I have installed prestashop and upgraded from V8.1.1 to 8.2 and now when i log to admin area i have this message , Page not found : The controller AdminPsEditionBasicHomepageController is missing or invalid .

Please check screenshot in the attachment. Thanks. 

I have upgraded my Prestashop from 1.7.6.7 to 8.1.7. There are many broken things which I am facing at the time of checking. One of them is Modules tab is not showing on the product create/edit page. I am not getting what is wrong with it. Can anyone please suggest a solution?

I have just bumped into a problem on www.sechap-klabik.cz
When I successfully log in, it redirects me to index and then back to login page. Ive seen many threads related to this problem on different PS versions, but none helped me. Nor Cookies, init, login files changes..

I am quite desperate now.

I tried to upgrade Prestashop from 1.7.8.9 to 8.0.4 and to 8.1.0 with 1-Click Module v4.16.0 on 3 different shops on 2 servers.
All shops on 3 languages.

After update to 8.1.0 back office translations are broken and layout at the right upper edge is broken.

Only on Dashboard page layout not broken.

After upgrade to 8.0.4 only translations are broken.

These problems do not occur if I initially install version 8.0.4 or 8.1.0.

Can anyone tell me how to do the upgrade so that the problems I described don't occur?

Thank you and best regards.

I have restored my prestashop from backup. I want to update prestashop but i have an error:

The version of PrestaShop does not match the one stored in database. Your database structure may not be up-to-date and/or the value of PS_VERSION_DB needs to be updated in the configuration table. Learn more.

How may i sort this problem out?

I have a question about updating Prestashop 1.7. In the update section, the recommended version for Prestashop 1.7.8.7 is 1.7.8.11. I would like to know if updating to version 1.7.8.11 will cause any issues?

Also, I see that version 8 is a major update. If I update to 1.7.8.11, will version 8 still be considered a major update? In other words, how long do you recommend staying on version 1.7?

Thank you.

The situation with the database is more complex. A table is missing, and even if I attempt to create it, I am unsure of its structure.
Please find attached a screenshot of the errors I have encountered.

Thank you so much in advance

You have requested a non-existent service "mbo.cdc.context_builder".

[Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException 0]

what is interesting is that the upgrade process ended succesfully, it seems like the operation has succeded, but the patient has died.

Please help me with this issue

Link to database cannot be established: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES)

I see some changes in the settings.inc.old.php and the new one.

Old: 

<?php

I wanted to update the Prestashop but I get the following error

[INTERNAL] /modules/ps_accounts/ps_accounts.php line 24 - Trait 'PrestaShop\Module\PsAccounts\Provider\OAuth2\PrestaShopLogoutTrait' not found

and this one when I try to log in

Argument 2 passed to PrestaShop\Module\Mbo\Service\View\ContextBuilder::__construct() must be an instance of PrestaShop\PrestaShop\Core\Addon\Module\ModuleRepository, instance of ModuleRepository_091bb2f given, called in /var/cache/prod/ContainerPZKJTC2/getMbo_Cdc_ContextBuilderService.php on line 9

[TypeError 0]

I have also tried to delete the cache file, delete the module, update it etc. but it has not been useful, could someone help me?

Thank you very much!

We had our shop up and running (in maintenance mode) before we launch next month. Everything was working well until the other day there were 3 updates in the modules section. I dont remember what they were exactly but one was official prestashop i think. Anyways, we started updating the modules.

after the first module updated, it was saying we needed to upgrade out php to 8.1 (we were using 7.4) which we did, but it still doesnt work. we still get 503 error once we log in to the back end. i tried switching back to php v7.4 and every other version and none of them fixes it. we have some modules requiring 8.1 and some requiring older versions.

our site works perfectly fine once we log into the backend, but the backend itself gives 503 error, if that makes sense. ie: if you go to our site not logged in, you get maintenance mode page. if you log into the back end, you get a 503 error instead of the actual back end where you can edit modules and pages. but after logging in we can view our site on the front end fine and all pages work

i just need to know what to do from here so i dont make it worse. can i manually uninstall the modules? manually update the other 2 modules? i dont want to make it worse.

im pretty sure i have the latest prestashop version but i dont know how to check since im getting 503 error on the back office. let me know what info you need and ill reply with it. thanks in advanced