Datasets:

DanCip

/

github-issues-top50-repos

like 0

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi I've a customer with a site which contains 160000 products, all files are 32GB I want to upgrade from 8.1.2 to 8.1.3, now I've activated webp images and now it's even bigger it uses cloudflare and even if I deactivated all proxied, put it in dev mode, I can't avoid this 90 second timeout. the problem I have in the module and in the last step, when I put the site into maintenance and do the last general check before displaying the button to upgrade to 8.1.3 unfortunately it takes a long time, a few minutes and then after 90 seconds it times out Is there a way to remove some controls to reduce the loading of the form page to a few dozen seconds? why is it necessary to wait all this time, when in the end it is only necessary to overwrite the prestashop files and update the database? surely the problem is the images folder, couldn't it be excluded from any checks? thanks ### Expected behavior _No response_ ### Steps to reproduce 1. a site very big 2. cloudflare pro 3. upgrade from 8.1.2 to 8.1.3 ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade 5.0.0 ### Your company or customer's name goes here (if applicable). _No response_

autoupgrade module + cloudflare pro, with big website is not possible upgrade prestashop due the timeout

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34989/comments

https://github.com/PrestaShop/PrestaShop/issues/34989

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : autoupgrade module + cloudflare pro, with big website is not possible upgrade prestashop due the timeout Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi I've a customer with a site which contains 160000 products, all files are 32GB I want to upgrade from 8.1.2 to 8.1.3, now I've activated webp images and now it's even bigger it uses cloudflare and even if I deactivated all proxied, put it in dev mode, I can't avoid this 90 second timeout. the problem I have in the module and in the last step, when I put the site into maintenance and do the last general check before displaying the button to upgrade to 8.1.3 unfortunately it takes a long time, a few minutes and then after 90 seconds it times out Is there a way to remove some controls to reduce the loading of the form page to a few dozen seconds? why is it necessary to wait all this time, when in the end it is only necessary to overwrite the prestashop files and update the database? surely the problem is the images folder, couldn't it be excluded from any checks? thanks ### Expected behavior _No response_ ### Steps to reproduce 1. a site very big 2. cloudflare pro 3. upgrade from 8.1.2 to 8.1.3 ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade 5.0.0 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments During the upgrade process received a fatal error about a undefined function named **get_magic_quotes_gpc()** https://github.com/PrestaShop/autoupgrade/blob/dev/classes/UpgradeTools/Translation.php#L175 This function **get_magic_quotes_gpc() always returns false** since PHP 5.4, **DEPRECATED** in PHP 7.4 and **REMOVED** in PHP 8.0 Autoupgrade module requires PHP 5.6, so this code (lines 175-177) could be useless To fix my upgrade I added a **function_exists()** check `if (function_exists('get_magic_quotes_gpc') && get_magic_quotes_gpc())` ### Expected behavior Complete upgrade without errors ### Steps to reproduce Try upgrade using autoupgrade module (1-Click Upgrade) using PHP 8.1 ### PrestaShop version(s) where the bug happened Upgrading from 1.8.0 to 1.8.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade ### Your company or customer's name goes here (if applicable). _No response_

Autoupgrade (1-Click Upgrade) failed using PHP 8.x (get_magic_quotes_gpc function deprecated)

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34988/comments

https://github.com/PrestaShop/PrestaShop/issues/34988

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade (1-Click Upgrade) failed using PHP 8.x (get_magic_quotes_gpc function deprecated) Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments During the upgrade process received a fatal error about a undefined function named **get_magic_quotes_gpc()** https://github.com/PrestaShop/autoupgrade/blob/dev/classes/UpgradeTools/Translation.php#L175 This function **get_magic_quotes_gpc() always returns false** since PHP 5.4, **DEPRECATED** in PHP 7.4 and **REMOVED** in PHP 8.0 Autoupgrade module requires PHP 5.6, so this code (lines 175-177) could be useless To fix my upgrade I added a **function_exists()** check `if (function_exists('get_magic_quotes_gpc') && get_magic_quotes_gpc())` ### Expected behavior Complete upgrade without errors ### Steps to reproduce Try upgrade using autoupgrade module (1-Click Upgrade) using PHP 8.1 ### PrestaShop version(s) where the bug happened Upgrading from 1.8.0 to 1.8.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When upgrading PrestaShop 8.1.2 to 8.1.3 using autoupgrade module with command line, the database upgrade fails: > INFO - === Step upgradeDb INFO - Cleaning file cache INFO - Running opcache_reset INFO - Initializing required environment constants INFO - Checking version validity ERROR - Error during database upgrade. You may need to restore your database. ERROR - [ERROR] Version to install is too old. Current version: 8.1.3.0. Version to install: 8.1.3. ### Expected behavior _No response_ ### Steps to reproduce 1. Install PS 8.1.2 2. Install the autoupgrade module 3. Manually unzip PS 8.1.3 4. Run command line: `php modules/autoupgrade/cli-upgrade.php --dir=admin-dev --channel=private --action=upgradeDb` ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.0 ### Your company or customer's name goes here (if applicable). _No response_

[autoupgrade] cli upgrade 8.1.2 > 8.1.3 fails on db upgrade

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34987/comments

https://github.com/PrestaShop/PrestaShop/issues/34987

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [autoupgrade] cli upgrade 8.1.2 > 8.1.3 fails on db upgrade Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When upgrading PrestaShop 8.1.2 to 8.1.3 using autoupgrade module with command line, the database upgrade fails: > INFO - === Step upgradeDb INFO - Cleaning file cache INFO - Running opcache_reset INFO - Initializing required environment constants INFO - Checking version validity ERROR - Error during database upgrade. You may need to restore your database. ERROR - [ERROR] Version to install is too old. Current version: 8.1.3.0. Version to install: 8.1.3. ### Expected behavior _No response_ ### Steps to reproduce 1. Install PS 8.1.2 2. Install the autoupgrade module 3. Manually unzip PS 8.1.3 4. Run command line: `php modules/autoupgrade/cli-upgrade.php --dir=admin-dev --channel=private --action=upgradeDb` ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.0 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When going to the commands pages my client complained about the page to load the order being incredibly slow to the point he could not work with the website as a single page was taking up to 50sec to load. Digging into it I found out it was related to notifications and AdminStats which were taking ages to load. (Mocking them to empty values fixed the issue) BTW I found [that issue](https://github.com/PrestaShop/PrestaShop/issues/18956) closed for the same problem but they said the problem was fixed with 1.7.7.0 which can't be the case cause the website of my client is under 1.7.8.9 ### Expected behavior I think the use of caching on that calls should be able to fix the problem or at least to make it acceptable. So we would have the first load that take a long time but not the other times. ### Steps to reproduce 1. Fill your db with a lot of orders, visitors and carts. 2. Visit the commands page on the BO 3. Try to access a single command page right after. 4. You should have to wait for ages :D ### PrestaShop version(s) where the bug happened 1.7.8.9 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Commands loading is extremely slow due to KPI on old websites with tons of data.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34986/comments

https://github.com/PrestaShop/PrestaShop/issues/34986

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Commands loading is extremely slow due to KPI on old websites with tons of data. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When going to the commands pages my client complained about the page to load the order being incredibly slow to the point he could not work with the website as a single page was taking up to 50sec to load. Digging into it I found out it was related to notifications and AdminStats which were taking ages to load. (Mocking them to empty values fixed the issue) BTW I found [that issue](https://github.com/PrestaShop/PrestaShop/issues/18956) closed for the same problem but they said the problem was fixed with 1.7.7.0 which can't be the case cause the website of my client is under 1.7.8.9 ### Expected behavior I think the use of caching on that calls should be able to fix the problem or at least to make it acceptable. So we would have the first load that take a long time but not the other times. ### Steps to reproduce 1. Fill your db with a lot of orders, visitors and carts. 2. Visit the commands page on the BO 3. Try to access a single command page right after. 4. You should have to wait for ages :D ### PrestaShop version(s) where the bug happened 1.7.8.9 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After updating the store to version **8.1.3**, category pages in the front-end stopped working. The error returned was related to the **buildPaginatedUrl** function referenced by the **getCanonicalURL()** function: Fatal error: Uncaught Error: Call to undefined method CategoryController::buildPaginatedUrl() in /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php:63 Stack trace: #0 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(1800): CategoryControllerCore->getCanonicalURL() #1 /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php(275): FrontControllerCore->getTemplateVarPage() #2 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(543): CategoryControllerCore->getTemplateVarPage() #3 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(607): FrontControllerCore->assignGeneralPurposeVariables() #4 /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php(127): FrontControllerCore->initContent() #5 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/Controller. in /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php on line 63 I replaced the code with: ``` public function getCanonicalURL() { /*if (!Validate::isLoadedObject($this->category)) { return ''; } return $this->buildPaginatedUrl($this->context->link->getCategoryLink($this->category));*/ $canonicalUrl = $this->context->link->getCategoryLink($this->category); $parsedUrl = parse_url($canonicalUrl); if (isset($parsedUrl['query'])) { parse_str($parsedUrl['query'], $params); } else { $params = array(); } $page = (int) Tools::getValue('page'); if ($page > 1) { $params['page'] = $page; } else { unset($params['page']); } $canonicalUrl = http_build_url($parsedUrl, ['query' => http_build_query($params)]); return $canonicalUrl; } ``` And everything started working correctly. This is my first time reporting an issue on GitHub, and I apologize if I mixed anything up. ### Expected behavior _No response_ ### Steps to reproduce 1. Click on any category at Prestashop 8.1.3 ### PrestaShop version(s) where the bug happened Prestashop 8.1.3 ### PHP version(s) where the bug happened PHP 7.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PixelDuetWeb

Prestashop 8.1.3 BuildPaginated URL

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34985/comments

https://github.com/PrestaShop/PrestaShop/issues/34985

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 8.1.3 BuildPaginated URL Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After updating the store to version **8.1.3**, category pages in the front-end stopped working. The error returned was related to the **buildPaginatedUrl** function referenced by the **getCanonicalURL()** function: Fatal error: Uncaught Error: Call to undefined method CategoryController::buildPaginatedUrl() in /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php:63 Stack trace: #0 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(1800): CategoryControllerCore->getCanonicalURL() #1 /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php(275): FrontControllerCore->getTemplateVarPage() #2 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(543): CategoryControllerCore->getTemplateVarPage() #3 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/FrontController.php(607): FrontControllerCore->assignGeneralPurposeVariables() #4 /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php(127): FrontControllerCore->initContent() #5 /home/admin/domains/pixeldev.davicar.pl/public_html/classes/controller/Controller. in /home/admin/domains/pixeldev.davicar.pl/public_html/controllers/front/listing/CategoryController.php on line 63 I replaced the code with: ``` public function getCanonicalURL() { /*if (!Validate::isLoadedObject($this->category)) { return ''; } return $this->buildPaginatedUrl($this->context->link->getCategoryLink($this->category));*/ $canonicalUrl = $this->context->link->getCategoryLink($this->category); $parsedUrl = parse_url($canonicalUrl); if (isset($parsedUrl['query'])) { parse_str($parsedUrl['query'], $params); } else { $params = array(); } $page = (int) Tools::getValue('page'); if ($page > 1) { $params['page'] = $page; } else { unset($params['page']); } $canonicalUrl = http_build_url($parsedUrl, ['query' => http_build_query($params)]); return $canonicalUrl; } ``` And everything started working correctly. This is my first time reporting an issue on GitHub, and I apologize if I mixed anything up. ### Expected behavior _No response_ ### Steps to reproduce 1. Click on any category at Prestashop 8.1.3 ### PrestaShop version(s) where the bug happened Prestashop 8.1.3 ### PHP version(s) where the bug happened PHP 7.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PixelDuetWeb --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When you want to write directly in the html space, the Keybord key "Enter" is not funtionning on both product description and short description. ### Expected behavior We must be able to write our codes directly in the HTML space with the possibility of organizing the work in each line by "Enter" key. ### Steps to reproduce 1- Try to create a new product, or change an existant product. 2- Go to the html icon to type your html code 3- Type anything 4- Clic The Keybord key "Enter" = > you will find that's impossible ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

The "Enter" key on the keyboard does not work with 8.1.3 in the product html space

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34984/comments

https://github.com/PrestaShop/PrestaShop/issues/34984

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : The "Enter" key on the keyboard does not work with 8.1.3 in the product html space Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When you want to write directly in the html space, the Keybord key "Enter" is not funtionning on both product description and short description. ### Expected behavior We must be able to write our codes directly in the HTML space with the possibility of organizing the work in each line by "Enter" key. ### Steps to reproduce 1- Try to create a new product, or change an existant product. 2- Go to the html icon to type your html code 3- Type anything 4- Clic The Keybord key "Enter" = > you will find that's impossible ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello. I would like to present a problem that I have seen in PrestaShop and not in other platforms and which I consider to be a problem of the functioning and management of root categories in Multistore: In the context of a MultiStore ... once the root category has been established in the "Multistore Tree" settings menu, this category should become the base category (root) of the entire subsite, of the Multistore, which is then only the sub categories (in the photo "Home-1) will be visible on the site If an admin in the Multistore presses "ADD new root category" in the context in which he is logged in/entered into his subsite (not in "All stores", as in the photo)... it should be created inside the Folder previously defined by us, and not in the basic Root category of the basic category structure ... If you want to insert other base categories into the Root, just select "All stores" from the top menu and you should only be able to insert categories into the root base from here (how it already works now) ! Today, if I am in the Group and the menu for managing a single shop as in the photo, if I press Root category... this is automatically inserted into the Root base and not into the root devised by me for my shop in the multistore which for many other third-party modules is a defect/problem... it creates categories which are then not visible in the shop due to their inclusion in the Root base of the Multistore...  ### Expected behavior How could I make a change in the code to make "Home-1" become the basic root category of my shop (1.Tech ...) in my case (in the photo) ... without being able to be bypassed by any other addon third and be seen by everyone as the root category of my shop "1.Tech ... "? In Advanced parameter > Multistore tree > 1.Tech ... I have already set "Home-1" as Category root ... Even if like Template, shop has become the new root, for many modu les that work with the creation of categories (import from CSV) nothing changes, saving continues to be carried out in the old Root base of the Multistore ### Steps to reproduce - ### PrestaShop version(s) where the bug happened v. 8.1.2 ### PHP version(s) where the bug happened PHP 8.1 ### If your bug is related to a module, specify its name and its version - ### Your company or customer's name goes here (if applicable). _No response_

​Multistore: Incorrect creation of a Root category in the activated multistore context.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34979/comments

https://github.com/PrestaShop/PrestaShop/issues/34979

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ​Multistore: Incorrect creation of a Root category in the activated multistore context. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello. I would like to present a problem that I have seen in PrestaShop and not in other platforms and which I consider to be a problem of the functioning and management of root categories in Multistore: In the context of a MultiStore ... once the root category has been established in the "Multistore Tree" settings menu, this category should become the base category (root) of the entire subsite, of the Multistore, which is then only the sub categories (in the photo "Home-1) will be visible on the site If an admin in the Multistore presses "ADD new root category" in the context in which he is logged in/entered into his subsite (not in "All stores", as in the photo)... it should be created inside the Folder previously defined by us, and not in the basic Root category of the basic category structure ... If you want to insert other base categories into the Root, just select "All stores" from the top menu and you should only be able to insert categories into the root base from here (how it already works now) ! Today, if I am in the Group and the menu for managing a single shop as in the photo, if I press Root category... this is automatically inserted into the Root base and not into the root devised by me for my shop in the multistore which for many other third-party modules is a defect/problem... it creates categories which are then not visible in the shop due to their inclusion in the Root base of the Multistore...  ### Expected behavior How could I make a change in the code to make "Home-1" become the basic root category of my shop (1.Tech ...) in my case (in the photo) ... without being able to be bypassed by any other addon third and be seen by everyone as the root category of my shop "1.Tech ... "? In Advanced parameter > Multistore tree > 1.Tech ... I have already set "Home-1" as Category root ... Even if like Template, shop has become the new root, for many modu les that work with the creation of categories (import from CSV) nothing changes, saving continues to be carried out in the old Root base of the Multistore ### Steps to reproduce - ### PrestaShop version(s) where the bug happened v. 8.1.2 ### PHP version(s) where the bug happened PHP 8.1 ### If your bug is related to a module, specify its name and its version - ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Your current PrestaShop version: 1.7.8.11 Your current PHP version: 7.4.33 Latest official version for major channel.: 8.1 stable - (8.1.3) Info from log.txt /* PHP:update_null_values(); */</div> [2024-01-04 17:54:47] Updating database schema... [2024-01-04 17:54:47] 17:54:47 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "Unknown column type "tinyint" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information." ["exception" => Doctrine\DBAL\Exception { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => "Unknown column type "tinyint" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."] [2024-01-04 17:54:47] In DBALException.php line 282: [2024-01-04 17:54:47] [2024-01-04 17:54:47] Unknown column type "tinyint" requested. Any Doctrine type that you use has [2024-01-04 17:54:47] to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a [2024-01-04 17:54:47] list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). [2024-01-04 17:54:47] If this error occurs during database introspection then you might have forg [2024-01-04 17:54:47] otten to register all database types for a Doctrine Type. Use AbstractPlatf [2024-01-04 17:54:47] orm#registerDoctrineTypeMapping() or have your custom types implement Type# [2024-01-04 17:54:47] getMappedDatabaseTypes(). If the type name is empty you might have a proble [2024-01-04 17:54:47] m with the cache or forgot some mapping information. [2024-01-04 17:54:47] [2024-01-04 17:54:47] prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] <command> [2024-01-04 17:54:47] Error during database upgrade. You may need to restore your database. [2024-01-04 17:54:47] Error upgrading Doctrine schema ### Expected behavior _No response_ ### Steps to reproduce 1. start 1 click update 2. Start update ### PrestaShop version(s) where the bug happened from 1.7.8.11 tot 8.1.3 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version N.A. ### Your company or customer's name goes here (if applicable). derks wielersport

Update from 1.7.8.11 to 8.1.3 update database error

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34976/comments

https://github.com/PrestaShop/PrestaShop/issues/34976

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Update from 1.7.8.11 to 8.1.3 update database error Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Your current PrestaShop version: 1.7.8.11 Your current PHP version: 7.4.33 Latest official version for major channel.: 8.1 stable - (8.1.3) Info from log.txt /* PHP:update_null_values(); */</div> [2024-01-04 17:54:47] Updating database schema... [2024-01-04 17:54:47] 17:54:47 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "Unknown column type "tinyint" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information." ["exception" => Doctrine\DBAL\Exception { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => "Unknown column type "tinyint" requested. Any Doctrine type that you use has to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). If this error occurs during database introspection then you might have forgotten to register all database types for a Doctrine Type. Use AbstractPlatform#registerDoctrineTypeMapping() or have your custom types implement Type#getMappedDatabaseTypes(). If the type name is empty you might have a problem with the cache or forgot some mapping information."] [2024-01-04 17:54:47] In DBALException.php line 282: [2024-01-04 17:54:47] [2024-01-04 17:54:47] Unknown column type "tinyint" requested. Any Doctrine type that you use has [2024-01-04 17:54:47] to be registered with \Doctrine\DBAL\Types\Type::addType(). You can get a [2024-01-04 17:54:47] list of all the known types with \Doctrine\DBAL\Types\Type::getTypesMap(). [2024-01-04 17:54:47] If this error occurs during database introspection then you might have forg [2024-01-04 17:54:47] otten to register all database types for a Doctrine Type. Use AbstractPlatf [2024-01-04 17:54:47] orm#registerDoctrineTypeMapping() or have your custom types implement Type# [2024-01-04 17:54:47] getMappedDatabaseTypes(). If the type name is empty you might have a proble [2024-01-04 17:54:47] m with the cache or forgot some mapping information. [2024-01-04 17:54:47] [2024-01-04 17:54:47] prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] <command> [2024-01-04 17:54:47] Error during database upgrade. You may need to restore your database. [2024-01-04 17:54:47] Error upgrading Doctrine schema ### Expected behavior _No response_ ### Steps to reproduce 1. start 1 click update 2. Start update ### PrestaShop version(s) where the bug happened from 1.7.8.11 tot 8.1.3 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version N.A. ### Your company or customer's name goes here (if applicable). derks wielersport --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When Importing Store Contacts with the import tool, the fields hours is not required. However, if this field is not included in the csv file, then the db get a bad value stored and when trying to edit the store contact you get the error "count(): Argument #1 ($value) must be of type Countable|array, null given" ### Expected behavior When importing store contacts I expect to be able to edit them. ### Steps to reproduce 1. Go to Import feature and select to import store contacts 2. upload the attached file and match the fields [storecontacts.csv](https://github.com/PrestaShop/PrestaShop/files/13831504/storecontacts.csv) 3. complete the import- 4. Go to Store Contacts, you should now have a new store contact named Test 5. Edit the store contact Test ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Prestaworks AB

Store contact import can insert bad data in DB

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34974/comments

https://github.com/PrestaShop/PrestaShop/issues/34974

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Store contact import can insert bad data in DB Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When Importing Store Contacts with the import tool, the fields hours is not required. However, if this field is not included in the csv file, then the db get a bad value stored and when trying to edit the store contact you get the error "count(): Argument #1 ($value) must be of type Countable|array, null given" ### Expected behavior When importing store contacts I expect to be able to edit them. ### Steps to reproduce 1. Go to Import feature and select to import store contacts 2. upload the attached file and match the fields [storecontacts.csv](https://github.com/PrestaShop/PrestaShop/files/13831504/storecontacts.csv) 3. complete the import- 4. Go to Store Contacts, you should now have a new store contact named Test 5. Edit the store contact Test ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Prestaworks AB --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I add a comment and a rating to a product, the stars flash the standard rating (3 stars). It should not. Only the rating that I put to the product should be displayed. Tested on hummingbirg and classic themes. https://github.com/PrestaShop/PrestaShop/assets/16019289/e27e61ab-3b25-4848-bd45-89a559d0653c ### Expected behavior The stars should not flash the standard rating. ### Steps to reproduce 1. In FO, sign into your customer account 2. Open a product page > Click Write a review 3. Choose a rating star ≠ 3 4. Add Title and Review > Send 5. See the stars displayed 3 for a moment :x: ### PrestaShop version(s) where the bug happened 8.0.x, 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Product Comments v6.0.2 ### Your company or customer's name goes here (if applicable). _No response_

productcomments - Rating stars flash the wrong rating while adding a comment

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34970/comments

https://github.com/PrestaShop/PrestaShop/issues/34970

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : productcomments - Rating stars flash the wrong rating while adding a comment Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I add a comment and a rating to a product, the stars flash the standard rating (3 stars). It should not. Only the rating that I put to the product should be displayed. Tested on hummingbirg and classic themes. https://github.com/PrestaShop/PrestaShop/assets/16019289/e27e61ab-3b25-4848-bd45-89a559d0653c ### Expected behavior The stars should not flash the standard rating. ### Steps to reproduce 1. In FO, sign into your customer account 2. Open a product page > Click Write a review 3. Choose a rating star ≠ 3 4. Add Title and Review > Send 5. See the stars displayed 3 for a moment :x: ### PrestaShop version(s) where the bug happened 8.0.x, 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Product Comments v6.0.2 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [x] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When a customer sends a message from an order in FO, characters `<` and `>` are not displayed properly in BO, the html entity is displayed instead. It only does that when the character is alone, not when used in a html tag like `<div>`. This happening following a security PR that sets `isCleanHtml` as a validation method in the `OrderMessage` object model on the `message` field. It appears that when an object model has a field configured with `isCleanHtml` as a `validate` property, it also runs `HTMLPurifier` on the content of the field. This could be the reason (to be verified). ### Expected behavior `<` and `>` should be displayed correctly in the message on the order page in BO. ### Steps to reproduce 1. In FO, create an order 2. Once order is finished, go on the order page in FO, and send a message containing the character `<` alone (not a html tag like `<div>`, this will work) 3. In BO, go to the order you just created and check the message ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1

character < and > are not displayed correctly in order messages in back office

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34968/comments

https://github.com/PrestaShop/PrestaShop/issues/34968

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : character < and > are not displayed correctly in order messages in back office Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [x] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When a customer sends a message from an order in FO, characters `<` and `>` are not displayed properly in BO, the html entity is displayed instead. It only does that when the character is alone, not when used in a html tag like `<div>`. This happening following a security PR that sets `isCleanHtml` as a validation method in the `OrderMessage` object model on the `message` field. It appears that when an object model has a field configured with `isCleanHtml` as a `validate` property, it also runs `HTMLPurifier` on the content of the field. This could be the reason (to be verified). ### Expected behavior `<` and `>` should be displayed correctly in the message on the order page in BO. ### Steps to reproduce 1. In FO, create an order 2. Once order is finished, go on the order page in FO, and send a message containing the character `<` alone (not a html tag like `<div>`, this will work) 3. In BO, go to the order you just created and check the message ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1 --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Advanced Parameters -> Import For example, if you select "Products" to import, the "Available fields" on the right and the "Download sample csv files" on the lower right do not completely correspond. # Optional and optional default values are not marked, and required items are not marked. Which items can be ignored, and what the default value is if ignored, are currently not clearly marked, and all required fields are not completely marked. # Categories (x,y,z...) Feature (Name:Value:Position:Customized) I don't know how to use these, can I only enter ID, or can I also enter text? There is no demonstration in the example, so I don't know how to use it. Please add a complete CSV sample file. # Import -> Match your data There is no correct and complete automatic correspondence. ``` fputcsv($fp, ['ID', 'Active (0/1)', 'Name*', 'Categories (x,y,z...)', 'Price tax excluded', 'Price tax included', 'On sale (0/1)', 'Discount percent', 'Discount from (yyyy-mm-dd)', 'Discount to (yyyy-mm-dd)', 'Reference #', 'Supplier', 'Brand', 'Quantity', 'Minimal quantity', 'Visibility', 'Summary', 'Description', 'Tags (x,y,z...)', 'Meta title', 'Meta keywords', 'Meta description', 'Available for order (0 = No, 1 = Yes)', 'Show price (0 = No, 1 = Yes)', 'Image URLs (x,y,z...)', 'Delete existing images (0 = No, 1 = Yes)', 'Feature (Name:Value:Position:Customized)']); ``` Even though I have generated the CSV exactly according to "Available fields", when it comes to "Match your data", there are still some data corresponding errors. ### Expected behavior Looking forward to CSV import being simpler and easier to use. It's currently too complex, too difficult to understand, there are no adequate and perfect demonstrations, and it's too time-consuming. ### Steps to reproduce 1.Advanced Parameters -> Import 2.Select "Products" to import 3.Match your data ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

CSV import related issues

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34967/comments

https://github.com/PrestaShop/PrestaShop/issues/34967

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CSV import related issues Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Advanced Parameters -> Import For example, if you select "Products" to import, the "Available fields" on the right and the "Download sample csv files" on the lower right do not completely correspond. # Optional and optional default values are not marked, and required items are not marked. Which items can be ignored, and what the default value is if ignored, are currently not clearly marked, and all required fields are not completely marked. # Categories (x,y,z...) Feature (Name:Value:Position:Customized) I don't know how to use these, can I only enter ID, or can I also enter text? There is no demonstration in the example, so I don't know how to use it. Please add a complete CSV sample file. # Import -> Match your data There is no correct and complete automatic correspondence. ``` fputcsv($fp, ['ID', 'Active (0/1)', 'Name*', 'Categories (x,y,z...)', 'Price tax excluded', 'Price tax included', 'On sale (0/1)', 'Discount percent', 'Discount from (yyyy-mm-dd)', 'Discount to (yyyy-mm-dd)', 'Reference #', 'Supplier', 'Brand', 'Quantity', 'Minimal quantity', 'Visibility', 'Summary', 'Description', 'Tags (x,y,z...)', 'Meta title', 'Meta keywords', 'Meta description', 'Available for order (0 = No, 1 = Yes)', 'Show price (0 = No, 1 = Yes)', 'Image URLs (x,y,z...)', 'Delete existing images (0 = No, 1 = Yes)', 'Feature (Name:Value:Position:Customized)']); ``` Even though I have generated the CSV exactly according to "Available fields", when it comes to "Match your data", there are still some data corresponding errors. ### Expected behavior Looking forward to CSV import being simpler and easier to use. It's currently too complex, too difficult to understand, there are no adequate and perfect demonstrations, and it's too time-consuming. ### Steps to reproduce 1.Advanced Parameters -> Import 2.Select "Products" to import 3.Match your data ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  Advanced Parameters -> Import, import products, the progress bar displays the HTML source code and should be displayed as a progress percentage value. ### Expected behavior _No response_ ### Steps to reproduce 1.Advanced Parameters -> Import 2.import products 3.The progress bar displays the HTML source code and should be displayed as a progress percentage value. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Advanced Parameters -> Import, import products, the progress bar displays the HTML source code and should be displayed as a progress percentage value.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34966/comments

https://github.com/PrestaShop/PrestaShop/issues/34966

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Advanced Parameters -> Import, import products, the progress bar displays the HTML source code and should be displayed as a progress percentage value. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  Advanced Parameters -> Import, import products, the progress bar displays the HTML source code and should be displayed as a progress percentage value. ### Expected behavior _No response_ ### Steps to reproduce 1.Advanced Parameters -> Import 2.import products 3.The progress bar displays the HTML source code and should be displayed as a progress percentage value. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments On my prestashop site www.doro.cy I have an issue with the menu on mobile phone. When I click on the menu it doesn't open the menu items but just refreshes the current page. This happens on every page. ### Expected behavior Clicking on Menu button should open all menu items ### Steps to reproduce 1. Open www.doro.cy on your mobile phone 2. Click on the yellow menu button ### PrestaShop version(s) where the bug happened 1.7.6.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). adscore

Menu button on mobile not working

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34963/comments

https://github.com/PrestaShop/PrestaShop/issues/34963

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Menu button on mobile not working Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments On my prestashop site www.doro.cy I have an issue with the menu on mobile phone. When I click on the menu it doesn't open the menu items but just refreshes the current page. This happens on every page. ### Expected behavior Clicking on Menu button should open all menu items ### Steps to reproduce 1. Open www.doro.cy on your mobile phone 2. Click on the yellow menu button ### PrestaShop version(s) where the bug happened 1.7.6.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). adscore --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Your current PrestaShop version: 1.7.8.10 Your current PHP version: 7.4.33 Latest official version for minor channel.: 1.7.8 stable - (1.7.8.11) from log.txt [2024-01-03 19:08:21] [INTERNAL] /var/www/vhosts/xxxxxxxxxxxxxx/httpdocs/src/PrestaShopBundle/Form/Admin/Extension/ModifyAllShopsExtension.php line 49 - 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) ### Expected behavior expected update of the database ### Steps to reproduce Update was done via 1-click-update V5.0.0 ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version NA ### Your company or customer's name goes here (if applicable). derks-wielersport

Update 1.7.8.10 to 1.7.8.11 update database error

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34962/comments

https://github.com/PrestaShop/PrestaShop/issues/34962

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Update 1.7.8.10 to 1.7.8.11 update database error Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Your current PrestaShop version: 1.7.8.10 Your current PHP version: 7.4.33 Latest official version for minor channel.: 1.7.8 stable - (1.7.8.11) from log.txt [2024-01-03 19:08:21] [INTERNAL] /var/www/vhosts/xxxxxxxxxxxxxx/httpdocs/src/PrestaShopBundle/Form/Admin/Extension/ModifyAllShopsExtension.php line 49 - 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) ### Expected behavior expected update of the database ### Steps to reproduce Update was done via 1-click-update V5.0.0 ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version NA ### Your company or customer's name goes here (if applicable). derks-wielersport --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The **Status** of upgrade finish is clean without errors. No possibility to access backoffice: It gives 500 error After activating debug mode, I think this is the cause: Warning: Zend OPcache API is restricted by "restrict_api" configuration directive Also downgrading is failed. So only one solution: Restauration day-1 with OVH..... ### Expected behavior We must have a website that works after upgrade ### Steps to reproduce Do a simple upgrade from 8.1.2 to 8.1.3 ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Failed upgrade from 8.1.2 to 8.1.3

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34961/comments

https://github.com/PrestaShop/PrestaShop/issues/34961

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Failed upgrade from 8.1.2 to 8.1.3 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The **Status** of upgrade finish is clean without errors. No possibility to access backoffice: It gives 500 error After activating debug mode, I think this is the cause: Warning: Zend OPcache API is restricted by "restrict_api" configuration directive Also downgrading is failed. So only one solution: Restauration day-1 with OVH..... ### Expected behavior We must have a website that works after upgrade ### Steps to reproduce Do a simple upgrade from 8.1.2 to 8.1.3 ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Sometimes, when a customer logs in back, with a non empty cart, an error occurs about precision. Here are the details ``` <!--StartFragment--> (1/1) ContextErrorExceptionNotice: Trying to get property 'precision' of non-object -- in Context.php line 498 at ContextCore->getComputingPrecision() in Product.php line 5685 at ProductCore::getProductProperties(2, array('id_product_attribute' => 0, 'id_product' => '7779', 'cart_quantity' => '2', 'id_shop' => '1', 'id_customization' => null, 'name' => 'Product n° 12', 'is_virtual' => '0', 'description_short' => '<ul><li>point of description d\'ifferent".</li></ul>', 'available_now' => '', 'available_later' => '', 'id_category_default' => '21225', 'id_supplier' => '4', 'id_manufacturer' => '3', 'manufacturer_name' => 'Amazon', 'on_sale' => '1', 'ecotax' => '0.000000', 'additional_shipping_cost' => '0.000000', 'available_for_order' => '1', 'show_price' => '1', 'price' => '600.320000', 'active' => '1', 'unity' => '', 'unit_price_ratio' => '0.000000', 'quantity_available' => '7', 'width' => '38.000000', 'height' => '43.000000', 'depth' => '22.000000', 'out_of_stock' => '2', 'weight' => '21.000000', 'available_date' => '0000-00-00', 'date_add' => '2022-12-16 12:10:15', 'date_upd' => '2023-12-19 00:52:24', 'quantity' => '7', 'link_rewrite' => 'product-n-12', 'category' => 'best-sellers', 'unique_id' => '0000007679000000000084120', 'id_address_delivery' => '8412', 'advanced_stock_management' => '1', 'supplier_reference' => 'VX18', 'customization_quantity' => null, 'price_attribute' => null, 'ecotax_attr' => null, 'reference' => 'VX18', 'weight_attribute' => null, 'ean13' => '', 'isbn' => '', 'upc' => '', 'mpn' => '', 'minimal_quantity' => '1', 'wholesale_price' => '0.000000', 'id_image' => '3641471', 'legend' => 'Product n° 12', 'reduction_type' => 'percentage', 'is_gift' => false, 'cust_attri' => 'test 2', 'stocks_details' => array(array(array('id_warehouse' => '1', 'physical_quantity' => '7', 'name' => 'Amazon FR', 'delivery_time' => '', 'location' => '', 'id_address' => '13', 'country' => 'France', 'available_quantity' => 6, 'reserved_quantity' => 0), array('id_warehouse' => '2', 'physical_quantity' => '0', 'name' => 'Amazon BE', 'delivery_time' => '', 'location' => '', 'id_address' => '14', 'country' => 'Belgique', 'available_quantity' => 0, 'reserved_quantity' => 0))), 'stock_be' => 0, 'stock_fr' => 6, 'allow_oosp' => 1, 'cover_image_id' => '3641471', 'category_name' => 'Best sellers', 'link' => 'https://www.mywebsite.com/best-sellers/product-n-12-7779.html', 'attribute_price' => 0, 'price_tax_exc' => 497.541758)) <!--EndFragment--> ``` It doesn't happen with all customers or with the same products in cart. How can i fix it ? ### Expected behavior No error for the customer after log in back. ### Steps to reproduce 1. log in to customer account 2. add some products with decimal in price (with VAT ok) 3. leave the session ending by itself 4. log in back to the website ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

ContextErrorException Notice: Trying to get property 'precision' of non-object

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34960/comments

https://github.com/PrestaShop/PrestaShop/issues/34960

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ContextErrorException Notice: Trying to get property 'precision' of non-object Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Sometimes, when a customer logs in back, with a non empty cart, an error occurs about precision. Here are the details ``` <!--StartFragment--> (1/1) ContextErrorExceptionNotice: Trying to get property 'precision' of non-object -- in Context.php line 498 at ContextCore->getComputingPrecision() in Product.php line 5685 at ProductCore::getProductProperties(2, array('id_product_attribute' => 0, 'id_product' => '7779', 'cart_quantity' => '2', 'id_shop' => '1', 'id_customization' => null, 'name' => 'Product n° 12', 'is_virtual' => '0', 'description_short' => '<ul><li>point of description d\'ifferent".</li></ul>', 'available_now' => '', 'available_later' => '', 'id_category_default' => '21225', 'id_supplier' => '4', 'id_manufacturer' => '3', 'manufacturer_name' => 'Amazon', 'on_sale' => '1', 'ecotax' => '0.000000', 'additional_shipping_cost' => '0.000000', 'available_for_order' => '1', 'show_price' => '1', 'price' => '600.320000', 'active' => '1', 'unity' => '', 'unit_price_ratio' => '0.000000', 'quantity_available' => '7', 'width' => '38.000000', 'height' => '43.000000', 'depth' => '22.000000', 'out_of_stock' => '2', 'weight' => '21.000000', 'available_date' => '0000-00-00', 'date_add' => '2022-12-16 12:10:15', 'date_upd' => '2023-12-19 00:52:24', 'quantity' => '7', 'link_rewrite' => 'product-n-12', 'category' => 'best-sellers', 'unique_id' => '0000007679000000000084120', 'id_address_delivery' => '8412', 'advanced_stock_management' => '1', 'supplier_reference' => 'VX18', 'customization_quantity' => null, 'price_attribute' => null, 'ecotax_attr' => null, 'reference' => 'VX18', 'weight_attribute' => null, 'ean13' => '', 'isbn' => '', 'upc' => '', 'mpn' => '', 'minimal_quantity' => '1', 'wholesale_price' => '0.000000', 'id_image' => '3641471', 'legend' => 'Product n° 12', 'reduction_type' => 'percentage', 'is_gift' => false, 'cust_attri' => 'test 2', 'stocks_details' => array(array(array('id_warehouse' => '1', 'physical_quantity' => '7', 'name' => 'Amazon FR', 'delivery_time' => '', 'location' => '', 'id_address' => '13', 'country' => 'France', 'available_quantity' => 6, 'reserved_quantity' => 0), array('id_warehouse' => '2', 'physical_quantity' => '0', 'name' => 'Amazon BE', 'delivery_time' => '', 'location' => '', 'id_address' => '14', 'country' => 'Belgique', 'available_quantity' => 0, 'reserved_quantity' => 0))), 'stock_be' => 0, 'stock_fr' => 6, 'allow_oosp' => 1, 'cover_image_id' => '3641471', 'category_name' => 'Best sellers', 'link' => 'https://www.mywebsite.com/best-sellers/product-n-12-7779.html', 'attribute_price' => 0, 'price_tax_exc' => 497.541758)) <!--EndFragment--> ``` It doesn't happen with all customers or with the same products in cart. How can i fix it ? ### Expected behavior No error for the customer after log in back. ### Steps to reproduce 1. log in to customer account 2. add some products with decimal in price (with VAT ok) 3. leave the session ending by itself 4. log in back to the website ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello When you place an order with a voucher code, if you have to make a refund it generates a credit slip with the wrong numbers. The voucher code is not taken into account and so the credit slip total is wrong. Ex : You place an order of 100€ with a voucher of 20€. The customer pays 80€. You do the refund and the credit slip indicates 100€ and not 80€ as the customer paid. ### Expected behavior The credit slip should be equal to the total paid discounts/vouchers included. ### Steps to reproduce 1. place an order with a voucher code 2. in the BO, do a partial refund with credit slip generated 3. open the PDF credit slip. You'll see that the total doesn't take in consigeration the voucher code. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ITIS Commerce

Error in credit slip with voucher code

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34958/comments

https://github.com/PrestaShop/PrestaShop/issues/34958

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error in credit slip with voucher code Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello When you place an order with a voucher code, if you have to make a refund it generates a credit slip with the wrong numbers. The voucher code is not taken into account and so the credit slip total is wrong. Ex : You place an order of 100€ with a voucher of 20€. The customer pays 80€. You do the refund and the credit slip indicates 100€ and not 80€ as the customer paid. ### Expected behavior The credit slip should be equal to the total paid discounts/vouchers included. ### Steps to reproduce 1. place an order with a voucher code 2. in the BO, do a partial refund with credit slip generated 3. open the PDF credit slip. You'll see that the total doesn't take in consigeration the voucher code. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ITIS Commerce --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments download from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.2/prestashop_8.1.2.zip When I log in to the management backend and click on the menu Oh no! The mobile version of this page is not available yet. Please use a desktop computer to access this page, until is adapted to mobile. Thank you. ### Expected behavior _No response_ ### Steps to reproduce install admin lack of template ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

8.1.2 The backend management page is missing this and that. Is this software free

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34943/comments

https://github.com/PrestaShop/PrestaShop/issues/34943

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : 8.1.2 The backend management page is missing this and that. Is this software free Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments download from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.2/prestashop_8.1.2.zip When I log in to the management backend and click on the menu Oh no! The mobile version of this page is not available yet. Please use a desktop computer to access this page, until is adapted to mobile. Thank you. ### Expected behavior _No response_ ### Steps to reproduce install admin lack of template ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments This is the bug, to save carrier data: Prestashop Technical Error: Details: Error thrown: [object Object] Text status: error When saving or attempting to save carriers, the system is bugged and the error mentioned above appears, although SSL is already active throughout the site and does not allow enabling SSL, this happens on one of the servers that was tested, on the other simply was forced to reproduce the error I never save the carriers, now if I delete it and recreate it, it saves but when I start to put a lot of data it gets bugged. ### Expected behavior _No response_ ### Steps to reproduce 1. Go to "Carriers" 2. Modify or create a carrier (put all informations: price, ranges,...) 3. Click "Save" ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Cléo Créations

Saving carrier Technical Error: Details: Error thrown: [object Object] Text status: error

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34937/comments

https://github.com/PrestaShop/PrestaShop/issues/34937

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Saving carrier Technical Error: Details: Error thrown: [object Object] Text status: error Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments This is the bug, to save carrier data: Prestashop Technical Error: Details: Error thrown: [object Object] Text status: error When saving or attempting to save carriers, the system is bugged and the error mentioned above appears, although SSL is already active throughout the site and does not allow enabling SSL, this happens on one of the servers that was tested, on the other simply was forced to reproduce the error I never save the carriers, now if I delete it and recreate it, it saves but when I start to put a lot of data it gets bugged. ### Expected behavior _No response_ ### Steps to reproduce 1. Go to "Carriers" 2. Modify or create a carrier (put all informations: price, ranges,...) 3. Click "Save" ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Cléo Créations --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  Good morning, Following an update of the website. To move from version 1.6.8 to version 1.7.8 we encountered a problem. The update was carried out without problems but a few minutes later the Prestashop page no longer works and displays an error 500. ### Expected behavior _No response_ ### Steps to reproduce After updating Prestashop, error message 500 was displayed. ### PrestaShop version(s) where the bug happened 1.6.8 / 1.7.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). StreetOfWorker

HTTP ERROR 500

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34936/comments

https://github.com/PrestaShop/PrestaShop/issues/34936

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : HTTP ERROR 500 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  Good morning, Following an update of the website. To move from version 1.6.8 to version 1.7.8 we encountered a problem. The update was carried out without problems but a few minutes later the Prestashop page no longer works and displays an error 500. ### Expected behavior _No response_ ### Steps to reproduce After updating Prestashop, error message 500 was displayed. ### PrestaShop version(s) where the bug happened 1.6.8 / 1.7.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). StreetOfWorker --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments With Prestashop 8.1.1, I created a new virtual product and attached a file to download. The problem is that it won't download. https://github.com/PrestaShop/PrestaShop/assets/16019289/e414ffce-1c93-4d5d-934c-d1f58881e37d Here's the configuration of the virtual attached file : <img width="796" alt="Screenshot 2024-01-03 at 14 38 23" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2dadf42b-fbe2-4897-afc1-4c3aee7a63a3"> It only downloads correctly if I don't add the following : - Number of allowed downloads - Expiration date - Number of days ### Expected behavior I should be able to download my product. ### Steps to reproduce 1. Go to BO > Advanced Parameters > Configure your email to receive them 2. Enable Add downloadable file > Add a download to a virtual product 3. Add Number of allowed downloads = 1 4. Add Number of days = 5 5. In FO > Log into a customer account 6. Add this product to your cart > Process to checkout 7. In BO > Change status to Payment accepted 8. In FO > Check details or order 9. Download your file > Error "Expiration date has passed, you cannot download this product" ❌ 10. In your email check the email "The virtual product that you bought is available for download" 11. Click on the download link :x: ### PrestaShop version(s) where the bug happened 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Can't download a virtual product because "Expiration date has passed, you cannot download this product."

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34935/comments

https://github.com/PrestaShop/PrestaShop/issues/34935

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Can't download a virtual product because "Expiration date has passed, you cannot download this product." Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments With Prestashop 8.1.1, I created a new virtual product and attached a file to download. The problem is that it won't download. https://github.com/PrestaShop/PrestaShop/assets/16019289/e414ffce-1c93-4d5d-934c-d1f58881e37d Here's the configuration of the virtual attached file : <img width="796" alt="Screenshot 2024-01-03 at 14 38 23" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2dadf42b-fbe2-4897-afc1-4c3aee7a63a3"> It only downloads correctly if I don't add the following : - Number of allowed downloads - Expiration date - Number of days ### Expected behavior I should be able to download my product. ### Steps to reproduce 1. Go to BO > Advanced Parameters > Configure your email to receive them 2. Enable Add downloadable file > Add a download to a virtual product 3. Add Number of allowed downloads = 1 4. Add Number of days = 5 5. In FO > Log into a customer account 6. Add this product to your cart > Process to checkout 7. In BO > Change status to Payment accepted 8. In FO > Check details or order 9. Download your file > Error "Expiration date has passed, you cannot download this product" ❌ 10. In your email check the email "The virtual product that you bought is available for download" 11. Click on the download link :x: ### PrestaShop version(s) where the bug happened 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments ello everyone, I would like to bring to everyone's attention a PHP Warning present in the log, precisely two: PHP Warning: Undefined array key 1 in /home//public_html/webservice/dispatcher.php on line 44 PHP Warning: Undefined array key 1 in /home//public_html/webservice/dispatcher.php on line 50 The Prestashop version is 8.1.1 with PHP 8.1. I also attach a screen. <img width="792" alt="Screenshot 2023-12-29 alle 10 12 47" src="https://github.com/PrestaShop/PrestaShop/assets/47750947/21ef1c8d-0465-4141-a2c4-7335d07fe010"> ### Expected behavior _No response_ ### Steps to reproduce Check error_log_php in your root and you will see the errors. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Max - MDP

PHP Warning: Undefined array key 1 in dispatcher.php

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34932/comments

https://github.com/PrestaShop/PrestaShop/issues/34932

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PHP Warning: Undefined array key 1 in dispatcher.php Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments ello everyone, I would like to bring to everyone's attention a PHP Warning present in the log, precisely two: PHP Warning: Undefined array key 1 in /home//public_html/webservice/dispatcher.php on line 44 PHP Warning: Undefined array key 1 in /home//public_html/webservice/dispatcher.php on line 50 The Prestashop version is 8.1.1 with PHP 8.1. I also attach a screen. <img width="792" alt="Screenshot 2023-12-29 alle 10 12 47" src="https://github.com/PrestaShop/PrestaShop/assets/47750947/21ef1c8d-0465-4141-a2c4-7335d07fe010"> ### Expected behavior _No response_ ### Steps to reproduce Check error_log_php in your root and you will see the errors. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Max - MDP --- end body --- comments : --- start comments --- --- end comments ---

All issues related to **`Merchandise Return`**: ### Bugs - [ ] #34922 - [x] #35362 ### Features ## Fixed ### Bugs

[EPIC] - Merchandise Return

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34926/comments

https://github.com/PrestaShop/PrestaShop/issues/34926

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [EPIC] - Merchandise Return Issue date: --- start body --- All issues related to **`Merchandise Return`**: ### Bugs - [ ] #34922 - [x] #35362 ### Features ## Fixed ### Bugs --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments _Old product page:_ maximum characters for meta title and meta description is 70 and 160 chars. Although **more characters can be saved** when old product page is used. The table accepts 128 characters for meta title and 512 characters for meta description. _New Product Page:_ maximum characters for meta title and meta description is 70 and 160 chars. **Saving page with more characters can't not be done** and **information is showing under the form informing than only 70/160 characters can be used**. The different behaviours of those two pages, old vs. new, is complicating updating products in the future. When using old page, longer titles and longer desctiptions can be saved. Those longer titles and desctiptions can be showed in the New Product Page, but then the product can't be updated with other info, unless the title and description has been decreased to 70/160 characters. For some older shop owners this will complictate things, they will have to update all meta titles and description in order to use the New Product Page, just to be able to update simple things like stock amount. This change in the New PRoduct Page will be a massive problems for many updated shop and owners. Should it be better if the **product can be saved anyway**, but **with warning text that recommendation** is that meta title should be maximum 70 chars and meta description 160 chars? ### Expected behavior x the number of characters in the field. - for the meta_title Display on the bottom of the field : "x of 70 characters used (recommended)" Validation server: 255 characters, like on the previous page. - for the meta_description Display on the bottom of the field : "x of 160 characters used (recommended)" Validation server: 512 characters, like on the previous page. ### Steps to reproduce Swithing between old and new product page, shows clearly what can be saved. ### PrestaShop version(s) where the bug happened 8.1.0, 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

New Product Page vs. Old product page; maxchar for meta title and description

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34925/comments

https://github.com/PrestaShop/PrestaShop/issues/34925

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : New Product Page vs. Old product page; maxchar for meta title and description Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments _Old product page:_ maximum characters for meta title and meta description is 70 and 160 chars. Although **more characters can be saved** when old product page is used. The table accepts 128 characters for meta title and 512 characters for meta description. _New Product Page:_ maximum characters for meta title and meta description is 70 and 160 chars. **Saving page with more characters can't not be done** and **information is showing under the form informing than only 70/160 characters can be used**. The different behaviours of those two pages, old vs. new, is complicating updating products in the future. When using old page, longer titles and longer desctiptions can be saved. Those longer titles and desctiptions can be showed in the New Product Page, but then the product can't be updated with other info, unless the title and description has been decreased to 70/160 characters. For some older shop owners this will complictate things, they will have to update all meta titles and description in order to use the New Product Page, just to be able to update simple things like stock amount. This change in the New PRoduct Page will be a massive problems for many updated shop and owners. Should it be better if the **product can be saved anyway**, but **with warning text that recommendation** is that meta title should be maximum 70 chars and meta description 160 chars? ### Expected behavior x the number of characters in the field. - for the meta_title Display on the bottom of the field : "x of 70 characters used (recommended)" Validation server: 255 characters, like on the previous page. - for the meta_description Display on the bottom of the field : "x of 160 characters used (recommended)" Validation server: 512 characters, like on the previous page. ### Steps to reproduce Swithing between old and new product page, shows clearly what can be saved. ### PrestaShop version(s) where the bug happened 8.1.0, 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Monitoring view filtering will always scroll you at the page top as you filter results. This is pretty frustrating as you have to scroll for each page view. ### Expected behavior What is expected : - When you apply a filter on a grid, you expect, at the page reload, to be scrolled back to the filtered grid ( in our case, the second grid : "List of products with combinations but without available quantities for sale" ) ### Steps to reproduce How to : - Have a shop with multiple empty categories, and products with combinations but without available quantities for sale ( at least 20 ) - Limit items per page to 10 - Go to the second grid : "List of products with combinations but without available quantities for sale" and go to page 2 of the grid - The page reloads, you are now on top of the page. ### PrestaShop version(s) where the bug happened 1.7.7.4+ ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Evolutive

Monitoring page grid filterting will not scroll back to wanted grid

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34924/comments

https://github.com/PrestaShop/PrestaShop/issues/34924

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Monitoring page grid filterting will not scroll back to wanted grid Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Monitoring view filtering will always scroll you at the page top as you filter results. This is pretty frustrating as you have to scroll for each page view. ### Expected behavior What is expected : - When you apply a filter on a grid, you expect, at the page reload, to be scrolled back to the filtered grid ( in our case, the second grid : "List of products with combinations but without available quantities for sale" ) ### Steps to reproduce How to : - Have a shop with multiple empty categories, and products with combinations but without available quantities for sale ( at least 20 ) - Limit items per page to 10 - Go to the second grid : "List of products with combinations but without available quantities for sale" and go to page 2 of the grid - The page reloads, you are now on top of the page. ### PrestaShop version(s) where the bug happened 1.7.7.4+ ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Evolutive --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I click on a specific message on the notification, I'm redirect to the list of messages instead of the specific customer thread. https://github.com/PrestaShop/PrestaShop/assets/16019289/7ef5cd97-615c-4401-a4a9-34b9f472f2a1 ### Expected behavior It should redirect to the customer thread page ### Steps to reproduce 1. In FO > Contactform > Send a message 2. Go to BO > Click on notification center > Messages 3. Click on the latest message 4. The Customer Service page is displayed instead of the Customer Thread page :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_faviconnotificationbo ### Your company or customer's name goes here (if applicable). _No response_

ps_faviconnotificationbo - Customer notifications doesn't redirect to the right customer thread

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34923/comments

https://github.com/PrestaShop/PrestaShop/issues/34923

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_faviconnotificationbo - Customer notifications doesn't redirect to the right customer thread Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I click on a specific message on the notification, I'm redirect to the list of messages instead of the specific customer thread. https://github.com/PrestaShop/PrestaShop/assets/16019289/7ef5cd97-615c-4401-a4a9-34b9f472f2a1 ### Expected behavior It should redirect to the customer thread page ### Steps to reproduce 1. In FO > Contactform > Send a message 2. Go to BO > Click on notification center > Messages 3. Click on the latest message 4. The Customer Service page is displayed instead of the Customer Thread page :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_faviconnotificationbo ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can't delete a product from a Merchandise return without having a red message [recording(21).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/4e0dc6bb-6159-4ef7-9f6a-b464fa91372b) https://github.com/PrestaShop/PrestaShop/assets/16019289/60826f89-fde7-4ed7-b2da-753a6d0edc7f ### Expected behavior I should be able to delete a product without red alert ### Steps to reproduce 1. Enable returns in BO > Customer Service > Merchandise returns 2. Go to FO > Log into your customer > Complete an order with two different order 3. Go to BO > Change status of latest order to Delivered 4. Go to FO > Customer account > Order Detail > Ask for a return of all the product 5. Go to BO > Merchandise returns > Delete the product 6. Message error : warning Invalid security token 7. Clic on "I understand the risks [...]" 8. Clic Again on the last merchandise return > Delete the product 9. Message error : You need at least one product. displayed ### PrestaShop version(s) where the bug happened 1.7.8.9, 8.0.x, 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PS

BO - Merchandise return - I can't Delete a product in RMA without a "special" request on the BO

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34922/comments

https://github.com/PrestaShop/PrestaShop/issues/34922

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - Merchandise return - I can't Delete a product in RMA without a "special" request on the BO Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can't delete a product from a Merchandise return without having a red message [recording(21).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/4e0dc6bb-6159-4ef7-9f6a-b464fa91372b) https://github.com/PrestaShop/PrestaShop/assets/16019289/60826f89-fde7-4ed7-b2da-753a6d0edc7f ### Expected behavior I should be able to delete a product without red alert ### Steps to reproduce 1. Enable returns in BO > Customer Service > Merchandise returns 2. Go to FO > Log into your customer > Complete an order with two different order 3. Go to BO > Change status of latest order to Delivered 4. Go to FO > Customer account > Order Detail > Ask for a return of all the product 5. Go to BO > Merchandise returns > Delete the product 6. Message error : warning Invalid security token 7. Clic on "I understand the risks [...]" 8. Clic Again on the last merchandise return > Delete the product 9. Message error : You need at least one product. displayed ### PrestaShop version(s) where the bug happened 1.7.8.9, 8.0.x, 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PS --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am having difficulties on uploading new sliders for my webpage PRESTASHOP version 1.7.6.8  Everytime i try to upload a photo it crashes at gives me that error! ### Expected behavior _No response_ ### Steps to reproduce 1 Moduls 2 ps_imageslider 3 configure 4 upload a new photo 5 Save ### PrestaShop version(s) where the bug happened 1.7.6.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version ps_imageslider ### Your company or customer's name goes here (if applicable). Elektro-Tek

Slider Image not Uploading

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34921/comments

https://github.com/PrestaShop/PrestaShop/issues/34921

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Slider Image not Uploading Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am having difficulties on uploading new sliders for my webpage PRESTASHOP version 1.7.6.8  Everytime i try to upload a photo it crashes at gives me that error! ### Expected behavior _No response_ ### Steps to reproduce 1 Moduls 2 ps_imageslider 3 configure 4 upload a new photo 5 Save ### PrestaShop version(s) where the bug happened 1.7.6.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version ps_imageslider ### Your company or customer's name goes here (if applicable). Elektro-Tek --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After turning ON webp images, some goods will start to display different images than they should. When I turn OFF webp and only JPG images remain on, everything is fine. It does not do this for all images, max 7% of all! I still haven't found the reason why I do this with some pictures. When I turn off webp, everything is fine. Tested on about 3000 products. Tested on the basic template. ### Expected behavior _No response_ ### Steps to reproduce 1. turn off webp 2. go to web site and load products on products lists with images 3. turn ON webp 4. open next window and load products on products lists with images 5. compare both products lists 6. some products have different pictures than they should have ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Prestashop 8.1.2 - show different images when turn ON webp images

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34920/comments

https://github.com/PrestaShop/PrestaShop/issues/34920

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 8.1.2 - show different images when turn ON webp images Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After turning ON webp images, some goods will start to display different images than they should. When I turn OFF webp and only JPG images remain on, everything is fine. It does not do this for all images, max 7% of all! I still haven't found the reason why I do this with some pictures. When I turn off webp, everything is fine. Tested on about 3000 products. Tested on the basic template. ### Expected behavior _No response_ ### Steps to reproduce 1. turn off webp 2. go to web site and load products on products lists with images 3. turn ON webp 4. open next window and load products on products lists with images 5. compare both products lists 6. some products have different pictures than they should have ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When i trying delete all catalogs and i select delete product when it does not have category then that error appear. This problem happened during trying delete demo categories who put after install. "No route found for "GET /sell/catalog/categories/bulk-delete": Method Not Allowed (Allow: POST)"  ### Expected behavior The categories will be deleted along with the products without any error messages. ### Steps to reproduce 1. Go to Prestashop Backoffice 2. Then go to Catalog/Categories 3. Check all categories 4. Click "mass activites" and delete 5. Select "If they don't have other categories, I want to remove them too." ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Error "no route" during trying delete all catalogs with all products

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34918/comments

https://github.com/PrestaShop/PrestaShop/issues/34918

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error "no route" during trying delete all catalogs with all products Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When i trying delete all catalogs and i select delete product when it does not have category then that error appear. This problem happened during trying delete demo categories who put after install. "No route found for "GET /sell/catalog/categories/bulk-delete": Method Not Allowed (Allow: POST)"  ### Expected behavior The categories will be deleted along with the products without any error messages. ### Steps to reproduce 1. Go to Prestashop Backoffice 2. Then go to Catalog/Categories 3. Check all categories 4. Click "mass activites" and delete 5. Select "If they don't have other categories, I want to remove them too." ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I installed PrestaShop 8.1.2 and the "Home" and "Settings" tabs are empty: https://prnt.sc/HbWEK5u2tfum https://prnt.sc/ex2TkoUhQA3T I tested this in clean PrestaShop on localhost, my server and the customer server and in all shops I see the same problem. ### Expected behavior These tabs should display data or should be removed. ### Steps to reproduce 1.Install clean PrestaShop 8.1.2 on the server. 2.Open the "Home" and "Settings" tab. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

PrestaShop 8.1.2 "Home" and "Settings" tabs in backoffice are empty

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34916/comments

https://github.com/PrestaShop/PrestaShop/issues/34916

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop 8.1.2 "Home" and "Settings" tabs in backoffice are empty Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I installed PrestaShop 8.1.2 and the "Home" and "Settings" tabs are empty: https://prnt.sc/HbWEK5u2tfum https://prnt.sc/ex2TkoUhQA3T I tested this in clean PrestaShop on localhost, my server and the customer server and in all shops I see the same problem. ### Expected behavior These tabs should display data or should be removed. ### Steps to reproduce 1.Install clean PrestaShop 8.1.2 on the server. 2.Open the "Home" and "Settings" tab. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I installed Mail Alerts module on Prestashop 1.8.9 and I receive emails about new orders and stock shortages but I don't receive emails about product returns when a customer enters their email address to request a product return. My SMTP configuration is correct because all emails are sent except for product returns. How can I correct this problem? Thank you ### Expected behavior _No response_ ### Steps to reproduce 1. Install Mail alerts module (v2.4.2 on Prestashop 1.7.8.9) 2. Go in Mail alerts module from back-office 3. Click on the "Returns" toggle to enable it 4. Fill "Send to" field by your email address 5. On the store front, go to the product page of the product that is out of stock, enter your email address and click on the button to be notified 6. Put the product in stock and check your emails ### PrestaShop version(s) where the bug happened 1.7.8.9 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version ps_emailalerts v2.4.2 ### Your company or customer's name goes here (if applicable). _No response_

Emails for product returns not received

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34915/comments

https://github.com/PrestaShop/PrestaShop/issues/34915

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Emails for product returns not received Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I installed Mail Alerts module on Prestashop 1.8.9 and I receive emails about new orders and stock shortages but I don't receive emails about product returns when a customer enters their email address to request a product return. My SMTP configuration is correct because all emails are sent except for product returns. How can I correct this problem? Thank you ### Expected behavior _No response_ ### Steps to reproduce 1. Install Mail alerts module (v2.4.2 on Prestashop 1.7.8.9) 2. Go in Mail alerts module from back-office 3. Click on the "Returns" toggle to enable it 4. Fill "Send to" field by your email address 5. On the store front, go to the product page of the product that is out of stock, enter your email address and click on the button to be notified 6. Put the product in stock and check your emails ### PrestaShop version(s) where the bug happened 1.7.8.9 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version ps_emailalerts v2.4.2 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Just installed the latest version 8.1.2 on a live server I logged into the back office On the next request, it logs me out. It does not matter how, clicking on a link or reloading the page logs me out ### Expected behavior _No response_ ### Steps to reproduce 1. just install the latest version 2. try to login ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Fresh Install 8.1.2 logs out of admin panel for no reason

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34909/comments

https://github.com/PrestaShop/PrestaShop/issues/34909

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Fresh Install 8.1.2 logs out of admin panel for no reason Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Just installed the latest version 8.1.2 on a live server I logged into the back office On the next request, it logs me out. It does not matter how, clicking on a link or reloading the page logs me out ### Expected behavior _No response_ ### Steps to reproduce 1. just install the latest version 2. try to login ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments PHP Deprecated: ucfirst(): Passing null to parameter #1 ($string) of type string is deprecated in /classes/controller/AdminController.php on line 987 PHP Deprecated: ucfirst(): Passing null to parameter #1 ($string) of type string is deprecated in /classes/controller/AdminController.php on line 988 PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /vendor/twig/twig/src/Loader/FilesystemLoader.php on line 134 PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135 ### Expected behavior _No response_ ### Steps to reproduce 1. Go to server error_log ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

PHP 8.1 compatibility errors

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34906/comments

https://github.com/PrestaShop/PrestaShop/issues/34906

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PHP 8.1 compatibility errors Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments PHP Deprecated: ucfirst(): Passing null to parameter #1 ($string) of type string is deprecated in /classes/controller/AdminController.php on line 987 PHP Deprecated: ucfirst(): Passing null to parameter #1 ($string) of type string is deprecated in /classes/controller/AdminController.php on line 988 PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /vendor/twig/twig/src/Loader/FilesystemLoader.php on line 134 PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135 ### Expected behavior _No response_ ### Steps to reproduce 1. Go to server error_log ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

Following the [rebranding](https://build.prestashop-project.org/news/2023/new-project-branding/) of project websites, here is a list of small items to fix/finish ## Project website Live website https://www.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/open-source This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] On homepage, the button "Latest releases" should be given the same style as the button "Get started" on prestashop.com: a pattern behind the button, and a little animation  ## Project blog Live website https://build.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/prestaShop.github.io/ This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] Some texts on the homepage have a #222222 (grey) color -> modify it to have #000000 (black) - [x] The horizontal line between each blog post on the homepage is also grey -> make it black - [x] In the "Continue reading" buttons (see below) the text is not centered **"Continue reading" buttons**  ## Developer documentation Live website https://devdocs.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/devdocs-site This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] Update the meta image ; use https://build.prestashop-project.org/assets/images/theme/meta-logo-build-2024.png - fixed by https://github.com/PrestaShop/devdocs-site/pull/30 - [x] The h1 on homepage "Developer Documentation" uses the Prestafont, but it does not enable the illustrated letters because it has a `letter-spacing` of -1px applied. Remove the `letter-spacing` of -1px to enable Prestafont illustrated letters - fixed by https://github.com/PrestaShop/ps-docs-theme/pull/50 - [x] Some texts on the homepage have a #222222 (grey) color -> modify it to have #000000 - [x] Convert the buttons on the homepage from "background white, color black" to "background black, color white" to (see below) **Buttons:**  ## TopContributors Live website https://contributors.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/TopContributors This website is built using Nuxt. Read the README to see how to run it locally. - [x] Update the favicon, use the favicon of https://build.prestashop-project.org/ - fixed by https://github.com/PrestaShop/TopContributors/pull/120 - [x] The title "Top contribution achievements" has a shadow -> remove it - [x] Make the subtitle "Welcome! This page is dedicated to the code..." bold - [x] On the arrow, the word "contributions" in light blue (see below) is tiny ; make it bold - [x] Below the arrow, in "experts" and "enthusiasts" section (see below), some texts are very thin so it's hard to read them ; make it bold **The word "contributions" in light blue on the arrow:**  **"Experts" and "enthusiasts" section:** 

Small bugs on project websites following rebranding

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34900/comments

https://github.com/PrestaShop/PrestaShop/issues/34900

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Small bugs on project websites following rebranding Issue date: --- start body --- Following the [rebranding](https://build.prestashop-project.org/news/2023/new-project-branding/) of project websites, here is a list of small items to fix/finish ## Project website Live website https://www.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/open-source This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] On homepage, the button "Latest releases" should be given the same style as the button "Get started" on prestashop.com: a pattern behind the button, and a little animation  ## Project blog Live website https://build.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/prestaShop.github.io/ This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] Some texts on the homepage have a #222222 (grey) color -> modify it to have #000000 (black) - [x] The horizontal line between each blog post on the homepage is also grey -> make it black - [x] In the "Continue reading" buttons (see below) the text is not centered **"Continue reading" buttons**  ## Developer documentation Live website https://devdocs.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/devdocs-site This website is built using GitHub Actions and Hugo 0.121.1 . Read the README to run the site locally. - [x] Update the meta image ; use https://build.prestashop-project.org/assets/images/theme/meta-logo-build-2024.png - fixed by https://github.com/PrestaShop/devdocs-site/pull/30 - [x] The h1 on homepage "Developer Documentation" uses the Prestafont, but it does not enable the illustrated letters because it has a `letter-spacing` of -1px applied. Remove the `letter-spacing` of -1px to enable Prestafont illustrated letters - fixed by https://github.com/PrestaShop/ps-docs-theme/pull/50 - [x] Some texts on the homepage have a #222222 (grey) color -> modify it to have #000000 - [x] Convert the buttons on the homepage from "background white, color black" to "background black, color white" to (see below) **Buttons:**  ## TopContributors Live website https://contributors.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/TopContributors This website is built using Nuxt. Read the README to see how to run it locally. - [x] Update the favicon, use the favicon of https://build.prestashop-project.org/ - fixed by https://github.com/PrestaShop/TopContributors/pull/120 - [x] The title "Top contribution achievements" has a shadow -> remove it - [x] Make the subtitle "Welcome! This page is dedicated to the code..." bold - [x] On the arrow, the word "contributions" in light blue (see below) is tiny ; make it bold - [x] Below the arrow, in "experts" and "enthusiasts" section (see below), some texts are very thin so it's hard to read them ; make it bold **The word "contributions" in light blue on the arrow:**  **"Experts" and "enthusiasts" section:**  --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments See steps to reproduce ### Expected behavior It should not attempt to load the language pack if it does not exist in `/js/tiny_mce/langs` folder. On legacy pages, this was taken care of and it loaded english - `$this->tpl_vars['iso'] = file_exists(_PS_CORE_DIR_ . '/js/tiny_mce/langs/' . $iso . '.js') ? $iso : 'en';`. ### Steps to reproduce 1. Install develop, maybe happens also on 8.1.x. 2. Import United Kingdom localization pack, choose only Languages. 3. Change your BO language to English. 4. Go edit any product or visit any modern page with tinymce editor. 5. See errors in browser console and in the page corner.   ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Errors on page and in console due to tinymce language file

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34899/comments

https://github.com/PrestaShop/PrestaShop/issues/34899

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Errors on page and in console due to tinymce language file Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments See steps to reproduce ### Expected behavior It should not attempt to load the language pack if it does not exist in `/js/tiny_mce/langs` folder. On legacy pages, this was taken care of and it loaded english - `$this->tpl_vars['iso'] = file_exists(_PS_CORE_DIR_ . '/js/tiny_mce/langs/' . $iso . '.js') ? $iso : 'en';`. ### Steps to reproduce 1. Install develop, maybe happens also on 8.1.x. 2. Import United Kingdom localization pack, choose only Languages. 3. Change your BO language to English. 4. Go edit any product or visit any modern page with tinymce editor. 5. See errors in browser console and in the page corner.   ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When we create a multi-shop PrestaShop with different domain names for the 2 stores, we end up with errors when generating the product images on the product sheets in the stores' back-office.  In the browser console, we can see the following error : `Uncaught DOMException: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The canvas has been tainted by cross-origin data.` ⚠️ Please note that this case is possible if, when creating a new store, we enter an **existing domain name** in the store's URL fields! The problem is also possible when we create a new product. When we import an image, it is correctly added with its visual, then as soon as we save our changes and reload the page, we get the same error again. For your information, when we run the same tests on a server with 2 existing but different domain names. We end up with the same errors. However, the domain names are correctly configured and point to the root of the PrestaShop folder on the server. (This is where we discovered the bug). Multi-shop configuration (below) :   ### Expected behavior The aim of creating a multi-store PrestaShop would be to be able to view the product images of 2 stores configured with different domain names without having problems displaying product images, as we can do with PrestaShop v1.7.8.X. ### Steps to reproduce 1. Activate PrestaShop multi-shop mode 2. Create a new store 3. Once the new store has been created, you can click on "Click here to define a URL for this store". 4. In the "Shop URL" section of the domain fields, enter an existing domain name. 5. Empty or leave empty the Virtual URL and Final URL fields, then click on the "Save" button to save your changes. 6. Next, go to Catalog > Products, select your new store and click on a product with a correctly displayed image https://github.com/PrestaShop/PrestaShop/assets/90344180/0959eb1d-6bda-44f1-9478-f70bcae81938 ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ScaleDEV

Product Images does not work in BO multishop with different domain names

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34898/comments

https://github.com/PrestaShop/PrestaShop/issues/34898

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Product Images does not work in BO multishop with different domain names Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When we create a multi-shop PrestaShop with different domain names for the 2 stores, we end up with errors when generating the product images on the product sheets in the stores' back-office.  In the browser console, we can see the following error : `Uncaught DOMException: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The canvas has been tainted by cross-origin data.` ⚠️ Please note that this case is possible if, when creating a new store, we enter an **existing domain name** in the store's URL fields! The problem is also possible when we create a new product. When we import an image, it is correctly added with its visual, then as soon as we save our changes and reload the page, we get the same error again. For your information, when we run the same tests on a server with 2 existing but different domain names. We end up with the same errors. However, the domain names are correctly configured and point to the root of the PrestaShop folder on the server. (This is where we discovered the bug). Multi-shop configuration (below) :   ### Expected behavior The aim of creating a multi-store PrestaShop would be to be able to view the product images of 2 stores configured with different domain names without having problems displaying product images, as we can do with PrestaShop v1.7.8.X. ### Steps to reproduce 1. Activate PrestaShop multi-shop mode 2. Create a new store 3. Once the new store has been created, you can click on "Click here to define a URL for this store". 4. In the "Shop URL" section of the domain fields, enter an existing domain name. 5. Empty or leave empty the Virtual URL and Final URL fields, then click on the "Save" button to save your changes. 6. Next, go to Catalog > Products, select your new store and click on a product with a correctly displayed image https://github.com/PrestaShop/PrestaShop/assets/90344180/0959eb1d-6bda-44f1-9478-f70bcae81938 ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ScaleDEV --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrading from 1.7.8.7 to latest 8.1.2, I don't see the New Product Page options anywhere. I can't find any information either that this is only availböe for new installations and not upgrades. Under "New & Experimental Features" I only find one option: Multiple image formats. ### Expected behavior _No response_ ### Steps to reproduce New & Experimental Features ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

New Product Page not available after upgrade from 1.7.8.7

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34897/comments

https://github.com/PrestaShop/PrestaShop/issues/34897

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : New Product Page not available after upgrade from 1.7.8.7 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrading from 1.7.8.7 to latest 8.1.2, I don't see the New Product Page options anywhere. I can't find any information either that this is only availböe for new installations and not upgrades. Under "New & Experimental Features" I only find one option: Multiple image formats. ### Expected behavior _No response_ ### Steps to reproduce New & Experimental Features ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments It is not posible to paste many tags att the same time on new product page. On old product you can paste as meny tags as you want att once.   ### Expected behavior Tags on new product page should work as tags on old product page ### Steps to reproduce Copy one list of tags with comma separated values, longer then five words, an try to paste it in tags field you will not get all your words pasted there. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version ### Your company or customer's name goes here (if applicable). Zoran

Tags on new product page not exeptintg "paste" You can only paste two words att the time.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34896/comments

https://github.com/PrestaShop/PrestaShop/issues/34896

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Tags on new product page not exeptintg "paste" You can only paste two words att the time. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments It is not posible to paste many tags att the same time on new product page. On old product you can paste as meny tags as you want att once.   ### Expected behavior Tags on new product page should work as tags on old product page ### Steps to reproduce Copy one list of tags with comma separated values, longer then five words, an try to paste it in tags field you will not get all your words pasted there. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version ### Your company or customer's name goes here (if applicable). Zoran --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There are many issues on the migrated features page. - Extra message that features are enabled on store. It wasn't there on the legacy page and just wastes space. - Feature grid rows are not clickable. - Feature value grid rows are not clickable. - When adding new feature value and clicking cancel, you are always redirected to feature listing, instead of value listing. ### Expected behavior _No response_ ### Steps to reproduce 1. Get develop branch. 2. Check Catalog > Attributes and features ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Bugs on migrated features and feature values page

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34889/comments

https://github.com/PrestaShop/PrestaShop/issues/34889

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Bugs on migrated features and feature values page Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There are many issues on the migrated features page. - Extra message that features are enabled on store. It wasn't there on the legacy page and just wastes space. - Feature grid rows are not clickable. - Feature value grid rows are not clickable. - When adding new feature value and clicking cancel, you are always redirected to feature listing, instead of value listing. ### Expected behavior _No response_ ### Steps to reproduce 1. Get develop branch. 2. Check Catalog > Attributes and features ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Adding new product has a problem with uploading product picture.     I have tested it on my two different servers, and on two different servers of two different web-hosting providers. I had same problem on every server. ### Expected behavior Pictures should be visible and clickable. That you can click on picture set as default or delete it. As it is now it is not possible. ### Steps to reproduce Ad new product with one or more pictures. Save it Exit from product Try to edit this product, to change default picture if you have uploaded two pictures. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Zoran

Adding new product has a problem with uploading product picture.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34886/comments

https://github.com/PrestaShop/PrestaShop/issues/34886

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adding new product has a problem with uploading product picture. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Adding new product has a problem with uploading product picture.     I have tested it on my two different servers, and on two different servers of two different web-hosting providers. I had same problem on every server. ### Expected behavior Pictures should be visible and clickable. That you can click on picture set as default or delete it. As it is now it is not possible. ### Steps to reproduce Ad new product with one or more pictures. Save it Exit from product Try to edit this product, to change default picture if you have uploaded two pictures. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Zoran --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I do an upgrade from 1.7.8.11 to 8.0.5, I've this error on every migrated page, on the other I can go on it :  there is a video of the full proces : [recording(10).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/2621803e-f053-4944-bf0b-dc9042792241) ### Expected behavior I wish I could go on migrated page when I do my upgrade ### Steps to reproduce 1. fresh install of Prestashop 1.7.8.11 2. Install Autoupgrade (currently 5.0.0) 3. Go to 1-Click Upgrade tab (or clic on configure at the end of the installation) 4. Put your Zip file and you xml file of prestashop v 8.0.5 on the folder [yourshop]/admin-dev/autoupgrade/download 5. Restart your page of 1-Click Upgrade 6. On the expert mode, select local archive and put the 8.0.5 on it 7. Save it 8. Clic on the button to launch the update 9. At the end of the installation, Connect to the BO with your ID 10. Go to a migrated page like Orders > Orders ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version autoupgrade 5.0.0 ### Your company or customer's name goes here (if applicable). PS

Autoupgrade - From 1.7.8.11 to 8.0.5 - Compile Error from class Attribute

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34885/comments

https://github.com/PrestaShop/PrestaShop/issues/34885

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade - From 1.7.8.11 to 8.0.5 - Compile Error from class Attribute Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I do an upgrade from 1.7.8.11 to 8.0.5, I've this error on every migrated page, on the other I can go on it :  there is a video of the full proces : [recording(10).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/2621803e-f053-4944-bf0b-dc9042792241) ### Expected behavior I wish I could go on migrated page when I do my upgrade ### Steps to reproduce 1. fresh install of Prestashop 1.7.8.11 2. Install Autoupgrade (currently 5.0.0) 3. Go to 1-Click Upgrade tab (or clic on configure at the end of the installation) 4. Put your Zip file and you xml file of prestashop v 8.0.5 on the folder [yourshop]/admin-dev/autoupgrade/download 5. Restart your page of 1-Click Upgrade 6. On the expert mode, select local archive and put the 8.0.5 on it 7. Save it 8. Clic on the button to launch the update 9. At the end of the installation, Connect to the BO with your ID 10. Go to a migrated page like Orders > Orders ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version autoupgrade 5.0.0 ### Your company or customer's name goes here (if applicable). PS --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can't add a discount for a specific category for a customer group if I expand/collapse all my categories. <img width="1440" alt="Screenshot 2023-12-19 at 17 27 51" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/fb3e616c-7098-4254-8431-8875addcd33b"> ### Expected behavior I should be able to add a discount to a specific category easily. ### Steps to reproduce 1. Go to BO > Shop parameters > Customer Settings > Groups tab > Edit Visitor 2. Click "Add a category discount" 3. Click "Expand all" > See Page not found :x: 4. Add 10% discount > Click Add > See an alert Wrong category ID. :x: ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

BO - Customer groups > Error Page not found & Wrong category ID. when trying to display all the categories

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34881/comments

https://github.com/PrestaShop/PrestaShop/issues/34881

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - Customer groups > Error Page not found & Wrong category ID. when trying to display all the categories Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can't add a discount for a specific category for a customer group if I expand/collapse all my categories. <img width="1440" alt="Screenshot 2023-12-19 at 17 27 51" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/fb3e616c-7098-4254-8431-8875addcd33b"> ### Expected behavior I should be able to add a discount to a specific category easily. ### Steps to reproduce 1. Go to BO > Shop parameters > Customer Settings > Groups tab > Edit Visitor 2. Click "Add a category discount" 3. Click "Expand all" > See Page not found :x: 4. Add 10% discount > Click Add > See an alert Wrong category ID. :x: ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The email has [no_sync] at the end of the title. I don't know what it is about. It is not supposed to be there. If I check Design > Email theme > modern > check HTTP of contact email, I don't see the [no_sync] part <img width="1183" alt="Screenshot 2023-12-19 at 16 52 09" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/1ff28cf9-ae83-423e-a8ba-16b144955f8e"> ### Expected behavior Just the simple title should be displayed. ### Steps to reproduce 1. Go to BO > Modules > Edit Contact form module 2. Enable 2nd option Receive customers' messages by email : YES > Save 3. Go to FO > Contact Us > Send a message 4. Go to BO > Advanced parameters > Email 5. See last email sent : [no_sync] at the end of the email :x: ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Contact form v4.4.1 ### Your company or customer's name goes here (if applicable). _No response_

ps_emailalerts - Email title has [no_sync] at the end

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34880/comments

https://github.com/PrestaShop/PrestaShop/issues/34880

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_emailalerts - Email title has [no_sync] at the end Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The email has [no_sync] at the end of the title. I don't know what it is about. It is not supposed to be there. If I check Design > Email theme > modern > check HTTP of contact email, I don't see the [no_sync] part <img width="1183" alt="Screenshot 2023-12-19 at 16 52 09" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/1ff28cf9-ae83-423e-a8ba-16b144955f8e"> ### Expected behavior Just the simple title should be displayed. ### Steps to reproduce 1. Go to BO > Modules > Edit Contact form module 2. Enable 2nd option Receive customers' messages by email : YES > Save 3. Go to FO > Contact Us > Send a message 4. Go to BO > Advanced parameters > Email 5. See last email sent : [no_sync] at the end of the email :x: ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Contact form v4.4.1 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments It's possible to save the column/database matches when importing csv files, however, when loading a saved setting, the display is not updated so the user will not see the correct data that was loaded from the save. ### Expected behavior the display should show the same data as the hidden selectors in the background. ### Steps to reproduce 1. go to advanced settings -> import 2. select to import products 3. make a few changes to the column matches and save. 4. go back to advanced settings -> import 5. select to import products 6. load the saved matches from step 3. 7. Nothing changes in the display. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Prestaworks AB

loading import field matches does not show settings to user.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34876/comments

https://github.com/PrestaShop/PrestaShop/issues/34876

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : loading import field matches does not show settings to user. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments It's possible to save the column/database matches when importing csv files, however, when loading a saved setting, the display is not updated so the user will not see the correct data that was loaded from the save. ### Expected behavior the display should show the same data as the hidden selectors in the background. ### Steps to reproduce 1. go to advanced settings -> import 2. select to import products 3. make a few changes to the column matches and save. 4. go back to advanced settings -> import 5. select to import products 6. load the saved matches from step 3. 7. Nothing changes in the display. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Prestaworks AB --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments In Catalog statistics, when I try to edit a product, the new page product is displayed instead of the product page that I want to edit. https://github.com/PrestaShop/PrestaShop/assets/16019289/2f6b6594-64d4-4655-a314-cfaa940d1043 ### Expected behavior It should displayed the edition page of the product ### Steps to reproduce 1. Go to BO > Stats > Catalog statistcs 2. Scroll down to Products never purchased 3. Click Edit 4. New product page is displayed :x: should display the product to edit ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Catalog statistics v2.0.4 ### Your company or customer's name goes here (if applicable). _No response_

statscatalog - Edit product button displays the new page product instead of the specific product that I want to edit

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34874/comments

https://github.com/PrestaShop/PrestaShop/issues/34874

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : statscatalog - Edit product button displays the new page product instead of the specific product that I want to edit Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments In Catalog statistics, when I try to edit a product, the new page product is displayed instead of the product page that I want to edit. https://github.com/PrestaShop/PrestaShop/assets/16019289/2f6b6594-64d4-4655-a314-cfaa940d1043 ### Expected behavior It should displayed the edition page of the product ### Steps to reproduce 1. Go to BO > Stats > Catalog statistcs 2. Scroll down to Products never purchased 3. Click Edit 4. New product page is displayed :x: should display the product to edit ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version Catalog statistics v2.0.4 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments on wire payment we get blank page on validation page! ` Fatal error: Uncaught Error: Call to undefined function proc_open() in /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:291 Stack trace: #0 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php(54): Swift_Transport_StreamBuffer->establishProcessConnection() #1 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(143): Swift_Transport_StreamBuffer->initialize() #2 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SendmailTransport.php(50): Swift_Transport_AbstractSmtpTransport->start() #3 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php(65): Swift_Transport_SendmailTransport->start() #4 /home/sepidal/domains/sepidal.com/public_html/classes/Mail.php(629): Swift_Mailer->send() #5 /home/sepidal/domains/sepidal.com/public_html/classes/order/OrderHistory.php(549): MailCore::send() #6 /home/sepidal/domains/sepidal.com/public_html/classes/order/OrderHistory.php(452): OrderHistoryCore->sendEmail() #7 /home/sepidal/domains/sepidal.com/public_html/classes/PaymentModule.php(575): OrderHistoryCore->addWithemail() #8 /home/sepidal/domains/sepidal.com/public_html/modules/ps_wirepayment/controllers/front/validation.php(63): PaymentModuleCore->validateOrder() #9 /home/sepidal/domains/sepidal.com/public_html/classes/controller/Controller.php(308): Ps_WirepaymentValidationModuleFrontController->postProcess() #10 /home/sepidal/domains/sepidal.com/public_html/classes/Dispatcher.php(510): ControllerCore->run() #11 /home/sepidal/domains/sepidal.com/public_html/index.php(28): DispatcherCore->dispatch() #12 {main} thrown in /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php on line 291` ### Expected behavior wire payment must show bank account detail on last page ### Steps to reproduce 1 order a product 2 select wire payment as payment 3 submit order 4 blank page on /module/ps_wirepayment/validation ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_wirepayment ### Your company or customer's name goes here (if applicable). _No response_

ps_wirepayment show blank page on validation

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34871/comments

https://github.com/PrestaShop/PrestaShop/issues/34871

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_wirepayment show blank page on validation Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments on wire payment we get blank page on validation page! ` Fatal error: Uncaught Error: Call to undefined function proc_open() in /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:291 Stack trace: #0 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php(54): Swift_Transport_StreamBuffer->establishProcessConnection() #1 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(143): Swift_Transport_StreamBuffer->initialize() #2 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SendmailTransport.php(50): Swift_Transport_AbstractSmtpTransport->start() #3 /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php(65): Swift_Transport_SendmailTransport->start() #4 /home/sepidal/domains/sepidal.com/public_html/classes/Mail.php(629): Swift_Mailer->send() #5 /home/sepidal/domains/sepidal.com/public_html/classes/order/OrderHistory.php(549): MailCore::send() #6 /home/sepidal/domains/sepidal.com/public_html/classes/order/OrderHistory.php(452): OrderHistoryCore->sendEmail() #7 /home/sepidal/domains/sepidal.com/public_html/classes/PaymentModule.php(575): OrderHistoryCore->addWithemail() #8 /home/sepidal/domains/sepidal.com/public_html/modules/ps_wirepayment/controllers/front/validation.php(63): PaymentModuleCore->validateOrder() #9 /home/sepidal/domains/sepidal.com/public_html/classes/controller/Controller.php(308): Ps_WirepaymentValidationModuleFrontController->postProcess() #10 /home/sepidal/domains/sepidal.com/public_html/classes/Dispatcher.php(510): ControllerCore->run() #11 /home/sepidal/domains/sepidal.com/public_html/index.php(28): DispatcherCore->dispatch() #12 {main} thrown in /home/sepidal/domains/sepidal.com/public_html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php on line 291` ### Expected behavior wire payment must show bank account detail on last page ### Steps to reproduce 1 order a product 2 select wire payment as payment 3 submit order 4 blank page on /module/ps_wirepayment/validation ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_wirepayment ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Nos visiteurs sont susceptibles de nous contacter via le formulaire de contact : https://www.maison-colibri.com/fr/info/contact Or, lorsqu'ils ajoutent une pj, elle s'affiche, dans le mail depuis le formulaire, comme un lien. Ce lien renvoie vers une page avec une erreur. Le pb se situe dans le HT access. Comment le corriger ? Nom : MAXENCE TEST Email : [maxence.michel@maison-colibri.com](mailto:maxence.michel@maison-colibri.com) Objet : [adv@maison-colibri.com](mailto:adv@maison-colibri.com) Pièce jointe : • http://www.maison-colibri.com/upload/pfg/658048fc16fd2.pdf Message : Bonjour ceci est un test. Pouvez-vous me confirmer en retour de mail que vous arrivez à ouvrir la PJ ? Merci ### Expected behavior La PJ est cliquable et téléchargeable. On peut l'ouvrir sur le navigateur (.pdf) ou le télécharger (.doc / .docx). ### Steps to reproduce 1. Aller sur la page : https://www.maison-colibri.com/fr/info/contact 2. Compléter le formulaire en ajoutant une pj 3. Envoyer le formulaire 4. Recevoir le formulaire (pas possible de reproduire pour vous) ### PrestaShop version(s) where the bug happened v1.7.8.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version prestashop/contactform v4.3.0 ### Your company or customer's name goes here (if applicable). MAISON COLIBRI

Nous recontrons un bug sur la gestion et téléchargement des PJ sur GitHub - PrestaShop/contactform: Adds a contact form to the "Contact us" page

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34869/comments

https://github.com/PrestaShop/PrestaShop/issues/34869

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Nous recontrons un bug sur la gestion et téléchargement des PJ sur GitHub - PrestaShop/contactform: Adds a contact form to the "Contact us" page Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Nos visiteurs sont susceptibles de nous contacter via le formulaire de contact : https://www.maison-colibri.com/fr/info/contact Or, lorsqu'ils ajoutent une pj, elle s'affiche, dans le mail depuis le formulaire, comme un lien. Ce lien renvoie vers une page avec une erreur. Le pb se situe dans le HT access. Comment le corriger ? Nom : MAXENCE TEST Email : [maxence.michel@maison-colibri.com](mailto:maxence.michel@maison-colibri.com) Objet : [adv@maison-colibri.com](mailto:adv@maison-colibri.com) Pièce jointe : • http://www.maison-colibri.com/upload/pfg/658048fc16fd2.pdf Message : Bonjour ceci est un test. Pouvez-vous me confirmer en retour de mail que vous arrivez à ouvrir la PJ ? Merci ### Expected behavior La PJ est cliquable et téléchargeable. On peut l'ouvrir sur le navigateur (.pdf) ou le télécharger (.doc / .docx). ### Steps to reproduce 1. Aller sur la page : https://www.maison-colibri.com/fr/info/contact 2. Compléter le formulaire en ajoutant une pj 3. Envoyer le formulaire 4. Recevoir le formulaire (pas possible de reproduire pour vous) ### PrestaShop version(s) where the bug happened v1.7.8.8 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version prestashop/contactform v4.3.0 ### Your company or customer's name goes here (if applicable). MAISON COLIBRI --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello On each backoffice content load, logs are showing a critical error request.CRITICAL: Uncaught PHP Exception Symfony\Component\Routing\Exception\RouteNotFoundException: "Unable to generate a URL for the named route "admin_logos_index" as such route does not exist." at /home/thiasmax/public_prestashop/thias_skwal_prod/vendor/symfony/symfony/src/Symfony/Component/Routing/Generator/CompiledUrlGenerator.php line 50 {"exception":"[object] (Symfony\\Component\\Routing\\Exception\\RouteNotFoundException(code: 0): Unable to generate a URL for the named route \"admin_logos_index\" as such route does not exist. at /home/thiasmax/public_prestashop/thias_skwal_prod/vendor/symfony/symfony/src/Symfony/Component/Routing/Generator/CompiledUrlGenerator.php:50)"} [] It probably cause the slownesses to load pages on the backoffice I joined a log file containing 2 examples of this issue with other debug and info log link to the critical one [log.txt](https://github.com/PrestaShop/PrestaShop/files/13695176/log.txt) Could you help me to investigate it ? Thanks :-) ### Expected behavior _No response_ ### Steps to reproduce Load the backoffice page after login ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Critical log on each backooffice load

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34862/comments

https://github.com/PrestaShop/PrestaShop/issues/34862

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Critical log on each backooffice load Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello On each backoffice content load, logs are showing a critical error request.CRITICAL: Uncaught PHP Exception Symfony\Component\Routing\Exception\RouteNotFoundException: "Unable to generate a URL for the named route "admin_logos_index" as such route does not exist." at /home/thiasmax/public_prestashop/thias_skwal_prod/vendor/symfony/symfony/src/Symfony/Component/Routing/Generator/CompiledUrlGenerator.php line 50 {"exception":"[object] (Symfony\\Component\\Routing\\Exception\\RouteNotFoundException(code: 0): Unable to generate a URL for the named route \"admin_logos_index\" as such route does not exist. at /home/thiasmax/public_prestashop/thias_skwal_prod/vendor/symfony/symfony/src/Symfony/Component/Routing/Generator/CompiledUrlGenerator.php:50)"} [] It probably cause the slownesses to load pages on the backoffice I joined a log file containing 2 examples of this issue with other debug and info log link to the critical one [log.txt](https://github.com/PrestaShop/PrestaShop/files/13695176/log.txt) Could you help me to investigate it ? Thanks :-) ### Expected behavior _No response_ ### Steps to reproduce Load the backoffice page after login ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, When a module is updated, PrestaShop doesn't update override files. I dont know if this is intentional but I am facing that issue every time i upgrade a module that include changes in override files. I found that [StackOverflow post](https://stackoverflow.com/questions/31681282/how-to-update-class-override-when-upgrading-module-to-new-version-in-prestashop) providing a solution where the module author needs to add some code to trigger update of override files during the update. But most module doesn't implement that solution and override files are never updated. I always have to reset module after update, but we lose all data previously saved when doing a reset. ### Expected behavior When a module is updated, PrestaShop should automatically update override files. ### Steps to reproduce 1. Install a module which has override files 2. Update the module with a new version including changes in the override files 3. See that override files has not been updated ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Module update doesn't update override files

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34861/comments

https://github.com/PrestaShop/PrestaShop/issues/34861

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module update doesn't update override files Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, When a module is updated, PrestaShop doesn't update override files. I dont know if this is intentional but I am facing that issue every time i upgrade a module that include changes in override files. I found that [StackOverflow post](https://stackoverflow.com/questions/31681282/how-to-update-class-override-when-upgrading-module-to-new-version-in-prestashop) providing a solution where the module author needs to add some code to trigger update of override files during the update. But most module doesn't implement that solution and override files are never updated. I always have to reset module after update, but we lose all data previously saved when doing a reset. ### Expected behavior When a module is updated, PrestaShop should automatically update override files. ### Steps to reproduce 1. Install a module which has override files 2. Update the module with a new version including changes in the override files 3. See that override files has not been updated ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi, We built a custom CI/CD pipeline to deploy our PrestaShop projects and for this we use the [`autoupgrade`](https://github.com/PrestaShop/autoupgrade) module to upgrade our project during deployment. ### Expected behavior Our project may contains some custom modules shipped at the same time, and we execute the following command: ``` php modules/autoupgrade/cli-upgrade.php --dir=admin-path --channel=private --action=upgradeModules ``` We expect that command to upgrade all modules requiring an upgrade (= when the version of the module save in the database is different from the actual version of the module). But it looks like no module update happens and we still need to manually update our modules from the admin panel. ### Steps to reproduce 1. install prestashop 2. install a module version 1.0.0 3. change the module version to 1.0.1 by modifying th module code 4. run command line `php modules/autoupgrade/cli-upgrade.php --dir=admin-path --channel=private --action=upgradeModules` 5. See that the module has not been updated ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.0 ### Your company or customer's name goes here (if applicable). _No response_

[autoupgrade] Action `upgradeModules` is not upgrading modules on command line

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34860/comments

https://github.com/PrestaShop/PrestaShop/issues/34860

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [autoupgrade] Action `upgradeModules` is not upgrading modules on command line Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi, We built a custom CI/CD pipeline to deploy our PrestaShop projects and for this we use the [`autoupgrade`](https://github.com/PrestaShop/autoupgrade) module to upgrade our project during deployment. ### Expected behavior Our project may contains some custom modules shipped at the same time, and we execute the following command: ``` php modules/autoupgrade/cli-upgrade.php --dir=admin-path --channel=private --action=upgradeModules ``` We expect that command to upgrade all modules requiring an upgrade (= when the version of the module save in the database is different from the actual version of the module). But it looks like no module update happens and we still need to manually update our modules from the admin panel. ### Steps to reproduce 1. install prestashop 2. install a module version 1.0.0 3. change the module version to 1.0.1 by modifying th module code 4. run command line `php modules/autoupgrade/cli-upgrade.php --dir=admin-path --channel=private --action=upgradeModules` 5. See that the module has not been updated ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.0 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When "Back office token protection" is turned off translations doesn't work at all. ### Expected behavior It must work as normal ### Steps to reproduce 1. Go to backoffice -> Advanced Parameters -> Security 2. Tuen off "Back office token protection" and save 3. Go to International -> Translations 4. Type of translation -> Front Office Translations 5. Select your theme -> Core (no theme selected) 6. Select your language -> English in my case (any if not english) 7. Now click modify:- We expect to load fields with translation option but it doesnot come ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Translation doesn't work when backoffice token is turned off

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34859/comments

https://github.com/PrestaShop/PrestaShop/issues/34859

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Translation doesn't work when backoffice token is turned off Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When "Back office token protection" is turned off translations doesn't work at all. ### Expected behavior It must work as normal ### Steps to reproduce 1. Go to backoffice -> Advanced Parameters -> Security 2. Tuen off "Back office token protection" and save 3. Go to International -> Translations 4. Type of translation -> Front Office Translations 5. Select your theme -> Core (no theme selected) 6. Select your language -> English in my case (any if not english) 7. Now click modify:- We expect to load fields with translation option but it doesnot come ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am trying to create a command in my PrestaShop 1.7 module to generate an order from the client's cart. However, when I attempt to use **$cart->getOrderTotal**, I always encounter a Fatal error. ``` protected function execute(InputInterface $input, OutputInterface $output){ try{ $cart = new Cart(2433); $total = (float)$cart->getOrderTotal(true, Cart::BOTH); $output->writeln('total '. $total); }catch (Exception $e){ $output->writeln('error'. $e->getMessage()); die(); } } ``` Error: ``` Fatal error - #0 /project/classes/Product.php(3623): ToolsCore::displayError() #1 /project/classes/Product.php(5632): ProductCore::getPriceStatic(20, false, 0, 6, NULL, false, true, 1) #2 /project/classes/Cart.php(833): ProductCore::getProductProperties(2, Array) #3 /project/classes/Cart.php(2144): CartCore->getProducts(false, false, NULL, true, false) #4 /project/modules/order_install/src/Command/CheckOrderCreationCommand.php(105): CartCore->getOrderTotal(true, 4) #5 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Command/Command.php(255): order_install\Command\CheckOrderCreationCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #6 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(1010): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #7 /project/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(86): Symfony\Component\Console\Application->doRunCommand(Object(order_install\Command\CheckOrderCreationCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #8 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(255): Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand(Object(order_install\Command\CheckOrderCreationCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #9 /project/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(74): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #10 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(148): Symfony\Bundle\FrameworkBundle\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #11 /project/bin/console(27): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput)) #12 {main} ``` I think the cause is `$context->employee` is always NULL from Command Function : getPriceStatic File: classes/Product.php ``` if (!$id_cart && !isset($context->employee)) { die(Tools::displayError()); } ``` ### Expected behavior _No response_ ### Steps to reproduce Make new Command in each module Try to getOrderTotal of existed Cart You will get the bug ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.3.29 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

$cart->getOrderTotal from module/src/Command

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34858/comments

https://github.com/PrestaShop/PrestaShop/issues/34858

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : $cart->getOrderTotal from module/src/Command Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am trying to create a command in my PrestaShop 1.7 module to generate an order from the client's cart. However, when I attempt to use **$cart->getOrderTotal**, I always encounter a Fatal error. ``` protected function execute(InputInterface $input, OutputInterface $output){ try{ $cart = new Cart(2433); $total = (float)$cart->getOrderTotal(true, Cart::BOTH); $output->writeln('total '. $total); }catch (Exception $e){ $output->writeln('error'. $e->getMessage()); die(); } } ``` Error: ``` Fatal error - #0 /project/classes/Product.php(3623): ToolsCore::displayError() #1 /project/classes/Product.php(5632): ProductCore::getPriceStatic(20, false, 0, 6, NULL, false, true, 1) #2 /project/classes/Cart.php(833): ProductCore::getProductProperties(2, Array) #3 /project/classes/Cart.php(2144): CartCore->getProducts(false, false, NULL, true, false) #4 /project/modules/order_install/src/Command/CheckOrderCreationCommand.php(105): CartCore->getOrderTotal(true, 4) #5 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Command/Command.php(255): order_install\Command\CheckOrderCreationCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #6 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(1010): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #7 /project/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(86): Symfony\Component\Console\Application->doRunCommand(Object(order_install\Command\CheckOrderCreationCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #8 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(255): Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand(Object(order_install\Command\CheckOrderCreationCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #9 /project/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php(74): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #10 /project/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php(148): Symfony\Bundle\FrameworkBundle\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #11 /project/bin/console(27): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput)) #12 {main} ``` I think the cause is `$context->employee` is always NULL from Command Function : getPriceStatic File: classes/Product.php ``` if (!$id_cart && !isset($context->employee)) { die(Tools::displayError()); } ``` ### Expected behavior _No response_ ### Steps to reproduce Make new Command in each module Try to getOrderTotal of existed Cart You will get the bug ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.3.29 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We have set Prestashop 8.1 to debug mode. After that we got error message : Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Container.php:289 Stack trace: #0 /folder/to/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Container.php(231): Symfony\Component\DependencyInjection\Container->make('product_comment...', 1) #1 /folder/to/prestashop/modules/productcomments/productcomments.php(1029): Symfony\Component\DependencyInjection\Container->get('product_comment...') #2 /folder/to/prestashop/modules/productcomments/productcomments.php(1049): ProductComments->getWidgetVariables('displayProductL...', Array) #3 /folder/to/prestashop/classes/Hook.php(1004): ProductComments->renderWidget('displayProductL...', Array) #4 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #5 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #6 /folder/to/prestashop/config/smarty.config.inc.php(205): HookCore::exec('displayProductL...', Array, NULL) #7 /folder/to/prestashop/classes/Smarty/SmartyLazyRegister.php(81): smartyHook(Array, Object(SmartyDevTemplate)) #8 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(196): SmartyLazyRegister->__call('smartyHook', Array) #9 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_362279806657c04100cb126_19422279->callBlock(Object(SmartyDevTemplate)) #10 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_362279806657c04100cb126_19422279), Object(SmartyDevTemplate)) #11 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_362279806657c04100cb126_19422279)) #12 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(287): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_362279806...', 'product_reviews', 0) #13 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_670396815657c04100b3626_90206869->callBlock(Object(SmartyDevTemplate)) #14 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_670396815657c04100b3626_90206869), Object(SmartyDevTemplate)) #15 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_670396815657c04100b3626_90206869)) #16 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(29): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_670396815...', 'product_miniatu...') #17 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c04100cc2a0_15741833(Object(SmartyDevTemplate)) #18 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #19 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #20 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/3d/e2/fb/3de2fb917c69babe598ca8bc6a5d96952160b3d4_2.file.productlist.tpl.cache.php(42): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, true) #21 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041009d187_74148331(Object(SmartyDevTemplate)) #22 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #23 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #24 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/fa/6c/c3/fa6cc378d2942c8857b89d6bca728048c0caeedd_2.module.ps_featuredproductsviewstemplateshookps_featuredproducts.tpl.cache.php(32): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, false) #25 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041007eab9_79755881(Object(SmartyDevTemplate)) #26 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #27 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_updatecache.php(38): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #28 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_cached.php(143): Smarty_Internal_Runtime_UpdateCache->updateCache(Object(Smarty_Template_Cached), Object(SmartyDevTemplate), false) #29 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(212): Smarty_Template_Cached->render(Object(SmartyDevTemplate), false) #30 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 0) #31 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute(Object(SmartyDevTemplate), NULL, NULL, NULL, 0) #32 /folder/to/prestashop/classes/Smarty/SmartyDevTemplate.php(55): Smarty_Internal_TemplateBase->fetch(NULL, NULL, NULL, NULL) #33 /folder/to/prestashop/classes/module/Module.php(2270): SmartyDevTemplateCore->fetch() #34 /folder/to/prestashop/modules/ps_featuredproducts/ps_featuredproducts.php(247): ModuleCore->fetch('module:ps_featu...', 'ps_featuredprod...') #35 /folder/to/prestashop/classes/Hook.php(1004): Ps_FeaturedProducts->renderWidget('displayHome', Array) #36 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #37 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #38 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #39 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #40 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #41 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #42 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/classes/Hook.php:1008 Stack trace: #0 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #1 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #2 /folder/to/prestashop/config/smarty.config.inc.php(205): HookCore::exec('displayProductL...', Array, NULL) #3 /folder/to/prestashop/classes/Smarty/SmartyLazyRegister.php(81): smartyHook(Array, Object(SmartyDevTemplate)) #4 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(196): SmartyLazyRegister->__call('smartyHook', Array) #5 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_362279806657c04100cb126_19422279->callBlock(Object(SmartyDevTemplate)) #6 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_362279806657c04100cb126_19422279), Object(SmartyDevTemplate)) #7 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_362279806657c04100cb126_19422279)) #8 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(287): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_362279806...', 'product_reviews', 0) #9 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_670396815657c04100b3626_90206869->callBlock(Object(SmartyDevTemplate)) #10 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_670396815657c04100b3626_90206869), Object(SmartyDevTemplate)) #11 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_670396815657c04100b3626_90206869)) #12 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(29): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_670396815...', 'product_miniatu...') #13 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c04100cc2a0_15741833(Object(SmartyDevTemplate)) #14 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #15 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #16 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/3d/e2/fb/3de2fb917c69babe598ca8bc6a5d96952160b3d4_2.file.productlist.tpl.cache.php(42): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, true) #17 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041009d187_74148331(Object(SmartyDevTemplate)) #18 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #19 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #20 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/fa/6c/c3/fa6cc378d2942c8857b89d6bca728048c0caeedd_2.module.ps_featuredproductsviewstemplateshookps_featuredproducts.tpl.cache.php(32): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, false) #21 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041007eab9_79755881(Object(SmartyDevTemplate)) #22 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #23 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_updatecache.php(38): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #24 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_cached.php(143): Smarty_Internal_Runtime_UpdateCache->updateCache(Object(Smarty_Template_Cached), Object(SmartyDevTemplate), false) #25 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(212): Smarty_Template_Cached->render(Object(SmartyDevTemplate), false) #26 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 0) #27 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute(Object(SmartyDevTemplate), NULL, NULL, NULL, 0) #28 /folder/to/prestashop/classes/Smarty/SmartyDevTemplate.php(55): Smarty_Internal_TemplateBase->fetch(NULL, NULL, NULL, NULL) #29 /folder/to/prestashop/classes/module/Module.php(2270): SmartyDevTemplateCore->fetch() #30 /folder/to/prestashop/modules/ps_featuredproducts/ps_featuredproducts.php(247): ModuleCore->fetch('module:ps_featu...', 'ps_featuredprod...') #31 /folder/to/prestashop/classes/Hook.php(1004): Ps_FeaturedProducts->renderWidget('displayHome', Array) #32 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #33 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #34 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #35 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #36 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #37 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #38 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/classes/Hook.php:1008 Stack trace: #0 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #1 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #2 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #3 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #4 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #5 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #6 {main} thrown in /folder/to/prestashop/classes/Hook.php on line 1008 We were able to remove the error message by deleting all of the cache: Advanced Parameters -> Performance ### Expected behavior No such error message, and cache automaticly erased, when going to debug mode. ### Steps to reproduce Advanced Parameters -> Performance Debug mode -> Yes Debug profiler -> Yes ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version prestacomments 5.0.3 ### Your company or customer's name goes here (if applicable). _No response_

Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "product_comment_repository".

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34856/comments

https://github.com/PrestaShop/PrestaShop/issues/34856

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "product_comment_repository". Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We have set Prestashop 8.1 to debug mode. After that we got error message : Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Container.php:289 Stack trace: #0 /folder/to/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Container.php(231): Symfony\Component\DependencyInjection\Container->make('product_comment...', 1) #1 /folder/to/prestashop/modules/productcomments/productcomments.php(1029): Symfony\Component\DependencyInjection\Container->get('product_comment...') #2 /folder/to/prestashop/modules/productcomments/productcomments.php(1049): ProductComments->getWidgetVariables('displayProductL...', Array) #3 /folder/to/prestashop/classes/Hook.php(1004): ProductComments->renderWidget('displayProductL...', Array) #4 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #5 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #6 /folder/to/prestashop/config/smarty.config.inc.php(205): HookCore::exec('displayProductL...', Array, NULL) #7 /folder/to/prestashop/classes/Smarty/SmartyLazyRegister.php(81): smartyHook(Array, Object(SmartyDevTemplate)) #8 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(196): SmartyLazyRegister->__call('smartyHook', Array) #9 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_362279806657c04100cb126_19422279->callBlock(Object(SmartyDevTemplate)) #10 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_362279806657c04100cb126_19422279), Object(SmartyDevTemplate)) #11 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_362279806657c04100cb126_19422279)) #12 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(287): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_362279806...', 'product_reviews', 0) #13 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_670396815657c04100b3626_90206869->callBlock(Object(SmartyDevTemplate)) #14 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_670396815657c04100b3626_90206869), Object(SmartyDevTemplate)) #15 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_670396815657c04100b3626_90206869)) #16 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(29): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_670396815...', 'product_miniatu...') #17 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c04100cc2a0_15741833(Object(SmartyDevTemplate)) #18 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #19 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #20 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/3d/e2/fb/3de2fb917c69babe598ca8bc6a5d96952160b3d4_2.file.productlist.tpl.cache.php(42): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, true) #21 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041009d187_74148331(Object(SmartyDevTemplate)) #22 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #23 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #24 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/fa/6c/c3/fa6cc378d2942c8857b89d6bca728048c0caeedd_2.module.ps_featuredproductsviewstemplateshookps_featuredproducts.tpl.cache.php(32): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, false) #25 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041007eab9_79755881(Object(SmartyDevTemplate)) #26 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #27 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_updatecache.php(38): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #28 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_cached.php(143): Smarty_Internal_Runtime_UpdateCache->updateCache(Object(Smarty_Template_Cached), Object(SmartyDevTemplate), false) #29 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(212): Smarty_Template_Cached->render(Object(SmartyDevTemplate), false) #30 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 0) #31 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute(Object(SmartyDevTemplate), NULL, NULL, NULL, 0) #32 /folder/to/prestashop/classes/Smarty/SmartyDevTemplate.php(55): Smarty_Internal_TemplateBase->fetch(NULL, NULL, NULL, NULL) #33 /folder/to/prestashop/classes/module/Module.php(2270): SmartyDevTemplateCore->fetch() #34 /folder/to/prestashop/modules/ps_featuredproducts/ps_featuredproducts.php(247): ModuleCore->fetch('module:ps_featu...', 'ps_featuredprod...') #35 /folder/to/prestashop/classes/Hook.php(1004): Ps_FeaturedProducts->renderWidget('displayHome', Array) #36 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #37 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #38 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #39 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #40 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #41 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #42 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/classes/Hook.php:1008 Stack trace: #0 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #1 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(ProductComments), 'displayProductL...', Array) #2 /folder/to/prestashop/config/smarty.config.inc.php(205): HookCore::exec('displayProductL...', Array, NULL) #3 /folder/to/prestashop/classes/Smarty/SmartyLazyRegister.php(81): smartyHook(Array, Object(SmartyDevTemplate)) #4 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(196): SmartyLazyRegister->__call('smartyHook', Array) #5 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_362279806657c04100cb126_19422279->callBlock(Object(SmartyDevTemplate)) #6 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_362279806657c04100cb126_19422279), Object(SmartyDevTemplate)) #7 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_362279806657c04100cb126_19422279)) #8 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(287): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_362279806...', 'product_reviews', 0) #9 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_670396815657c04100b3626_90206869->callBlock(Object(SmartyDevTemplate)) #10 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock(Object(Block_670396815657c04100b3626_90206869), Object(SmartyDevTemplate)) #11 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process(Object(SmartyDevTemplate), Object(Block_670396815657c04100b3626_90206869)) #12 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/d9/f6/3a/d9f63a9eef01e6e8aefc815b488cef7516a2db57_2.file.product.tpl.cache.php(29): Smarty_Internal_Runtime_Inheritance->instanceBlock(Object(SmartyDevTemplate), 'Block_670396815...', 'product_miniatu...') #13 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c04100cc2a0_15741833(Object(SmartyDevTemplate)) #14 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #15 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #16 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/3d/e2/fb/3de2fb917c69babe598ca8bc6a5d96952160b3d4_2.file.productlist.tpl.cache.php(42): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, true) #17 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041009d187_74148331(Object(SmartyDevTemplate)) #18 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #19 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(384): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #20 /folder/to/prestashop/var/cache/dev/smarty/compile/classic/fa/6c/c3/fa6cc378d2942c8857b89d6bca728048c0caeedd_2.module.ps_featuredproductsviewstemplateshookps_featuredproducts.tpl.cache.php(32): Smarty_Internal_Template->_subTemplateRender('file:catalog/_p...', 'ps_featuredprod...', 'classic', 9999, 31536000, Array, 0, false) #21 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_657c041007eab9_79755881(Object(SmartyDevTemplate)) #22 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(SmartyDevTemplate)) #23 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_updatecache.php(38): Smarty_Template_Compiled->render(Object(SmartyDevTemplate)) #24 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_template_cached.php(143): Smarty_Internal_Runtime_UpdateCache->updateCache(Object(Smarty_Template_Cached), Object(SmartyDevTemplate), false) #25 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(212): Smarty_Template_Cached->render(Object(SmartyDevTemplate), false) #26 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 0) #27 /folder/to/prestashop/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute(Object(SmartyDevTemplate), NULL, NULL, NULL, 0) #28 /folder/to/prestashop/classes/Smarty/SmartyDevTemplate.php(55): Smarty_Internal_TemplateBase->fetch(NULL, NULL, NULL, NULL) #29 /folder/to/prestashop/classes/module/Module.php(2270): SmartyDevTemplateCore->fetch() #30 /folder/to/prestashop/modules/ps_featuredproducts/ps_featuredproducts.php(247): ModuleCore->fetch('module:ps_featu...', 'ps_featuredprod...') #31 /folder/to/prestashop/classes/Hook.php(1004): Ps_FeaturedProducts->renderWidget('displayHome', Array) #32 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #33 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #34 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #35 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #36 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #37 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #38 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: You have requested a non-existent service "product_comment_repository". in /folder/to/prestashop/classes/Hook.php:1008 Stack trace: #0 /folder/to/prestashop/tools/profiling/Hook.php(64): HookCore::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #1 /folder/to/prestashop/classes/Hook.php(948): Hook::coreRenderWidget(Object(Ps_FeaturedProducts), 'displayHome', Array) #2 /folder/to/prestashop/controllers/front/IndexController.php(40): HookCore::exec('displayHome') #3 /folder/to/prestashop/tools/profiling/Controller.php(60): IndexControllerCore->initContent() #4 /folder/to/prestashop/classes/Dispatcher.php(510): Controller->run() #5 /folder/to/prestashop/index.php(28): DispatcherCore->dispatch() #6 {main} thrown in /folder/to/prestashop/classes/Hook.php on line 1008 We were able to remove the error message by deleting all of the cache: Advanced Parameters -> Performance ### Expected behavior No such error message, and cache automaticly erased, when going to debug mode. ### Steps to reproduce Advanced Parameters -> Performance Debug mode -> Yes Debug profiler -> Yes ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version prestacomments 5.0.3 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When we try to update stock from our ERP system over API call it throw an error java.lang.Exception: Update of 80 stocks failed: Connection failed : 500 ; Respond : <?xml version="1.0" encoding="UTF-8"?> <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <errors> <error> <code><![CDATA[133]]></code> <message><![CDATA[You can't update stock that is available ; Request : https://pivovarium.si/api/stock_availables/ at com.metakocka.MetaKockaMain.server.GenericWebShop.PrestaShop.GenericWebShopPrestaShop.updateStock(GenericWebShopPrestaShop.java:749) at com.metakocka.MetaKockaMain.server.GenericWebShop.PrestaShop.GenericWebShopPrestaShop.syncProductStockToEShop(GenericWebShopPrestaShop.java:712) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.eShopSyncManualSync(WebLinksDBImpl.java:2341) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.callMethodOnePerCompany(WebLinksDBImpl.java:395) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.callMethod(WebLinksDBImpl.java:303) at com.metakocka.MetaKockaMain.server.MainServiceImpl.callMethod(MainServiceImpl.java:3021) at com.metakocka.MetaKockaMain.server.MainServiceImpl.callMethod(MainServiceImpl.java:2949) at sun.reflect.GeneratedMethodAccessor1397.invoke(Unknown Source) ### Expected behavior _No response_ ### Steps to reproduce After API call to update stock from our ERP system. ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version API call ### Your company or customer's name goes here (if applicable). _No response_

Updating stock via API call thow error

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34855/comments

https://github.com/PrestaShop/PrestaShop/issues/34855

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Updating stock via API call thow error Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When we try to update stock from our ERP system over API call it throw an error java.lang.Exception: Update of 80 stocks failed: Connection failed : 500 ; Respond : <?xml version="1.0" encoding="UTF-8"?> <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <errors> <error> <code><![CDATA[133]]></code> <message><![CDATA[You can't update stock that is available ; Request : https://pivovarium.si/api/stock_availables/ at com.metakocka.MetaKockaMain.server.GenericWebShop.PrestaShop.GenericWebShopPrestaShop.updateStock(GenericWebShopPrestaShop.java:749) at com.metakocka.MetaKockaMain.server.GenericWebShop.PrestaShop.GenericWebShopPrestaShop.syncProductStockToEShop(GenericWebShopPrestaShop.java:712) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.eShopSyncManualSync(WebLinksDBImpl.java:2341) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.callMethodOnePerCompany(WebLinksDBImpl.java:395) at com.metakocka.MetaKockaMain.server.DBImpl.WebLinksDBImpl.callMethod(WebLinksDBImpl.java:303) at com.metakocka.MetaKockaMain.server.MainServiceImpl.callMethod(MainServiceImpl.java:3021) at com.metakocka.MetaKockaMain.server.MainServiceImpl.callMethod(MainServiceImpl.java:2949) at sun.reflect.GeneratedMethodAccessor1397.invoke(Unknown Source) ### Expected behavior _No response_ ### Steps to reproduce After API call to update stock from our ERP system. ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version API call ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

Depending of the SF version update at least the API Platform v3 blocked by https://github.com/PrestaShop/PrestaShop/issues/34006

Upgrade APIPlatform to version 3

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34854/comments

https://github.com/PrestaShop/PrestaShop/issues/34854

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade APIPlatform to version 3 Issue date: --- start body --- Depending of the SF version update at least the API Platform v3 blocked by https://github.com/PrestaShop/PrestaShop/issues/34006 --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Customers put products on the wish list and they don't appear in the back office Product is well added : <img width="441" alt="Screenshot 2023-12-18 at 12 03 50" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d5c743f4-800a-4f8c-a53b-5663afaf8071"> In BO > Customer page > empty <img width="584" alt="Screenshot 2023-12-18 at 12 03 54" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/45aa260e-bf9b-4350-ab90-ac7551198ef4"> ### Expected behavior In the customer page, the wishlist should be updated with the products added to it. ### Steps to reproduce 1. Go to FO > Log into customer account 2. Add product to wishlist 3. Go to BO > Customer page 4. See Wishlist block is empty ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version blockwishlist v3.0.1 ### Your company or customer's name goes here (if applicable). Arcoíris Mágico Baby Shop

blockwishlist - In BO > Customer page, the wishlist is always empty

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34853/comments

https://github.com/PrestaShop/PrestaShop/issues/34853

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : blockwishlist - In BO > Customer page, the wishlist is always empty Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Customers put products on the wish list and they don't appear in the back office Product is well added : <img width="441" alt="Screenshot 2023-12-18 at 12 03 50" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d5c743f4-800a-4f8c-a53b-5663afaf8071"> In BO > Customer page > empty <img width="584" alt="Screenshot 2023-12-18 at 12 03 54" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/45aa260e-bf9b-4350-ab90-ac7551198ef4"> ### Expected behavior In the customer page, the wishlist should be updated with the products added to it. ### Steps to reproduce 1. Go to FO > Log into customer account 2. Add product to wishlist 3. Go to BO > Customer page 4. See Wishlist block is empty ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version blockwishlist v3.0.1 ### Your company or customer's name goes here (if applicable). Arcoíris Mágico Baby Shop --- end body --- comments : --- start comments --- --- end comments ---

## Description As a PM I don't want MultiShop support into the MVP for API so I need to block it in order that the developper is aware about this limitation #### Spec - **New & Experimental features** On back-office, enabled the "Authorization server" Feature flag as default value. (Handle the autoupgrade) Add new feature flag "Authorization server - Multistore" disabled it by default. Help text: Enable or disable the multistore for the Authorization server. The new feature flag is displayed when "Authorization server" is enabled and when Multishop is enabled - **Authorization server form** When the feature flag "Authorization server - Multistore" is disabled Then on the API access list to display a warning message "The API feature is available as an experimental feature. .... Go to the page blabla" and the API access form Edit and Add is blocked and redirected to the list with the warning message. #### Acceptance test When the multistore is enabled and user edit or add an API access Then the warning is displayed

Display a warning the API access when multistore enabled

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34852/comments

https://github.com/PrestaShop/PrestaShop/issues/34852

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Display a warning the API access when multistore enabled Issue date: --- start body --- ## Description As a PM I don't want MultiShop support into the MVP for API so I need to block it in order that the developper is aware about this limitation #### Spec - **New & Experimental features** On back-office, enabled the "Authorization server" Feature flag as default value. (Handle the autoupgrade) Add new feature flag "Authorization server - Multistore" disabled it by default. Help text: Enable or disable the multistore for the Authorization server. The new feature flag is displayed when "Authorization server" is enabled and when Multishop is enabled - **Authorization server form** When the feature flag "Authorization server - Multistore" is disabled Then on the API access list to display a warning message "The API feature is available as an experimental feature. .... Go to the page blabla" and the API access form Edit and Add is blocked and redirected to the list with the warning message. #### Acceptance test When the multistore is enabled and user edit or add an API access Then the warning is displayed --- end body --- comments : --- start comments --- --- end comments ---

As a Core member I don't want MultiShop support into the MVP for API so I need to block it in order that the developper is aware about this limitation ### Specs - When the FF Authorization Server is disabled Then return 404 - When Multishop is enabled and the feature API multistore is disabled Then Use the request listener but only API URLs that return 404 ### Acceptance test return 404 when Multishop is enabled for any call of the API

Block the API access when Multishop is enabled

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34851/comments

https://github.com/PrestaShop/PrestaShop/issues/34851

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Block the API access when Multishop is enabled Issue date: --- start body --- As a Core member I don't want MultiShop support into the MVP for API so I need to block it in order that the developper is aware about this limitation ### Specs - When the FF Authorization Server is disabled Then return 404 - When Multishop is enabled and the feature API multistore is disabled Then Use the request listener but only API URLs that return 404 ### Acceptance test return 404 when Multishop is enabled for any call of the API --- end body --- comments : --- start comments --- --- end comments ---

#### Specs 2 options available, still under discussion with committers: 1. Only one language in parameter and one language displayed, fallback default language ~2. As many language parameters and by default all the language are displayed~ Monolanguage Product list endpoint Blocked by https://github.com/PrestaShop/PrestaShop/issues/34849 & https://github.com/PrestaShop/PrestaShop/issues/34301

Handle listing in the new API in a multilanguage context

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34850/comments

https://github.com/PrestaShop/PrestaShop/issues/34850

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Handle listing in the new API in a multilanguage context Issue date: --- start body --- #### Specs 2 options available, still under discussion with committers: 1. Only one language in parameter and one language displayed, fallback default language ~2. As many language parameters and by default all the language are displayed~ Monolanguage Product list endpoint Blocked by https://github.com/PrestaShop/PrestaShop/issues/34849 & https://github.com/PrestaShop/PrestaShop/issues/34301 --- end body --- comments : --- start comments --- --- end comments ---

### Objective For patch endpoint to test if the Patch & Put work for only one language - UpdateProductCommand for Patch endpoint to test if the Patch & Put work for only one language - Add the fallback for the shop parameter with the default shop for the product command - Add the shop listener for the API context to initialize the shop context based on the context refacto on the Symfony Layout

POC UpdateProductCommand for Patch method for the API with id shop and id language as parameter

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34849/comments

https://github.com/PrestaShop/PrestaShop/issues/34849

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : POC UpdateProductCommand for Patch method for the API with id shop and id language as parameter Issue date: --- start body --- ### Objective For patch endpoint to test if the Patch & Put work for only one language - UpdateProductCommand for Patch endpoint to test if the Patch & Put work for only one language - Add the fallback for the shop parameter with the default shop for the product command - Add the shop listener for the API context to initialize the shop context based on the context refacto on the Symfony Layout --- end body --- comments : --- start comments --- --- end comments ---

Study the impact of Multi-languages for the API ## Steps Objectives: Test & understand how the multilanguage behave for Patch and the listing method on the API with the different CQRS command: V.1 - [x] #34849 - Based on the solution, specify in the API contract whether the API can fully utilize the Patch method or not. - [x] [Update the ADR](https://github.com/orgs/PrestaShop/projects/7/views/81?pane=issue&itemId=47602319) - [x] #34850 - 1. Only one language in parameter and one language displayed, fallback default language - 2. As many language parameters and by default all the language are displayed NTH - [ ] List all the CQRS method that don't have partial updates - If there are just a few, we could consider adapting them for the partial method - [ ] The listing of language would be required if we want the dev to use the multilanguage to map the language ID with their use case.

[EPIC] Impact of Multi-language

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34848/comments

https://github.com/PrestaShop/PrestaShop/issues/34848

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [EPIC] Impact of Multi-language Issue date: --- start body --- Study the impact of Multi-languages for the API ## Steps Objectives: Test & understand how the multilanguage behave for Patch and the listing method on the API with the different CQRS command: V.1 - [x] #34849 - Based on the solution, specify in the API contract whether the API can fully utilize the Patch method or not. - [x] [Update the ADR](https://github.com/orgs/PrestaShop/projects/7/views/81?pane=issue&itemId=47602319) - [x] #34850 - 1. Only one language in parameter and one language displayed, fallback default language - 2. As many language parameters and by default all the language are displayed NTH - [ ] List all the CQRS method that don't have partial updates - If there are just a few, we could consider adapting them for the partial method - [ ] The listing of language would be required if we want the dev to use the multilanguage to map the language ID with their use case. --- end body --- comments : --- start comments --- --- end comments ---

#### Context #### How to manage the API when Multishop is disabled - [x] #34851 - [x] #34852 - [x] [POC Add the fallback for the shop parameter with the default shop for the product command](https://github.com/PrestaShop/PrestaShop/issues/34849) - 1. It will determine how we can handle the multishop and how long it is going to take for the use case 2 - 2. Add the shop listener for the API context to initialize the shop context based on the context refacto on the Symfony Layout #### Next to support Multishop - Associate the API by shop in the form - Add the parameter to the shop constraint that can be shop ID, group ID or all shops - Handle the permission of the API access depending on shop association configuration - Search how are constructed the command on the multistore

[EPIC] Impact of Multishop on the new API

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34847/comments

https://github.com/PrestaShop/PrestaShop/issues/34847

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [EPIC] Impact of Multishop on the new API Issue date: --- start body --- #### Context #### How to manage the API when Multishop is disabled - [x] #34851 - [x] #34852 - [x] [POC Add the fallback for the shop parameter with the default shop for the product command](https://github.com/PrestaShop/PrestaShop/issues/34849) - 1. It will determine how we can handle the multishop and how long it is going to take for the use case 2 - 2. Add the shop listener for the API context to initialize the shop context based on the context refacto on the Symfony Layout #### Next to support Multishop - Associate the API by shop in the form - Add the parameter to the shop constraint that can be shop ID, group ID or all shops - Handle the permission of the API access depending on shop association configuration - Search how are constructed the command on the multistore --- end body --- comments : --- start comments --- --- end comments ---

#### Specs 1. Investigate → How to launch integration test into the module, but the module needs the core. So one of the possibility is to use flashlight @jokesterfr (check faceted search module may have CI) 2. Integrate the CI test into the module repo ! #### Acceptance test Working and green CI

Add integration test for API endpoint from the module CI

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34846/comments

https://github.com/PrestaShop/PrestaShop/issues/34846

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Add integration test for API endpoint from the module CI Issue date: --- start body --- #### Specs 1. Investigate → How to launch integration test into the module, but the module needs the core. So one of the possibility is to use flashlight @jokesterfr (check faceted search module may have CI) 2. Integrate the CI test into the module repo ! #### Acceptance test Working and green CI --- end body --- comments : --- start comments --- --- end comments ---

#### Specs Now the module is created the endpoint on the core has to be moved into the module FROM [src/PrestaShopBundle/ApiPlatform/Resources](https://github.com/PrestaShop/PrestaShop/tree/1bd3248e71ebb8a4987279fd8bfd8afb9b6661ce/src/PrestaShopBundle/ApiPlatform/Resources) - CartRule.php - CustomerGroup.php - FoundProduct.php - Hook.php TO https://github.com/PrestaShop/ps_apiresources/tree/dev/src/ApiPlatform/Resources Blocked https://github.com/PrestaShop/PrestaShop/issues/34846 #### Acceptance test API should function the same as before. The UI test shouldn't move !

Move all the endpoints into the module

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34845/comments

https://github.com/PrestaShop/PrestaShop/issues/34845

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Move all the endpoints into the module Issue date: --- start body --- #### Specs Now the module is created the endpoint on the core has to be moved into the module FROM [src/PrestaShopBundle/ApiPlatform/Resources](https://github.com/PrestaShop/PrestaShop/tree/1bd3248e71ebb8a4987279fd8bfd8afb9b6661ce/src/PrestaShopBundle/ApiPlatform/Resources) - CartRule.php - CustomerGroup.php - FoundProduct.php - Hook.php TO https://github.com/PrestaShop/ps_apiresources/tree/dev/src/ApiPlatform/Resources Blocked https://github.com/PrestaShop/PrestaShop/issues/34846 #### Acceptance test API should function the same as before. The UI test shouldn't move ! --- end body --- comments : --- start comments --- --- end comments ---

### Specs: A default scope has to be defined, otherwise the API access will get access to all the scopes. is_authenticated to /api-access/infos → get the info of the scope allowed and the shop associated (the name of the endpoint still have to be defined) - List of shops (no multishop for now) - List scopes - All API access info except the secret -- A query get access info, handle the info of the API access (get the id or to be managed by the handler) The endpoint should be defined in the core (not in the module) ### Acceptance test When the endpoint is called with the authorization Then - List of shops associated to the API access - List scopes allowed - All API access info except the secret are displayed - Add integration tests in the core ### Technical note First we should check if the `is_authenticated` scope is really useful to access public endpoints (without any scopes assigned on it), and if the other ones are correctly protected If yes then we could remove the `is_authenticated` scope completely

API Access Info endpoint

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34844/comments

https://github.com/PrestaShop/PrestaShop/issues/34844

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : API Access Info endpoint Issue date: --- start body --- ### Specs: A default scope has to be defined, otherwise the API access will get access to all the scopes. is_authenticated to /api-access/infos → get the info of the scope allowed and the shop associated (the name of the endpoint still have to be defined) - List of shops (no multishop for now) - List scopes - All API access info except the secret -- A query get access info, handle the info of the API access (get the id or to be managed by the handler) The endpoint should be defined in the core (not in the module) ### Acceptance test When the endpoint is called with the authorization Then - List of shops associated to the API access - List scopes allowed - All API access info except the secret are displayed - Add integration tests in the core ### Technical note First we should check if the `is_authenticated` scope is really useful to access public endpoints (without any scopes assigned on it), and if the other ones are correctly protected If yes then we could remove the `is_authenticated` scope completely --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Since the migration from PS 1.7.9.10 to PS 8.1.2, these 5 modules do not connect with their respective sites : Prestashop acount Prestashop Checkout Colissimo Mondial Relay Relais Colis ### Expected behavior Find the solution ### Steps to reproduce Migrate 1.7.9.10 to 8.1.2 ### PrestaShop version(s) where the bug happened 1.7.9.10 to 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Marc

Bug : impossible to connect modules with their respectives site

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34842/comments

https://github.com/PrestaShop/PrestaShop/issues/34842

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Bug : impossible to connect modules with their respectives site Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Since the migration from PS 1.7.9.10 to PS 8.1.2, these 5 modules do not connect with their respective sites : Prestashop acount Prestashop Checkout Colissimo Mondial Relay Relais Colis ### Expected behavior Find the solution ### Steps to reproduce Migrate 1.7.9.10 to 8.1.2 ### PrestaShop version(s) where the bug happened 1.7.9.10 to 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Marc --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can create a pack product with just a title, a quantity, a price and sell it. But no specific products are added to it. <img width="1217" alt="Screenshot 2023-12-14 at 15 22 50" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/f0164971-d185-4976-960b-85d21204b5c8"> <img width="1064" alt="Screenshot 2023-12-14 at 15 23 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2a6a976e-ee48-4199-a3cb-99013dcd710b"> Found by @SD1982 ### Expected behavior I should have an error when I try to create a Pack product without product. ``` Unable to update settings This pack is empty. You must add at least one product item. ``` ### Steps to reproduce 1. Go to BO > Product > Click Add new products > Choose pack of products > Enter a name > Add quantity > Add price 2. Click on save 3. See Successful update :x: I should have messages those messages displayed : "Unable to update settings" "This pack is empty. You must add at least one product item." ### PrestaShop version(s) where the bug happened 8.1.x, develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

PS 8.1.x - Pack product can be created even though they're empty

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34839/comments

https://github.com/PrestaShop/PrestaShop/issues/34839

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PS 8.1.x - Pack product can be created even though they're empty Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I can create a pack product with just a title, a quantity, a price and sell it. But no specific products are added to it. <img width="1217" alt="Screenshot 2023-12-14 at 15 22 50" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/f0164971-d185-4976-960b-85d21204b5c8"> <img width="1064" alt="Screenshot 2023-12-14 at 15 23 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2a6a976e-ee48-4199-a3cb-99013dcd710b"> Found by @SD1982 ### Expected behavior I should have an error when I try to create a Pack product without product. ``` Unable to update settings This pack is empty. You must add at least one product item. ``` ### Steps to reproduce 1. Go to BO > Product > Click Add new products > Choose pack of products > Enter a name > Add quantity > Add price 2. Click on save 3. See Successful update :x: I should have messages those messages displayed : "Unable to update settings" "This pack is empty. You must add at least one product item." ### PrestaShop version(s) where the bug happened 8.1.x, develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I change my currency and I want to sort my product by Prices, no produce are displayed. https://github.com/PrestaShop/PrestaShop/assets/16019289/947c1233-bf9b-4a4d-8f18-148d6895c8dc I tested with Vietnamese Dong and Argentine Peso. ### Expected behavior I should be able to sort my product by Prices. ### Steps to reproduce 1. Go to BO > International > Localization 2. Add 2 localization packs : Vietnam and Argentina 3. Go to FO > Display all products 4. Change currency to `VND` or `ARS` 5. Sort by `Prices, low to high` or `Prices, high to low` 6. No products are displayed :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PS

FO - In All products page, Sort by Prices doesn't work with all currencies

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34838/comments

https://github.com/PrestaShop/PrestaShop/issues/34838

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO - In All products page, Sort by Prices doesn't work with all currencies Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I change my currency and I want to sort my product by Prices, no produce are displayed. https://github.com/PrestaShop/PrestaShop/assets/16019289/947c1233-bf9b-4a4d-8f18-148d6895c8dc I tested with Vietnamese Dong and Argentine Peso. ### Expected behavior I should be able to sort my product by Prices. ### Steps to reproduce 1. Go to BO > International > Localization 2. Add 2 localization packs : Vietnam and Argentina 3. Go to FO > Display all products 4. Change currency to `VND` or `ARS` 5. Sort by `Prices, low to high` or `Prices, high to low` 6. No products are displayed :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). PS --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I created products on a PS 8.1.2 with 7 personalization fields with a precise order. and when I go to the front office the fields are not in the same order  ### Expected behavior when we create personalization fields in the back office, we expect them to appear in the same order in the front office ### Steps to reproduce Create product insert personalization fields (7 for my website) If we don't like the final result, we remove or modify some of them. back office fields are not in the same order as front office ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

order of personalization fields product sheet

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34837/comments

https://github.com/PrestaShop/PrestaShop/issues/34837

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : order of personalization fields product sheet Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I created products on a PS 8.1.2 with 7 personalization fields with a precise order. and when I go to the front office the fields are not in the same order  ### Expected behavior when we create personalization fields in the back office, we expect them to appear in the same order in the front office ### Steps to reproduce Create product insert personalization fields (7 for my website) If we don't like the final result, we remove or modify some of them. back office fields are not in the same order as front office ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments In PS 8.1.3 build 1, enabling the product image option does not work in Delivery Slips and Invoices. <img width="344" alt="Screenshot 2023-12-14 at 14 21 40" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/30860fd2-c1e0-42b7-aad8-a5f6d5df6c3b"> ### Expected behavior I should be able to see the product image in my delivery slip and invoice. <img width="763" alt="Screenshot 2023-12-14 at 14 23 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/9889b844-30ad-4537-b587-40777bbd65d5"> <img width="980" alt="Screenshot 2023-12-14 at 14 23 12" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/3f45b9ec-c2fe-4c38-97c3-66d8f16d661a"> ### Steps to reproduce 1. Go to BO > Invoices > Enable product image 2. Go to BO > Orders > Change status of any order to Payment accepted 3. Click on the Invoice icon 4. See no product image displayed :x: 5. Go to BO > Delivery slips > Enable product image 6. Go to BO > Orders > Change status of any order to Delivered 7. Click on the Delivery slip icon 8. See no product image displayed :x: ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

PS 8.1.3 - Enable product image in Delivery slip/Invoices doesn't work anymore

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34835/comments

https://github.com/PrestaShop/PrestaShop/issues/34835

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PS 8.1.3 - Enable product image in Delivery slip/Invoices doesn't work anymore Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments In PS 8.1.3 build 1, enabling the product image option does not work in Delivery Slips and Invoices. <img width="344" alt="Screenshot 2023-12-14 at 14 21 40" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/30860fd2-c1e0-42b7-aad8-a5f6d5df6c3b"> ### Expected behavior I should be able to see the product image in my delivery slip and invoice. <img width="763" alt="Screenshot 2023-12-14 at 14 23 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/9889b844-30ad-4537-b587-40777bbd65d5"> <img width="980" alt="Screenshot 2023-12-14 at 14 23 12" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/3f45b9ec-c2fe-4c38-97c3-66d8f16d661a"> ### Steps to reproduce 1. Go to BO > Invoices > Enable product image 2. Go to BO > Orders > Change status of any order to Payment accepted 3. Click on the Invoice icon 4. See no product image displayed :x: 5. Go to BO > Delivery slips > Enable product image 6. Go to BO > Orders > Change status of any order to Delivered 7. Click on the Delivery slip icon 8. See no product image displayed :x: ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

id_employee | StockMvt | #### Spec - Add enpoint: UpdateCombinationStockAvailableCommand -> /products/{productId}/combination/{combinationId}/stock or /combinations/{combinationId}/stock UpdateProductStockAvailableCommand -> /products/{productId}/stock - Update StockMvt to handle the API access ID - Update the method (path file: PrestaShop\PrestaShop\Core\Stock\StockManager) prepareMovement to save the API access ID in StockMvt - Adapt the page view to display the API access name in the stock movement page and the product page / history (and the combination in the modal) instead of the employee name ### Acceptance test When a stock have changed from the API access Then the stock movement page displayed the API access name instead of the employee Also check endpoint order status impacts the stock movement correctly

Adapt StockManager for the API access

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34832/comments

https://github.com/PrestaShop/PrestaShop/issues/34832

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adapt StockManager for the API access Issue date: --- start body --- id_employee | StockMvt | #### Spec - Add enpoint: UpdateCombinationStockAvailableCommand -> /products/{productId}/combination/{combinationId}/stock or /combinations/{combinationId}/stock UpdateProductStockAvailableCommand -> /products/{productId}/stock - Update StockMvt to handle the API access ID - Update the method (path file: PrestaShop\PrestaShop\Core\Stock\StockManager) prepareMovement to save the API access ID in StockMvt - Adapt the page view to display the API access name in the stock movement page and the product page / history (and the combination in the modal) instead of the employee name ### Acceptance test When a stock have changed from the API access Then the stock movement page displayed the API access name instead of the employee Also check endpoint order status impacts the stock movement correctly --- end body --- comments : --- start comments --- --- end comments ---

id_employee | order_payment | #### Specs - Add endpoint /orders/{orderId}/add-payment - Add column ID for the API access in order_payment - Adapt the command addPaymentCommand to put either ID employee or ID of the API Access - Adapt the command processor to be able to add at the CQRS command creation the API access ID (either naming convention or explicit configuration) - Adapt the page view to display API access instead of employee #### Acceptance

Adapt the command Order payment for the API access

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34831/comments

https://github.com/PrestaShop/PrestaShop/issues/34831

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adapt the command Order payment for the API access Issue date: --- start body --- id_employee | order_payment | #### Specs - Add endpoint /orders/{orderId}/add-payment - Add column ID for the API access in order_payment - Adapt the command addPaymentCommand to put either ID employee or ID of the API Access - Adapt the command processor to be able to add at the CQRS command creation the API access ID (either naming convention or explicit configuration) - Adapt the page view to display API access instead of employee #### Acceptance --- end body --- comments : --- start comments --- --- end comments ---

id_employee | order_history | #### Specs - create the endpoint: /orders/{orderId}/update-status /orders/bulk-update-status - Adapt the command to be able to save API access and associated to the API ID - BulkChangeOrderStatusCommand - UpdateOrderStatusCommand - Add the new column in table order_history to store the ID API access - Adapt the page to display the API access name if the status is updated by the API. #### Acceptance When an API access updates the order status Then the API access name is displayed on the order page in the order status history next to the new order status

Adapt the command Order status for the API access

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34830/comments

https://github.com/PrestaShop/PrestaShop/issues/34830

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adapt the command Order status for the API access Issue date: --- start body --- id_employee | order_history | #### Specs - create the endpoint: /orders/{orderId}/update-status /orders/bulk-update-status - Adapt the command to be able to save API access and associated to the API ID - BulkChangeOrderStatusCommand - UpdateOrderStatusCommand - Add the new column in table order_history to store the ID API access - Adapt the page to display the API access name if the status is updated by the API. #### Acceptance When an API access updates the order status Then the API access name is displayed on the order page in the order status history next to the new order status --- end body --- comments : --- start comments --- --- end comments ---

PrestaShopLogger | classes/PrestaShopLogger.php | 58, 59, 97, 155, 156, 160 | ### Spec <img width="698" alt="Capture d’écran 2023-12-13 à 17 30 43" src="https://github.com/PrestaShop/PrestaShop/assets/43613217/c53ae09f-156f-4d79-aba3-4931d78789c0"> - Add new column - Adapt the method addLog to fulfill automatically the ID user employee and the ID from the API access. ### NTH - check how we can adapt the grid ### Acceptance test to investigate how to trigger logs from the API. We need to find how to create a log to make to trigger it from the API

Adapt PrestaShopLogger class for the API access

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34828/comments

https://github.com/PrestaShop/PrestaShop/issues/34828

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adapt PrestaShopLogger class for the API access Issue date: --- start body --- PrestaShopLogger | classes/PrestaShopLogger.php | 58, 59, 97, 155, 156, 160 | ### Spec <img width="698" alt="Capture d’écran 2023-12-13 à 17 30 43" src="https://github.com/PrestaShop/PrestaShop/assets/43613217/c53ae09f-156f-4d79-aba3-4931d78789c0"> - Add new column - Adapt the method addLog to fulfill automatically the ID user employee and the ID from the API access. ### NTH - check how we can adapt the grid ### Acceptance test to investigate how to trigger logs from the API. We need to find how to create a log to make to trigger it from the API --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I tried to remove the ‘legal notes’ from the footer of my store’s homepage but without success. I went to the module management section and then to the ‘links tree’ module which is already updated and in which the ‘legal notes’ item that I would like to remove does not appear, but it continues to appear on the homepage. [I am attaching the screenshots."] Is it possible to reupdate that model in order to eliminate the "note legali" voice? Thanks in advance   ### Expected behavior I would like to have the voice "note legali" to be seen in the Links tree, in order to remove it ### Steps to reproduce Go to Module Management section Click on Links Tree Search for the "Legal Notes " voice Delete it ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.2 ### If your bug is related to a module, specify its name and its version Link Tree V5.0.5 ### Your company or customer's name goes here (if applicable). StreetSport.it

Unable to remove the "legal notes" from the Home page footer”.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34822/comments

https://github.com/PrestaShop/PrestaShop/issues/34822

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unable to remove the "legal notes" from the Home page footer”. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I tried to remove the ‘legal notes’ from the footer of my store’s homepage but without success. I went to the module management section and then to the ‘links tree’ module which is already updated and in which the ‘legal notes’ item that I would like to remove does not appear, but it continues to appear on the homepage. [I am attaching the screenshots."] Is it possible to reupdate that model in order to eliminate the "note legali" voice? Thanks in advance   ### Expected behavior I would like to have the voice "note legali" to be seen in the Links tree, in order to remove it ### Steps to reproduce Go to Module Management section Click on Links Tree Search for the "Legal Notes " voice Delete it ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.2 ### If your bug is related to a module, specify its name and its version Link Tree V5.0.5 ### Your company or customer's name goes here (if applicable). StreetSport.it --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I receive on error_log_php many times the same error ``` [12-Dec-2023 16:39:08 Europe/Rome] PHP Fatal error: Uncaught PrestaShop\PrestaShop\Core\Product\Search\Exception\InvalidSortOrderDirectionException: Invalid SortOrder direction `desc?order=product`. Expecting one of: `ASC`, `DESC`, or `RANDOM`. in /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php:199 Stack trace: #0 /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php(67): PrestaShop\PrestaShop\Core\Product\Search\SortOrder->setDirection('desc?order=prod...') #1 /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php(125): PrestaShop\PrestaShop\Core\Product\Search\SortOrder->__construct('product', 'name', 'desc?order=prod...') #2 /home/jvillagc/public_html/shop/classes/controller/ProductListingFrontController.php(286): PrestaShop\PrestaShop\Core\Product\Search\SortOrder::newFromString('product.name.de...') #3 /home/jvillagc/public_html/shop/classes/controller/ProductListingFrontController.php(580): ProductListingFrontControllerCore->getProductSearchVariables() #4 /home/jvillagc/public_html/shop/controllers/fro in /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php on line 199 ``` ### Expected behavior changing short order cannot be a problem nor generate a PHP error. I don't know if is related to a theme (warehouse) or a core bug. ### Steps to reproduce 1. enter into a category 2. try to change short order type and filters (faceted) using also ASC and DESC ### PrestaShop version(s) where the bug happened 1.7.6.9 ### PHP version(s) where the bug happened 7.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

PHP Fatal Error SortOrder

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34819/comments

https://github.com/PrestaShop/PrestaShop/issues/34819

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PHP Fatal Error SortOrder Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I receive on error_log_php many times the same error ``` [12-Dec-2023 16:39:08 Europe/Rome] PHP Fatal error: Uncaught PrestaShop\PrestaShop\Core\Product\Search\Exception\InvalidSortOrderDirectionException: Invalid SortOrder direction `desc?order=product`. Expecting one of: `ASC`, `DESC`, or `RANDOM`. in /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php:199 Stack trace: #0 /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php(67): PrestaShop\PrestaShop\Core\Product\Search\SortOrder->setDirection('desc?order=prod...') #1 /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php(125): PrestaShop\PrestaShop\Core\Product\Search\SortOrder->__construct('product', 'name', 'desc?order=prod...') #2 /home/jvillagc/public_html/shop/classes/controller/ProductListingFrontController.php(286): PrestaShop\PrestaShop\Core\Product\Search\SortOrder::newFromString('product.name.de...') #3 /home/jvillagc/public_html/shop/classes/controller/ProductListingFrontController.php(580): ProductListingFrontControllerCore->getProductSearchVariables() #4 /home/jvillagc/public_html/shop/controllers/fro in /home/jvillagc/public_html/shop/src/Core/Product/Search/SortOrder.php on line 199 ``` ### Expected behavior changing short order cannot be a problem nor generate a PHP error. I don't know if is related to a theme (warehouse) or a core bug. ### Steps to reproduce 1. enter into a category 2. try to change short order type and filters (faceted) using also ASC and DESC ### PrestaShop version(s) where the bug happened 1.7.6.9 ### PHP version(s) where the bug happened 7.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

The PrestaShop project site must follow the new branding guidelines. # General informations Live website https://www.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/open-source This website is built using GitHub Actions and [Hugo](https://gohugo.io/). Read the README to run the site locally. Don't hesitate to ask @matks. # Header and title “Welcome to the PrestaShop project”  - Replace current logo with puffin by simple “PRESTASHOP” SVG logo - Background color #F8E08E - Menu uses font Arial Black in Capital Letters - Title uses PRESTAFONT black - Subtitle Arial bold PRESTAFONT is a custom PrestaShop font # Section “Project documentation” Below the header - TITLE SECTION ARIAL BLACK BOLD - Please use attached icons SVG / PNG - 3 columns, title bold + text arial black # CTA “Ready to get started”  - Background black - Use given Picture - Title ARIAL WHITE BOLD CAPITAL LETTERS - Call To Action Button white box + TRIANGLE + CAPITAL LETTERS # Footer Follow style of prestashop.com footer Use the SVG logo Menu in black + triangle # Rest of the site / other pages - Navbar -> follow homepage example, background color yellow f8e08e - Page title Header PrestaFont corps 120pt - Subtitle when there is one: Arial Corps 28pt - Header 1 when there is one: Arial Black corps 41pt - CTA white on black background, triangle ► HTML - Bullet points: Black on white background # Favicon Nice-to-have: change the favicon to use the same as https://prestashop.com/

Applying the new PrestaShop branding on PrestaShop project site

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34895/comments

https://github.com/PrestaShop/PrestaShop/issues/34895

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Applying the new PrestaShop branding on PrestaShop project site Issue date: --- start body --- The PrestaShop project site must follow the new branding guidelines. # General informations Live website https://www.prestashop-project.org/ GitHub repository https://github.com/PrestaShop/open-source This website is built using GitHub Actions and [Hugo](https://gohugo.io/). Read the README to run the site locally. Don't hesitate to ask @matks. # Header and title “Welcome to the PrestaShop project”  - Replace current logo with puffin by simple “PRESTASHOP” SVG logo - Background color #F8E08E - Menu uses font Arial Black in Capital Letters - Title uses PRESTAFONT black - Subtitle Arial bold PRESTAFONT is a custom PrestaShop font # Section “Project documentation” Below the header - TITLE SECTION ARIAL BLACK BOLD - Please use attached icons SVG / PNG - 3 columns, title bold + text arial black # CTA “Ready to get started”  - Background black - Use given Picture - Title ARIAL WHITE BOLD CAPITAL LETTERS - Call To Action Button white box + TRIANGLE + CAPITAL LETTERS # Footer Follow style of prestashop.com footer Use the SVG logo Menu in black + triangle # Rest of the site / other pages - Navbar -> follow homepage example, background color yellow f8e08e - Page title Header PrestaFont corps 120pt - Subtitle when there is one: Arial Corps 28pt - Header 1 when there is one: Arial Black corps 41pt - CTA white on black background, triangle ► HTML - Bullet points: Black on white background # Favicon Nice-to-have: change the favicon to use the same as https://prestashop.com/ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hook displayAdminProductsPriceStepBottom should display additional content on Admin -> Products -> (Product) -> Pricing tab. It worked on 1.7.8.x. [It is currently present in 8.x documentation.](https://devdocs.prestashop-project.org/8/modules/concepts/hooks/list-of-hooks/displayadminproductspricestepbottom/) The file, where the hook is rendered, is no longer called. Product page is completely new. Now it renders the whole product form and all specific forms on tabs as Symfony form (PrestaShopBundle\Form\Admin\Sell\Product\EditProductFormType). This results in the hook not being rendered at all. This might influence other hooks called on admin product page and should be looked into (if not done yet). The hook should be added into the form, or removed from documentation. ### Expected behavior The hook (displayAdminProductsPriceStepBottom) should be called. ### Steps to reproduce 1. Turn on debug mode 2. Open specific product in new admin page 3. Look into profiler, search for "Hooks" section 4. See that no displayAdminProductsPriceStepBottom is called ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Hook displayAdminProductsPriceStepBottom no longer executed

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34815/comments

https://github.com/PrestaShop/PrestaShop/issues/34815

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Hook displayAdminProductsPriceStepBottom no longer executed Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hook displayAdminProductsPriceStepBottom should display additional content on Admin -> Products -> (Product) -> Pricing tab. It worked on 1.7.8.x. [It is currently present in 8.x documentation.](https://devdocs.prestashop-project.org/8/modules/concepts/hooks/list-of-hooks/displayadminproductspricestepbottom/) The file, where the hook is rendered, is no longer called. Product page is completely new. Now it renders the whole product form and all specific forms on tabs as Symfony form (PrestaShopBundle\Form\Admin\Sell\Product\EditProductFormType). This results in the hook not being rendered at all. This might influence other hooks called on admin product page and should be looked into (if not done yet). The hook should be added into the form, or removed from documentation. ### Expected behavior The hook (displayAdminProductsPriceStepBottom) should be called. ### Steps to reproduce 1. Turn on debug mode 2. Open specific product in new admin page 3. Look into profiler, search for "Hooks" section 4. See that no displayAdminProductsPriceStepBottom is called ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments As a visitor I comment a product and I give a note. Actual behavior : The count of comments appear and the grade but not the commentary text  ### Expected behavior The commentary text is displayed with all the commentaries ### Steps to reproduce 1. As a visitor on FO 2. Write a review and add a grade ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version productcomments v6.0.2 ### Your company or customer's name goes here (if applicable). PrestaShop

Product comment module doesn't display comments in FO

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34814/comments

https://github.com/PrestaShop/PrestaShop/issues/34814

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Product comment module doesn't display comments in FO Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments As a visitor I comment a product and I give a note. Actual behavior : The count of comments appear and the grade but not the commentary text  ### Expected behavior The commentary text is displayed with all the commentaries ### Steps to reproduce 1. As a visitor on FO 2. Write a review and add a grade ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version productcomments v6.0.2 ### Your company or customer's name goes here (if applicable). PrestaShop --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi I've seen that Google has started reporting the lack of these two microdata, reported by Google Search Console for the Product microdata hasMerchantReturnPolicy shippingDetails  bye ### Expected behavior _No response_ ### Steps to reproduce 1. look from google search console the product snippet ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Missing two new microdata hasMerchantReturnPolicy and shippingDetails

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34813/comments

https://github.com/PrestaShop/PrestaShop/issues/34813

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Missing two new microdata hasMerchantReturnPolicy and shippingDetails Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi I've seen that Google has started reporting the lack of these two microdata, reported by Google Search Console for the Product microdata hasMerchantReturnPolicy shippingDetails  bye ### Expected behavior _No response_ ### Steps to reproduce 1. look from google search console the product snippet ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

[[Epic][Pricing][MOC] : Method Of Calculating a cart total without discount](https://github.com/PrestaShop/PrestaShop/issues/32227) https://github.com/PrestaShop/PrestaShop/issues/32227 [[EPIC][Pricing] : Discount in the Catalog](https://github.com/PrestaShop/PrestaShop/issues/34292) https://github.com/PrestaShop/PrestaShop/issues/34292 [EPIC][Pricing] : Discount in the Chart https://github.com/PrestaShop/PrestaShop/issues/34308 [[EPIC][Pricing] : Invoice](https://github.com/PrestaShop/PrestaShop/issues/34310) https://github.com/PrestaShop/PrestaShop/issues/34310 [[Epic][Pricing]: Rounding](https://github.com/PrestaShop/PrestaShop/issues/34009) https://github.com/PrestaShop/PrestaShop/issues/34009 [[EPIC][Pricing] : Prices depending on currencies](https://github.com/PrestaShop/PrestaShop/issues/34010) https://github.com/PrestaShop/PrestaShop/issues/34010 [[EPIC][Pricing] : Ecotax](https://github.com/PrestaShop/PrestaShop/issues/34011) https://github.com/PrestaShop/PrestaShop/issues/34011 [[EPIC][Pricing] : Rules by country](https://github.com/PrestaShop/PrestaShop/issues/34012) https://github.com/PrestaShop/PrestaShop/issues/34012 [[EPIC][Pricing] : Check that Paypal and concurrents had all required datas](https://github.com/PrestaShop/PrestaShop/issues/32323) https://github.com/PrestaShop/PrestaShop/issues/32323 [[EPIC] [Pricing]: Migration of the shipping motor used by the pricing](https://github.com/PrestaShop/PrestaShop/issues/34312) https://github.com/PrestaShop/PrestaShop/issues/34312 [[EPIC][Pricing] : Multishipping](https://github.com/PrestaShop/PrestaShop/issues/34320) https://github.com/PrestaShop/PrestaShop/issues/34320 [[EPIC][Pricing]Refund](https://github.com/PrestaShop/PrestaShop/issues/34319) https://github.com/PrestaShop/PrestaShop/issues/34319 [[EPIC][Pricing] : Unify the FO and BO basket calculation methods](https://github.com/PrestaShop/PrestaShop/issues/32315) https://github.com/PrestaShop/PrestaShop/issues/32315 [[EPIC][Pricing] : new rules for gifts](https://github.com/PrestaShop/PrestaShop/issues/32324) https://github.com/PrestaShop/PrestaShop/issues/32324 [[EPIC][Pricing] : Improve priority management and compatibility between different promotion strategies](https://github.com/PrestaShop/PrestaShop/issues/32226) https://github.com/PrestaShop/PrestaShop/issues/32226 [[EPIC][Pricing] : Improve the performance of the Cart Rules display](https://github.com/PrestaShop/PrestaShop/issues/32224) https://github.com/PrestaShop/PrestaShop/issues/32224 [EPIC][Pricing] : Improved user experience https://github.com/PrestaShop/PrestaShop/issues/32229 [[EPIC][Pricing] : Bonus](https://github.com/PrestaShop/PrestaShop/issues/32230) https://github.com/PrestaShop/PrestaShop/issues/32230

[EPIC][Pricing] All Pricing and Invoicing issues and improvements

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34805/comments

https://github.com/PrestaShop/PrestaShop/issues/34805

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [EPIC][Pricing] All Pricing and Invoicing issues and improvements Issue date: --- start body --- [[Epic][Pricing][MOC] : Method Of Calculating a cart total without discount](https://github.com/PrestaShop/PrestaShop/issues/32227) https://github.com/PrestaShop/PrestaShop/issues/32227 [[EPIC][Pricing] : Discount in the Catalog](https://github.com/PrestaShop/PrestaShop/issues/34292) https://github.com/PrestaShop/PrestaShop/issues/34292 [EPIC][Pricing] : Discount in the Chart https://github.com/PrestaShop/PrestaShop/issues/34308 [[EPIC][Pricing] : Invoice](https://github.com/PrestaShop/PrestaShop/issues/34310) https://github.com/PrestaShop/PrestaShop/issues/34310 [[Epic][Pricing]: Rounding](https://github.com/PrestaShop/PrestaShop/issues/34009) https://github.com/PrestaShop/PrestaShop/issues/34009 [[EPIC][Pricing] : Prices depending on currencies](https://github.com/PrestaShop/PrestaShop/issues/34010) https://github.com/PrestaShop/PrestaShop/issues/34010 [[EPIC][Pricing] : Ecotax](https://github.com/PrestaShop/PrestaShop/issues/34011) https://github.com/PrestaShop/PrestaShop/issues/34011 [[EPIC][Pricing] : Rules by country](https://github.com/PrestaShop/PrestaShop/issues/34012) https://github.com/PrestaShop/PrestaShop/issues/34012 [[EPIC][Pricing] : Check that Paypal and concurrents had all required datas](https://github.com/PrestaShop/PrestaShop/issues/32323) https://github.com/PrestaShop/PrestaShop/issues/32323 [[EPIC] [Pricing]: Migration of the shipping motor used by the pricing](https://github.com/PrestaShop/PrestaShop/issues/34312) https://github.com/PrestaShop/PrestaShop/issues/34312 [[EPIC][Pricing] : Multishipping](https://github.com/PrestaShop/PrestaShop/issues/34320) https://github.com/PrestaShop/PrestaShop/issues/34320 [[EPIC][Pricing]Refund](https://github.com/PrestaShop/PrestaShop/issues/34319) https://github.com/PrestaShop/PrestaShop/issues/34319 [[EPIC][Pricing] : Unify the FO and BO basket calculation methods](https://github.com/PrestaShop/PrestaShop/issues/32315) https://github.com/PrestaShop/PrestaShop/issues/32315 [[EPIC][Pricing] : new rules for gifts](https://github.com/PrestaShop/PrestaShop/issues/32324) https://github.com/PrestaShop/PrestaShop/issues/32324 [[EPIC][Pricing] : Improve priority management and compatibility between different promotion strategies](https://github.com/PrestaShop/PrestaShop/issues/32226) https://github.com/PrestaShop/PrestaShop/issues/32226 [[EPIC][Pricing] : Improve the performance of the Cart Rules display](https://github.com/PrestaShop/PrestaShop/issues/32224) https://github.com/PrestaShop/PrestaShop/issues/32224 [EPIC][Pricing] : Improved user experience https://github.com/PrestaShop/PrestaShop/issues/32229 [[EPIC][Pricing] : Bonus](https://github.com/PrestaShop/PrestaShop/issues/32230) https://github.com/PrestaShop/PrestaShop/issues/32230 --- end body --- comments : --- start comments --- --- end comments ---

This issue tracks the status of the PrestaShop 1.7.8.11 release # Information Q | A --------------------------------------|--------------- **Type** | Patch version **Build date**. | 13-12-2023 **Milestone** | [1.7.8.11](https://github.com/PrestaShop/PrestaShop/milestone/99) **Freeze date** | 11-12-2023 **Delivery date** | 02-01-2024 **Release manager tech** | @tleon / @boherm **Release manager product** | **Release manager QA** | @AureRita _Nota Bene: the release date may vary, if major bugs are identified during the test phase_ RMT = Release manager tech RMQ = Release manager QA # Current status - [x] Create milestone ## 1. Development ## 2. Preparing the source code for release - [x] [Preliminary tasks](https://www.prestashop-project.org/maintainers-guide/releasing-prestashop/preliminary-tasks/) **RMT** - [x] 1. Make sure the version number has been updated in the Core (done by https://github.com/PrestaShop/PrestaShop/pull/34810) - [x] 2. Perform multiple manual verifications as documented in the release process ## 3. Build process - [x] Create the new version in Addons Marketplace and update native module compatibility - [x] Prepare communication **Communicator** - [x] Merge security PRs locally if there are some **RMT** - [x] Update the Changelog and Contributors list **RMT** - [x] Build the zip archive. **This is a security release, please do not share the ZIP here. RMT** - [x] QA validation **RMQ** - [x] Release **RMT** - [x] Merge security PRs on GitHub if there are some - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub. - [x] Provide Communicator with up to date informations (contributors list, changelog...) **RMT** - [x] Communicate - [x] Release note **Communicator** ## 4. After release steps - [x] Make new version available for upgrade - [x] Publish Docker image - [x] Close milestone

Release 1.7.8.11 🎅

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34804/comments

https://github.com/PrestaShop/PrestaShop/issues/34804

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Release 1.7.8.11 🎅 Issue date: --- start body --- This issue tracks the status of the PrestaShop 1.7.8.11 release # Information Q | A --------------------------------------|--------------- **Type** | Patch version **Build date**. | 13-12-2023 **Milestone** | [1.7.8.11](https://github.com/PrestaShop/PrestaShop/milestone/99) **Freeze date** | 11-12-2023 **Delivery date** | 02-01-2024 **Release manager tech** | @tleon / @boherm **Release manager product** | **Release manager QA** | @AureRita _Nota Bene: the release date may vary, if major bugs are identified during the test phase_ RMT = Release manager tech RMQ = Release manager QA # Current status - [x] Create milestone ## 1. Development ## 2. Preparing the source code for release - [x] [Preliminary tasks](https://www.prestashop-project.org/maintainers-guide/releasing-prestashop/preliminary-tasks/) **RMT** - [x] 1. Make sure the version number has been updated in the Core (done by https://github.com/PrestaShop/PrestaShop/pull/34810) - [x] 2. Perform multiple manual verifications as documented in the release process ## 3. Build process - [x] Create the new version in Addons Marketplace and update native module compatibility - [x] Prepare communication **Communicator** - [x] Merge security PRs locally if there are some **RMT** - [x] Update the Changelog and Contributors list **RMT** - [x] Build the zip archive. **This is a security release, please do not share the ZIP here. RMT** - [x] QA validation **RMQ** - [x] Release **RMT** - [x] Merge security PRs on GitHub if there are some - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub. - [x] Provide Communicator with up to date informations (contributors list, changelog...) **RMT** - [x] Communicate - [x] Release note **Communicator** ## 4. After release steps - [x] Make new version available for upgrade - [x] Publish Docker image - [x] Close milestone --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We have lanuched our platform about a month ago and are tracking the most important metrics - unique visitors and their conversion to registered users. However, our metrics on dashboard "Unique visitors" seems to be showing a number, that is very much similar to another metrics shown their as well: "Visits". At this moment (2023-12-11, 10:32 a.m.) tthe metrics "Visits" indicates 2926 and "Unique visitors" 2518. See attached print screen. [Metrics.docx](https://github.com/PrestaShop/PrestaShop/files/13632863/Metrics.docx) We have contacted PrestaShop support team to investigate. They came back with an answer: "The problem that you reported does not fall within the scope of PrestaShop Support, as it is a core issue. You must therefore create a ticket on GitHub from this link". The issue is, that by default the number of visits to the site cannot be so similar to the Unique visitors. It is virtually not possible. Can you, please, investigate, how the number "Unique Visitors" is calculated and provide an explanation, if there is an error? ### Expected behavior The number "Unique visitors" should be much less than overall number of "Visits" to the site. ### Steps to reproduce 1. Go to admin panel. 2. See Traffic under Dashboard. 3. Compare numbers "Visits" and "Unique Visitors". ### PrestaShop version(s) where the bug happened 8.0.4 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Dezerd UAB

Incorrect calculation of unique visitors

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34803/comments

https://github.com/PrestaShop/PrestaShop/issues/34803

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Incorrect calculation of unique visitors Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We have lanuched our platform about a month ago and are tracking the most important metrics - unique visitors and their conversion to registered users. However, our metrics on dashboard "Unique visitors" seems to be showing a number, that is very much similar to another metrics shown their as well: "Visits". At this moment (2023-12-11, 10:32 a.m.) tthe metrics "Visits" indicates 2926 and "Unique visitors" 2518. See attached print screen. [Metrics.docx](https://github.com/PrestaShop/PrestaShop/files/13632863/Metrics.docx) We have contacted PrestaShop support team to investigate. They came back with an answer: "The problem that you reported does not fall within the scope of PrestaShop Support, as it is a core issue. You must therefore create a ticket on GitHub from this link". The issue is, that by default the number of visits to the site cannot be so similar to the Unique visitors. It is virtually not possible. Can you, please, investigate, how the number "Unique Visitors" is calculated and provide an explanation, if there is an error? ### Expected behavior The number "Unique visitors" should be much less than overall number of "Visits" to the site. ### Steps to reproduce 1. Go to admin panel. 2. See Traffic under Dashboard. 3. Compare numbers "Visits" and "Unique Visitors". ### PrestaShop version(s) where the bug happened 8.0.4 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Dezerd UAB --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I did an upgrade to PS 8.1.2 and a fresh installation. The software is different in the file /classes/Context.php In the upgrade this starts with `if (null !== $this->translator && $this->language->locale === $this->translator->getLocale()) { return $this->translator; }` In the new installation that code is outcommented. ### Expected behavior software in new installations and upgrade is the same ### Steps to reproduce Install and upgrade ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Upgrade and new install use different software

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34799/comments

https://github.com/PrestaShop/PrestaShop/issues/34799

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade and new install use different software Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I did an upgrade to PS 8.1.2 and a fresh installation. The software is different in the file /classes/Context.php In the upgrade this starts with `if (null !== $this->translator && $this->language->locale === $this->translator->getLocale()) { return $this->translator; }` In the new installation that code is outcommented. ### Expected behavior software in new installations and upgrade is the same ### Steps to reproduce Install and upgrade ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I did a fresh install of Prestashop 8.1.2 under Windows with PHP 7.4. WIndows is slow with webshops but I never have seen something like this: the installation took nearly a full hour. Despite the many errors it looks at first sight as if the installation succeeded and the shop is running ok. I found the following error messages in my error log: > [Sat Dec 09 16:28:34.175958 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61546] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.880252 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61546] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.972406 2023] [php7:notice] [pid 13836:tid 1956] [client ::1:61584] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:39.675261 2023] [php7:error] [pid 13836:tid 1956] [client ::1:61584] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:51.272644 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61593] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:53.969883 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61593] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:notice] [pid 13836:tid 1972] [client ::1:61592] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:56.754498 2023] [php7:error] [pid 13836:tid 1972] [client ::1:61592] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.870150 2023] [php7:notice] [pid 13836:tid 1948] [client ::1:61598] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.601075 2023] [php7:error] [pid 13836:tid 1948] [client ::1:61598] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815379 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61597] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.819873 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:12.510462 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61597] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.813084 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61623] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.536365 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61623] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.629510 2023] [php7:notice] [pid 13836:tid 1944] [client ::1:61620] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:15.339801 2023] [php7:error] [pid 13836:tid 1944] [client ::1:61620] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.963505 2023] [php7:notice] [pid 13836:tid 1972] [client ::1:61626] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.966585 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.685819 2023] [php7:error] [pid 13836:tid 1972] [client ::1:61626] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.739734 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61627] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:23.439614 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61627] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.449523 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61654] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.178676 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61654] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.264693 2023] [php7:notice] [pid 13836:tid 1956] [client ::1:61639] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.267690 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:55.947305 2023] [php7:error] [pid 13836:tid 1956] [client ::1:61639] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:40:25.717372 2023] [php7:notice] [pid 13836:tid 1948] [client ::1:61652] PHP Notice: Trying to get property 'theme_name' of non-object in D:\\xampp74g\\htdocs\\_ps812\\var\\cache\\prod\\ContainerWsSZiJA\\appAppKernelProdContainer.php on line 2869, referer: http://localhost/_ps812/install/index.php ### Expected behavior no errors ### Steps to reproduce Install Prestashop under Windows ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Installing PS 8.1.2 under PHP 7.4 produces 85 errors

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34797/comments

https://github.com/PrestaShop/PrestaShop/issues/34797

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Installing PS 8.1.2 under PHP 7.4 produces 85 errors Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I did a fresh install of Prestashop 8.1.2 under Windows with PHP 7.4. WIndows is slow with webshops but I never have seen something like this: the installation took nearly a full hour. Despite the many errors it looks at first sight as if the installation succeeded and the shop is running ok. I found the following error messages in my error log: > [Sat Dec 09 16:28:34.175958 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61546] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:34.180102 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61546] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.880252 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61546] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.972406 2023] [php7:notice] [pid 13836:tid 1956] [client ::1:61584] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:36.979971 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61584] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:39.675261 2023] [php7:error] [pid 13836:tid 1956] [client ::1:61584] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/ [Sat Dec 09 16:28:51.272644 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61593] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:51.274631 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61593] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:53.969883 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61593] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:notice] [pid 13836:tid 1972] [client ::1:61592] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:54.069835 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61592] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:28:56.754498 2023] [php7:error] [pid 13836:tid 1972] [client ::1:61592] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.870150 2023] [php7:notice] [pid 13836:tid 1948] [client ::1:61598] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:06.874696 2023] [php7:warn] [pid 13836:tid 1948] [client ::1:61598] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.601075 2023] [php7:error] [pid 13836:tid 1948] [client ::1:61598] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815379 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61597] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.815828 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:09.819873 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61597] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:29:12.510462 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61597] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.813084 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61623] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:09.819627 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61623] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.536365 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61623] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.629510 2023] [php7:notice] [pid 13836:tid 1944] [client ::1:61620] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:12.639560 2023] [php7:warn] [pid 13836:tid 1944] [client ::1:61620] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:15.339801 2023] [php7:error] [pid 13836:tid 1944] [client ::1:61620] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.963505 2023] [php7:notice] [pid 13836:tid 1972] [client ::1:61626] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.966585 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:17.967609 2023] [php7:warn] [pid 13836:tid 1972] [client ::1:61626] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.685819 2023] [php7:error] [pid 13836:tid 1972] [client ::1:61626] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.739734 2023] [php7:notice] [pid 13836:tid 2004] [client ::1:61627] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:20.749903 2023] [php7:warn] [pid 13836:tid 2004] [client ::1:61627] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:23.439614 2023] [php7:error] [pid 13836:tid 2004] [client ::1:61627] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.449523 2023] [php7:notice] [pid 13836:tid 1960] [client ::1:61654] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:50.459624 2023] [php7:warn] [pid 13836:tid 1960] [client ::1:61654] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.178676 2023] [php7:error] [pid 13836:tid 1960] [client ::1:61654] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.264693 2023] [php7:notice] [pid 13836:tid 1956] [client ::1:61639] PHP Notice: Constant _PS_DO_NOT_LOAD_CONFIGURATION_ already defined in D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php on line 26, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.267690 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_PREFIX_ - assumed '_DB_PREFIX_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php on line 175, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_SERVER_ - assumed '_DB_SERVER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_USER_ - assumed '_DB_USER_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_PASSWD_ - assumed '_DB_PASSWD_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:53.268693 2023] [php7:warn] [pid 13836:tid 1956] [client ::1:61639] PHP Warning: Use of undefined constant _DB_NAME_ - assumed '_DB_NAME_' (this will throw an Error in a future version of PHP) in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php on line 219, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:30:55.947305 2023] [php7:error] [pid 13836:tid 1956] [client ::1:61639] PHP Fatal error: Uncaught PrestaShopException: Link to database cannot be established: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Host is onbekend. in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php:119\nStack trace:\n#0 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(331): DbPDOCore->connect()\n#1 D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\Db.php(241): DbCore->__construct('_DB_SERVER_', '_DB_USER_', '_DB_PASSWD_', '_DB_NAME_')\n#2 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(47): DbCore::getInstance()\n#3 D:\\xampp74g\\htdocs\\_ps812\\config\\alias.php(52): pSQL('configuration')\n#4 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(175): bqSQL('configuration')\n#5 D:\\xampp74g\\htdocs\\_ps812\\classes\\Configuration.php(229): ConfigurationCore::loadConfiguration()\n#6 D:\\xampp74g\\htdocs\\_ps812\\config\\smarty.config.inc.php(28): ConfigurationCore::get('PS_SMARTY_LOCAL')\n#7 D:\\xampp74g\\htdocs\\_ps812\\install\\controllers\\http\\smarty_compile.php(37): require_once('D:\\\\xampp74g\\\\htd...')\n#8 D:\\xampp74g\\htdocs\\_ps812\\install\\classes\\c in D:\\xampp74g\\htdocs\\_ps812\\classes\\db\\DbPDO.php on line 119, referer: http://localhost/_ps812/install/index.php [Sat Dec 09 16:40:25.717372 2023] [php7:notice] [pid 13836:tid 1948] [client ::1:61652] PHP Notice: Trying to get property 'theme_name' of non-object in D:\\xampp74g\\htdocs\\_ps812\\var\\cache\\prod\\ContainerWsSZiJA\\appAppKernelProdContainer.php on line 2869, referer: http://localhost/_ps812/install/index.php ### Expected behavior no errors ### Steps to reproduce Install Prestashop under Windows ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments This form contains fields for PHP and PS versions. However, not one for the operating system. I believe that is a mistake. Many problems are Windows specific. And I suspect that other operating systems such as IIS have their share too. This lack leads to errors that cannot be reproduced. ### Expected behavior An "operating system" field added ### Steps to reproduce happens always ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Add an operating system field

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34796/comments

https://github.com/PrestaShop/PrestaShop/issues/34796

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Add an operating system field Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments This form contains fields for PHP and PS versions. However, not one for the operating system. I believe that is a mistake. Many problems are Windows specific. And I suspect that other operating systems such as IIS have their share too. This lack leads to errors that cannot be reproduced. ### Expected behavior An "operating system" field added ### Steps to reproduce happens always ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am receiving the following PHP error when trying to use JSON output format for Web Services, regardless if I pass the Query String or Header parameter to specify the output format. ``` [Sat Dec 09 01:37:07.914633 2023] [php:error] [pid 00000] [client 000.000.000.000:00000] PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, string given in /my/prestashop/classes/webservice/WebserviceOutputJSON.php:168\nStack trace:\n#0 /my/prestashop/classes/webservice/WebserviceOutputJSON.php(168): array_filter()\n#1 [internal function]: WebserviceOutputJSONCore->{closure}()\n#2 /my/prestashop/classes/webservice/WebserviceOutputJSON.php(169): array_walk()\n#3 /my/prestashop/classes/webservice/WebserviceOutputBuilder.php(350): WebserviceOutputJSONCore->overrideContent()\n#4 /my/prestashop/classes/webservice/WebserviceRequest.php(1842): WebserviceOutputBuilderCore->getResourcesList()\n#5 /my/prestashop/classes/webservice/WebserviceRequest.php(634): WebserviceRequestCore->returnOutput()\n#6 /my/prestashop/webservice/dispatcher.php(94): WebserviceRequestCore->fetch()\n#7 {main}\n thrown in /my/prestashop/classes/webservice/WebserviceOutputJSON.php on line 168 ``` When I looked into the `classes/webservice/WebserviceOutputJSON.php:168`, I noticed that `array_walk` call in that method wasn't type-checking the `$item`: ```php array_walk($this->content, function (&$item) { $item = array_filter($item); }); ``` That can lead to unexpected behavior, since `array_filter` always expects an `array`. In order to proceed using JSON output format, I've applied a small patch: ```php array_walk($this->content, function (&$item) { if(is_array($item)) $item = array_filter($item); }); ``` ### Expected behavior I expected to get JSON output format, instead, I got a `500 Internal Server Error`. For example, for the following call: ```http GET /api HTTP/1.1 Host: my.prestashop.tld Authorization: Basic AaBbCcDdEeFfGgHhIJKLMNOPQRSTUVWXYZ0123456789 Output-Format: JSON Cookie: 4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e ``` I expected to get this response: ```json [ "attachments", "categories", "images", "price_ranges", "product_customization_fields", "product_feature_values", "product_features", "product_option_values", "product_options", "product_suppliers", "products", "shop_groups", "shop_urls", "specific_price_rules", "specific_prices", "stock_availables", "suppliers", "tags", "tax_rules", "taxes", "warehouses" ] ``` ### Steps to reproduce 1. Enable Web Services 2. Create a new key 3. Select the resource items from the list below 4. Try sending any HTTP request towards a Web Service endpoint and include JSON output format parameters Resources I selected (all HTTP methods) ``` attachments categories images price_ranges product_customization_fields product_feature_values product_features product_option_values product_options product_suppliers products shop_groups shop_urls specific_price_rules specific_prices stock_availables suppliers tags tax_rules taxes warehouses ``` ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

WebServices when using JSON output format: Uncaught TypeError: array_filter(): Argument #1 ($array)

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34794/comments

https://github.com/PrestaShop/PrestaShop/issues/34794

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : WebServices when using JSON output format: Uncaught TypeError: array_filter(): Argument #1 ($array) Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am receiving the following PHP error when trying to use JSON output format for Web Services, regardless if I pass the Query String or Header parameter to specify the output format. ``` [Sat Dec 09 01:37:07.914633 2023] [php:error] [pid 00000] [client 000.000.000.000:00000] PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, string given in /my/prestashop/classes/webservice/WebserviceOutputJSON.php:168\nStack trace:\n#0 /my/prestashop/classes/webservice/WebserviceOutputJSON.php(168): array_filter()\n#1 [internal function]: WebserviceOutputJSONCore->{closure}()\n#2 /my/prestashop/classes/webservice/WebserviceOutputJSON.php(169): array_walk()\n#3 /my/prestashop/classes/webservice/WebserviceOutputBuilder.php(350): WebserviceOutputJSONCore->overrideContent()\n#4 /my/prestashop/classes/webservice/WebserviceRequest.php(1842): WebserviceOutputBuilderCore->getResourcesList()\n#5 /my/prestashop/classes/webservice/WebserviceRequest.php(634): WebserviceRequestCore->returnOutput()\n#6 /my/prestashop/webservice/dispatcher.php(94): WebserviceRequestCore->fetch()\n#7 {main}\n thrown in /my/prestashop/classes/webservice/WebserviceOutputJSON.php on line 168 ``` When I looked into the `classes/webservice/WebserviceOutputJSON.php:168`, I noticed that `array_walk` call in that method wasn't type-checking the `$item`: ```php array_walk($this->content, function (&$item) { $item = array_filter($item); }); ``` That can lead to unexpected behavior, since `array_filter` always expects an `array`. In order to proceed using JSON output format, I've applied a small patch: ```php array_walk($this->content, function (&$item) { if(is_array($item)) $item = array_filter($item); }); ``` ### Expected behavior I expected to get JSON output format, instead, I got a `500 Internal Server Error`. For example, for the following call: ```http GET /api HTTP/1.1 Host: my.prestashop.tld Authorization: Basic AaBbCcDdEeFfGgHhIJKLMNOPQRSTUVWXYZ0123456789 Output-Format: JSON Cookie: 4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e2ec4541c5e9e2f4a3201b735f5d5238e ``` I expected to get this response: ```json [ "attachments", "categories", "images", "price_ranges", "product_customization_fields", "product_feature_values", "product_features", "product_option_values", "product_options", "product_suppliers", "products", "shop_groups", "shop_urls", "specific_price_rules", "specific_prices", "stock_availables", "suppliers", "tags", "tax_rules", "taxes", "warehouses" ] ``` ### Steps to reproduce 1. Enable Web Services 2. Create a new key 3. Select the resource items from the list below 4. Try sending any HTTP request towards a Web Service endpoint and include JSON output format parameters Resources I selected (all HTTP methods) ``` attachments categories images price_ranges product_customization_fields product_feature_values product_features product_option_values product_options product_suppliers products shop_groups shop_urls specific_price_rules specific_prices stock_availables suppliers tags tax_rules taxes warehouses ``` ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1.2 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am very sorry to see that this is the only way to reopen https://github.com/PrestaShop/PrestaShop/issues/34383 Quote from previous post: The virtual_uri field is a rather obscure field in the ps_shop_url table. In this Github there is just one post where it is even named. The field is supposed to provide altenative urls for the frontside. However, there is now a complaint on the forum that is changing some backoffice links too - with a resulting dysfunction. See: https://www.prestashop.com/forums/topic/1081141-no-input-file-specified-backoffice-url-prefix-is-not-working/ After that post [florine2623](https://github.com/florine2623) provided a test and said that he found no problems. The issue is that in his case the first shop had no virtual_uri while in the mentioned forum post all shops had a virtual_uri. This matters as the first shop is used for the backoffice. The forum post has in the mean time evolved. It provides the code trace how the admin is link is created. And that looks indeed problematic: /classes/Link.php contains the function getAdminBaseLink() getAdminBaseLink() contains the line: return $base.$shop->getBaseURI(); /classes/shop/Shop.php contains the function getBaseUri. getBaseUri() contains the line: return $this->physical_uri . $this->virtual_uri; ### Expected behavior Correct links in the backoffice ### Steps to reproduce See above ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

is the virtual_uri buggy 2?

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34793/comments

https://github.com/PrestaShop/PrestaShop/issues/34793

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : is the virtual_uri buggy 2? Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am very sorry to see that this is the only way to reopen https://github.com/PrestaShop/PrestaShop/issues/34383 Quote from previous post: The virtual_uri field is a rather obscure field in the ps_shop_url table. In this Github there is just one post where it is even named. The field is supposed to provide altenative urls for the frontside. However, there is now a complaint on the forum that is changing some backoffice links too - with a resulting dysfunction. See: https://www.prestashop.com/forums/topic/1081141-no-input-file-specified-backoffice-url-prefix-is-not-working/ After that post [florine2623](https://github.com/florine2623) provided a test and said that he found no problems. The issue is that in his case the first shop had no virtual_uri while in the mentioned forum post all shops had a virtual_uri. This matters as the first shop is used for the backoffice. The forum post has in the mean time evolved. It provides the code trace how the admin is link is created. And that looks indeed problematic: /classes/Link.php contains the function getAdminBaseLink() getAdminBaseLink() contains the line: return $base.$shop->getBaseURI(); /classes/shop/Shop.php contains the function getBaseUri. getBaseUri() contains the line: return $this->physical_uri . $this->virtual_uri; ### Expected behavior Correct links in the backoffice ### Steps to reproduce See above ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Two people on the forum report the same problem. Their backoffice crashes with the error: _Warning Undefined array key tabs_simplify_ The error happens during a "getLegacyLayout" function call in a Twig file. The error is puzzling as the word "tabs_simplify" is not present in the Prestashop code. The forum posts are: https://www.prestashop.com/forums/topic/1082345-probl%C3%A8me-prestashop-81-warning-undefined-array-key-tabs_simplify/ and https://www.prestashop.com/forums/topic/1082642-oops-please-correct-the-items-below-and-then-click-refresh-information-to-test-the-compatibility-of-your-new-system/?do=findComment&comment=3468757 ### Expected behavior correct running of backoffice ### Steps to reproduce Open backoffice ### PrestaShop version(s) where the bug happened 8.0 and 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Undefined array key tabs_simplify

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34791/comments

https://github.com/PrestaShop/PrestaShop/issues/34791

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Undefined array key tabs_simplify Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Two people on the forum report the same problem. Their backoffice crashes with the error: _Warning Undefined array key tabs_simplify_ The error happens during a "getLegacyLayout" function call in a Twig file. The error is puzzling as the word "tabs_simplify" is not present in the Prestashop code. The forum posts are: https://www.prestashop.com/forums/topic/1082345-probl%C3%A8me-prestashop-81-warning-undefined-array-key-tabs_simplify/ and https://www.prestashop.com/forums/topic/1082642-oops-please-correct-the-items-below-and-then-click-refresh-information-to-test-the-compatibility-of-your-new-system/?do=findComment&comment=3468757 ### Expected behavior correct running of backoffice ### Steps to reproduce Open backoffice ### PrestaShop version(s) where the bug happened 8.0 and 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I develop a module for a customer and I use the new translation system in a PrestaShop 1.7.8.10. I respect the recommendations of your documentation for the constructor: ```php class MyModule extends Module { public function __construct(string $name = null, Context $context = null) { $this->version = ... $this->name = ... $this->author = ... $this->tab = ... $this->ps_versions_compliancy = ... parent::__construct($name, $context); $this->displayName = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); $this->description = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); $this->confirmUninstall = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); } public function isUsingNewTranslationSystem(): bool { return true; } } ``` I need to add a tab in left menu of the back-office to access to the module faster. So I add this following code during my module installation in an other file for better code maintenance: ```php class ModuleInstaller { public function install(MyModule $module): bool { $module = MyModule::getInstance(); $tab = new Tab(); $tab->id_parent = (int) Tab::getIdFromClassName('AdminParentModulesSf'); $tab->active = true; $tab->module = $module->getName(); $tab->class_name = 'AdminMyModuleIndexController'; $tab->route_name = 'prestashop_module_mymodule_admin_index'; $tab->name = []; foreach (Language::getLanguages() as $languageData) { $tab->name[$languageData['id_lang']] = $module->getTranslation( 'module_name', $languageData['locale'] ); } return $tab->save(); } } ``` In my module class, I have this following code: ```php class MyModule extends Module { // ... public static function getInstance(): ?MyModule { $instance = self::getInstanceByName('mymodule'); return $instance instanceof MyModule ? $instance : null; } public function getTranslation(string $key, string $locale = null): ?string { $translationsList = [ 'module_name' => $this->trans('My module', [], 'Modules.Mymodule.Admin', $locale), ]; if (array_key_exists($key, $translationsList)) { return $translationsList[$key]; } return null; } public function install(): bool { try { if (Shop::isFeatureActive()) { Shop::setContext(Shop::CONTEXT_ALL); } return parent::install() && (new ModuleInstaller())->install($this) ; } catch (Exception $e) { $this->_errors[] = $e->getMessage(); return false; } } // ... } ``` After a first installation, I translated my expressions in "International > Translations > Installed modules > My module" and I exported my module translations in `/modules/mymodule/translations/fr-FR/ModulesMymoduleAdmin.fr-FR.xlf`. I also have the translations recorded in `ps_translations` table by the PrestaShop modules installation process. After a next installation and a cache clearing, I have the correct translations for my module display name, description, ..., in the modules manager but not for the tab in the back-office left menu. The module installation in CLI displays this error message: ``` WARNING [translation] Translation not found. ["id" => "My module","domain" => "ModulesMymoduleAdmin","locale" => "fr-FR"] L'action Install sur le module mymodule a réussi. ``` Thank you for your help. Have a nice day! ### Expected behavior After the module installation, I should see "Mon module" in the back-office left menu for a french user but I still have "My module". ### Steps to reproduce 1. Create a module with this code. 2. Install it for a first time. 3. Translate the module and export translations. 4. Uninstall the module (translations in `ps_translations` table should be still here). 5. Clear the cache. 6. Install the module. 7. Clear the cache again. ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Module tab not translated with given "$locale" parameter in "Module::trans()" method in 1.7.8.10

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34789/comments

https://github.com/PrestaShop/PrestaShop/issues/34789

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module tab not translated with given "$locale" parameter in "Module::trans()" method in 1.7.8.10 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, I develop a module for a customer and I use the new translation system in a PrestaShop 1.7.8.10. I respect the recommendations of your documentation for the constructor: ```php class MyModule extends Module { public function __construct(string $name = null, Context $context = null) { $this->version = ... $this->name = ... $this->author = ... $this->tab = ... $this->ps_versions_compliancy = ... parent::__construct($name, $context); $this->displayName = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); $this->description = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); $this->confirmUninstall = $this->trans('My display name', [], 'Modules.Mymodule.Admin'); } public function isUsingNewTranslationSystem(): bool { return true; } } ``` I need to add a tab in left menu of the back-office to access to the module faster. So I add this following code during my module installation in an other file for better code maintenance: ```php class ModuleInstaller { public function install(MyModule $module): bool { $module = MyModule::getInstance(); $tab = new Tab(); $tab->id_parent = (int) Tab::getIdFromClassName('AdminParentModulesSf'); $tab->active = true; $tab->module = $module->getName(); $tab->class_name = 'AdminMyModuleIndexController'; $tab->route_name = 'prestashop_module_mymodule_admin_index'; $tab->name = []; foreach (Language::getLanguages() as $languageData) { $tab->name[$languageData['id_lang']] = $module->getTranslation( 'module_name', $languageData['locale'] ); } return $tab->save(); } } ``` In my module class, I have this following code: ```php class MyModule extends Module { // ... public static function getInstance(): ?MyModule { $instance = self::getInstanceByName('mymodule'); return $instance instanceof MyModule ? $instance : null; } public function getTranslation(string $key, string $locale = null): ?string { $translationsList = [ 'module_name' => $this->trans('My module', [], 'Modules.Mymodule.Admin', $locale), ]; if (array_key_exists($key, $translationsList)) { return $translationsList[$key]; } return null; } public function install(): bool { try { if (Shop::isFeatureActive()) { Shop::setContext(Shop::CONTEXT_ALL); } return parent::install() && (new ModuleInstaller())->install($this) ; } catch (Exception $e) { $this->_errors[] = $e->getMessage(); return false; } } // ... } ``` After a first installation, I translated my expressions in "International > Translations > Installed modules > My module" and I exported my module translations in `/modules/mymodule/translations/fr-FR/ModulesMymoduleAdmin.fr-FR.xlf`. I also have the translations recorded in `ps_translations` table by the PrestaShop modules installation process. After a next installation and a cache clearing, I have the correct translations for my module display name, description, ..., in the modules manager but not for the tab in the back-office left menu. The module installation in CLI displays this error message: ``` WARNING [translation] Translation not found. ["id" => "My module","domain" => "ModulesMymoduleAdmin","locale" => "fr-FR"] L'action Install sur le module mymodule a réussi. ``` Thank you for your help. Have a nice day! ### Expected behavior After the module installation, I should see "Mon module" in the back-office left menu for a french user but I still have "My module". ### Steps to reproduce 1. Create a module with this code. 2. Install it for a first time. 3. Translate the module and export translations. 4. Uninstall the module (translations in `ps_translations` table should be still here). 5. Clear the cache. 6. Install the module. 7. Clear the cache again. ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I launch an upgrade via CLI commande : D:\xampp\php>php D:\mysite\modules\autoupgrade\cli-upgrade.php --dir=admin --channel=major I have this error : PHP Fatal error: Uncaught Exception: Can't find PrestaShop Version in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php:90 Stack trace: #0 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(202): PrestaShop\Module\AutoUpgrade\PrestashopConfiguration->getPrestaShopVersion() #1 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(299): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getProperty('version') #2 D:\pixomaniakWebSites\modules\autoupgrade\classes\TaskRunner\Upgrade\AllUpgradeTasks.php(64): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getUpgrader() #3 D:\pixomaniakWebSites\modules\autoupgrade\cli-upgrade.php(37): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\AllUpgradeTasks->setOptions(Array) #4 {main} thrown in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php on line 90 Fatal error: Uncaught Exception: Can't find PrestaShop Version in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php:90 Stack trace: #0 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(202): PrestaShop\Module\AutoUpgrade\PrestashopConfiguration->getPrestaShopVersion() #1 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(299): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getProperty('version') #2 D:\pixomaniakWebSites\modules\autoupgrade\classes\TaskRunner\Upgrade\AllUpgradeTasks.php(64): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getUpgrader() #3 D:\pixomaniakWebSites\modules\autoupgrade\cli-upgrade.php(37): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\AllUpgradeTasks->setOptions(Array) #4 {main} thrown in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php on line 90 ### Expected behavior I exprect that upgrade should be smooth ### Steps to reproduce Upgrade with SQLI ### PrestaShop version(s) where the bug happened 1.7.7.0 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Bug when Upgrading from 1.7.0.0 to 8.1.2

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34787/comments

https://github.com/PrestaShop/PrestaShop/issues/34787

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Bug when Upgrading from 1.7.0.0 to 8.1.2 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I launch an upgrade via CLI commande : D:\xampp\php>php D:\mysite\modules\autoupgrade\cli-upgrade.php --dir=admin --channel=major I have this error : PHP Fatal error: Uncaught Exception: Can't find PrestaShop Version in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php:90 Stack trace: #0 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(202): PrestaShop\Module\AutoUpgrade\PrestashopConfiguration->getPrestaShopVersion() #1 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(299): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getProperty('version') #2 D:\pixomaniakWebSites\modules\autoupgrade\classes\TaskRunner\Upgrade\AllUpgradeTasks.php(64): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getUpgrader() #3 D:\pixomaniakWebSites\modules\autoupgrade\cli-upgrade.php(37): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\AllUpgradeTasks->setOptions(Array) #4 {main} thrown in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php on line 90 Fatal error: Uncaught Exception: Can't find PrestaShop Version in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php:90 Stack trace: #0 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(202): PrestaShop\Module\AutoUpgrade\PrestashopConfiguration->getPrestaShopVersion() #1 D:\pixomaniakWebSites\modules\autoupgrade\classes\UpgradeContainer.php(299): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getProperty('version') #2 D:\pixomaniakWebSites\modules\autoupgrade\classes\TaskRunner\Upgrade\AllUpgradeTasks.php(64): PrestaShop\Module\AutoUpgrade\UpgradeContainer->getUpgrader() #3 D:\pixomaniakWebSites\modules\autoupgrade\cli-upgrade.php(37): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\AllUpgradeTasks->setOptions(Array) #4 {main} thrown in D:\pixomaniakWebSites\modules\autoupgrade\classes\PrestashopConfiguration.php on line 90 ### Expected behavior I exprect that upgrade should be smooth ### Steps to reproduce Upgrade with SQLI ### PrestaShop version(s) where the bug happened 1.7.7.0 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am using Prestashop 1.7.8 and tried to upgrade to 1.7.8.10 I tried to do it by using 1-Clip-Upgrade, but it shows the following error  ### Expected behavior I expected to upgrade without any problems, becasuse, I have done the same process before. I will explain: I made a backup in september and **AFTER** that I upgraded to 1.7.8.10 using 1-click upgrade. Everything went well. So, recenttly I restored my website from a that backup (which did not include the upgrade). Since my backup did not include this update I proceed to upgrade again in the same way I did it before, but now it shows the error I mentioned. I have attached the final part of the log fil.e  0/559572d8-3952-49ba-be9b-8bee9d3fa982) ### Steps to reproduce 1. I installed module 1-Click Upgrade 2. I put website in maintenance mode 3. All conditions to proceed were checked ok 4. I proceed to press UPGRADE 5. The process started 6. Just inmediately it show the error I mentioned above. ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened native 8.2 ### If your bug is related to a module, specify its name and its version 1-click upgrade ### Your company or customer's name goes here (if applicable). Corporación Yachay SAC

1-click upgrade error to upgrade to 1.7.8.10

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34786/comments

https://github.com/PrestaShop/PrestaShop/issues/34786

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : 1-click upgrade error to upgrade to 1.7.8.10 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I am using Prestashop 1.7.8 and tried to upgrade to 1.7.8.10 I tried to do it by using 1-Clip-Upgrade, but it shows the following error  ### Expected behavior I expected to upgrade without any problems, becasuse, I have done the same process before. I will explain: I made a backup in september and **AFTER** that I upgraded to 1.7.8.10 using 1-click upgrade. Everything went well. So, recenttly I restored my website from a that backup (which did not include the upgrade). Since my backup did not include this update I proceed to upgrade again in the same way I did it before, but now it shows the error I mentioned. I have attached the final part of the log fil.e  0/559572d8-3952-49ba-be9b-8bee9d3fa982) ### Steps to reproduce 1. I installed module 1-Click Upgrade 2. I put website in maintenance mode 3. All conditions to proceed were checked ok 4. I proceed to press UPGRADE 5. The process started 6. Just inmediately it show the error I mentioned above. ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened native 8.2 ### If your bug is related to a module, specify its name and its version 1-click upgrade ### Your company or customer's name goes here (if applicable). Corporación Yachay SAC --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The fact that I have to put all inputs in email field to not get an error is not a good user experience. <img width="1222" alt="Screenshot 2023-12-07 at 16 34 45" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/1a4c6b92-e326-4164-be26-8e54cbedea7f"> Maybe if all options are enabled, the admin address email should be automatically displayed. ### Expected behavior I should be able to add just an email address in just one of the options of Merchant Notifications without having an error. ### Steps to reproduce 1. Go to BO > Module Manager > Email alerts > Configure 2. See in Merchants Notifications > All options are enabled 3. Add 1 email address for "New order" > Save 4. See error :x: ### Acceptance tests * Remove these lines : https://github.com/PrestaShop/PrestaShop/blob/51a646b1b31c4be3c2f8b0d8db5303b0d582c35b/tests/UI/pages/BO/modules/psEmailAlerts/index.ts#L66-L68 https://github.com/PrestaShop/PrestaShop/blob/51a646b1b31c4be3c2f8b0d8db5303b0d582c35b/tests/UI/pages/BO/modules/psEmailAlerts/index.ts#L82-L84 ### PrestaShop version(s) where the bug happened 1.7.8.x to 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_emailalerts v2.4.2 ### Your company or customer's name goes here (if applicable). _No response_

ps_emailalerts - Merchant notifications options are all enabled, but with no email saved.

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34784/comments

https://github.com/PrestaShop/PrestaShop/issues/34784

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_emailalerts - Merchant notifications options are all enabled, but with no email saved. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The fact that I have to put all inputs in email field to not get an error is not a good user experience. <img width="1222" alt="Screenshot 2023-12-07 at 16 34 45" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/1a4c6b92-e326-4164-be26-8e54cbedea7f"> Maybe if all options are enabled, the admin address email should be automatically displayed. ### Expected behavior I should be able to add just an email address in just one of the options of Merchant Notifications without having an error. ### Steps to reproduce 1. Go to BO > Module Manager > Email alerts > Configure 2. See in Merchants Notifications > All options are enabled 3. Add 1 email address for "New order" > Save 4. See error :x: ### Acceptance tests * Remove these lines : https://github.com/PrestaShop/PrestaShop/blob/51a646b1b31c4be3c2f8b0d8db5303b0d582c35b/tests/UI/pages/BO/modules/psEmailAlerts/index.ts#L66-L68 https://github.com/PrestaShop/PrestaShop/blob/51a646b1b31c4be3c2f8b0d8db5303b0d582c35b/tests/UI/pages/BO/modules/psEmailAlerts/index.ts#L82-L84 ### PrestaShop version(s) where the bug happened 1.7.8.x to 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_emailalerts v2.4.2 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We try to send the combinations of the products via webservice, sending all the values ​​associated with the product at once, I leave an example of the xml. <prestashop xmlns:xlink='http://www.w3.org/1999/xlink'> <combination> <id_product>3666</id_product> <location></location> <ean13></ean13> <isbn></isbn> <upc></upc> <mpn></mpn> <quantity>1300</quantity> <reference></reference> <supplier_reference></supplier_reference> <wholesale_price></wholesale_price> <price></price> <ecotax></ecotax> <weight></weight> <unit_price_impact></unit_price_impact> <minimal_quantity>1</minimal_quantity> <low_stock_threshold></low_stock_threshold> <low_stock_alert></low_stock_alert> <default_on></default_on> <available_date></available_date> <associations> <product_option_values> <product_option_value> <id>5550</id> <id>5496</id> <id>5959</id> <id>6087</id> </product_option_value> </product_option_values> </associations> </combination> </prestashop> Whats wrong with this xml? Its possible send multiple assosiations? Only associate the product with 1 attribute. ### Expected behavior An association of combinations with multiple attributes ### Steps to reproduce - ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Combinations via webservice

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34779/comments

https://github.com/PrestaShop/PrestaShop/issues/34779

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Combinations via webservice Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments We try to send the combinations of the products via webservice, sending all the values ​​associated with the product at once, I leave an example of the xml. <prestashop xmlns:xlink='http://www.w3.org/1999/xlink'> <combination> <id_product>3666</id_product> <location></location> <ean13></ean13> <isbn></isbn> <upc></upc> <mpn></mpn> <quantity>1300</quantity> <reference></reference> <supplier_reference></supplier_reference> <wholesale_price></wholesale_price> <price></price> <ecotax></ecotax> <weight></weight> <unit_price_impact></unit_price_impact> <minimal_quantity>1</minimal_quantity> <low_stock_threshold></low_stock_threshold> <low_stock_alert></low_stock_alert> <default_on></default_on> <available_date></available_date> <associations> <product_option_values> <product_option_value> <id>5550</id> <id>5496</id> <id>5959</id> <id>6087</id> </product_option_value> </product_option_values> </associations> </combination> </prestashop> Whats wrong with this xml? Its possible send multiple assosiations? Only associate the product with 1 attribute. ### Expected behavior An association of combinations with multiple attributes ### Steps to reproduce - ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments after putting the store in maintenance, emptying the cache, I launched 1ClickUpgrade with these parameters all points to check are green Disable backup (i have backup server) server power : low disable non-prestashop modules: yes disable override : no upgrade default theme : yes switch to default : no RTL and email template : no and the error is [INTERNAL] /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 180 - Symfony\Component\Config\Exception\LoaderLoadException: The file "/home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../parameters.yml" does not contain valid YAML: Duplicate key "parameters" detected at line 7 in /home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../parameters.yml (which is being imported from "/home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../common.yml"). #0 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport('/home/hfrquggt/...', NULL, false, '/home/hfrquggt/...') #1 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import('parameters.yml', NULL, false, '/home/hfrquggt/...') #2 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import('parameters.yml', NULL, false, '/home/hfrquggt/...') #3 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports(Array, '/home/hfrquggt/...') #4 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(165): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load('/home/hfrquggt/...', NULL) #5 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport('/home/hfrquggt/...', NULL, false, '/home/hfrquggt/...') #6 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import('../common.yml', NULL, false, '/home/hfrquggt/...') #7 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import('../common.yml', NULL, false, '/home/hfrquggt/...') #8 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports(Array, '/home/hfrquggt/...') #9 /home/hfrquggt/public_html/src/PrestaShopBundle/DependencyInjection/Compiler/LoadServicesFromModulesPass.php(83): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load('services.yml') #10 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php(94): PrestaShopBundle\DependencyInjection\Compiler\LoadServicesFromModulesPass->process(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #11 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php(762): Symfony\Component\DependencyInjection\Compiler\Compiler->compile(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #12 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(594): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #13 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #14 /home/hfrquggt/public_html/app/AppKernel.php(96): Symfony\Component\HttpKernel\Kernel->boot() #15 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(76): AppKernel->boot() #16 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(45): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #17 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(88): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #18 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #19 /home/hfrquggt/public_html/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #20 /home/hfrquggt/public_html/arriereboutique/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #21 {main} RE update actions : Copied /vendor/willdurand/negotiation/src/Negotiation/Exception/InvalidMediaType.php. Copied /vendor/willdurand/negotiation/src/Negotiation/LanguageNegotiator.php. Copied /vendor/willdurand/negotiation/src/Negotiation/Negotiator.php. Directory /webservice already exists. Copied /webservice/dispatcher.php. Copied /webservice/index.php. [SKIP] directory "/app/cache/" does not exist and cannot be emptied. [CLEANING CACHE] File dev removed [CLEANING CACHE] File dsd removed [CLEANING CACHE] File gfhfdh removed [CLEANING CACHE] File prod removed Cleaning file cache API keys not present in parameters, generating Keys generated using openssl_pkey_new, exporting private and public keys Updating parameters file Parameters file updated Running opcache_reset ### Expected behavior A complete upgrade ### Steps to reproduce after putting the store in maintenance, emptying the cache, I launched 1ClickUpgrade with these parameters all points to check are green Disable backup (i have backup server) server power : low disable non-prestashop modules: yes disable override : no upgrade default theme : yes switch to default : no RTL and email template : no ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

1clickUpgrade 1.7.8.10 to 8.1.2

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34777/comments

https://github.com/PrestaShop/PrestaShop/issues/34777

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : 1clickUpgrade 1.7.8.10 to 8.1.2 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments after putting the store in maintenance, emptying the cache, I launched 1ClickUpgrade with these parameters all points to check are green Disable backup (i have backup server) server power : low disable non-prestashop modules: yes disable override : no upgrade default theme : yes switch to default : no RTL and email template : no and the error is [INTERNAL] /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php line 180 - Symfony\Component\Config\Exception\LoaderLoadException: The file "/home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../parameters.yml" does not contain valid YAML: Duplicate key "parameters" detected at line 7 in /home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../parameters.yml (which is being imported from "/home/hfrquggt/public_html/modules/ps_eventbus/config/admin/../common.yml"). #0 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport('/home/hfrquggt/...', NULL, false, '/home/hfrquggt/...') #1 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import('parameters.yml', NULL, false, '/home/hfrquggt/...') #2 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import('parameters.yml', NULL, false, '/home/hfrquggt/...') #3 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports(Array, '/home/hfrquggt/...') #4 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(165): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load('/home/hfrquggt/...', NULL) #5 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/Config/Loader/FileLoader.php(104): Symfony\Component\Config\Loader\FileLoader->doImport('/home/hfrquggt/...', NULL, false, '/home/hfrquggt/...') #6 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/FileLoader.php(66): Symfony\Component\Config\Loader\FileLoader->import('../common.yml', NULL, false, '/home/hfrquggt/...') #7 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(197): Symfony\Component\DependencyInjection\Loader\FileLoader->import('../common.yml', NULL, false, '/home/hfrquggt/...') #8 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Loader/YamlFileLoader.php(133): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->parseImports(Array, '/home/hfrquggt/...') #9 /home/hfrquggt/public_html/src/PrestaShopBundle/DependencyInjection/Compiler/LoadServicesFromModulesPass.php(83): Symfony\Component\DependencyInjection\Loader\YamlFileLoader->load('services.yml') #10 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/Compiler.php(94): PrestaShopBundle\DependencyInjection\Compiler\LoadServicesFromModulesPass->process(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #11 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ContainerBuilder.php(762): Symfony\Component\DependencyInjection\Compiler\Compiler->compile(Object(Symfony\Component\DependencyInjection\ContainerBuilder)) #12 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(594): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #13 /home/hfrquggt/public_html/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(136): Symfony\Component\HttpKernel\Kernel->initializeContainer() #14 /home/hfrquggt/public_html/app/AppKernel.php(96): Symfony\Component\HttpKernel\Kernel->boot() #15 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(76): AppKernel->boot() #16 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(45): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initAppKernel() #17 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(88): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #18 /home/hfrquggt/public_html/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #19 /home/hfrquggt/public_html/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #20 /home/hfrquggt/public_html/arriereboutique/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #21 {main} RE update actions : Copied /vendor/willdurand/negotiation/src/Negotiation/Exception/InvalidMediaType.php. Copied /vendor/willdurand/negotiation/src/Negotiation/LanguageNegotiator.php. Copied /vendor/willdurand/negotiation/src/Negotiation/Negotiator.php. Directory /webservice already exists. Copied /webservice/dispatcher.php. Copied /webservice/index.php. [SKIP] directory "/app/cache/" does not exist and cannot be emptied. [CLEANING CACHE] File dev removed [CLEANING CACHE] File dsd removed [CLEANING CACHE] File gfhfdh removed [CLEANING CACHE] File prod removed Cleaning file cache API keys not present in parameters, generating Keys generated using openssl_pkey_new, exporting private and public keys Updating parameters file Parameters file updated Running opcache_reset ### Expected behavior A complete upgrade ### Steps to reproduce after putting the store in maintenance, emptying the cache, I launched 1ClickUpgrade with these parameters all points to check are green Disable backup (i have backup server) server power : low disable non-prestashop modules: yes disable override : no upgrade default theme : yes switch to default : no RTL and email template : no ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I will upgrade Prestashop 8.0.5 to 8.1.2 But the autoupgrade module doesn't detect the latest version. Also manual upgrade have a lot of problems Autoupgrade module shows this: Congratulations, you are already using the latest version available! Your current PrestaShop version: 8.0.5 Your current PHP version: 8.0.30 Latest official version for minor channel.: 8.0 stable - (8.0.5)  How can I fix it? ### Expected behavior Get the latest version 8.1.2 ### Steps to reproduce ? ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.0.30 ### If your bug is related to a module, specify its name and its version 1-click upgrade ### Your company or customer's name goes here (if applicable). _No response_

Autoupgrade doesn't detect latest version

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34776/comments

https://github.com/PrestaShop/PrestaShop/issues/34776

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade doesn't detect latest version Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I will upgrade Prestashop 8.0.5 to 8.1.2 But the autoupgrade module doesn't detect the latest version. Also manual upgrade have a lot of problems Autoupgrade module shows this: Congratulations, you are already using the latest version available! Your current PrestaShop version: 8.0.5 Your current PHP version: 8.0.30 Latest official version for minor channel.: 8.0 stable - (8.0.5)  How can I fix it? ### Expected behavior Get the latest version 8.1.2 ### Steps to reproduce ? ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.0.30 ### If your bug is related to a module, specify its name and its version 1-click upgrade ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Prevent set the same order state twice (or more) in a row For example: If the order has current state "Awaiting bank wire payment" the employees, function in the module, via request webservice etc. can't set as next state "Awaiting bank wire payment". Next order state need to be different order state. ### Expected behavior _No response_ ### Steps to reproduce Iam experienced that card payment gateway sent answer about payment 3 times in one moment. The result is 3 payment statuses "Payment Accepted" in the order and 3 notification emails to customer in one moment. It is unwanted behaviour. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Prevent set the same order state twice (or more) in a row

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34774/comments

https://github.com/PrestaShop/PrestaShop/issues/34774

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prevent set the same order state twice (or more) in a row Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Prevent set the same order state twice (or more) in a row For example: If the order has current state "Awaiting bank wire payment" the employees, function in the module, via request webservice etc. can't set as next state "Awaiting bank wire payment". Next order state need to be different order state. ### Expected behavior _No response_ ### Steps to reproduce Iam experienced that card payment gateway sent answer about payment 3 times in one moment. The result is 3 payment statuses "Payment Accepted" in the order and 3 notification emails to customer in one moment. It is unwanted behaviour. ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments - PrestaShop Version: Prestashop 8.1.2 - PHP Version: PHP version: 8.1.16 - Database client version: libmysql - mysqlnd 8.1.16 - Steps to reproduce the problem 1. Godaddy.com = Web Hosting Deluxe 2. Run Setup Prestashop 8.1.2 3. -> Step 1  Step 2 Error Message An error has occurrederror  | ID | Description | Description1 | |-----:|:------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------| | nan | Useful settings | nan | | 1 | System: Unix, Linux, or Windows | Linux | | 2 | MySQL: 5.6 or later | Server version: 5.7.43-cll-lve - MySQL - Community Server - (GPL) | | 3 | PHP: 7.2 or later | PHP Version 8.1.24 | | 4 | allow_url_fopen | on | | 5 | register_globals | off | | 6 | upload_max_filesize set to "16MB" or more | 32 MB | | nan | Must have PHP extensions | nan | | 7 | CURL: the Client URL extension is used to download remote resources like modules and localization packages. | enabled | | 8 | DOM: the DOM extension is needed to parse XML documents. | enabled | | 9 | Fileinfo: the File information extension is used to find out the file type of uploaded files. | enabled | | 10 | GD: the GD extension is used to create thumbnails for the images that you upload. | enabled | | 11 | Intl: the ICONV extension is used to convert character sets. | enabled | | 12 | Mbstring: the Multibyte string extension is used to perform string operations everywhere. | enabled | | 13 | Zip: the Zip extension is used to expand compressed files such as modules and localization packages. | enabled | | 14 | JSON: the JSON extension is used to manage JSON format. | enabled | | 15 | Iconv: the ICONV extension is used to convert character sets. | enabled | ### Expected behavior Complete Setup the Prestashop ### Steps to reproduce 1. Godaddy.com = Web Hosting Deluxe 2. Run Setup Prestashop 8.1.2 3. Error An error has occurrederror (75%) ### PrestaShop version(s) where the bug happened Prestashop 8.1.2 ### PHP version(s) where the bug happened PHP version: 8.1.16 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Prestashop 8.1.2 An error occurred during installation (75%)

https://api.github.com/repos/PrestaShop/PrestaShop/issues/34771/comments

https://github.com/PrestaShop/PrestaShop/issues/34771

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 8.1.2 An error occurred during installation (75%) Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments - PrestaShop Version: Prestashop 8.1.2 - PHP Version: PHP version: 8.1.16 - Database client version: libmysql - mysqlnd 8.1.16 - Steps to reproduce the problem 1. Godaddy.com = Web Hosting Deluxe 2. Run Setup Prestashop 8.1.2 3. -> Step 1  Step 2 Error Message An error has occurrederror  | ID | Description | Description1 | |-----:|:------------------------------------------------------------------------------------------------------------|:----------------------------------------------------------------| | nan | Useful settings | nan | | 1 | System: Unix, Linux, or Windows | Linux | | 2 | MySQL: 5.6 or later | Server version: 5.7.43-cll-lve - MySQL - Community Server - (GPL) | | 3 | PHP: 7.2 or later | PHP Version 8.1.24 | | 4 | allow_url_fopen | on | | 5 | register_globals | off | | 6 | upload_max_filesize set to "16MB" or more | 32 MB | | nan | Must have PHP extensions | nan | | 7 | CURL: the Client URL extension is used to download remote resources like modules and localization packages. | enabled | | 8 | DOM: the DOM extension is needed to parse XML documents. | enabled | | 9 | Fileinfo: the File information extension is used to find out the file type of uploaded files. | enabled | | 10 | GD: the GD extension is used to create thumbnails for the images that you upload. | enabled | | 11 | Intl: the ICONV extension is used to convert character sets. | enabled | | 12 | Mbstring: the Multibyte string extension is used to perform string operations everywhere. | enabled | | 13 | Zip: the Zip extension is used to expand compressed files such as modules and localization packages. | enabled | | 14 | JSON: the JSON extension is used to manage JSON format. | enabled | | 15 | Iconv: the ICONV extension is used to convert character sets. | enabled | ### Expected behavior Complete Setup the Prestashop ### Steps to reproduce 1. Godaddy.com = Web Hosting Deluxe 2. Run Setup Prestashop 8.1.2 3. Error An error has occurrederror (75%) ### PrestaShop version(s) where the bug happened Prestashop 8.1.2 ### PHP version(s) where the bug happened PHP version: 8.1.16 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---