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 The new Admin theme - v8.1.5 implements the download of a foreign source: https://unpkg.com/@prestashopcorp/edition-reskin@0.2.4/dist/back.min.css ( which in my opinion is also a little out of privacy as this site can track exactly who and how is using prestashop! ) Aside from all legality problems.... it is not possible to change the way in which the list of products is displayed on the admin page which for a large store becomes difficult to follow all the products... making the central part narrower even if in reality there is plenty of space to adjust the page with products so as not to force the admin to scroll to the bottom of the page every time to pull the horizontal bar and then return again to up and down again... the self-adaptation of the central part is missing due precisely to instructions that we don't know because they are there ... but they do more harm than good... and above all, being a remote .css file, you can't even modify them... I also post some screenshots so can understand the situation:   ### Expected behavior _No response_ ### Steps to reproduce Go to Admin page of products ### PrestaShop version(s) where the bug happened v8.1.5 ### 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_

Product list display issue in Admin - v8.1.5

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Product list display issue in Admin - v8.1.5 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 new Admin theme - v8.1.5 implements the download of a foreign source: https://unpkg.com/@prestashopcorp/edition-reskin@0.2.4/dist/back.min.css ( which in my opinion is also a little out of privacy as this site can track exactly who and how is using prestashop! ) Aside from all legality problems.... it is not possible to change the way in which the list of products is displayed on the admin page which for a large store becomes difficult to follow all the products... making the central part narrower even if in reality there is plenty of space to adjust the page with products so as not to force the admin to scroll to the bottom of the page every time to pull the horizontal bar and then return again to up and down again... the self-adaptation of the central part is missing due precisely to instructions that we don't know because they are there ... but they do more harm than good... and above all, being a remote .css file, you can't even modify them... I also post some screenshots so can understand the situation:   ### Expected behavior _No response_ ### Steps to reproduce Go to Admin page of products ### PrestaShop version(s) where the bug happened v8.1.5 ### 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 you sign in with an account, then you sign out. if you try to sign in with a different account, you will stay seeing the name of the first account   ### Expected behavior the name of the new account you are signing in should be shown ### Steps to reproduce enter to the website https://souk-beirut.com 1-sign in with gm@souk-beirut.com / password: omaromar 2- sign out from souk-beirut.com 3- sign in with fashionlb.market@gmail.com / password: omaromar 4- you will see the name of the account gm@souk-beirut.com not the name of fashionlb.market@gmail.com. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### If your bug is related to a module, specify its name and its version ps_customersignin V2.0.5 ### Your company or customer's name goes here (if applicable). _No response_

ps_customersignin - Module

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_customersignin - Module 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 sign in with an account, then you sign out. if you try to sign in with a different account, you will stay seeing the name of the first account   ### Expected behavior the name of the new account you are signing in should be shown ### Steps to reproduce enter to the website https://souk-beirut.com 1-sign in with gm@souk-beirut.com / password: omaromar 2- sign out from souk-beirut.com 3- sign in with fashionlb.market@gmail.com / password: omaromar 4- you will see the name of the account gm@souk-beirut.com not the name of fashionlb.market@gmail.com. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### If your bug is related to a module, specify its name and its version ps_customersignin V2.0.5 ### 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 generating an invoice for 400 orders, an error is displayed (error 500) <img width="1383" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/122271944/ee6941eb-4a04-4d8e-a8d0-5fb726bec3ed"> This problem can only be bypassed by increasing the parameter **max_execution_time** in **php.ini** file but there is still a latency of more than 1 minute during invoice generation. In the OrderInvoiceCore class, I find the SQL query with double join captured below, in the getProductsDetail() method:  This query has a double join(an expensive transaction) > 1. Optimization of the query or indexing of the target columns is necessary. > 2. The approach to invoice generation needs to be improved to gain on processing time. ### Expected behavior No latency when generating invoices for orders ### Steps to reproduce BO > Order > invoice > generate a pdf file ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.27 ### 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_

Performance issue for generating invoice for an important number of orders

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Performance issue for generating invoice for an important number of orders 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 generating an invoice for 400 orders, an error is displayed (error 500) <img width="1383" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/122271944/ee6941eb-4a04-4d8e-a8d0-5fb726bec3ed"> This problem can only be bypassed by increasing the parameter **max_execution_time** in **php.ini** file but there is still a latency of more than 1 minute during invoice generation. In the OrderInvoiceCore class, I find the SQL query with double join captured below, in the getProductsDetail() method:  This query has a double join(an expensive transaction) > 1. Optimization of the query or indexing of the target columns is necessary. > 2. The approach to invoice generation needs to be improved to gain on processing time. ### Expected behavior No latency when generating invoices for orders ### Steps to reproduce BO > Order > invoice > generate a pdf file ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.27 ### 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 PrestaShop BO versions 8 and 9, when accessing certain pages such as the module configuration page _(**for example:** the `statsdata` configuration page)_, we can observe that there are two occurrences of the `page-head` element in the code. Each `page-head` contains different information. Both sections are not visible on the page because they are overlapping, so one is hiding the other. **_Note:_** In v9, if the **Symfony layout** is activated in the Lab features section, the problem is also present.  ### Expected behavior There must be only one `page-head` on the page with the correct data. ### Steps to reproduce 1. Go to the modules page and search for `statsdata`. 2. Click the "**Configure**" button. 3. Inspect the page HTML and check for the elements inside `<div id="content" class="bootstrap">`. 4. If you have two `page-head` elements like in the screenshot, there is a problem; you should have only one. <img width="317" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/110676325/98b34886-4379-49f8-b3cb-069a8d664762"> ### PrestaShop version(s) where the bug happened FROM v8.1.4 TO v9 ### 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). PrestaShopCorp

Page head appear duplicated with varying content on specific pages

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Page head appear duplicated with varying content on specific pages 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 PrestaShop BO versions 8 and 9, when accessing certain pages such as the module configuration page _(**for example:** the `statsdata` configuration page)_, we can observe that there are two occurrences of the `page-head` element in the code. Each `page-head` contains different information. Both sections are not visible on the page because they are overlapping, so one is hiding the other. **_Note:_** In v9, if the **Symfony layout** is activated in the Lab features section, the problem is also present.  ### Expected behavior There must be only one `page-head` on the page with the correct data. ### Steps to reproduce 1. Go to the modules page and search for `statsdata`. 2. Click the "**Configure**" button. 3. Inspect the page HTML and check for the elements inside `<div id="content" class="bootstrap">`. 4. If you have two `page-head` elements like in the screenshot, there is a problem; you should have only one. <img width="317" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/110676325/98b34886-4379-49f8-b3cb-069a8d664762"> ### PrestaShop version(s) where the bug happened FROM v8.1.4 TO v9 ### 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). PrestaShopCorp --- 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 Only on branch develop of PS with mode debug enabled, I have an exception when I try to configure my productcomments module. If I disable debug mode, it is OK. <img width="1078" alt="Screenshot 2024-04-05 at 15 12 10" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d1186e92-ced1-4c6e-aad8-de906e27058f"> ### Expected behavior No exception should be displayed. The Configure page should be displayed correctly. ### Steps to reproduce 1. Go to BO > Advanced parameters > Enable Debug Mode 2. Go to Modules > Search productcomments 3. Click Configure :x: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version productcomments v6.0.2, v6.0.3 ### Your company or customer's name goes here (if applicable). _No response_

productcomments - Exception is thrown on develop when mode debug is enabled

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : productcomments - Exception is thrown on develop when mode debug is enabled 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 Only on branch develop of PS with mode debug enabled, I have an exception when I try to configure my productcomments module. If I disable debug mode, it is OK. <img width="1078" alt="Screenshot 2024-04-05 at 15 12 10" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d1186e92-ced1-4c6e-aad8-de906e27058f"> ### Expected behavior No exception should be displayed. The Configure page should be displayed correctly. ### Steps to reproduce 1. Go to BO > Advanced parameters > Enable Debug Mode 2. Go to Modules > Search productcomments 3. Click Configure :x: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version productcomments v6.0.2, v6.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 A customer adds products to their wishlist. In the Administration panel, in the customer details page, the wishlist counter remains at 0 and no further details are available. ### Expected behavior Expected wishlist details to be visibile in the administration panel ### Steps to reproduce 1. As a customer, add one or more products to your wishlist. 2. As an admin, open the administration page. 3. Go to Customers, Customers. 4. Open the details for the customer used in step 1. 5. See that the wishlist badge remains at 0 and no details are shown. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### 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). _No response_

Wishlist Module - Not possible to view wishlist details in customer details page.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Wishlist Module - Not possible to view wishlist details in customer details 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 A customer adds products to their wishlist. In the Administration panel, in the customer details page, the wishlist counter remains at 0 and no further details are available. ### Expected behavior Expected wishlist details to be visibile in the administration panel ### Steps to reproduce 1. As a customer, add one or more products to your wishlist. 2. As an admin, open the administration page. 3. Go to Customers, Customers. 4. Open the details for the customer used in step 1. 5. See that the wishlist badge remains at 0 and no details are shown. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### 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). _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 go one a customer view on backoffice ### Expected behavior not to have this error <img width="1729" alt="Capture d’écran 2024-04-05 à 11 59 00" src="https://github.com/PrestaShop/PrestaShop/assets/4788787/2e9d27d1-6ad2-4665-9b33-7023e6ea6fbb"> ### Steps to reproduce I'll join the PR for the explaination ### PrestaShop version(s) where the bug happened 8.1.5 ### 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). PrestaSafe

CartRuleCore::checkProductRestrictionsFromCart(): Argument #1 ($cart) must be of type CartCore

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CartRuleCore::checkProductRestrictionsFromCart(): Argument #1 ($cart) must be of type CartCore 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 go one a customer view on backoffice ### Expected behavior not to have this error <img width="1729" alt="Capture d’écran 2024-04-05 à 11 59 00" src="https://github.com/PrestaShop/PrestaShop/assets/4788787/2e9d27d1-6ad2-4665-9b33-7023e6ea6fbb"> ### Steps to reproduce I'll join the PR for the explaination ### PrestaShop version(s) where the bug happened 8.1.5 ### 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). PrestaSafe --- 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 would like to add a comment to a product, but if it has no criteria I cannot. I wish I could add an overall comment, not specifically on a criteria. <img width="1036" alt="Screenshot 2024-04-05 at 10 15 23" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/fc689359-a196-4313-8eff-ead335be8f12"> ### Expected behavior I should be able to add a comment even if there's no defined criteria. ### Steps to reproduce 1. Go to BO > Modules > Configure Product comments 2. In block Review Criteria > Click Edit > Set Active to NO > Save 3. Go to FO > Open a product page 4. Add a comment as a customer 5. See modal : YOUR REVIEW CANNOT BE SENT ### 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 productomments v6.0.2, v6.0.3 ### Your company or customer's name goes here (if applicable). _No response_

productcomments - Customers can't add a comment if there's no criteria

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : productcomments - Customers can't add a comment if there's no criteria 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 would like to add a comment to a product, but if it has no criteria I cannot. I wish I could add an overall comment, not specifically on a criteria. <img width="1036" alt="Screenshot 2024-04-05 at 10 15 23" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/fc689359-a196-4313-8eff-ead335be8f12"> ### Expected behavior I should be able to add a comment even if there's no defined criteria. ### Steps to reproduce 1. Go to BO > Modules > Configure Product comments 2. In block Review Criteria > Click Edit > Set Active to NO > Save 3. Go to FO > Open a product page 4. Add a comment as a customer 5. See modal : YOUR REVIEW CANNOT BE SENT ### 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 productomments v6.0.2, v6.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 As now, the SQL Request export use by default the `;` char. Regarding : https://github.com/PrestaShop/PrestaShop/blob/develop/src/Core/Export/FileWriter/ExportCsvFileWriter.php#L58 ### Expected behavior Add an option (with a legacy HelperOptions, 😎) to allow to use `;`or `,` separator. ### Steps to reproduce Export a SQL Request. ### PrestaShop version(s) where the bug happened 8.1.x ### 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). @Wepika

Allow to edit the CSV separator in SQL Request export

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Allow to edit the CSV separator in SQL Request export 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 now, the SQL Request export use by default the `;` char. Regarding : https://github.com/PrestaShop/PrestaShop/blob/develop/src/Core/Export/FileWriter/ExportCsvFileWriter.php#L58 ### Expected behavior Add an option (with a legacy HelperOptions, 😎) to allow to use `;`or `,` separator. ### Steps to reproduce Export a SQL Request. ### PrestaShop version(s) where the bug happened 8.1.x ### 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). @Wepika --- 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 have an issue with the 8.1.3 Prestashop Version. I can't find more the native module "Carrousel" as u can see in my captur screen below. ![Uploading Capture d'écran 2024-04-04 194226.png…]() ### Expected behavior _No response_ ### Steps to reproduce 1. Go to module section 2. Look for "carrousel" 3. If you fin module, all good, but if you dont find it we have the same problem. ### 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 _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Disparition module Carrousel

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Disparition module Carrousel 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 have an issue with the 8.1.3 Prestashop Version. I can't find more the native module "Carrousel" as u can see in my captur screen below. ![Uploading Capture d'écran 2024-04-04 194226.png…]() ### Expected behavior _No response_ ### Steps to reproduce 1. Go to module section 2. Look for "carrousel" 3. If you fin module, all good, but if you dont find it we have the same problem. ### 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 _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 search index regeneration is called by CRON, errors are logged in console, if the URL contains `&redirect=1`. ``` PHP Warning: Undefined array key "HTTP_REFERER" in /var/www/vhosts/xxxxx.cz/xxxxx.cz/controllers/admin/AdminSearchController.php on line 569' PHP Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/xxxxx.cz/classes/Tab.php on line 389 PHP message: PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/xxxxx.cz/classes/Dispatcher.php on line 973' ``` because $_SERVER['HTTP_REFERER'] may not be passed when calling the URL by cron. ### Expected behavior No error should be logged. ### Steps to reproduce See issue description. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1, Plesk management panel ### 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 when regenerating index by cron call

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Errors when regenerating index by cron call 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 search index regeneration is called by CRON, errors are logged in console, if the URL contains `&redirect=1`. ``` PHP Warning: Undefined array key "HTTP_REFERER" in /var/www/vhosts/xxxxx.cz/xxxxx.cz/controllers/admin/AdminSearchController.php on line 569' PHP Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/xxxxx.cz/classes/Tab.php on line 389 PHP message: PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/xxxxx.cz/classes/Dispatcher.php on line 973' ``` because $_SERVER['HTTP_REFERER'] may not be passed when calling the URL by cron. ### Expected behavior No error should be logged. ### Steps to reproduce See issue description. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1, Plesk management panel ### 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 [Capture vidéo du 04-04-2024 15:10:43.webm](https://github.com/PrestaShop/PrestaShop/assets/36233446/3a86b2c7-0f6b-41d0-8139-b380521b4147) The context is not correct in the symfony layout, it should be in all context, as indicated in the warning. This error is present on all pages which should switch from context to all shops ### Expected behavior The context should be in all shops on the symfony layout ### Steps to reproduce 1. Enable multistore && symfony layout 2. Create a new shop 3. Select a shop in a page allowing you to select a store, like the product page 4. Go to a page which normally switches to an all shop context 5. See shop context ### PrestaShop version(s) where the bug happened 9 ### PHP version(s) where the bug happened 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). -

Problem when switching context for multistore in symfony layout

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem when switching context for multistore in symfony layout 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 [Capture vidéo du 04-04-2024 15:10:43.webm](https://github.com/PrestaShop/PrestaShop/assets/36233446/3a86b2c7-0f6b-41d0-8139-b380521b4147) The context is not correct in the symfony layout, it should be in all context, as indicated in the warning. This error is present on all pages which should switch from context to all shops ### Expected behavior The context should be in all shops on the symfony layout ### Steps to reproduce 1. Enable multistore && symfony layout 2. Create a new shop 3. Select a shop in a page allowing you to select a store, like the product page 4. Go to a page which normally switches to an all shop context 5. See shop context ### PrestaShop version(s) where the bug happened 9 ### PHP version(s) where the bug happened 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). - --- 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 error always appears on most symfony pages in BO. rootPath is null for some reason. ``` [Mon Mar 25 15:49:42.960001 2024] [pid 29434:tid 139870026925824] [client 213.29.230.63:48990] AH01071: Got error ' PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/eshop.agrola.cz/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 134 PHP message: PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /var/www/vhosts/agrola.cz/eshop.agrola.cz/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135', referer: https://eshop.agrola.cz/xxxxxx/index.php/sell/orders/?_token=xxxxxxx [28-Mar-2024 13:41:14 Europe/Prague] PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /srv/www/deskyhevea.cz/public/www/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135 ``` ### Expected behavior No errors should be in console. ### Steps to reproduce 1. Install 8.1.5. 2. Enable debug mode. 3. Browse through few symfony pages. 4. See errors in var/cache/logs/php-xxx-xx-xx.log. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Twig errors in logs

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Twig errors in logs 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 error always appears on most symfony pages in BO. rootPath is null for some reason. ``` [Mon Mar 25 15:49:42.960001 2024] [pid 29434:tid 139870026925824] [client 213.29.230.63:48990] AH01071: Got error ' PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/vhosts/agrola.cz/eshop.agrola.cz/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 134 PHP message: PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /var/www/vhosts/agrola.cz/eshop.agrola.cz/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135', referer: https://eshop.agrola.cz/xxxxxx/index.php/sell/orders/?_token=xxxxxxx [28-Mar-2024 13:41:14 Europe/Prague] PHP Deprecated: strncmp(): Passing null to parameter #1 ($string1) of type string is deprecated in /srv/www/deskyhevea.cz/public/www/vendor/twig/twig/src/Loader/FilesystemLoader.php on line 135 ``` ### Expected behavior No errors should be in console. ### Steps to reproduce 1. Install 8.1.5. 2. Enable debug mode. 3. Browse through few symfony pages. 4. See errors in var/cache/logs/php-xxx-xx-xx.log. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 Good morning In my prestashop page I have 2 errors that I can't figure out where it comes from: 1. When I modify the manual stock of a product and save it, the configuration appears updated, as if everything went well, but then I refresh the page and that information is deleted and there is no record in the logs. So the customer continues to see my product at 0. 2. When we make partial refunds or full refunds of orders we have observed that depending on the date it is recorded and goes to my ERP or not automatically I mean. The date is the only common link that we have been able to observe between the products that we wanted to refund. The version of prestashop is 1.7.7.2 I look forward to hearing from you, thanks Best regards ### Expected behavior _No response_ ### Steps to reproduce Steps for each error: 1. enter some product > combinations modify the quantity manually > save > save > "configuration updated" appears > we give to product preview > no change in quantities is seen the product appears out of stock. 2. enter the order to be refunded > partial refund > select the quantity and the amount to be refunded > deselect Re-enter products in stock > partial refund As mentioned above, we have noticed that the ERP only generates the credit note after this action for the orders in due month, for example today 04/04 the orders of March no problem are recorded in logs but if the order is from 29/02 there is no record. Thanks ### PrestaShop version(s) where the bug happened 1.7.7.2 ### PHP version(s) where the bug happened 7.3.32 ### 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_

MANUAL STOCK UPDATE ERROR / REFUNDS

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : MANUAL STOCK UPDATE ERROR / REFUNDS 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 In my prestashop page I have 2 errors that I can't figure out where it comes from: 1. When I modify the manual stock of a product and save it, the configuration appears updated, as if everything went well, but then I refresh the page and that information is deleted and there is no record in the logs. So the customer continues to see my product at 0. 2. When we make partial refunds or full refunds of orders we have observed that depending on the date it is recorded and goes to my ERP or not automatically I mean. The date is the only common link that we have been able to observe between the products that we wanted to refund. The version of prestashop is 1.7.7.2 I look forward to hearing from you, thanks Best regards ### Expected behavior _No response_ ### Steps to reproduce Steps for each error: 1. enter some product > combinations modify the quantity manually > save > save > "configuration updated" appears > we give to product preview > no change in quantities is seen the product appears out of stock. 2. enter the order to be refunded > partial refund > select the quantity and the amount to be refunded > deselect Re-enter products in stock > partial refund As mentioned above, we have noticed that the ERP only generates the credit note after this action for the orders in due month, for example today 04/04 the orders of March no problem are recorded in logs but if the order is from 29/02 there is no record. Thanks ### PrestaShop version(s) where the bug happened 1.7.7.2 ### PHP version(s) where the bug happened 7.3.32 ### 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 have received several complaints from customers who report that they receive a new order email but when they log into prestashop they discover that the order has not been carried out as there has been an error in the payment, i.e. the order has been generated but has not been completed due to an error in the payment. Normally customers only check their email to see if they receive new orders and more than once they have prepared and sent the order and then realised that there was an error in the payment. In the mail alerts module you will find the code that sends these new order mails. I do not know if prestashop has taken into account that another type of email is sent saying that someone has placed an order but there has been a failure in the payment, or directly if the order status is error in the payment that this email is not sent. ### Expected behavior _No response_ ### Steps to reproduce To reproduce it you only have to generate an error in the payment in a test environment with card payment and you will receive a new order email. ### PrestaShop version(s) where the bug happened 8.1 ### 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_

A new order email is sent when the order status is payment error

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : A new order email is sent when the order status is payment 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 I have received several complaints from customers who report that they receive a new order email but when they log into prestashop they discover that the order has not been carried out as there has been an error in the payment, i.e. the order has been generated but has not been completed due to an error in the payment. Normally customers only check their email to see if they receive new orders and more than once they have prepared and sent the order and then realised that there was an error in the payment. In the mail alerts module you will find the code that sends these new order mails. I do not know if prestashop has taken into account that another type of email is sent saying that someone has placed an order but there has been a failure in the payment, or directly if the order status is error in the payment that this email is not sent. ### Expected behavior _No response_ ### Steps to reproduce To reproduce it you only have to generate an error in the payment in a test environment with card payment and you will receive a new order email. ### PrestaShop version(s) where the bug happened 8.1 ### 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 had Prestashop 1.7.8.7 and I decided to update it to Prestashop 8.1.5 the update went without errors except that it said that some modules could not be updated... The problem is that when trying to update them, being modules created by Prestashop itself, they cannot be updated, an error appears that says: "Could not perform action update for module undefined" This happens with both native Prestashop modules and its own modules, the only solution is to uninstall and reinstall them, but it is a strange problem that I would like to solve.   ### Expected behavior I was hoping it could be updated from the panel without errors. ### Steps to reproduce 1. Upgrade from Prestashop 1.7.8.7 to 8.1.5 with the official Prestashop upgrade module 2. in the update module remove image and database backups 3) try to update Prestashop modules. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 7.3.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_

Error updating modules after updating to ps8.1.5

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error updating modules after updating to ps8.1.5 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 had Prestashop 1.7.8.7 and I decided to update it to Prestashop 8.1.5 the update went without errors except that it said that some modules could not be updated... The problem is that when trying to update them, being modules created by Prestashop itself, they cannot be updated, an error appears that says: "Could not perform action update for module undefined" This happens with both native Prestashop modules and its own modules, the only solution is to uninstall and reinstall them, but it is a strange problem that I would like to solve.   ### Expected behavior I was hoping it could be updated from the panel without errors. ### Steps to reproduce 1. Upgrade from Prestashop 1.7.8.7 to 8.1.5 with the official Prestashop upgrade module 2. in the update module remove image and database backups 3) try to update Prestashop modules. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 7.3.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 you go to the product / details page and enter a gtin number that is more than 14 length the error message that is shown is duplicated. It seems that this is an [old bug returning ](https://github.com/PrestaShop/PrestaShop/pull/29584). <img width="428" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/4093454/fab10e01-d046-4692-97d0-4ab7b7c6cc98"> ### Expected behavior Have the error message not be duplicated. ### Steps to reproduce Go to the prodoct page in the BO. Go to the details tab. Enter a 15 length gtin See the error message. ### PrestaShop version(s) where the bug happened 9.0.0 ### 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). PrestaShop SA

The error message is duplicated when entering a gtin that is too long.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : The error message is duplicated when entering a gtin that is too long. 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 go to the product / details page and enter a gtin number that is more than 14 length the error message that is shown is duplicated. It seems that this is an [old bug returning ](https://github.com/PrestaShop/PrestaShop/pull/29584). <img width="428" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/4093454/fab10e01-d046-4692-97d0-4ab7b7c6cc98"> ### Expected behavior Have the error message not be duplicated. ### Steps to reproduce Go to the prodoct page in the BO. Go to the details tab. Enter a 15 length gtin See the error message. ### PrestaShop version(s) where the bug happened 9.0.0 ### 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). PrestaShop SA --- 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 Put ``` {l s='(%unit_price%)' d='Shop.Theme.Catalog' sprintf=['%unit_price%' => $product.unit_price_full]} ``` anywhere into `/classic/templates/catalog/_partials/miniatures/product.tpl` and see that it has wrong values. ### Expected behavior Unit price must display correctly everywhere, with taxes, with specific prices. ### Steps to reproduce See issue description. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Unit price not working correctly outside of product page and cart

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unit price not working correctly outside of product page and cart 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 Put ``` {l s='(%unit_price%)' d='Shop.Theme.Catalog' sprintf=['%unit_price%' => $product.unit_price_full]} ``` anywhere into `/classic/templates/catalog/_partials/miniatures/product.tpl` and see that it has wrong values. ### Expected behavior Unit price must display correctly everywhere, with taxes, with specific prices. ### Steps to reproduce See issue description. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 have install "prestashop marketing with google" module to have a product flow. I configure it. Then, it tell me a date for the next sync. It doesn't create product in my google account. But i have a fatal error in logs : `02-Apr-2024 07:00:01 Europe/Paris] PHP Fatal error: Uncaught TypeError: ProductControllerCore::addProductCustomizationData(): Argument #1 ($product_full) must be of type array, bool given, called in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php on line 1208 and defined in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php:1359 Stack trace: #0 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php(1208): ProductControllerCore->addProductCustomizationData() #1 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/classes/Provider/PageViewEventDataProvider.php(49): ProductControllerCore->getTemplateVarProduct() #2 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/classes/Handler/RemarketingHookHandler.php(103): PrestaShop\Module\PsxMarketingWithGoogle\Provider\PageViewEventDataProvider->getEventData() #3 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/psxmarketingwithgoogle.php(249): PrestaShop\Module\PsxMarketingWithGoogle\Handler\RemarketingHookHandler->handleHook() #4 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(993): PsxMarketingWithGoogle->hookDisplayTop() #5 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(418): HookCore::coreCallHook() #6 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(928): HookCore::callHookOn() #7 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/config/smarty.config.inc.php(205): HookCore::exec() #8 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #9 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/5e/94/80/5e94807def2ac301dbd2ae9ebf26a25a143f6cc5_2.file.header.tpl.php(131): SmartyLazyRegister->__call() #10 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_120400009066092416d74404_32527093->callBlock() #11 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #12 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #13 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/5e/94/80/5e94807def2ac301dbd2ae9ebf26a25a143f6cc5_2.file.header.tpl.php(40): Smarty_Internal_Runtime_Inheritance->instanceBlock() #14 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416d800f6_17315481() #15 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #16 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #17 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #18 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/3e/f6/25/3ef6258f81a1fd82a23dec124856f25191be9bdf_2.file.layout-both-columns.tpl.php(307): Smarty_Internal_Template->_subTemplateRender() #19 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_165324000266092416c0c705_76419572->callBlock() #20 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #21 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #22 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/3e/f6/25/3ef6258f81a1fd82a23dec124856f25191be9bdf_2.file.layout-both-columns.tpl.php(129): Smarty_Internal_Runtime_Inheritance->instanceBlock() #23 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416c27e69_97769044() #24 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #25 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #26 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #27 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #28 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/05/e9/33/05e933f512ffe90f825805d88162708fd50e5d35_2.file.layout-full-width.tpl.php(43): Smarty_Internal_Runtime_Inheritance->endChild() #29 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416bb7ed8_50989580() #30 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #31 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #32 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #33 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #34 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/7b/4c/ce/7b4cce38228e4a7c82c12cb5534fae848510971a_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #35 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416b99897_96439688() #36 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #37 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #38 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #39 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #40 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/b3/77/e3/b377e3c0bf7a92d4c80f7e60e4b968b24db51d05_2.file.404.tpl.php(39): Smarty_Internal_Runtime_Inheritance->endChild() #41 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_660940c91410a4_99527948() #42 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #43 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #44 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #45 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #46 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/FrontController.php(715): Smarty_Internal_TemplateBase->fetch() #47 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/FrontController.php(697): FrontControllerCore->smartyOutputContent() #48 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/Controller.php(339): FrontControllerCore->display() #49 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Dispatcher.php(510): ControllerCore->run() #50 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/index.php(28): DispatcherCore->dispatch() #51 {main} thrown in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php on line 1359` ### Expected behavior Create google products and sync theme with my google account, with no fatal error php. ### Steps to reproduce Install module, set up, wait sync. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.2.13 ### If your bug is related to a module, specify its name and its version Prestashop marketing with google v1.69.0 ### Your company or customer's name goes here (if applicable). besancon archerie

Prestashop marketing with google error when sync

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop marketing with google error when sync 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 have install "prestashop marketing with google" module to have a product flow. I configure it. Then, it tell me a date for the next sync. It doesn't create product in my google account. But i have a fatal error in logs : `02-Apr-2024 07:00:01 Europe/Paris] PHP Fatal error: Uncaught TypeError: ProductControllerCore::addProductCustomizationData(): Argument #1 ($product_full) must be of type array, bool given, called in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php on line 1208 and defined in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php:1359 Stack trace: #0 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php(1208): ProductControllerCore->addProductCustomizationData() #1 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/classes/Provider/PageViewEventDataProvider.php(49): ProductControllerCore->getTemplateVarProduct() #2 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/classes/Handler/RemarketingHookHandler.php(103): PrestaShop\Module\PsxMarketingWithGoogle\Provider\PageViewEventDataProvider->getEventData() #3 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/modules/psxmarketingwithgoogle/psxmarketingwithgoogle.php(249): PrestaShop\Module\PsxMarketingWithGoogle\Handler\RemarketingHookHandler->handleHook() #4 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(993): PsxMarketingWithGoogle->hookDisplayTop() #5 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(418): HookCore::coreCallHook() #6 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Hook.php(928): HookCore::callHookOn() #7 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/config/smarty.config.inc.php(205): HookCore::exec() #8 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #9 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/5e/94/80/5e94807def2ac301dbd2ae9ebf26a25a143f6cc5_2.file.header.tpl.php(131): SmartyLazyRegister->__call() #10 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_120400009066092416d74404_32527093->callBlock() #11 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #12 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #13 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/5e/94/80/5e94807def2ac301dbd2ae9ebf26a25a143f6cc5_2.file.header.tpl.php(40): Smarty_Internal_Runtime_Inheritance->instanceBlock() #14 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416d800f6_17315481() #15 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #16 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #17 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #18 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/3e/f6/25/3ef6258f81a1fd82a23dec124856f25191be9bdf_2.file.layout-both-columns.tpl.php(307): Smarty_Internal_Template->_subTemplateRender() #19 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_165324000266092416c0c705_76419572->callBlock() #20 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #21 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #22 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/3e/f6/25/3ef6258f81a1fd82a23dec124856f25191be9bdf_2.file.layout-both-columns.tpl.php(129): Smarty_Internal_Runtime_Inheritance->instanceBlock() #23 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416c27e69_97769044() #24 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #25 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #26 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #27 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #28 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/05/e9/33/05e933f512ffe90f825805d88162708fd50e5d35_2.file.layout-full-width.tpl.php(43): Smarty_Internal_Runtime_Inheritance->endChild() #29 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416bb7ed8_50989580() #30 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #31 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #32 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #33 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #34 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/7b/4c/ce/7b4cce38228e4a7c82c12cb5534fae848510971a_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #35 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_66092416b99897_96439688() #36 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #37 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #38 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #39 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(115): Smarty_Internal_Template->_subTemplateRender() #40 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/var/cache/prod/smarty/compile/AngarThemelayouts_layout_full_width_tpl/b3/77/e3/b377e3c0bf7a92d4c80f7e60e4b968b24db51d05_2.file.404.tpl.php(39): Smarty_Internal_Runtime_Inheritance->endChild() #41 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_660940c91410a4_99527948() #42 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #43 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #44 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #45 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #46 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/FrontController.php(715): Smarty_Internal_TemplateBase->fetch() #47 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/FrontController.php(697): FrontControllerCore->smartyOutputContent() #48 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/controller/Controller.php(339): FrontControllerCore->display() #49 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/classes/Dispatcher.php(510): ControllerCore->run() #50 /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/index.php(28): DispatcherCore->dispatch() #51 {main} thrown in /srv/data/web/vhosts/besancon-archerie.fr/htdocs/boutique/controllers/front/ProductController.php on line 1359` ### Expected behavior Create google products and sync theme with my google account, with no fatal error php. ### Steps to reproduce Install module, set up, wait sync. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.2.13 ### If your bug is related to a module, specify its name and its version Prestashop marketing with google v1.69.0 ### Your company or customer's name goes here (if applicable). besancon archerie --- 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 in the meta preview of SEO section appears the html code, if the meta description is not set  bye ### Expected behavior _No response_ ### Steps to reproduce 1. go to the product from the admin side 2. set some text in the short description 3. go in the SEO section 4. do not set any text in the meta description 5. look the meta preview ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Html code in the meta description preview admin site in prestashop 8.1.5

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Html code in the meta description preview admin site in prestashop 8.1.5 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 in the meta preview of SEO section appears the html code, if the meta description is not set  bye ### Expected behavior _No response_ ### Steps to reproduce 1. go to the product from the admin side 2. set some text in the short description 3. go in the SEO section 4. do not set any text in the meta description 5. look the meta preview ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 everyone, It is impossible to display the order slip PDF document when the order contain a one product's reduction and the order slip is about shipping cost.  Log just contain the following content : ` [2024-04-02 15:17:21] request.CRITICAL: Uncaught PHP Exception TypeError: "PrestaShop\PrestaShop\Core\Util\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in /var/www/html/prestashop8-test/classes/pdf/HTMLTemplateOrderSlip.php on line 167" at /var/www/html/prestashop8-test/src/Core/Util/Sorter.php line 43 {"exception":"[object] (TypeError(code: 0): PrestaShop\\PrestaShop\\Core\\Util\\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in /var/www/html/prestashop8-test/classes/pdf/HTMLTemplateOrderSlip.php on line 167 at /var/www/html/prestashop8-test/src/Core/Util/Sorter.php:43)"} [] ` Please note : my using Prestashop is full-vanilla. Thanks. Mel ### Expected behavior _No response_ ### Steps to reproduce 1. Make a reduction for a specific product 2. Make an order by the Backoffice admin interface : 1. Order the product 2. Order another product 3. Apply the reduction for the first product 4. Set the command as "payment accepted" 5. Make sure the command has no free shipping 3. Set the command to "delivered" 4. Make an order slip for the order : 1. Click "partial refund" 2. just put the shipping cost in the order slip 3. Apply 5. Try display de order slip -> 500 internal error ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.27 ### 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 > Orders - Exception displayed when I create a credit slip with only Shipping cost

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Orders - Exception displayed when I create a credit slip with only Shipping cost 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 everyone, It is impossible to display the order slip PDF document when the order contain a one product's reduction and the order slip is about shipping cost.  Log just contain the following content : ` [2024-04-02 15:17:21] request.CRITICAL: Uncaught PHP Exception TypeError: "PrestaShop\PrestaShop\Core\Util\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in /var/www/html/prestashop8-test/classes/pdf/HTMLTemplateOrderSlip.php on line 167" at /var/www/html/prestashop8-test/src/Core/Util/Sorter.php line 43 {"exception":"[object] (TypeError(code: 0): PrestaShop\\PrestaShop\\Core\\Util\\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in /var/www/html/prestashop8-test/classes/pdf/HTMLTemplateOrderSlip.php on line 167 at /var/www/html/prestashop8-test/src/Core/Util/Sorter.php:43)"} [] ` Please note : my using Prestashop is full-vanilla. Thanks. Mel ### Expected behavior _No response_ ### Steps to reproduce 1. Make a reduction for a specific product 2. Make an order by the Backoffice admin interface : 1. Order the product 2. Order another product 3. Apply the reduction for the first product 4. Set the command as "payment accepted" 5. Make sure the command has no free shipping 3. Set the command to "delivered" 4. Make an order slip for the order : 1. Click "partial refund" 2. just put the shipping cost in the order slip 3. Apply 5. Try display de order slip -> 500 internal error ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.27 ### 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 ---

This issue tracks the status of the PrestaShop 9.0.0 Alpha release ### Information Q | A -----------------------|-------- **Type** | Major version / Alpha step **Milestone** | [9.0.0](https://github.com/PrestaShop/PrestaShop/milestone/85) **Publish date** | [06-06-2024](https://build.prestashop-project.org/news/2024/prestashop-9-alpha1-available/) _What is an Alpha release ? An alpha release is an under-development version of software that is ready for initial testing by a small group of users._ ### Release steps - [x] Specification - [x] Feature development - [x] Green nightly (no further manual tests) (https://nightly.prestashop-project.org/) **1. Preleminary tasks** - [x] Update the version number in the Core. - [x] Release classic Theme (to check with team cc @jolelievre ) - [x] Perform manual verifications (more infos here https://www.prestashop-project.org/maintainers-guide/processes/release/prestashop/preliminary-tasks/) **2. Create the build** - [x] Update the Changelog and Contributors list. - [x] Push your work into a build branch. - [x] Build and store the zip archive. **3. Release publicly** - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub (specific tag for V9 alpha) - [x] Communicate **4. Final steps** - [x] Check that the release note has been published on the [Build Blog](https://build.prestashop-project.org/)

Release 9.0.0 Alpha 🧪

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Release 9.0.0 Alpha 🧪 Issue date: --- start body --- This issue tracks the status of the PrestaShop 9.0.0 Alpha release ### Information Q | A -----------------------|-------- **Type** | Major version / Alpha step **Milestone** | [9.0.0](https://github.com/PrestaShop/PrestaShop/milestone/85) **Publish date** | [06-06-2024](https://build.prestashop-project.org/news/2024/prestashop-9-alpha1-available/) _What is an Alpha release ? An alpha release is an under-development version of software that is ready for initial testing by a small group of users._ ### Release steps - [x] Specification - [x] Feature development - [x] Green nightly (no further manual tests) (https://nightly.prestashop-project.org/) **1. Preleminary tasks** - [x] Update the version number in the Core. - [x] Release classic Theme (to check with team cc @jolelievre ) - [x] Perform manual verifications (more infos here https://www.prestashop-project.org/maintainers-guide/processes/release/prestashop/preliminary-tasks/) **2. Create the build** - [x] Update the Changelog and Contributors list. - [x] Push your work into a build branch. - [x] Build and store the zip archive. **3. Release publicly** - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub (specific tag for V9 alpha) - [x] Communicate **4. Final steps** - [x] Check that the release note has been published on the [Build Blog](https://build.prestashop-project.org/) --- 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 enabled the new & Experimental Feature for Attribute group, I still have the old page displayed. https://github.com/PrestaShop/PrestaShop/assets/16019289/31635d69-b807-45c5-afc4-661d5fdcb74e ### Expected behavior When I enabled the New & Experimental Feature for Attribute group, I should have the migrated page displayed. <img width="1428" alt="Screenshot 2024-04-02 at 15 42 14" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/191a02e1-fd30-4aec-9c13-11f35d5b2e80"> ### Steps to reproduce 1. Install branch develop 2. Go to BO > New & Experimental Features 3. Enable Attribute group > Save 4. Go to Catalog > Attributes & Features 5. See the old page is still displayed ### PrestaShop version(s) where the bug happened 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_

develop - New & Experimental Features > Attributes group enabled, but migrated page is not displayed

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : develop - New & Experimental Features > Attributes group enabled, but migrated page is not displayed 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 enabled the new & Experimental Feature for Attribute group, I still have the old page displayed. https://github.com/PrestaShop/PrestaShop/assets/16019289/31635d69-b807-45c5-afc4-661d5fdcb74e ### Expected behavior When I enabled the New & Experimental Feature for Attribute group, I should have the migrated page displayed. <img width="1428" alt="Screenshot 2024-04-02 at 15 42 14" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/191a02e1-fd30-4aec-9c13-11f35d5b2e80"> ### Steps to reproduce 1. Install branch develop 2. Go to BO > New & Experimental Features 3. Enable Attribute group > Save 4. Go to Catalog > Attributes & Features 5. See the old page is still displayed ### PrestaShop version(s) where the bug happened 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 For the input "Number of days for which the product is considered 'new'", we add some inputs and they are not considered as invalid. Input : * :heavy_check_mark: : `-1` * :heavy_check_mark: : `1000000000` * :red_circle: : : `1 500` * :red_circle: : : `0` * :red_circle: : : `@` Based on this scenario : * https://forge.prestashop.com/browse/TEST-4135 * https://build.prestashop-project.org/test-scenarios/scenarios/modules/ps-newproducts/configuration/new-products-block-module-configure-settings-of-number-of-days-for-which-the-product-is-considered-new-field.html ### Expected behavior _No response_ ### Steps to reproduce 1. Go to "Modules > Module Manager" page 2. Search the module "ps_newproducts" 3. Go to the configuration page 4. Enter in the field an invalid value 5. Save it 6. Go on the FrontOffice 7. The block "New products" should not be visible ### 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 ps_newproducts 1.0.4 ### Your company or customer's name goes here (if applicable). @PrestaShopCorp

`ps_newproducts` : Invalid input display the block or can't be saved

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : `ps_newproducts` : Invalid input display the block or can't be 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 For the input "Number of days for which the product is considered 'new'", we add some inputs and they are not considered as invalid. Input : * :heavy_check_mark: : `-1` * :heavy_check_mark: : `1000000000` * :red_circle: : : `1 500` * :red_circle: : : `0` * :red_circle: : : `@` Based on this scenario : * https://forge.prestashop.com/browse/TEST-4135 * https://build.prestashop-project.org/test-scenarios/scenarios/modules/ps-newproducts/configuration/new-products-block-module-configure-settings-of-number-of-days-for-which-the-product-is-considered-new-field.html ### Expected behavior _No response_ ### Steps to reproduce 1. Go to "Modules > Module Manager" page 2. Search the module "ps_newproducts" 3. Go to the configuration page 4. Enter in the field an invalid value 5. Save it 6. Go on the FrontOffice 7. The block "New products" should not be visible ### 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 ps_newproducts 1.0.4 ### Your company or customer's name goes here (if applicable). @PrestaShopCorp --- 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 Fresh install and made test order and if you mark order shipped and debug mode is on I will get this error:  Server information: Linux #1 SMP Wed Nov 15 10:55:18 -00 2023 x86_64 Server software version: Apache / ZoneOS PHP version: 8.1.27 Memory limit: 1024M Max execution time: 30 Upload Max File size: 2047M Anyone can help me how to fix it? ### Expected behavior _No response_ ### Steps to reproduce 1. Create a new order in frontend. 2. Finish ordering, payment etc. 3. emails are send, order is being made in backoffice. 4. click on order to view; 5. Mark shipped - the error occurs. ### PrestaShop version(s) where the bug happened 1.8.5 ### PHP version(s) where the bug happened 8.1.27 ### 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 v.8.1.5

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop v.8.1.5 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 Fresh install and made test order and if you mark order shipped and debug mode is on I will get this error:  Server information: Linux #1 SMP Wed Nov 15 10:55:18 -00 2023 x86_64 Server software version: Apache / ZoneOS PHP version: 8.1.27 Memory limit: 1024M Max execution time: 30 Upload Max File size: 2047M Anyone can help me how to fix it? ### Expected behavior _No response_ ### Steps to reproduce 1. Create a new order in frontend. 2. Finish ordering, payment etc. 3. emails are send, order is being made in backoffice. 4. click on order to view; 5. Mark shipped - the error occurs. ### PrestaShop version(s) where the bug happened 1.8.5 ### PHP version(s) where the bug happened 8.1.27 ### 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 Problematic SQL starts here: https://github.com/PrestaShop/dashactivity/blob/21e90c2d98dc797e2ce8927e6f6e510ac60a6159/dashactivity.php#L246 if (Module::isInstalled('productcomments')) { $product_reviews += Db::getInstance((bool) _PS_USE_SQL_SLAVE_)->getValue(' SELECT COUNT(*) FROM `' . _DB_PREFIX_ . 'product_comment` pc LEFT JOIN `' . _DB_PREFIX_ . 'product` p ON (pc.id_product = p.id_product) ' . Shop::addSqlAssociation('product', 'p') . ' WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "' . pSQL($params['date_from']) . '" AND "' . pSQL($params['date_to']) . '" ' . Shop::addSqlRestriction(Shop::SHARE_ORDER) ); } In our case it produces SQL: SELECT COUNT(*) FROM `ps_product_comment` pc LEFT JOIN `ps8468_product` p ON (pc.id_product = p.id_product) INNER JOIN ps8468_product_shop product_shop ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1) WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "2024-03-01 00:00:00" AND "2024-03-26 23:59:59" AND id_shop IN (1) We have Percona Server 5.7.36-39-log - Percona Server (GPL), Release '39', Revision '305619d' The server says: "#1052 - Column 'id_shop' in where clause is ambiguous" ### Expected behavior No error from Mysql server. Also SQL could be fixed like this SELECT COUNT(*) FROM `ps8468_product_comment` pc LEFT JOIN `ps8468_product` p ON (pc.id_product = p.id_product) INNER JOIN ps8468_product_shop product_shop ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1) WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "2024-03-01 00:00:00" AND "2024-03-26 23:59:59" -- Next line is a fix AND product_shop.id_shop IN (1) ; ### Steps to reproduce Open dashboard, and dashactivtiy returns json with empty string, when productcomments module is active. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.27 ### If your bug is related to a module, specify its name and its version dashactivity 2.1 ### Your company or customer's name goes here (if applicable). _No response_

Dashactivity module causes mysql to return "#1052 - Column 'id_shop' in where clause is ambiguous"

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Dashactivity module causes mysql to return "#1052 - Column 'id_shop' in where clause is ambiguous" 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 Problematic SQL starts here: https://github.com/PrestaShop/dashactivity/blob/21e90c2d98dc797e2ce8927e6f6e510ac60a6159/dashactivity.php#L246 if (Module::isInstalled('productcomments')) { $product_reviews += Db::getInstance((bool) _PS_USE_SQL_SLAVE_)->getValue(' SELECT COUNT(*) FROM `' . _DB_PREFIX_ . 'product_comment` pc LEFT JOIN `' . _DB_PREFIX_ . 'product` p ON (pc.id_product = p.id_product) ' . Shop::addSqlAssociation('product', 'p') . ' WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "' . pSQL($params['date_from']) . '" AND "' . pSQL($params['date_to']) . '" ' . Shop::addSqlRestriction(Shop::SHARE_ORDER) ); } In our case it produces SQL: SELECT COUNT(*) FROM `ps_product_comment` pc LEFT JOIN `ps8468_product` p ON (pc.id_product = p.id_product) INNER JOIN ps8468_product_shop product_shop ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1) WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "2024-03-01 00:00:00" AND "2024-03-26 23:59:59" AND id_shop IN (1) We have Percona Server 5.7.36-39-log - Percona Server (GPL), Release '39', Revision '305619d' The server says: "#1052 - Column 'id_shop' in where clause is ambiguous" ### Expected behavior No error from Mysql server. Also SQL could be fixed like this SELECT COUNT(*) FROM `ps8468_product_comment` pc LEFT JOIN `ps8468_product` p ON (pc.id_product = p.id_product) INNER JOIN ps8468_product_shop product_shop ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1) WHERE pc.deleted = 0 AND pc.`date_add` BETWEEN "2024-03-01 00:00:00" AND "2024-03-26 23:59:59" -- Next line is a fix AND product_shop.id_shop IN (1) ; ### Steps to reproduce Open dashboard, and dashactivtiy returns json with empty string, when productcomments module is active. ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1.27 ### If your bug is related to a module, specify its name and its version dashactivity 2.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 Lors de la migration de prestashop de la version 1.7.11 vers 8.1.5, via le module autoupgrade, une erreur sql a été levée: SQL 8.0.0 1146 in ALTER TABLE XXXX_webservice_permission MODIFY COLUMN method ENUM( 'GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'HEAD' ) NOT NULL: Table 'xxxx_test.xxxx_webservice_permission' doesn't exist Les xxx sont pour masquer le vrai nom de la base. Ensuite dans paramètres avancées, webservice: An exception occurred while executing 'SELECT wa.`id_webservice_account`, wa.`key`, wa.`description`, wa.`active` FROM xxx_webservice_account wa INNER JOIN xxx_webservice_account_shop was ON was.`id_webservice_account` = wa.`id_webservice_account` WHERE was.`id_shop` IN (?) GROUP BY wa.`id_webservice_account` ORDER BY wa.id_webservice_account asc LIMIT 50' with params [1]: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'xxx.yyy_webservice_account' doesn't exist [Doctrine\DBAL\Exception\TableNotFoundException 0] ### Expected behavior L'application est fonctionnel sauf la partie webservice qui renvoie vers une erreur 500. ### Steps to reproduce Installation via le module autoupgrade 1-click upgrade de prestashop. Une fois installé, dans paramètres avancées, webservice ### PrestaShop version(s) where the bug happened 1.7.8.11 ### 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). bijouxindiens.net

Migration de prestashop 1.7.8.11 vers 8.1.5 via autoupgrade module. Erreur sql webservice

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Migration de prestashop 1.7.8.11 vers 8.1.5 via autoupgrade module. Erreur sql 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 Lors de la migration de prestashop de la version 1.7.11 vers 8.1.5, via le module autoupgrade, une erreur sql a été levée: SQL 8.0.0 1146 in ALTER TABLE XXXX_webservice_permission MODIFY COLUMN method ENUM( 'GET', 'POST', 'PUT', 'PATCH', 'DELETE', 'HEAD' ) NOT NULL: Table 'xxxx_test.xxxx_webservice_permission' doesn't exist Les xxx sont pour masquer le vrai nom de la base. Ensuite dans paramètres avancées, webservice: An exception occurred while executing 'SELECT wa.`id_webservice_account`, wa.`key`, wa.`description`, wa.`active` FROM xxx_webservice_account wa INNER JOIN xxx_webservice_account_shop was ON was.`id_webservice_account` = wa.`id_webservice_account` WHERE was.`id_shop` IN (?) GROUP BY wa.`id_webservice_account` ORDER BY wa.id_webservice_account asc LIMIT 50' with params [1]: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'xxx.yyy_webservice_account' doesn't exist [Doctrine\DBAL\Exception\TableNotFoundException 0] ### Expected behavior L'application est fonctionnel sauf la partie webservice qui renvoie vers une erreur 500. ### Steps to reproduce Installation via le module autoupgrade 1-click upgrade de prestashop. Une fois installé, dans paramètres avancées, webservice ### PrestaShop version(s) where the bug happened 1.7.8.11 ### 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). bijouxindiens.net --- 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 was upgrading with the module and it shows [INTERNAL] /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Iterator/ExcludeDirectoryFilterIterator.php line 37 - Error: Call to undefined function Symfony\Component\Finder\Iterator\str_contains() #0 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Finder.php(691): Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator->__construct() #1 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Finder.php(573): Symfony\Component\Finder\Finder->searchInDirectory() #2 [internal function]: Symfony\Component\Finder\Finder->getIterator() #3 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Filesystem/Filesystem.php(165): iterator_to_array() #4 /var/www/html/prestashop/classes/Context.php(436): Symfony\Component\Filesystem\Filesystem->remove() #5 /var/www/html/prestashop/classes/Context.php(399): ContextCore->getTranslatorFromLocale() #6 /var/www/html/prestashop/classes/Translate.php(282): ContextCore->getTranslator() #7 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/Translator.php(60): TranslateCore::getModuleTranslation() #8 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(58): PrestaShop\Module\AutoUpgrade\UpgradeTools\Translator->trans() #9 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->writeNewSettings() #10 /var/www/html/prestashop/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(41): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #11 /var/www/html/prestashop/admin191dsf4mp/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #12 {main} it got crashed and white was shown I tried to rollback to the previous version and it also gives other error, now frontend shows erorr 500 and backend white page. i deleted cookies and it is the same.. Error logs from log.txt /admin/autoupgrade/tmp Please check attchment ### Expected behavior The store version 8.1.5 ### Steps to reproduce The upgrade process from module. [log.txt](https://github.com/PrestaShop/PrestaShop/files/14820190/log.txt) ### PrestaShop version(s) where the bug happened 1.7.8.11 to 8.1.5 ### PHP version(s) where the bug happened 7.4.3 ### If your bug is related to a module, specify its name and its version 1-click upgrade last version ### Your company or customer's name goes here (if applicable). _No response_

Upgrade PrestaShop 1.7.8.11 to 8.1.5 failed/White page backend and error 500 frontend

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade PrestaShop 1.7.8.11 to 8.1.5 failed/White page backend and error 500 frontend 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 was upgrading with the module and it shows [INTERNAL] /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Iterator/ExcludeDirectoryFilterIterator.php line 37 - Error: Call to undefined function Symfony\Component\Finder\Iterator\str_contains() #0 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Finder.php(691): Symfony\Component\Finder\Iterator\ExcludeDirectoryFilterIterator->__construct() #1 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Finder/Finder.php(573): Symfony\Component\Finder\Finder->searchInDirectory() #2 [internal function]: Symfony\Component\Finder\Finder->getIterator() #3 /var/www/html/prestashop/vendor/symfony/symfony/src/Symfony/Component/Filesystem/Filesystem.php(165): iterator_to_array() #4 /var/www/html/prestashop/classes/Context.php(436): Symfony\Component\Filesystem\Filesystem->remove() #5 /var/www/html/prestashop/classes/Context.php(399): ContextCore->getTranslatorFromLocale() #6 /var/www/html/prestashop/classes/Translate.php(282): ContextCore->getTranslator() #7 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/Translator.php(60): TranslateCore::getModuleTranslation() #8 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(58): PrestaShop\Module\AutoUpgrade\UpgradeTools\Translator->trans() #9 /var/www/html/prestashop/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(43): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->writeNewSettings() #10 /var/www/html/prestashop/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(41): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #11 /var/www/html/prestashop/admin191dsf4mp/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #12 {main} it got crashed and white was shown I tried to rollback to the previous version and it also gives other error, now frontend shows erorr 500 and backend white page. i deleted cookies and it is the same.. Error logs from log.txt /admin/autoupgrade/tmp Please check attchment ### Expected behavior The store version 8.1.5 ### Steps to reproduce The upgrade process from module. [log.txt](https://github.com/PrestaShop/PrestaShop/files/14820190/log.txt) ### PrestaShop version(s) where the bug happened 1.7.8.11 to 8.1.5 ### PHP version(s) where the bug happened 7.4.3 ### If your bug is related to a module, specify its name and its version 1-click upgrade last 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 This issue is about a disabled third-party modules using new translation system via .xlf files, own BO CSS and JS. Issue 1. When the module is not installed or is disabled, the translations by using .XLF files doesn't load. So module name and description on the Module Manager page is still in the English language no matter which BO language you are using. IMPORTANT: If module translations are loaded from DB PREFIX_translations table, everything working well. Issue 2. When you want to setup disabled module and go on module setting page, the translations are ignored too. Issue 3. If the disabled module using CSS and JS for back-office via displayBackOfficeHeader hook, this hook is disabled for the module. So setup of the module in disabled mode could be complicated depending features provided by JS. ### Expected behavior _No response_ ### Steps to reproduce 1. install into your PrestaShop Slovak language 2. setup your BO account to display BO in this new language. 3. install third-party module that is translated by a .xlf files. I can provide testing module for this testing purpose. 4. verify on Modules Manager page if enabled module load the translations. 5. disable the module. 6. clear PrestaShop cache. 7. go to Module Manager page and check the module - module name and description should be in English language. 8. go to module setting page - whole module BO will be in English and no translated. 9. when the module using additional back-office CSS and JS files by using displayBackOfficeHeader hook - these files can't load, the links into the files not render in the source code. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Disabled third-party modules can't load translation from .xlf files, and own BO CSS and JS

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Disabled third-party modules can't load translation from .xlf files, and own BO CSS and JS 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 issue is about a disabled third-party modules using new translation system via .xlf files, own BO CSS and JS. Issue 1. When the module is not installed or is disabled, the translations by using .XLF files doesn't load. So module name and description on the Module Manager page is still in the English language no matter which BO language you are using. IMPORTANT: If module translations are loaded from DB PREFIX_translations table, everything working well. Issue 2. When you want to setup disabled module and go on module setting page, the translations are ignored too. Issue 3. If the disabled module using CSS and JS for back-office via displayBackOfficeHeader hook, this hook is disabled for the module. So setup of the module in disabled mode could be complicated depending features provided by JS. ### Expected behavior _No response_ ### Steps to reproduce 1. install into your PrestaShop Slovak language 2. setup your BO account to display BO in this new language. 3. install third-party module that is translated by a .xlf files. I can provide testing module for this testing purpose. 4. verify on Modules Manager page if enabled module load the translations. 5. disable the module. 6. clear PrestaShop cache. 7. go to Module Manager page and check the module - module name and description should be in English language. 8. go to module setting page - whole module BO will be in English and no translated. 9. when the module using additional back-office CSS and JS files by using displayBackOfficeHeader hook - these files can't load, the links into the files not render in the source code. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 I have migrate shop from 1.6 to 8.1.5 and everything went fine, but on one order I get error and offered that debug mode enable. If you hit back you can work normally on Backoffice. But if you hit debug mode you get error.  after that i try to manually delete cache directory no luck. If i look at defines file there is no debug mode enable. ### Expected behavior back to normal work in BO ### Steps to reproduce Open order on new migrated shop from old shop On some order there is problem with decimal values and getting error If you hit enable debug mode you can't access to BO any more ang get this error If you don't hit debug mode everything work fine. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version no ### Your company or customer's name goes here (if applicable). _No response_

Failed to start the session: already started by PHP

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Failed to start the session: already started by 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 I have migrate shop from 1.6 to 8.1.5 and everything went fine, but on one order I get error and offered that debug mode enable. If you hit back you can work normally on Backoffice. But if you hit debug mode you get error.  after that i try to manually delete cache directory no luck. If i look at defines file there is no debug mode enable. ### Expected behavior back to normal work in BO ### Steps to reproduce Open order on new migrated shop from old shop On some order there is problem with decimal values and getting error If you hit enable debug mode you can't access to BO any more ang get this error If you don't hit debug mode everything work fine. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version no ### 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 Following the update of my prestashop with the new version 1.7.8 which did not work I had to reinstall my previous version Current PrestaShop version: 1.7.2.4 Current PHP version: 7.1.33 And since: In the back office, it is impossible to update the products, it is impossible to save. On the page of my site it is impossible for customers to access their account. And I no longer had the module page but my host (Planethooster) managed to make this page reappear by modifying the parameters.php file For the login file it is completely empty. In debug mode when I try to connect as a customer to my buyer account this is the page I get: see attachment          ### Expected behavior _No response_ ### Steps to reproduce Following the update of my prestashop with the new version 1.7.8 which did not work I had to reinstall my previous version Current PrestaShop version: 1.7.2.4 Current PHP version: 7.1.33 And since: In the back office, it is impossible to update the products, it is impossible to save. On the page of my site it is impossible for customers to access their account. And I no longer had the module page but my host (Planethooster) managed to make this page reappear by modifying the parameters.php file For the login file it is completely empty. ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.1.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). www.fightandshop.com

Prestashop 1.7.8 update problem

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 1.7.8 update problem 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 Following the update of my prestashop with the new version 1.7.8 which did not work I had to reinstall my previous version Current PrestaShop version: 1.7.2.4 Current PHP version: 7.1.33 And since: In the back office, it is impossible to update the products, it is impossible to save. On the page of my site it is impossible for customers to access their account. And I no longer had the module page but my host (Planethooster) managed to make this page reappear by modifying the parameters.php file For the login file it is completely empty. In debug mode when I try to connect as a customer to my buyer account this is the page I get: see attachment          ### Expected behavior _No response_ ### Steps to reproduce Following the update of my prestashop with the new version 1.7.8 which did not work I had to reinstall my previous version Current PrestaShop version: 1.7.2.4 Current PHP version: 7.1.33 And since: In the back office, it is impossible to update the products, it is impossible to save. On the page of my site it is impossible for customers to access their account. And I no longer had the module page but my host (Planethooster) managed to make this page reappear by modifying the parameters.php file For the login file it is completely empty. ### PrestaShop version(s) where the bug happened 1.7.8 ### PHP version(s) where the bug happened 7.1.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). www.fightandshop.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 This bug has been reported before #17759 and is not fixed in 8.1.5. The .htaccess file [in this directory 'mails/.htaccess'](https://github.com/PrestaShop/PrestaShop/blob/develop/mails/.htaccess) restricts access so email templates cannot be previewed ### Expected behavior Ability to preview email templates for order status changes ### Steps to reproduce Sign in to bo. Go to "Shop Parameters" -> "Order Settings" -> "Statuses" tab. Edit a status with "Send email to customer" set and try to preview that status' email template. Result 403 Forbidden Work around: remove the .htaccess file from https://github.com/PrestaShop/PrestaShop/blob/develop/mails/.htaccess Suggested permanent fix would be to move that directory to the administration directory and remove the .htaccess file ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 7.4.33

Email template access is forbidden in bo

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Email template access is forbidden in 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 This bug has been reported before #17759 and is not fixed in 8.1.5. The .htaccess file [in this directory 'mails/.htaccess'](https://github.com/PrestaShop/PrestaShop/blob/develop/mails/.htaccess) restricts access so email templates cannot be previewed ### Expected behavior Ability to preview email templates for order status changes ### Steps to reproduce Sign in to bo. Go to "Shop Parameters" -> "Order Settings" -> "Statuses" tab. Edit a status with "Send email to customer" set and try to preview that status' email template. Result 403 Forbidden Work around: remove the .htaccess file from https://github.com/PrestaShop/PrestaShop/blob/develop/mails/.htaccess Suggested permanent fix would be to move that directory to the administration directory and remove the .htaccess file ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 7.4.33 --- 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 the product admin page not all results are displayed when searching for related products. In many cases it only shows 1 result even though I see a whole list in the actual fetch response (ajax). Note that I am using 1.7.8.11 for this site but there are no notable changes for this part (besides codestyle/indentation): https://github.com/PrestaShop/PrestaShop/commits/develop/admin-dev/themes/new-theme/js/product-page/product-search-autocomplete.js ### Expected behavior Since the fetch results are correct (a full list of all possible matches) I would thing that all results should be rendered in the list. ### Steps to reproduce 1: Create many products staring with the same name (at least 30). Example: Presta Product 01, Presta Product 02, etc. 2: Create a new product and search for related products by typing "Presta". 3: Even though the fetch response will include all products, the actual HTML only renders 1 or in some cases a few. ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened N.A. ### 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). _No response_

Not all related products are showing in product admin when searching

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Not all related products are showing in product admin when searching 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 the product admin page not all results are displayed when searching for related products. In many cases it only shows 1 result even though I see a whole list in the actual fetch response (ajax). Note that I am using 1.7.8.11 for this site but there are no notable changes for this part (besides codestyle/indentation): https://github.com/PrestaShop/PrestaShop/commits/develop/admin-dev/themes/new-theme/js/product-page/product-search-autocomplete.js ### Expected behavior Since the fetch results are correct (a full list of all possible matches) I would thing that all results should be rendered in the list. ### Steps to reproduce 1: Create many products staring with the same name (at least 30). Example: Presta Product 01, Presta Product 02, etc. 2: Create a new product and search for related products by typing "Presta". 3: Even though the fetch response will include all products, the actual HTML only renders 1 or in some cases a few. ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened N.A. ### 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). _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 noticed that searching in Warehouse no longer works well. If I search for two separate words, it doesn't give me any results, I have to search in a single word. For example, if I have to search for this Retro Men's jacket which, as you can see from the screenshots, is present, I have to search for "retro men" all at once, and I can no longer build the search step by step, "retro" and then "man", as it could instead on 1.7.   ### Expected behavior _No response_ ### Steps to reproduce 1. Go to the Back Office 2. Click on Catalog --> Warehouse 3. Try search a product and then add another word in the search to be more specific ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1.27 ### 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 warehouse search not working

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop 8 warehouse search 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 We noticed that searching in Warehouse no longer works well. If I search for two separate words, it doesn't give me any results, I have to search in a single word. For example, if I have to search for this Retro Men's jacket which, as you can see from the screenshots, is present, I have to search for "retro men" all at once, and I can no longer build the search step by step, "retro" and then "man", as it could instead on 1.7.   ### Expected behavior _No response_ ### Steps to reproduce 1. Go to the Back Office 2. Click on Catalog --> Warehouse 3. Try search a product and then add another word in the search to be more specific ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1.27 ### 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 Deploy using docker-compose.yml with the following command docker run -ti --name some-prestashop_en --network prestashop-net -e DB_SERVER=some-mysql -e PS_DEV_MODE=false -e PS_INSTALL_AUTO=0 -e PS_ENABLE_SSL=0 -e PS_HOST=www.xxx.com -p 8080:80 -p 443:443 -d prestashop/prestashop:latest After the template is installed, the https in the foreground and background cannot be accessed. Perhaps there is a document for configuring https that can be provided. My domain name is ssl accelerated by cloudflare, I don't know if it can be used. We also tried not to enable ssl authentication. We checked all enable ssl on the page and found that it could not be started. ### Expected behavior _No response_ ### Steps to reproduce 1.Run the docker command docker run -ti --name some-prestashop_en --network prestashop-net -e DB_SERVER=some-mysql -e PS_DEV_MODE=false -e PS_INSTALL_AUTO=0 -e PS_ENABLE_SSL=0 -e PS_HOST=www.infinauto.com -p 8080:80 -p 443:443 -d prestashop/prestashop:latest 2. Access the web page by IP address :8080, enter the enterprise information, and select Enable ssl 3.After initialization, the domain name 443 cannot be accessed. ### PrestaShop version(s) where the bug happened 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). _No response_

PrestaShop8.* https

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop8.* https 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 Deploy using docker-compose.yml with the following command docker run -ti --name some-prestashop_en --network prestashop-net -e DB_SERVER=some-mysql -e PS_DEV_MODE=false -e PS_INSTALL_AUTO=0 -e PS_ENABLE_SSL=0 -e PS_HOST=www.xxx.com -p 8080:80 -p 443:443 -d prestashop/prestashop:latest After the template is installed, the https in the foreground and background cannot be accessed. Perhaps there is a document for configuring https that can be provided. My domain name is ssl accelerated by cloudflare, I don't know if it can be used. We also tried not to enable ssl authentication. We checked all enable ssl on the page and found that it could not be started. ### Expected behavior _No response_ ### Steps to reproduce 1.Run the docker command docker run -ti --name some-prestashop_en --network prestashop-net -e DB_SERVER=some-mysql -e PS_DEV_MODE=false -e PS_INSTALL_AUTO=0 -e PS_ENABLE_SSL=0 -e PS_HOST=www.infinauto.com -p 8080:80 -p 443:443 -d prestashop/prestashop:latest 2. Access the web page by IP address :8080, enter the enterprise information, and select Enable ssl 3.After initialization, the domain name 443 cannot be accessed. ### PrestaShop version(s) where the bug happened 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). _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 you want to upgrade from 1.7.8.11 to 9.0.0, you'll have an issue first of all with ps_checkout as you can see :  If you delete ps_checkout, the problem'll be about ps_account and if you delete it also, you'll have many error due to the different compatibility Error message : > "[INTERNAL] /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php line 88 - Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "mbo.addons.user" has a dependency on a non-existent service "session". Did you mean one of these: "argument_resolver.session", "session.factory", "session.storage.factory.native", "session.handler.native", "session_listener", "prestashop.core.grid.query_builder.security.session.employee", "prestashop.core.grid.query_builder.security.session.customer", "prestashop.core.grid.data_factory.security.session.employee", "prestashop.core.grid.data_factory.security.session.customer", "prestashop.core.grid.definition.factory.security.session.employee", "prestashop.core.grid.definition.factory.security.session.customer", "prestashop.core.grid.factory.security.session.employee", "prestashop.core.grid.factory.security.session.customer", "prestashop.adapter.security.command_handler.delete_customer_session_handler", "prestashop.adapter.security.command_handler.clear_customer_session_handler", "prestashop.adapter.security.command_handler.delete_employee_session_handler", "prestashop.adapter.security.command_handler.clear_employee_session_handler", "prestashop.adapter.security.command_handler.bulk_delete_employees_sessions_handler", "prestashop.adapter.security.command_handler.bulk_delete_customers_sessions_handler", "prestashop.adapter.security.repository.customer_session_repository", "prestashop.adapter.security.repository.employee_session_repository"? #0 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(90): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #1 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #2 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(99): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #3 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #4 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(90): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #5 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #6 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(48): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #7 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(42): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->process() #8 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/Compiler.php(80): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->process() #9 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/ContainerBuilder.php(767): Symfony\Component\DependencyInjection\Compiler\Compiler->compile() #10 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(506): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #11 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(763): Symfony\Component\HttpKernel\Kernel->initializeContainer() #12 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(126): Symfony\Component\HttpKernel\Kernel->preBoot() #13 /var/www/html/pr_autoup/app/AppKernel.php(102): Symfony\Component\HttpKernel\Kernel->boot() #14 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(87): AppKernel->boot() #15 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(45): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initKernel() #16 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(88): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #17 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #18 /var/www/html/pr_autoup/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(41): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #19 /var/www/html/pr_autoup/admin-dev/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #20 {main}" ### Expected behavior I wish I could update from 1.7.8.11 to 9.0.0 ### Steps to reproduce 1. Install Prestashop 1.7.8.11 2. Install module Autoupgrade from the develop branch 3. Clic on configure 4. Select major Release to upgrade to 8.1.5 5. Change your PHP to 8.1 6. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: ps_checkout is the problem 7. Uninstall ps_checkout from your shop and your files 8. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: ps_account is the problem 9. Uninstall ps_account from your shop and your files 10. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: You got all the error ### PrestaShop version(s) where the bug happened 1.7.8.11 to 8.1.5 to 9.0.0 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### Your company or customer's name goes here (if applicable). PS

Autoupgrade - Exception in autoupgrade for 1.7.8.11 to 9.0.0 due to ps_checkout and ps_account

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade - Exception in autoupgrade for 1.7.8.11 to 9.0.0 due to ps_checkout and ps_account 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 upgrade from 1.7.8.11 to 9.0.0, you'll have an issue first of all with ps_checkout as you can see :  If you delete ps_checkout, the problem'll be about ps_account and if you delete it also, you'll have many error due to the different compatibility Error message : > "[INTERNAL] /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php line 88 - Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException: The service "mbo.addons.user" has a dependency on a non-existent service "session". Did you mean one of these: "argument_resolver.session", "session.factory", "session.storage.factory.native", "session.handler.native", "session_listener", "prestashop.core.grid.query_builder.security.session.employee", "prestashop.core.grid.query_builder.security.session.customer", "prestashop.core.grid.data_factory.security.session.employee", "prestashop.core.grid.data_factory.security.session.customer", "prestashop.core.grid.definition.factory.security.session.employee", "prestashop.core.grid.definition.factory.security.session.customer", "prestashop.core.grid.factory.security.session.employee", "prestashop.core.grid.factory.security.session.customer", "prestashop.adapter.security.command_handler.delete_customer_session_handler", "prestashop.adapter.security.command_handler.clear_customer_session_handler", "prestashop.adapter.security.command_handler.delete_employee_session_handler", "prestashop.adapter.security.command_handler.clear_employee_session_handler", "prestashop.adapter.security.command_handler.bulk_delete_employees_sessions_handler", "prestashop.adapter.security.command_handler.bulk_delete_customers_sessions_handler", "prestashop.adapter.security.repository.customer_session_repository", "prestashop.adapter.security.repository.employee_session_repository"? #0 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(90): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #1 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #2 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(99): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #3 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #4 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(90): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #5 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(51): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue() #6 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/AbstractRecursivePass.php(48): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->processValue() #7 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php(42): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->process() #8 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/Compiler/Compiler.php(80): Symfony\Component\DependencyInjection\Compiler\CheckExceptionOnInvalidReferenceBehaviorPass->process() #9 /var/www/html/pr_autoup/vendor/symfony/dependency-injection/ContainerBuilder.php(767): Symfony\Component\DependencyInjection\Compiler\Compiler->compile() #10 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(506): Symfony\Component\DependencyInjection\ContainerBuilder->compile() #11 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(763): Symfony\Component\HttpKernel\Kernel->initializeContainer() #12 /var/www/html/pr_autoup/vendor/symfony/http-kernel/Kernel.php(126): Symfony\Component\HttpKernel\Kernel->preBoot() #13 /var/www/html/pr_autoup/app/AppKernel.php(102): Symfony\Component\HttpKernel\Kernel->boot() #14 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/SymfonyAdapter.php(87): AppKernel->boot() #15 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader80.php(45): PrestaShop\Module\AutoUpgrade\UpgradeTools\SymfonyAdapter->initKernel() #16 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader.php(88): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader80->initConstants() #17 /var/www/html/pr_autoup/modules/autoupgrade/classes/UpgradeTools/CoreUpgrader/CoreUpgrader81.php(46): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader->doUpgrade() #18 /var/www/html/pr_autoup/modules/autoupgrade/classes/TaskRunner/Upgrade/UpgradeDb.php(41): PrestaShop\Module\AutoUpgrade\UpgradeTools\CoreUpgrader\CoreUpgrader81->doUpgrade() #19 /var/www/html/pr_autoup/admin-dev/autoupgrade/ajax-upgradetab.php(53): PrestaShop\Module\AutoUpgrade\TaskRunner\Upgrade\UpgradeDb->run() #20 {main}" ### Expected behavior I wish I could update from 1.7.8.11 to 9.0.0 ### Steps to reproduce 1. Install Prestashop 1.7.8.11 2. Install module Autoupgrade from the develop branch 3. Clic on configure 4. Select major Release to upgrade to 8.1.5 5. Change your PHP to 8.1 6. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: ps_checkout is the problem 7. Uninstall ps_checkout from your shop and your files 8. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: ps_account is the problem 9. Uninstall ps_account from your shop and your files 10. Do an upgrade from a folder to have the version 9.0.0 :negative_squared_cross_mark: You got all the error ### PrestaShop version(s) where the bug happened 1.7.8.11 to 8.1.5 to 9.0.0 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### 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 Javascript async calls still executing in admin area https://www.w3.org/TR/permissions-policy/ For example carrier_wizard.js, Giving this error  This is solved by changing async: false to async:true ### Expected behavior _No response_ ### Steps to reproduce Version 123.0.6312.86 (Official Build) (arm64) Version 123.0.6312.86 (Official Build) (arm64) Create new carrier Select next ### PrestaShop version(s) where the bug happened 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). _No response_

[Violation] Permissions policy violation: Synchronous requests are disabled by permissions policy.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [Violation] Permissions policy violation: Synchronous requests are disabled by permissions policy. 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 Javascript async calls still executing in admin area https://www.w3.org/TR/permissions-policy/ For example carrier_wizard.js, Giving this error  This is solved by changing async: false to async:true ### Expected behavior _No response_ ### Steps to reproduce Version 123.0.6312.86 (Official Build) (arm64) Version 123.0.6312.86 (Official Build) (arm64) Create new carrier Select next ### PrestaShop version(s) where the bug happened 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). _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 total_tax_excl is wrong as it is doubled out. In case PS_ATCP_SHIPWRAP is not activated, $sum_of_tax_bases stays a 0, and so $delta_base is equal to $this->total_shipping_tax_excl which is then spread, and conducts to doubling the total_tax_excl in the result array. Making the getShippingTaxesBreakdown completely useless. ### Expected behavior Output the correct amounts ### Steps to reproduce Currently the getShippingTaxesBreakdown function result is not rendered anywhere, it is used in HTMLTemplateInvoice but not used in the render. Never the less the function exists in the codebase and can be used by developers for modules or other use cases, so it should return the good amout ### PrestaShop version(s) where the bug happened ALREADY IN 1.7.4.x AND STILL IN 8.1.x ### 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). Web Premiere

Shipping tax breakdown is wrong when not having PS_ATCP_SHIPWRAP activated

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Shipping tax breakdown is wrong when not having PS_ATCP_SHIPWRAP activated 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 total_tax_excl is wrong as it is doubled out. In case PS_ATCP_SHIPWRAP is not activated, $sum_of_tax_bases stays a 0, and so $delta_base is equal to $this->total_shipping_tax_excl which is then spread, and conducts to doubling the total_tax_excl in the result array. Making the getShippingTaxesBreakdown completely useless. ### Expected behavior Output the correct amounts ### Steps to reproduce Currently the getShippingTaxesBreakdown function result is not rendered anywhere, it is used in HTMLTemplateInvoice but not used in the render. Never the less the function exists in the codebase and can be used by developers for modules or other use cases, so it should return the good amout ### PrestaShop version(s) where the bug happened ALREADY IN 1.7.4.x AND STILL IN 8.1.x ### 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). Web Premiere --- 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 Don't show Category thumbnail images in parent category if not add Category cover image. Version 8.1.4. Dont show thumbnail images in parent category if not add cover image. only with cover image show thumbnail. ### Expected behavior _No response_ ### Steps to reproduce Don't show Category thumbnail images in parent category if not add Category cover image. Version 8.1.4. Dont show thumbnail images in parent category if not add cover image. only with cover image show thumbnail. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened PHP version: 8.2.17 ### 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_

Dont show Category thumbnail images in parent category if not add Category cover image

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Dont show Category thumbnail images in parent category if not add Category cover image 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 Don't show Category thumbnail images in parent category if not add Category cover image. Version 8.1.4. Dont show thumbnail images in parent category if not add cover image. only with cover image show thumbnail. ### Expected behavior _No response_ ### Steps to reproduce Don't show Category thumbnail images in parent category if not add Category cover image. Version 8.1.4. Dont show thumbnail images in parent category if not add cover image. only with cover image show thumbnail. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened PHP version: 8.2.17 ### 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 ## visual issue on mobile ### Add new file popup Problems with "Add new file" popup. https://capture.dropbox.com/ZLJ0vVA1ETZz2eB3 ### Expected behavior _No response_ ### Steps to reproduce Go to Product page - Tab details - btn add new file ### PrestaShop version(s) where the bug happened 8.1.0 ### 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_

[Style][Page-product-Tab-details] - modal add new file (visual issue on mobile)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [Style][Page-product-Tab-details] - modal add new file (visual issue on mobile) 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 ## visual issue on mobile ### Add new file popup Problems with "Add new file" popup. https://capture.dropbox.com/ZLJ0vVA1ETZz2eB3 ### Expected behavior _No response_ ### Steps to reproduce Go to Product page - Tab details - btn add new file ### PrestaShop version(s) where the bug happened 8.1.0 ### 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 The PrestaShop 8.15 installation assistant failed to install the theme after entering MySQL information.PrestaShop 8.15 version installation assistant, after entering the MySQL information, can not install the theme, retry many times can not, MySQL version is 5.7.44, looking forward to your reply, attached figure above.  ### Expected behavior _No response_ ### Steps to reproduce 1. Place the installation package in /var/www/html 2. Start nginx, automatically decompress, and configure the store information 3. Configure the database connection information and the connection is successful 4. Failed to install the store theme with error server500 ### PrestaShop version(s) where the bug happened 8.1.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). _No response_

The PrestaShop 8.15 installation assistant failed to install the theme after entering MySQL information.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : The PrestaShop 8.15 installation assistant failed to install the theme after entering MySQL information. 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 PrestaShop 8.15 installation assistant failed to install the theme after entering MySQL information.PrestaShop 8.15 version installation assistant, after entering the MySQL information, can not install the theme, retry many times can not, MySQL version is 5.7.44, looking forward to your reply, attached figure above.  ### Expected behavior _No response_ ### Steps to reproduce 1. Place the installation package in /var/www/html 2. Start nginx, automatically decompress, and configure the store information 3. Configure the database connection information and the connection is successful 4. Failed to install the store theme with error server500 ### PrestaShop version(s) where the bug happened 8.1.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). _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   ### Expected behavior _No response_ ### Steps to reproduce 1. create cms page with meta title and meta description. 2. go to the new cms page. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Problem with meta information on CMS pages. No meta title, meta description.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem with meta information on CMS pages. No meta title, meta 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   ### Expected behavior _No response_ ### Steps to reproduce 1. create cms page with meta title and meta description. 2. go to the new cms page. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 For some time it has been impossible to update stores (v1.7 to v8 and v8.1.x to v8.1.x ) with the "1-Click Upgrade" module v5.0.1. The error messages displayed during the attempts are : - [Ajax / Server Error for action backupFiles] textStatus: "error " errorThrown:" " jqXHR: " undefined" - **OR** [Ajax / Server Error for action unzip] textStatus: "error " errorThrown:" " jqXHR: " undefined" - **OR** [Ajax / Server Error for action _**XXX**_] textStatus: "error " errorThrown:" " jqXHR: " undefined" There are no error logs in "var/logs/*" and "admin/autoupgrade/tmp/log.txt" and no server-side error logs. The requests stop suddenly (all requests have the http code 200). Last logs of the last attempt in /admin/autoupgrade/tmp/log.txt : [2024-03-27 15:10:37] modules/colissimo/lib/xml/track.xml added to archive. 37074 files left. [2024-03-27 15:10:37] modules/colissimo/logo.gif added to archive. 37073 files left. [2024-03-27 15:10:37] modules/colissimo/logo.png added to archive. 37072 files left. [2024-03-27 15:10:37] modules/colissimo/logs/xxxx.log added to archive. 37071 files left. According to the hosting service there are no server-side configuration errors. max_execution_time : 165s ### Expected behavior Upgrade to latest minor and major Prestashop versions. ### Steps to reproduce - All modules are updated - Maintenance mode - Disable and clear cache - Disable all overrides - Disable non-native modules - Disable "CCC" in the "performance" tab / Apache optimization - Disable child theme - Restart SQL server on the host side + maintenance mode on all other stores - Without autoupgrade backup images / files / databases - Minor and major channel ### PrestaShop version(s) where the bug happened 17.8.11 AND 8.1.2 ### PHP version(s) where the bug happened 7.4 AND 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### Your company or customer's name goes here (if applicable). _No response_

Unable to update Prestashop to minor and major versions - "error " errorThrown:" " jqXHR: " undefined"

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unable to update Prestashop to minor and major versions - "error " errorThrown:" " jqXHR: " undefined" 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 For some time it has been impossible to update stores (v1.7 to v8 and v8.1.x to v8.1.x ) with the "1-Click Upgrade" module v5.0.1. The error messages displayed during the attempts are : - [Ajax / Server Error for action backupFiles] textStatus: "error " errorThrown:" " jqXHR: " undefined" - **OR** [Ajax / Server Error for action unzip] textStatus: "error " errorThrown:" " jqXHR: " undefined" - **OR** [Ajax / Server Error for action _**XXX**_] textStatus: "error " errorThrown:" " jqXHR: " undefined" There are no error logs in "var/logs/*" and "admin/autoupgrade/tmp/log.txt" and no server-side error logs. The requests stop suddenly (all requests have the http code 200). Last logs of the last attempt in /admin/autoupgrade/tmp/log.txt : [2024-03-27 15:10:37] modules/colissimo/lib/xml/track.xml added to archive. 37074 files left. [2024-03-27 15:10:37] modules/colissimo/logo.gif added to archive. 37073 files left. [2024-03-27 15:10:37] modules/colissimo/logo.png added to archive. 37072 files left. [2024-03-27 15:10:37] modules/colissimo/logs/xxxx.log added to archive. 37071 files left. According to the hosting service there are no server-side configuration errors. max_execution_time : 165s ### Expected behavior Upgrade to latest minor and major Prestashop versions. ### Steps to reproduce - All modules are updated - Maintenance mode - Disable and clear cache - Disable all overrides - Disable non-native modules - Disable "CCC" in the "performance" tab / Apache optimization - Disable child theme - Restart SQL server on the host side + maintenance mode on all other stores - Without autoupgrade backup images / files / databases - Minor and major channel ### PrestaShop version(s) where the bug happened 17.8.11 AND 8.1.2 ### PHP version(s) where the bug happened 7.4 AND 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.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 If you have a product with many combinations and activate the feature to hide out of stock options, the product page becomes much slower. This is because of tryToGetAvailableIdProductAttribute in productController. ### Expected behavior I expect the page to be a bit slower, but not as much as today. The difference can be several seconds. ### Steps to reproduce 1. Create a page with about 600+ combinations 2. Go to product page and measure load time. 3. Change the setting to display out of stock options in BO 4. Reload product page and measure load time. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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

FO: product page slow with many combinations and hiding out of stock options

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO: product page slow with many combinations and hiding out of stock options 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 If you have a product with many combinations and activate the feature to hide out of stock options, the product page becomes much slower. This is because of tryToGetAvailableIdProductAttribute in productController. ### Expected behavior I expect the page to be a bit slower, but not as much as today. The difference can be several seconds. ### Steps to reproduce 1. Create a page with about 600+ combinations 2. Go to product page and measure load time. 3. Change the setting to display out of stock options in BO 4. Reload product page and measure load time. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 Two languages are available (English and French) and only one is enabled (English). Because i need the FO is in English.  The BO is in French language. I added a product and it's missing of the listing of products. To display the product, i need to switch the language of the BO to English. ### Expected behavior Even the FO is in English, i need to have the BO in French with all products. ### Steps to reproduce 1. Go to International / Localization / Languages 2. Enable English / Disable French 3. Go to your profile / Switch to French language and Save.  4. Go to Catalogue / Produits 5. Add a product by clicking on the "+ Nouveau produit" button. 6. Give a name and a reference to the product and click on the "Enregistrer" button. 7. Return to Catalogue / Produits ==> the new product is missing 8. Go to your profile / Switch to English language and Save.  9. Go to Catalog / Products ==> the product is visible now ### PrestaShop version(s) where the bug happened 1.7.8.8 ### PHP version(s) where the bug happened 7.4.13 ### 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_

Products missing in BO due to languages

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Products missing in BO due to languages 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 languages are available (English and French) and only one is enabled (English). Because i need the FO is in English.  The BO is in French language. I added a product and it's missing of the listing of products. To display the product, i need to switch the language of the BO to English. ### Expected behavior Even the FO is in English, i need to have the BO in French with all products. ### Steps to reproduce 1. Go to International / Localization / Languages 2. Enable English / Disable French 3. Go to your profile / Switch to French language and Save.  4. Go to Catalogue / Produits 5. Add a product by clicking on the "+ Nouveau produit" button. 6. Give a name and a reference to the product and click on the "Enregistrer" button. 7. Return to Catalogue / Produits ==> the new product is missing 8. Go to your profile / Switch to English language and Save.  9. Go to Catalog / Products ==> the product is visible now ### PrestaShop version(s) where the bug happened 1.7.8.8 ### PHP version(s) where the bug happened 7.4.13 ### 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 ---

### Issue The endpoint logic of API has been deported to a module and core foundation of the API can therefor be added to the software definitely. The API can still be disabled if needed ### Specs Remove the feature auth server in the feature and experimental page. Keep the feature flag about the multistore but rename it "Admin API - Multistore" Rename "Auth Server" page to "Admin API" above bellow Webservice Page, Add new card on the bellow of the API client list. The new card is named "Configuration" with the configuration icon and be composed with a toggle to enable and disable the API. The toggle is named "Admin API", the input can be "Enabled" or "Disabled" The help text is: "Before enabling the Admin API, you must be sure to: 1. Check that the ps_apiressource is installed and enabled. 2. Check that URL rewriting is available on this server. 3. Check that the six methods GET, POST, PUT, PATCH, DELETE and HEAD are supported by this server. The multistore is still on beta, to test it out go the "New & Experimental features" page* Upgrade module need to be adapted accordingly. The default value for new shops will be enabled ### Acceptance test When the Admin API is enabled Then API can interrogate Else the API won't be access and throw a denied access 404

Remove feature flag for the API

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Remove feature flag for the API Issue date: --- start body --- ### Issue The endpoint logic of API has been deported to a module and core foundation of the API can therefor be added to the software definitely. The API can still be disabled if needed ### Specs Remove the feature auth server in the feature and experimental page. Keep the feature flag about the multistore but rename it "Admin API - Multistore" Rename "Auth Server" page to "Admin API" above bellow Webservice Page, Add new card on the bellow of the API client list. The new card is named "Configuration" with the configuration icon and be composed with a toggle to enable and disable the API. The toggle is named "Admin API", the input can be "Enabled" or "Disabled" The help text is: "Before enabling the Admin API, you must be sure to: 1. Check that the ps_apiressource is installed and enabled. 2. Check that URL rewriting is available on this server. 3. Check that the six methods GET, POST, PUT, PATCH, DELETE and HEAD are supported by this server. The multistore is still on beta, to test it out go the "New & Experimental features" page* Upgrade module need to be adapted accordingly. The default value for new shops will be enabled ### Acceptance test When the Admin API is enabled Then API can interrogate Else the API won't be access and throw a denied access 404 --- 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 Steps to reproduce the behavior: Run Prestashop 8.1.3; Delete a product in a order; Try to see the order detail. We'll get an error: "PrestaShop\PrestaShop\Core\Domain\Order\QueryResult\OrderProductForViewing::__construct(): Argument #19 ($location) must be of type string, null given, called in public_html/src/Adapter/Order/QueryHandler/GetOrderProductsForViewingHandler.php on line 279" Specs When a product is deleted, we cannot open the order detail anymore. I got this error in old orders, but since I had a new one closed, I’ve deleted one of the products that didn’t have stock anymore, to see if it happens with this new order. Everything was ok until I delete the product (I’ve seen the order detail several times). Now I cannot open the detail. I've investigated what I could and the error is about "location" field - I've thought since the table entry of the product was removed from ps_product - now, in the select this field is getting the "null" value, that leads to this error. I cannot investigate anymore since I don't know where to find the select and I'm not familiarized with PHP. Additional information PrestaShop version: 8.1.3 PHP version: 8.1.27 ### Expected behavior We should be able to open the order details even when it has deleted products. ### Steps to reproduce Run Prestashop 8.1.3; Delete a product in a order; Try to see the order detail. We'll get an error: "PrestaShop\PrestaShop\Core\Domain\Order\QueryResult\OrderProductForViewing::__construct(): Argument #19 ($location) must be of type string, null given, called in public_html/src/Adapter/Order/QueryHandler/GetOrderProductsForViewingHandler.php on line 279"  ### PrestaShop version(s) where the bug happened 1.8.3 ### PHP version(s) where the bug happened 8.1.27 ### 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_

Cannot open order on backoffice with deleted products

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Cannot open order on backoffice with deleted 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 Steps to reproduce the behavior: Run Prestashop 8.1.3; Delete a product in a order; Try to see the order detail. We'll get an error: "PrestaShop\PrestaShop\Core\Domain\Order\QueryResult\OrderProductForViewing::__construct(): Argument #19 ($location) must be of type string, null given, called in public_html/src/Adapter/Order/QueryHandler/GetOrderProductsForViewingHandler.php on line 279" Specs When a product is deleted, we cannot open the order detail anymore. I got this error in old orders, but since I had a new one closed, I’ve deleted one of the products that didn’t have stock anymore, to see if it happens with this new order. Everything was ok until I delete the product (I’ve seen the order detail several times). Now I cannot open the detail. I've investigated what I could and the error is about "location" field - I've thought since the table entry of the product was removed from ps_product - now, in the select this field is getting the "null" value, that leads to this error. I cannot investigate anymore since I don't know where to find the select and I'm not familiarized with PHP. Additional information PrestaShop version: 8.1.3 PHP version: 8.1.27 ### Expected behavior We should be able to open the order details even when it has deleted products. ### Steps to reproduce Run Prestashop 8.1.3; Delete a product in a order; Try to see the order detail. We'll get an error: "PrestaShop\PrestaShop\Core\Domain\Order\QueryResult\OrderProductForViewing::__construct(): Argument #19 ($location) must be of type string, null given, called in public_html/src/Adapter/Order/QueryHandler/GetOrderProductsForViewingHandler.php on line 279"  ### PrestaShop version(s) where the bug happened 1.8.3 ### PHP version(s) where the bug happened 8.1.27 ### 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 set up a local Docker-based development environment for theme and plugin development. The environment would be a copy of the existing store, however, I have encountered an issue. Despite completing the migration steps and adjusting the configuration settings, I cannot log into PrestaShop Back Office (BO). After migrating the database and setting the store's URLs in the appropriate tables in the database, the store seems to work locally at first sight. However, I can't log into the admin panel because when I try to access the Back Office (from the URL I defined in the PS_FOLDER_ADMIN environment variable in docker-compose.yaml), the site falls into redirect loop (error 302 - ERR_TOO_MANY_REDIRECTS). Has anyone of you encountered this issue before and is able to help me solve it? Here's what I've done so far: - I downloaded a database dump of the existing store. - I configured docker-compose and set up a clean store locally. - I imported the downloaded database dump. - I updated the appropriate values in the PS_CONFIGURATION and PS_SHOP_URL tables. - I deleted the cache files and even tried deleting the .htaccess file. Additional information: - Prestashop version: 8.1.4 - MySQL version: 5.7 The problem persists in different browsers, which rules out a cookie issue. Thank you in advance for your help! ### Expected behavior Back Office should work without any problems. ### Steps to reproduce 1. Download a database dump of the existing store. 2. Configure docker-compose and set up a clean store locally. 3. Import the downloaded database dump. 4. Update the appropriate values in the PS_CONFIGURATION and PS_SHOP_URL tables. ### PrestaShop version(s) where the bug happened 8.1.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). _No response_

Error 302: ERR_TOO_MANY_REDIRECTS in Back Office

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error 302: ERR_TOO_MANY_REDIRECTS 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 Hello, I would like to set up a local Docker-based development environment for theme and plugin development. The environment would be a copy of the existing store, however, I have encountered an issue. Despite completing the migration steps and adjusting the configuration settings, I cannot log into PrestaShop Back Office (BO). After migrating the database and setting the store's URLs in the appropriate tables in the database, the store seems to work locally at first sight. However, I can't log into the admin panel because when I try to access the Back Office (from the URL I defined in the PS_FOLDER_ADMIN environment variable in docker-compose.yaml), the site falls into redirect loop (error 302 - ERR_TOO_MANY_REDIRECTS). Has anyone of you encountered this issue before and is able to help me solve it? Here's what I've done so far: - I downloaded a database dump of the existing store. - I configured docker-compose and set up a clean store locally. - I imported the downloaded database dump. - I updated the appropriate values in the PS_CONFIGURATION and PS_SHOP_URL tables. - I deleted the cache files and even tried deleting the .htaccess file. Additional information: - Prestashop version: 8.1.4 - MySQL version: 5.7 The problem persists in different browsers, which rules out a cookie issue. Thank you in advance for your help! ### Expected behavior Back Office should work without any problems. ### Steps to reproduce 1. Download a database dump of the existing store. 2. Configure docker-compose and set up a clean store locally. 3. Import the downloaded database dump. 4. Update the appropriate values in the PS_CONFIGURATION and PS_SHOP_URL tables. ### PrestaShop version(s) where the bug happened 8.1.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). _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 I upgrade from 8.1.5 or 8.0.5 to V9.0.0, I have an Error 500 aboput the feature flag  ### Expected behavior I wish I could use my shop v9.0 ### Steps to reproduce 1. Install a fresh install of 8.1.5 2. Download an autoupgrade from dev version of presta 3. do an upgrade from a folder 4. Launch the upgrade 5. :negative_squared_cross_mark: you'll have the 500 error ### PrestaShop version(s) where the bug happened 8.0.5 and 8.1.5 to develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 - dev mode ### Your company or customer's name goes here (if applicable). PS

Autoupgrade - When you upgrade on V9.0, you'll have a feature flag doesn't exist

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade - When you upgrade on V9.0, you'll have a feature flag doesn't exist 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 I upgrade from 8.1.5 or 8.0.5 to V9.0.0, I have an Error 500 aboput the feature flag  ### Expected behavior I wish I could use my shop v9.0 ### Steps to reproduce 1. Install a fresh install of 8.1.5 2. Download an autoupgrade from dev version of presta 3. do an upgrade from a folder 4. Launch the upgrade 5. :negative_squared_cross_mark: you'll have the 500 error ### PrestaShop version(s) where the bug happened 8.0.5 and 8.1.5 to develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 - dev mode ### 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 After an update, 1click Upgrade, 8.1.3 to 8.1.5, we want to try the new product page in back office, and an error is displayed when i want to write the caution (legend or ALT balise). I had to put back the old back office product page  ### Expected behavior go to product edit product edit caution legend error displayed ### Steps to reproduce go to product edit product edit caution legend error displayed ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

unable to enter image captions

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : unable to enter image captions 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 an update, 1click Upgrade, 8.1.3 to 8.1.5, we want to try the new product page in back office, and an error is displayed when i want to write the caution (legend or ALT balise). I had to put back the old back office product page  ### Expected behavior go to product edit product edit caution legend error displayed ### Steps to reproduce go to product edit product edit caution legend error displayed ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 the contactform module is a path to contactform.tpl defined in incorrect way. In the module is path defined as: `return $this->display(__FILE__, 'views/templates/widget/contactform.tpl');` but contactform.tpl file is in the module structure in the path: `views/templates/hook/` Vice versa in the theme override is contactform.tpl file present in the path: ` themes/classic/modules/contactform/views/templates/widget/` It should be unified because when the module will be used with 3rd party theme without overrided contactform.tpl file, the module itself will wont find contactform.tpl file in the module folder. ### Expected behavior _No response_ ### Steps to reproduce 1. install contactform module 2. delete /themes/classic/modules/contactform/views/templates/widget/contactform.tpl 3. Contact page will return message "No template found for module contactform" ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version contactform v4.4.2 ### Your company or customer's name goes here (if applicable). _No response_

contactform module - Incorrect path to TPL file

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : contactform module - Incorrect path to TPL 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 In the contactform module is a path to contactform.tpl defined in incorrect way. In the module is path defined as: `return $this->display(__FILE__, 'views/templates/widget/contactform.tpl');` but contactform.tpl file is in the module structure in the path: `views/templates/hook/` Vice versa in the theme override is contactform.tpl file present in the path: ` themes/classic/modules/contactform/views/templates/widget/` It should be unified because when the module will be used with 3rd party theme without overrided contactform.tpl file, the module itself will wont find contactform.tpl file in the module folder. ### Expected behavior _No response_ ### Steps to reproduce 1. install contactform module 2. delete /themes/classic/modules/contactform/views/templates/widget/contactform.tpl 3. Contact page will return message "No template found for module contactform" ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version contactform v4.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 Hello, module ps_emailalerts generate TXT email templates with HTML code.  ### Expected behavior _No response_ ### Steps to reproduce 1. install and setup ps_emailalerts module 2. set text email notifications only in the Emails part of PS BO * 3. make an order 4. check received email about a new order 5. notification email about a new order included HTML code - see following screenshot *  ### PrestaShop version(s) where the bug happened 8.1.4 ### 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 3.0.0 ### Your company or customer's name goes here (if applicable). _No response_

ps_emailalerts module: text email templates render HTML

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_emailalerts module: text email templates render HTML 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, module ps_emailalerts generate TXT email templates with HTML code.  ### Expected behavior _No response_ ### Steps to reproduce 1. install and setup ps_emailalerts module 2. set text email notifications only in the Emails part of PS BO * 3. make an order 4. check received email about a new order 5. notification email about a new order included HTML code - see following screenshot *  ### PrestaShop version(s) where the bug happened 8.1.4 ### 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 3.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 Dear assistance, we faced an issue in updating our Prestashop version from the actual 1.7.8.7 to the desired 1.7.8.11. The problem was that Prestashop couldn't complete the backup of the files and stop the update. Here following the data that Prestashop support told us to report you: - Prestashop version: 1.7.8.7 - PHP version: 7.4.33 - Screenshots   - Steps to reproduce the problem: simply start the Prestashop version update ### Expected behavior To complete the Prestashop version update. ### Steps to reproduce 1. Launch the update to version 1.7.8.11 from the right side of the dashboard. 2. Save the update zip file in local. 3. Upload the zip file in Prestashop ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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). Saiet Telecomunicazioni

Problem in updating Prestashop 1.7.8.7

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem in updating Prestashop 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 Dear assistance, we faced an issue in updating our Prestashop version from the actual 1.7.8.7 to the desired 1.7.8.11. The problem was that Prestashop couldn't complete the backup of the files and stop the update. Here following the data that Prestashop support told us to report you: - Prestashop version: 1.7.8.7 - PHP version: 7.4.33 - Screenshots   - Steps to reproduce the problem: simply start the Prestashop version update ### Expected behavior To complete the Prestashop version update. ### Steps to reproduce 1. Launch the update to version 1.7.8.11 from the right side of the dashboard. 2. Save the update zip file in local. 3. Upload the zip file in Prestashop ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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). Saiet Telecomunicazioni --- 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 **Describe the bug** 500 response - PHP error When trying to create a new products (POST request to the webservice endpoint ) the server returns a 500 error due to a PHP error: `<error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error>` I appears that these errors are triggered by the name field of the ressource. When i leave the name field empty it triggers another error stating that the field is not an array ; similar issue in this issue #16896 ### Expected behavior 200 response and new product Created ### Steps to reproduce 1. Create an API with enabled access to products and all methods: 2. Make a POST request to the webservice URL /api/products with the below XML data (based on the output of /api/products?schema=blank - value fields are 'price' and 'name', removed id_category_default, and position_in_categories as these caused other errors.): ```php Create an API with enabled access to products and all methods: Make a POST request to the webservice URL /api/products with the below XML data (based on the output of /api/products?schema=blank - value fields are 'price' and 'name', removed id_category_default, and position_in_categories as these caused other errors.): <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <product> <id><![CDATA[]]></id> <id_manufacturer><![CDATA[]]></id_manufacturer> <id_supplier><![CDATA[]]></id_supplier> <new><![CDATA[]]></new> <cache_default_attribute><![CDATA[]]></cache_default_attribute> <id_default_image><![CDATA[]]></id_default_image> <id_default_combination><![CDATA[]]></id_default_combination> <id_tax_rules_group><![CDATA[]]></id_tax_rules_group> <type><![CDATA[]]></type> <id_shop_default><![CDATA[]]></id_shop_default> <reference><![CDATA[]]></reference> <supplier_reference><![CDATA[]]></supplier_reference> <location><![CDATA[]]></location> <width><![CDATA[]]></width> <height><![CDATA[]]></height> <depth><![CDATA[]]></depth> <weight><![CDATA[]]></weight> <quantity_discount><![CDATA[]]></quantity_discount> <ean13><![CDATA[]]></ean13> <isbn><![CDATA[]]></isbn> <upc><![CDATA[]]></upc> <mpn><![CDATA[]]></mpn> <cache_is_pack><![CDATA[]]></cache_is_pack> <cache_has_attachments><![CDATA[]]></cache_has_attachments> <is_virtual><![CDATA[]]></is_virtual> <state><![CDATA[]]></state> <additional_delivery_times><![CDATA[]]></additional_delivery_times> <delivery_in_stock> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </delivery_in_stock> <delivery_out_stock> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </delivery_out_stock> <on_sale><![CDATA[]]></on_sale> <online_only><![CDATA[]]></online_only> <ecotax><![CDATA[]]></ecotax> <minimal_quantity><![CDATA[]]></minimal_quantity> <low_stock_threshold><![CDATA[]]></low_stock_threshold> <low_stock_alert><![CDATA[]]></low_stock_alert> <price><![CDATA[1.00]]></price> <wholesale_price><![CDATA[]]></wholesale_price> <unity><![CDATA[]]></unity> <unit_price_ratio><![CDATA[]]></unit_price_ratio> <additional_shipping_cost><![CDATA[]]></additional_shipping_cost> <customizable><![CDATA[]]></customizable> <text_fields><![CDATA[]]></text_fields> <uploadable_files><![CDATA[]]></uploadable_files> <active><![CDATA[]]></active> <redirect_type><![CDATA[]]></redirect_type> <id_type_redirected><![CDATA[]]></id_type_redirected> <available_for_order><![CDATA[]]></available_for_order> <available_date><![CDATA[]]></available_date> <show_condition><![CDATA[]]></show_condition> <condition><![CDATA[]]></condition> <show_price><![CDATA[]]></show_price> <indexed><![CDATA[]]></indexed> <visibility><![CDATA[]]></visibility> <advanced_stock_management><![CDATA[]]></advanced_stock_management> <date_add><![CDATA[]]></date_add> <date_upd><![CDATA[]]></date_upd> <pack_stock_type><![CDATA[]]></pack_stock_type> <meta_description> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_description> <meta_keywords> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_keywords> <meta_title> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_title> <link_rewrite> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </link_rewrite> <name> <language id="1"><![CDATA[]]></language> </name> <description> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </description> <description_short> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </description_short> <available_now> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </available_now> <available_later> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </available_later> <associations> <categories> <category> <id><![CDATA[]]></id> </category> </categories> <images> <image> <id><![CDATA[]]></id> </image> </images> <combinations> <combination> <id><![CDATA[]]></id> </combination> </combinations> <product_option_values> <product_option_value> <id><![CDATA[]]></id> </product_option_value> </product_option_values> <product_features> <product_feature> <id><![CDATA[]]></id> <id_feature_value><![CDATA[]]></id_feature_value> </product_feature> </product_features> <tags> <tag> <id><![CDATA[]]></id> </tag> </tags> <stock_availables> <stock_available> <id><![CDATA[]]></id> <id_product_attribute><![CDATA[]]></id_product_attribute> </stock_available> </stock_availables> <attachments> <attachment> <id><![CDATA[]]></id> </attachment> </attachments> <accessories> <product> <id><![CDATA[]]></id> </product> </accessories> <product_bundle> <product> <id><![CDATA[]]></id> <id_product_attribute><![CDATA[]]></id_product_attribute> <quantity><![CDATA[]]></quantity> </product> </product_bundle> </associations> </product> ``` 3. Server returns following errors : ```php <?xml version="1.0" encoding="UTF-8"?> <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <errors> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_SafeParam::$wmode is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/SafeParam.php, line 30)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> </errors> </prestashop> ``` **Additional Information** Request sent with Postman Cloud ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.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_

Unknown PHP error when creating product through webservice : Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated]

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unknown PHP error when creating product through webservice : Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is 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 **Describe the bug** 500 response - PHP error When trying to create a new products (POST request to the webservice endpoint ) the server returns a 500 error due to a PHP error: `<error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error>` I appears that these errors are triggered by the name field of the ressource. When i leave the name field empty it triggers another error stating that the field is not an array ; similar issue in this issue #16896 ### Expected behavior 200 response and new product Created ### Steps to reproduce 1. Create an API with enabled access to products and all methods: 2. Make a POST request to the webservice URL /api/products with the below XML data (based on the output of /api/products?schema=blank - value fields are 'price' and 'name', removed id_category_default, and position_in_categories as these caused other errors.): ```php Create an API with enabled access to products and all methods: Make a POST request to the webservice URL /api/products with the below XML data (based on the output of /api/products?schema=blank - value fields are 'price' and 'name', removed id_category_default, and position_in_categories as these caused other errors.): <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <product> <id><![CDATA[]]></id> <id_manufacturer><![CDATA[]]></id_manufacturer> <id_supplier><![CDATA[]]></id_supplier> <new><![CDATA[]]></new> <cache_default_attribute><![CDATA[]]></cache_default_attribute> <id_default_image><![CDATA[]]></id_default_image> <id_default_combination><![CDATA[]]></id_default_combination> <id_tax_rules_group><![CDATA[]]></id_tax_rules_group> <type><![CDATA[]]></type> <id_shop_default><![CDATA[]]></id_shop_default> <reference><![CDATA[]]></reference> <supplier_reference><![CDATA[]]></supplier_reference> <location><![CDATA[]]></location> <width><![CDATA[]]></width> <height><![CDATA[]]></height> <depth><![CDATA[]]></depth> <weight><![CDATA[]]></weight> <quantity_discount><![CDATA[]]></quantity_discount> <ean13><![CDATA[]]></ean13> <isbn><![CDATA[]]></isbn> <upc><![CDATA[]]></upc> <mpn><![CDATA[]]></mpn> <cache_is_pack><![CDATA[]]></cache_is_pack> <cache_has_attachments><![CDATA[]]></cache_has_attachments> <is_virtual><![CDATA[]]></is_virtual> <state><![CDATA[]]></state> <additional_delivery_times><![CDATA[]]></additional_delivery_times> <delivery_in_stock> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </delivery_in_stock> <delivery_out_stock> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </delivery_out_stock> <on_sale><![CDATA[]]></on_sale> <online_only><![CDATA[]]></online_only> <ecotax><![CDATA[]]></ecotax> <minimal_quantity><![CDATA[]]></minimal_quantity> <low_stock_threshold><![CDATA[]]></low_stock_threshold> <low_stock_alert><![CDATA[]]></low_stock_alert> <price><![CDATA[1.00]]></price> <wholesale_price><![CDATA[]]></wholesale_price> <unity><![CDATA[]]></unity> <unit_price_ratio><![CDATA[]]></unit_price_ratio> <additional_shipping_cost><![CDATA[]]></additional_shipping_cost> <customizable><![CDATA[]]></customizable> <text_fields><![CDATA[]]></text_fields> <uploadable_files><![CDATA[]]></uploadable_files> <active><![CDATA[]]></active> <redirect_type><![CDATA[]]></redirect_type> <id_type_redirected><![CDATA[]]></id_type_redirected> <available_for_order><![CDATA[]]></available_for_order> <available_date><![CDATA[]]></available_date> <show_condition><![CDATA[]]></show_condition> <condition><![CDATA[]]></condition> <show_price><![CDATA[]]></show_price> <indexed><![CDATA[]]></indexed> <visibility><![CDATA[]]></visibility> <advanced_stock_management><![CDATA[]]></advanced_stock_management> <date_add><![CDATA[]]></date_add> <date_upd><![CDATA[]]></date_upd> <pack_stock_type><![CDATA[]]></pack_stock_type> <meta_description> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_description> <meta_keywords> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_keywords> <meta_title> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </meta_title> <link_rewrite> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </link_rewrite> <name> <language id="1"><![CDATA[]]></language> </name> <description> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </description> <description_short> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </description_short> <available_now> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </available_now> <available_later> <language id="1"><![CDATA[]]></language> <language id="2"><![CDATA[]]></language> </available_later> <associations> <categories> <category> <id><![CDATA[]]></id> </category> </categories> <images> <image> <id><![CDATA[]]></id> </image> </images> <combinations> <combination> <id><![CDATA[]]></id> </combination> </combinations> <product_option_values> <product_option_value> <id><![CDATA[]]></id> </product_option_value> </product_option_values> <product_features> <product_feature> <id><![CDATA[]]></id> <id_feature_value><![CDATA[]]></id_feature_value> </product_feature> </product_features> <tags> <tag> <id><![CDATA[]]></id> </tag> </tags> <stock_availables> <stock_available> <id><![CDATA[]]></id> <id_product_attribute><![CDATA[]]></id_product_attribute> </stock_available> </stock_availables> <attachments> <attachment> <id><![CDATA[]]></id> </attachment> </attachments> <accessories> <product> <id><![CDATA[]]></id> </product> </accessories> <product_bundle> <product> <id><![CDATA[]]></id> <id_product_attribute><![CDATA[]]></id_product_attribute> <quantity><![CDATA[]]></quantity> </product> </product_bundle> </associations> </product> ``` 3. Server returns following errors : ```php <?xml version="1.0" encoding="UTF-8"?> <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <errors> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_NameSync::$idDef is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/NameSync.php, line 13)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_AttrTransform_SafeParam::$wmode is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/AttrTransform/SafeParam.php, line 30)]]> </message> </error> <error> <code> <![CDATA[15]]> </code> <message> <![CDATA[[PHP Unknown error #8192] Creation of dynamic property HTMLPurifier_Lexer_DOMLex::$_entity_parser is deprecated (/home/vgquqqr/www/vendor/ezyang/htmlpurifier/library/HTMLPurifier/Lexer.php, line 154)]]> </message> </error> </errors> </prestashop> ``` **Additional Information** Request sent with Postman Cloud ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.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 Hi now I realized that the currency does not change automatically if you use a customer account with a currency other than the default one we assume that on the site there are the EURO and Swiss Franc currencies, with the French and German languages, but this also applies to other nations such as Sweden, Denmark, Norway ... We set the Swiss Franc as the default currency in the Swiss nation. I go to add a product to the cart, then log in and register, enter a Swiss address and I expect it to automatically change the currency to Swiss Franc from the Euro (but only the first time, because maybe I might want to pay in Euros and so I would be able to change it back into Euros if I wanted, otherwise I would pay with the default currency set in Switzerland). If not, what would be the point of setting the default currency in the country? Unfortunately I saw that no change occurs on the front after creating the address  bye ### Expected behavior _No response_ ### Steps to reproduce 1. start from a website with two currencies Euro and Swiss Franc 2. active the Swiss 3. set its default currency to Swiss Franc 4. Now go to the front-office and add a product to the cart 5. go to the checkout and create an account with a Swiss address 6. now the currency continue to be in Euro ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

FO - the currency does not change automatically if it is set in the country when the customer logs in

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO - the currency does not change automatically if it is set in the country when the customer logs in 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 now I realized that the currency does not change automatically if you use a customer account with a currency other than the default one we assume that on the site there are the EURO and Swiss Franc currencies, with the French and German languages, but this also applies to other nations such as Sweden, Denmark, Norway ... We set the Swiss Franc as the default currency in the Swiss nation. I go to add a product to the cart, then log in and register, enter a Swiss address and I expect it to automatically change the currency to Swiss Franc from the Euro (but only the first time, because maybe I might want to pay in Euros and so I would be able to change it back into Euros if I wanted, otherwise I would pay with the default currency set in Switzerland). If not, what would be the point of setting the default currency in the country? Unfortunately I saw that no change occurs on the front after creating the address  bye ### Expected behavior _No response_ ### Steps to reproduce 1. start from a website with two currencies Euro and Swiss Franc 2. active the Swiss 3. set its default currency to Swiss Franc 4. Now go to the front-office and add a product to the cart 5. go to the checkout and create an account with a Swiss address 6. now the currency continue to be in Euro ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 ---

### Describe the bug and add attachments When I disable module on module manager, the page greys out, but stays greyed and I can't do anything. ### Expected behavior The overlay should disappear. ### Steps to reproduce 1. Go to module manager. 2. Disable some module, bestsellers module for example. 3. Page greys out, modal shows. 4. You confirm it. 5. Green alert displays, but page stays grey. 6. You have to refresh the page.  ### PrestaShop version(s) where the bug happened 8.1.5

Module page overlayed and inactive after disabling module

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module page overlayed and inactive after disabling module Issue date: --- start body --- ### Describe the bug and add attachments When I disable module on module manager, the page greys out, but stays greyed and I can't do anything. ### Expected behavior The overlay should disappear. ### Steps to reproduce 1. Go to module manager. 2. Disable some module, bestsellers module for example. 3. Page greys out, modal shows. 4. You confirm it. 5. Green alert displays, but page stays grey. 6. You have to refresh the page.  ### PrestaShop version(s) where the bug happened 8.1.5 --- 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 Context: DB structure. It's a good practice to add attribute "unsigned" when using primary key auto-increment (and foreign key columns). Some Doctrine entities have `options={"unsigned":true}` but some not, this is not a big problem because tables such as connections/guest are not moved to Doctrine, but I think is a useful habit to get into. Also, this is a regression, here I compare lang table between ps1.7 and ps8: <img width="1091" alt="Capture d’écran, le 2024-03-24 à 20 52 33" src="https://github.com/PrestaShop/PrestaShop/assets/1219817/d073092e-0948-49b1-9a96-df5dd4af7a69"> Also another story, lot of index are missing !!! ### Expected behavior We should see unsigned attribute for any number columns that will be always positive. Moving to Doctrine entities should conserve data structure. ### Steps to reproduce Install Prestashop ### PrestaShop version(s) where the bug happened 8.1.0 ### 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_

[DB] Some primary keys / columns INT are not unsigned

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [DB] Some primary keys / columns INT are not unsigned 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 Context: DB structure. It's a good practice to add attribute "unsigned" when using primary key auto-increment (and foreign key columns). Some Doctrine entities have `options={"unsigned":true}` but some not, this is not a big problem because tables such as connections/guest are not moved to Doctrine, but I think is a useful habit to get into. Also, this is a regression, here I compare lang table between ps1.7 and ps8: <img width="1091" alt="Capture d’écran, le 2024-03-24 à 20 52 33" src="https://github.com/PrestaShop/PrestaShop/assets/1219817/d073092e-0948-49b1-9a96-df5dd4af7a69"> Also another story, lot of index are missing !!! ### Expected behavior We should see unsigned attribute for any number columns that will be always positive. Moving to Doctrine entities should conserve data structure. ### Steps to reproduce Install Prestashop ### PrestaShop version(s) where the bug happened 8.1.0 ### 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 You cannot filter products when you are reordering the products. It is something that should be able to be done since you may only be interested in reordering the products that are active [https://www.awesomescreenshot.com/video/26109913?key=3821cd5a704cdf222aa7cf7f34a753ac](https://www.awesomescreenshot.com/video/26109913?key=3821cd5a704cdf222aa7cf7f34a753ac) ### Expected behavior Be able to reorder the products and also be able to use the filter while ### Steps to reproduce 1. Products 2. Reorder 3. Try to use filters ### 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 _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Be able to filter products when you are reordering the products

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Be able to filter products when you are reordering the 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 You cannot filter products when you are reordering the products. It is something that should be able to be done since you may only be interested in reordering the products that are active [https://www.awesomescreenshot.com/video/26109913?key=3821cd5a704cdf222aa7cf7f34a753ac](https://www.awesomescreenshot.com/video/26109913?key=3821cd5a704cdf222aa7cf7f34a753ac) ### Expected behavior Be able to reorder the products and also be able to use the filter while ### Steps to reproduce 1. Products 2. Reorder 3. Try to use filters ### 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 _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 one of my customer's shop there are 180 000 orders in database. On new AdminOrder controller grid view that is PrestaShopBundle\Controller\Admin\Sell\Order\OrderController There is at least one query which is not listed in Profilling stopwatch queries but you can find it on doctrine debug page. <img width="1079" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/1394451/0aa15150-5843-4866-81e3-b4e11535c8ee"> https://github.com/PrestaShop/PrestaShop/blob/a574a1e0be0276d04489fb86e375429c5069d8b8/src/Core/Grid/Query/OrderQueryBuilder.php#L116 This function execute slow count query with many joins: `SELECT count(o.id_order) FROM ps_orders o LEFT JOIN ps_customer cu ON o.id_customer = cu.id_customer LEFT JOIN ps_currency cur ON o.id_currency = cur.id_currency INNER JOIN ps_address a ON o.id_address_delivery = a.id_address LEFT JOIN ps_order_state os ON o.current_state = os.id_order_state LEFT JOIN ps_shop s ON o.id_shop = s.id_shop INNER JOIN ps_country c ON a.id_country = c.id_country INNER JOIN ps_country_lang cl ON c.id_country = cl.id_country AND cl.id_lang = 1 LEFT JOIN ps_order_state_lang osl ON os.id_order_state = osl.id_order_state AND osl.id_lang = 1 WHERE o.id_shop IN (1); ` It lasts at least 0.3-0.5s on my Mac. On real server it lasts even more. I've made simpler query if there is no filters at all and it now works much better. before <img width="1478" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/1394451/5b8b3af1-0820-4d34-9b0e-574f8ba1d316"> after my changes  ### Expected behavior I think this can be improved so not only my customer will be happy. ### Steps to reproduce listed up ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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_

Very slow grid data count query with more then 180000 orders in database

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Very slow grid data count query with more then 180000 orders in database 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 one of my customer's shop there are 180 000 orders in database. On new AdminOrder controller grid view that is PrestaShopBundle\Controller\Admin\Sell\Order\OrderController There is at least one query which is not listed in Profilling stopwatch queries but you can find it on doctrine debug page. <img width="1079" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/1394451/0aa15150-5843-4866-81e3-b4e11535c8ee"> https://github.com/PrestaShop/PrestaShop/blob/a574a1e0be0276d04489fb86e375429c5069d8b8/src/Core/Grid/Query/OrderQueryBuilder.php#L116 This function execute slow count query with many joins: `SELECT count(o.id_order) FROM ps_orders o LEFT JOIN ps_customer cu ON o.id_customer = cu.id_customer LEFT JOIN ps_currency cur ON o.id_currency = cur.id_currency INNER JOIN ps_address a ON o.id_address_delivery = a.id_address LEFT JOIN ps_order_state os ON o.current_state = os.id_order_state LEFT JOIN ps_shop s ON o.id_shop = s.id_shop INNER JOIN ps_country c ON a.id_country = c.id_country INNER JOIN ps_country_lang cl ON c.id_country = cl.id_country AND cl.id_lang = 1 LEFT JOIN ps_order_state_lang osl ON os.id_order_state = osl.id_order_state AND osl.id_lang = 1 WHERE o.id_shop IN (1); ` It lasts at least 0.3-0.5s on my Mac. On real server it lasts even more. I've made simpler query if there is no filters at all and it now works much better. before <img width="1478" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/1394451/5b8b3af1-0820-4d34-9b0e-574f8ba1d316"> after my changes  ### Expected behavior I think this can be improved so not only my customer will be happy. ### Steps to reproduce listed up ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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 When I do an upgrade 8.0.5 from to 8.1.5, I don't have the experimental feature as we have with a fresh version of 8.1.5 as you can see : [recording(150).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/1dcfae17-ce55-42b3-91bc-95db241ddfae) ### Expected behavior I wish I could Find all the experimental feature as you can see here :  ### Steps to reproduce 1. Go to BO 2. Go to module manager 3. install Autoupgrade 4. Do an upgrade on 8.1.5 from major release 5. Go to Bo > Advanced Parameters > Experimental Feature ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### Your company or customer's name goes here (if applicable). PS

Autoupgrade - Don't have the experimental feature on autoupgrade

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade - Don't have the experimental feature on autoupgrade 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 8.0.5 from to 8.1.5, I don't have the experimental feature as we have with a fresh version of 8.1.5 as you can see : [recording(150).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/1dcfae17-ce55-42b3-91bc-95db241ddfae) ### Expected behavior I wish I could Find all the experimental feature as you can see here :  ### Steps to reproduce 1. Go to BO 2. Go to module manager 3. install Autoupgrade 4. Do an upgrade on 8.1.5 from major release 5. Go to Bo > Advanced Parameters > Experimental Feature ### PrestaShop version(s) where the bug happened 8.0.5 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### 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 When you install autoupgrade on Prestashop V9. You don't have the fast link of autoupgrade on the side bar as you can see :  ### Expected behavior I wish I could have my fast link on the side bar, like this :  ### Steps to reproduce 1. Go to BO 2. Go to Module Manager 3. Install Autoupgrade 4. Clic on Configure 5. Autoupgrade is not on side bar :negative_squared_cross_mark: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### Your company or customer's name goes here (if applicable). PS

Autoupgrade - We don't have the autoupgrade on the side bar for the v9

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoupgrade - We don't have the autoupgrade on the side bar for the v9 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 install autoupgrade on Prestashop V9. You don't have the fast link of autoupgrade on the side bar as you can see :  ### Expected behavior I wish I could have my fast link on the side bar, like this :  ### Steps to reproduce 1. Go to BO 2. Go to Module Manager 3. Install Autoupgrade 4. Clic on Configure 5. Autoupgrade is not on side bar :negative_squared_cross_mark: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version autoupgrade v5.0.1 ### 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 (httpd apache) In a unpredictable way, backoffice in my debug mode is not accessible when i turn off debug mode i see the modules are not grouped and the error is: An exception has been thrown during the rendering of a template ("file_get_contents_curl failed to download http://api.prestashop.com/xml/tab_modules_list_17.xml : (error code 7) "). i tried to delete config/xml but it doesn't generating.  ### Expected behavior _No response_ ### Steps to reproduce I turned debug mode. and got random error. ### PrestaShop version(s) where the bug happened 1.7.6.5 ### PHP version(s) where the bug happened 7.2.34 ### 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_

file_get_contents_curl failed to download http://api.prestashop.com/xml/tab_modules_list_17.xml : (error code 7)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : file_get_contents_curl failed to download http://api.prestashop.com/xml/tab_modules_list_17.xml : (error code 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 (httpd apache) In a unpredictable way, backoffice in my debug mode is not accessible when i turn off debug mode i see the modules are not grouped and the error is: An exception has been thrown during the rendering of a template ("file_get_contents_curl failed to download http://api.prestashop.com/xml/tab_modules_list_17.xml : (error code 7) "). i tried to delete config/xml but it doesn't generating.  ### Expected behavior _No response_ ### Steps to reproduce I turned debug mode. and got random error. ### PrestaShop version(s) where the bug happened 1.7.6.5 ### PHP version(s) where the bug happened 7.2.34 ### 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 During combinations import, via file import, the MPN field is not added or updated in the product. ### Expected behavior We except that all fields are created/updated if present in the file and imported via official combinations import. ### Steps to reproduce 1. Go to advanced parameters -> import 2. Select "combinations" on select field 3. Upload a sample combinations file with the MPN field 4. Map the attributes of the files with the Combination attributes 5. Import the file and wait to finish 6. Open the product in the backoffice, you notice that all fields are updated or created but the MPN still remain empty ### PrestaShop version(s) where the bug happened 8.x ### PHP version(s) where the bug happened 8.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_

MPN field is not imported during import combinations via file import

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : MPN field is not imported during import combinations via file import 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 combinations import, via file import, the MPN field is not added or updated in the product. ### Expected behavior We except that all fields are created/updated if present in the file and imported via official combinations import. ### Steps to reproduce 1. Go to advanced parameters -> import 2. Select "combinations" on select field 3. Upload a sample combinations file with the MPN field 4. Map the attributes of the files with the Combination attributes 5. Import the file and wait to finish 6. Open the product in the backoffice, you notice that all fields are updated or created but the MPN still remain empty ### PrestaShop version(s) where the bug happened 8.x ### PHP version(s) where the bug happened 8.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 Hello, Upgrade Prestashop from 8.1.3 to 8.1.5 does not work - MD5 sum does not match. I tried check autoupgrade folder permissions (755) and reset module - result: does not works too. After reset module I only lose previous backups (ROLLBACK) and setting. Thank you BR Petr **Here is log:** Analyzing the situation...Shop deactivated. Now downloading... (this can take a while) Download complete but MD5 sum does not match (d41d8cd98f00b204e9800998ecf8427e). Operation aborted. Starting upgrade... Downloaded archive will come from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip MD5 hash will be checked against f0c1fe954d9dceb205bf172cbc00a195 Downloading from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip File will be saved in /home/www/domain.cz/www/test.domain.cz/Admin/autoupgrade/download/prestashop.zip Download directory has been emptied [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(): SSL operation failed with code 1. OpenSSL Error messages: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(): Failed to enable crypto [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip): failed to open stream: operation failed [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 308 - fclose() expects parameter 1 to be resource, bool given ---- PHP: 7.4.33 MySQL: 10.1.48-MariaDB-0+deb9u2 1-Click Upgrade - v5.0.1 ### Expected behavior Working without a problem as before. ### Steps to reproduce Standard 1-Click Upgrade process. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened PHP: 7.4.33 ### If your bug is related to a module, specify its name and its version 1-Click Upgrade - v5.0.1 ### Your company or customer's name goes here (if applicable). _No response_

Upgrade PS from 8.1.3 to 8.1.5 does not work - MD5 sum does not match

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade PS from 8.1.3 to 8.1.5 does not work - MD5 sum does not match 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, Upgrade Prestashop from 8.1.3 to 8.1.5 does not work - MD5 sum does not match. I tried check autoupgrade folder permissions (755) and reset module - result: does not works too. After reset module I only lose previous backups (ROLLBACK) and setting. Thank you BR Petr **Here is log:** Analyzing the situation...Shop deactivated. Now downloading... (this can take a while) Download complete but MD5 sum does not match (d41d8cd98f00b204e9800998ecf8427e). Operation aborted. Starting upgrade... Downloaded archive will come from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip MD5 hash will be checked against f0c1fe954d9dceb205bf172cbc00a195 Downloading from https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip File will be saved in /home/www/domain.cz/www/test.domain.cz/Admin/autoupgrade/download/prestashop.zip Download directory has been emptied [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(): SSL operation failed with code 1. OpenSSL Error messages: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(): Failed to enable crypto [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 305 - fopen(https://github.com/PrestaShop/PrestaShop/releases/download/8.1.5/prestashop_8.1.5.zip): failed to open stream: operation failed [INTERNAL] /home/www/domain.cz/www/test.domain.cz/modules/autoupgrade/classes/Tools14.php line 308 - fclose() expects parameter 1 to be resource, bool given ---- PHP: 7.4.33 MySQL: 10.1.48-MariaDB-0+deb9u2 1-Click Upgrade - v5.0.1 ### Expected behavior Working without a problem as before. ### Steps to reproduce Standard 1-Click Upgrade process. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened PHP: 7.4.33 ### If your bug is related to a module, specify its name and its version 1-Click Upgrade - v5.0.1 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Issue The doc swagger doesn't work well. The input type of the API is wrongly scrapped. The config of the doc should be check on once the endpoint is merged but it might not be ideal if we receive multiple contributions. ### Solution - [ ] Investigate to match automatically the doc swagger - [ ] Check all the endpoints to match the ADR spec

POC doc swagger

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : POC doc swagger Issue date: --- start body --- ### Issue The doc swagger doesn't work well. The input type of the API is wrongly scrapped. The config of the doc should be check on once the endpoint is merged but it might not be ideal if we receive multiple contributions. ### Solution - [ ] Investigate to match automatically the doc swagger - [ ] Check all the endpoints to match the ADR spec --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments Some of cart rules created on previous versions of PrestaShop cannot be saved. ### Expected behavior I should be able to save all cart rules properly. ### Steps to reproduce 1. I click on edit cart rule. Edit page opens. 2. The URL is `/admin/index.php?controller=AdminCartRules&updatecart_rule=&id_cart_rule=70&token=xxx` 3. I change name. Click Save. 4. I get redirected to `/admin258ytdyrs/index.php?controller=AdminCartRules&token=xxx&addcart_rule` and nothing was saved. 5. I click save, page just refreshes. Nothing, no error, no message. 6. When I go back, the cart rule is still original. ### PrestaShop version(s) where the bug happened 8.1.5, did not happen on 1.7.6.9

Cannot save cart rules on some stores

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Cannot save cart rules on some stores Issue date: --- start body --- ### Describe the bug and add attachments Some of cart rules created on previous versions of PrestaShop cannot be saved. ### Expected behavior I should be able to save all cart rules properly. ### Steps to reproduce 1. I click on edit cart rule. Edit page opens. 2. The URL is `/admin/index.php?controller=AdminCartRules&updatecart_rule=&id_cart_rule=70&token=xxx` 3. I change name. Click Save. 4. I get redirected to `/admin258ytdyrs/index.php?controller=AdminCartRules&token=xxx&addcart_rule` and nothing was saved. 5. I click save, page just refreshes. Nothing, no error, no message. 6. When I go back, the cart rule is still original. ### PrestaShop version(s) where the bug happened 8.1.5, did not happen on 1.7.6.9 --- 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 receive hundreds of email from or contact form daily from strangers. This seems to be a way to scam us. We receive as much as 10 mails from the same adress per day in every language possible. We don't know how to block these spams without enabling our contact form. Here's one example. <img width="657" alt="Capture d’écran 2024-03-21 à 12 55 42" src="https://github.com/PrestaShop/PrestaShop/assets/164348485/cf88a9f1-e299-4d33-9406-278463270d76"> ### Expected behavior We want to stop these spams and block these false adress without enabling our contact form ### Steps to reproduce It's an issue with our contact form, I don't know how to reproduce it by myself. ### PrestaShop version(s) where the bug happened 1.7.8.3 ### PHP version(s) where the bug happened ? ### If your bug is related to a module, specify its name and its version Formulaire de contact v4.3.0 ### Your company or customer's name goes here (if applicable). Mait Armoir

Spams on my contact form

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Spams on my contact form 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 receive hundreds of email from or contact form daily from strangers. This seems to be a way to scam us. We receive as much as 10 mails from the same adress per day in every language possible. We don't know how to block these spams without enabling our contact form. Here's one example. <img width="657" alt="Capture d’écran 2024-03-21 à 12 55 42" src="https://github.com/PrestaShop/PrestaShop/assets/164348485/cf88a9f1-e299-4d33-9406-278463270d76"> ### Expected behavior We want to stop these spams and block these false adress without enabling our contact form ### Steps to reproduce It's an issue with our contact form, I don't know how to reproduce it by myself. ### PrestaShop version(s) where the bug happened 1.7.8.3 ### PHP version(s) where the bug happened ? ### If your bug is related to a module, specify its name and its version Formulaire de contact v4.3.0 ### Your company or customer's name goes here (if applicable). Mait Armoir --- 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 trying to add a new slide in the ps_imageslider module, file selection doesn't work. This problem occurs up to version 1.7.6.9 of Prestashop, in subsequent versions it does not occur, however the javascript error which is the cause of the problem is still there. I attach a video. The problem occurs because the `headerHTML` method of the form does not include the action of adding a new slide. https://github.com/PrestaShop/PrestaShop/assets/2463965/19908f45-5383-45aa-9f92-caba57f11f59 ### Expected behavior _No response_ ### Steps to reproduce 1. go to the ps_imageslider module 2. click on Add new slider 3. click on "Select a file" 4. The file selection popup is not shown ### PrestaShop version(s) where the bug happened <= 1.7.6.9 ### PHP version(s) where the bug happened all ### 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). Codencode

Adding new image slide in "Image slider" module (ps_imageslider) does not work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Adding new image slide in "Image slider" module (ps_imageslider) does not work 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 trying to add a new slide in the ps_imageslider module, file selection doesn't work. This problem occurs up to version 1.7.6.9 of Prestashop, in subsequent versions it does not occur, however the javascript error which is the cause of the problem is still there. I attach a video. The problem occurs because the `headerHTML` method of the form does not include the action of adding a new slide. https://github.com/PrestaShop/PrestaShop/assets/2463965/19908f45-5383-45aa-9f92-caba57f11f59 ### Expected behavior _No response_ ### Steps to reproduce 1. go to the ps_imageslider module 2. click on Add new slider 3. click on "Select a file" 4. The file selection popup is not shown ### PrestaShop version(s) where the bug happened <= 1.7.6.9 ### PHP version(s) where the bug happened all ### 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). Codencode --- 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 try to install prestashop with a custom theme with CLI command, I have a bug on the installation when the theme is loading informations from the theme.yml :  It seems that one of the modules to enable in theme.yml is not valid. I tried to reset all of these modules in the BO but all is working well. I also tried to delete the "to_enable" part in theme.yml but I have the same error ... So the installation blocks before installing image types and the result is an error 500 on front office. ### Expected behavior _No response_ ### Steps to reproduce 1. Get a custom theme from your prestashop 8.1.5 basic folder /themes/ 2. Launch composer install 3. Launch install cli with option "--theme=[your_theme]" ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### 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). BWA - Adrien Pleux

Prestashop 8.1.5 CLI Installation with custom theme bug

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 8.1.5 CLI Installation with custom theme bug 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 try to install prestashop with a custom theme with CLI command, I have a bug on the installation when the theme is loading informations from the theme.yml :  It seems that one of the modules to enable in theme.yml is not valid. I tried to reset all of these modules in the BO but all is working well. I also tried to delete the "to_enable" part in theme.yml but I have the same error ... So the installation blocks before installing image types and the result is an error 500 on front office. ### Expected behavior _No response_ ### Steps to reproduce 1. Get a custom theme from your prestashop 8.1.5 basic folder /themes/ 2. Launch composer install 3. Launch install cli with option "--theme=[your_theme]" ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.27 ### 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). BWA - Adrien Pleux --- 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 Scrolling in combination generator is weird and broken when there are many values.  ### Expected behavior It should look OK. There are some weird things going on, while it's just the matter of setting proper max sizing and overflows. ### Steps to reproduce 1. Make a attribute with many values. 2. Go to combination generator and see how the scroll behaves. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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_

Styling (overflow) broken in combination generator

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Styling (overflow) broken in combination generator 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 Scrolling in combination generator is weird and broken when there are many values.  ### Expected behavior It should look OK. There are some weird things going on, while it's just the matter of setting proper max sizing and overflows. ### Steps to reproduce 1. Make a attribute with many values. 2. Go to combination generator and see how the scroll behaves. ### PrestaShop version(s) where the bug happened 8.1.5 ### 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 ---

### Describe the bug and add attachments I have an attribute Color, with all values having some color or texture. See here - https://github.com/PrestaShop/PrestaShop/assets/6097524/42e8cbc4-3f12-4b7a-9022-3f61dbd8acde But on the product page combination generator, half of them are missing, all of the ones with a texture are blank. This is a regression from the old product page.  ### Expected behavior All colors should be displayed. Like on V1 product page.  ### PrestaShop version(s) where the bug happened 8.1.5

Textures are missing in combination generator

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Textures are missing in combination generator Issue date: --- start body --- ### Describe the bug and add attachments I have an attribute Color, with all values having some color or texture. See here - https://github.com/PrestaShop/PrestaShop/assets/6097524/42e8cbc4-3f12-4b7a-9022-3f61dbd8acde But on the product page combination generator, half of them are missing, all of the ones with a texture are blank. This is a regression from the old product page.  ### Expected behavior All colors should be displayed. Like on V1 product page.  ### PrestaShop version(s) where the bug happened 8.1.5 --- 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 Image Slider module is not working properly. When you try to delete the default images, the module displays a message that the photo has been successfully deleted, but the photo is not deleted. The same when it comes to uploading your own photos. Additionally, the slider does not appear on the store's website, it looks as if it was uninstalled. https://github.com/PrestaShop/PrestaShop/assets/16019289/f9db16ac-f508-4df5-9e87-48e0b7b0db20 Doesn't work on 8.0.x and 8.1.x, on develop it works fine. ### Expected behavior Add my own photo that shows on my shop. ### Steps to reproduce 1. Go to Image slider 2. Tap Configure 3. Ad Your own photo 4. The photo doesn't appear on the shop ### PrestaShop version(s) where the bug happened 8.0.x, 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_imageslider v3.1.4 ### Your company or customer's name goes here (if applicable). _No response_

ps_imageslider - Can't add/edit image in slider anymore

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_imageslider - Can't add/edit image in slider 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 PrestaShop Image Slider module is not working properly. When you try to delete the default images, the module displays a message that the photo has been successfully deleted, but the photo is not deleted. The same when it comes to uploading your own photos. Additionally, the slider does not appear on the store's website, it looks as if it was uninstalled. https://github.com/PrestaShop/PrestaShop/assets/16019289/f9db16ac-f508-4df5-9e87-48e0b7b0db20 Doesn't work on 8.0.x and 8.1.x, on develop it works fine. ### Expected behavior Add my own photo that shows on my shop. ### Steps to reproduce 1. Go to Image slider 2. Tap Configure 3. Ad Your own photo 4. The photo doesn't appear on the shop ### PrestaShop version(s) where the bug happened 8.0.x, 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_imageslider v3.1.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 Enable/Disable button doesn't work properly in slides list in ps_imageslider. Example you click to disable first slide:  After the the button shows what the slide is disabled:  Then you click to disable the second slide:  Result: The second slide's button shows what the second slide disabled **BUT the first slide is enabled now. Although the first slide was disabled before:**  Also the button doesn't actually change the status of the slide. Example, click to disable first slide:  After the the button shows what the slide is disabled:  Then go to first slide's settings:  And you see what the first slide is not disabled actually:  It turns out that the “on/off” button doesn’t actually turn off the slide at all, it’s just decoration. Also i recorded the video with bugs: https://github.com/PrestaShop/PrestaShop/assets/22581200/47c47097-42a1-488a-869e-7408c94c55a8 ### Expected behavior when you click to "enable/disable" slide button in slides list the slide will be disabled in slide's settings too:   Also if you disable first slide and then disable second slide the first slide must not be enabled. ### Steps to reproduce 1. Go to the "Image slider" settings. 2. Try to disable first slide, then disable second slide, then disable third slide. 3. Also go to the slide settings after disable to see wrong stutus. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.25 ### If your bug is related to a module, specify its name and its version ps_imageslider v3.1.4 ### Your company or customer's name goes here (if applicable). _No response_

Enable/Disable button doesn't work properly in slides list in ps_imageslider

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Enable/Disable button doesn't work properly in slides list in ps_imageslider 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 Enable/Disable button doesn't work properly in slides list in ps_imageslider. Example you click to disable first slide:  After the the button shows what the slide is disabled:  Then you click to disable the second slide:  Result: The second slide's button shows what the second slide disabled **BUT the first slide is enabled now. Although the first slide was disabled before:**  Also the button doesn't actually change the status of the slide. Example, click to disable first slide:  After the the button shows what the slide is disabled:  Then go to first slide's settings:  And you see what the first slide is not disabled actually:  It turns out that the “on/off” button doesn’t actually turn off the slide at all, it’s just decoration. Also i recorded the video with bugs: https://github.com/PrestaShop/PrestaShop/assets/22581200/47c47097-42a1-488a-869e-7408c94c55a8 ### Expected behavior when you click to "enable/disable" slide button in slides list the slide will be disabled in slide's settings too:   Also if you disable first slide and then disable second slide the first slide must not be enabled. ### Steps to reproduce 1. Go to the "Image slider" settings. 2. Try to disable first slide, then disable second slide, then disable third slide. 3. Also go to the slide settings after disable to see wrong stutus. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1.25 ### If your bug is related to a module, specify its name and its version ps_imageslider v3.1.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 Hello, module ps_emailalerts generate TXT email templates with HTML code. ### Expected behavior _No response_ ### Steps to reproduce 1. install and setup ps_emailalerts module 2. set text email notifications only in the Emails part of PS BO 3. make an order 4. check received email about a new order 5. notification email about a new order included HTML code - see following screenshot  ### PrestaShop version(s) where the bug happened 8.1.4 ### 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 3.0.0 ### Your company or customer's name goes here (if applicable). _No response_

ps_emailalerts module: text email templates render HTML

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_emailalerts module: text email templates render HTML 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, module ps_emailalerts generate TXT email templates with HTML code. ### Expected behavior _No response_ ### Steps to reproduce 1. install and setup ps_emailalerts module 2. set text email notifications only in the Emails part of PS BO 3. make an order 4. check received email about a new order 5. notification email about a new order included HTML code - see following screenshot  ### PrestaShop version(s) where the bug happened 8.1.4 ### 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 3.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 Cumulative coupons use the base price but not the discounted price. ### Expected behavior I have two 10% discount coupons and the PrestaShop calculation is : First coupon = 100-10% = 10€ Second Coupon = 100-10% = 10€ The total of the cart is 80€ Expected behavior First coupon = 100-10% = 10€ Second Coupon = 90-10% = 9€ The total of the cart is 81€ ### Steps to reproduce Description above ### PrestaShop version(s) where the bug happened 1.7.8 8.1 ### 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). Friend Of Presta

Cumulative coupons use the base price but not the discounted price.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Cumulative coupons use the base price but not the discounted price. 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 Cumulative coupons use the base price but not the discounted price. ### Expected behavior I have two 10% discount coupons and the PrestaShop calculation is : First coupon = 100-10% = 10€ Second Coupon = 100-10% = 10€ The total of the cart is 80€ Expected behavior First coupon = 100-10% = 10€ Second Coupon = 90-10% = 9€ The total of the cart is 81€ ### Steps to reproduce Description above ### PrestaShop version(s) where the bug happened 1.7.8 8.1 ### 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). Friend Of Presta --- 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 problem as noteed before seems to be back in Prestashop 8.1.5. Not sure if it is the same problem or a new created problem., https://github.com/PrestaShop/PrestaShop/issues/30716 We've updated 5 stores to 8.1.5 this morning and all of them have this translation problem again. The translations are correct in the backoffice, but not in the frontoffice (Warehouse theme).     ### Expected behavior The right translations should be visible. ### Steps to reproduce Install a non classic theme, preferred Warehouse and translate "View" of "Follow us" and you;ll see that the translations are not working. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1 and 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_

Translation for child theme does not work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Translation for child theme does not work 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 problem as noteed before seems to be back in Prestashop 8.1.5. Not sure if it is the same problem or a new created problem., https://github.com/PrestaShop/PrestaShop/issues/30716 We've updated 5 stores to 8.1.5 this morning and all of them have this translation problem again. The translations are correct in the backoffice, but not in the frontoffice (Warehouse theme).     ### Expected behavior The right translations should be visible. ### Steps to reproduce Install a non classic theme, preferred Warehouse and translate "View" of "Follow us" and you;ll see that the translations are not working. ### PrestaShop version(s) where the bug happened 8.1.5 ### PHP version(s) where the bug happened 8.1 and 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 State select is missing in Your account when we update existing address for country with states.  ### Expected behavior State select should be presented in Your account when we update existing address for country with states.  ### Steps to reproduce 1. Front office, default theme (https://demo.prestashop.com/#/en/front) 2. Go to Your account 3. Go to Addresses 4. Create new address (or use existing one) 5. Fill the required fields and select United States in Country select 6. Click Save button 7. Click Update on existing address with United States 8. Try to find State select box - it missing 9. Change Country to France 10. Change Country back to United States - State select box appears ### PrestaShop version(s) where the bug happened 8.1.0, 8.1.4 ### PHP version(s) where the bug happened 8.1.19, 7.4.20 ### 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 State select on Update address in Your account

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Missing State select on Update address in Your account 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 State select is missing in Your account when we update existing address for country with states.  ### Expected behavior State select should be presented in Your account when we update existing address for country with states.  ### Steps to reproduce 1. Front office, default theme (https://demo.prestashop.com/#/en/front) 2. Go to Your account 3. Go to Addresses 4. Create new address (or use existing one) 5. Fill the required fields and select United States in Country select 6. Click Save button 7. Click Update on existing address with United States 8. Try to find State select box - it missing 9. Change Country to France 10. Change Country back to United States - State select box appears ### PrestaShop version(s) where the bug happened 8.1.0, 8.1.4 ### PHP version(s) where the bug happened 8.1.19, 7.4.20 ### 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, the past few days we noticed on prestashop 1.7.8.9 that we receive orders which are missing an item that exists in the cart for example this order  You can see it has 10 items However the totals do not match. That's why we contacted the customer and he told us he added 11 items not 10. Then we went back to the DB and found that he indeed had 11 products associated with the cart_id that is connected to his order ``` +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ |id_cart|id_product|id_address_delivery|id_shop|id_product_attribute|id_customization|quantity|date_add | +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ |483546 |2436 |3207 |1 |17669 |0 |4 |2024-03-13 16:02:54| |483546 |2436 |3207 |1 |17677 |0 |8 |2024-03-13 16:02:54| |483546 |2436 |3207 |1 |17685 |0 |4 |2024-03-13 16:02:54| |483546 |6000 |3207 |1 |30934 |0 |8 |2024-03-13 16:01:42| |483546 |6006 |3207 |1 |31171 |0 |12 |2024-03-19 13:53:21| |483546 |6006 |3207 |1 |31172 |0 |5 |2024-03-19 11:40:02| |483546 |6006 |3207 |1 |35442 |0 |10 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35444 |0 |7 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35446 |0 |2 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35448 |0 |3 |2024-03-19 13:53:21| |483546 |6006 |3207 |1 |46157 |0 |5 |2024-02-27 14:15:57| +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ ``` ### Expected behavior Order items are equal to the cart items and the totals match ### Steps to reproduce I'm afraid we couldn't find the exact steps to replicate that's why we need your assistance to investigate potential culprits. ### 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). IOWEB TECHNOLOGIES P.C.

Orders are persisted with the cart totals but the items are less than the cart's items

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Orders are persisted with the cart totals but the items are less than the cart's items 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, the past few days we noticed on prestashop 1.7.8.9 that we receive orders which are missing an item that exists in the cart for example this order  You can see it has 10 items However the totals do not match. That's why we contacted the customer and he told us he added 11 items not 10. Then we went back to the DB and found that he indeed had 11 products associated with the cart_id that is connected to his order ``` +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ |id_cart|id_product|id_address_delivery|id_shop|id_product_attribute|id_customization|quantity|date_add | +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ |483546 |2436 |3207 |1 |17669 |0 |4 |2024-03-13 16:02:54| |483546 |2436 |3207 |1 |17677 |0 |8 |2024-03-13 16:02:54| |483546 |2436 |3207 |1 |17685 |0 |4 |2024-03-13 16:02:54| |483546 |6000 |3207 |1 |30934 |0 |8 |2024-03-13 16:01:42| |483546 |6006 |3207 |1 |31171 |0 |12 |2024-03-19 13:53:21| |483546 |6006 |3207 |1 |31172 |0 |5 |2024-03-19 11:40:02| |483546 |6006 |3207 |1 |35442 |0 |10 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35444 |0 |7 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35446 |0 |2 |2024-02-27 14:15:56| |483546 |6006 |3207 |1 |35448 |0 |3 |2024-03-19 13:53:21| |483546 |6006 |3207 |1 |46157 |0 |5 |2024-02-27 14:15:57| +-------+----------+-------------------+-------+--------------------+----------------+--------+-------------------+ ``` ### Expected behavior Order items are equal to the cart items and the totals match ### Steps to reproduce I'm afraid we couldn't find the exact steps to replicate that's why we need your assistance to investigate potential culprits. ### 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). IOWEB TECHNOLOGIES P.C. --- 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 the cart the label for the total always includes tax even if the price is shown without tax. The Tax is depending on the destination country.  ### Expected behavior The label for the total should be without tax when the prices is without tax ### Steps to reproduce Put something in the cart Add a address with a destination without Tax Check the prices are without tax ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2.14 ### If your bug is related to a module, specify its name and its version everything is latest version ### Your company or customer's name goes here (if applicable). KOK MC ApS

Total label in cart always displayed including tax even when the total is not including tax

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Total label in cart always displayed including tax even when the total is not including tax 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 the cart the label for the total always includes tax even if the price is shown without tax. The Tax is depending on the destination country.  ### Expected behavior The label for the total should be without tax when the prices is without tax ### Steps to reproduce Put something in the cart Add a address with a destination without Tax Check the prices are without tax ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2.14 ### If your bug is related to a module, specify its name and its version everything is latest version ### Your company or customer's name goes here (if applicable). KOK MC ApS --- end body --- comments : --- start comments --- --- end comments ---

### Issue Some migrated pages expected shopids association even tho the context is in single shops. Command impacted -> 14 Add Edition (6) Category & Attributes & CMS & Feature domain - endpoints: AddCustomerGroupCommand ### Solution The default shop is automatically assigned to the ShopsID list in single shops. See how we can adapt the doc swagger that will expect a list in single shops ```php protected function getContextParameters(): array { $shopConstraint = $this->shopContext->getShopConstraint(); return [ '_context' => [ 'shopConstraint' => [ 'shopId' => $shopConstraint->getShopId()?->getValue(), 'shopGroupId' => $shopConstraint->getShopGroupId()?->getValue(), 'isStrict' => $shopConstraint->isStrict(), ], 'shopId' => $this->shopContext->getId(), 'shopIds' => $this->shopContext->getAssociatedShopIds(), 'langId' => $this->languageContext->getId(), 'apiClientId' => $this->apiClientContext->getApiClient()?->getId(), ], ]; } ``` ```php CQRSCommandMapping: [ '[_context][shopIds]' => '[shopIds]', '[groupId]' => '[customerGroupId]', ], ```

Command on single shops that expects shopids

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Command on single shops that expects shopids Issue date: --- start body --- ### Issue Some migrated pages expected shopids association even tho the context is in single shops. Command impacted -> 14 Add Edition (6) Category & Attributes & CMS & Feature domain - endpoints: AddCustomerGroupCommand ### Solution The default shop is automatically assigned to the ShopsID list in single shops. See how we can adapt the doc swagger that will expect a list in single shops ```php protected function getContextParameters(): array { $shopConstraint = $this->shopContext->getShopConstraint(); return [ '_context' => [ 'shopConstraint' => [ 'shopId' => $shopConstraint->getShopId()?->getValue(), 'shopGroupId' => $shopConstraint->getShopGroupId()?->getValue(), 'isStrict' => $shopConstraint->isStrict(), ], 'shopId' => $this->shopContext->getId(), 'shopIds' => $this->shopContext->getAssociatedShopIds(), 'langId' => $this->languageContext->getId(), 'apiClientId' => $this->apiClientContext->getApiClient()?->getId(), ], ]; } ``` ```php CQRSCommandMapping: [ '[_context][shopIds]' => '[shopIds]', '[groupId]' => '[customerGroupId]', ], ``` --- end body --- comments : --- start comments --- --- end comments ---

### Issue The initial listing implemented by @tleon in https://github.com/PrestaShop/PrestaShop/pull/35630 is based on the QueryBuilder interface services that perform SQL queries and return raw data from the DB For 90% of our grids, and so four the listing API, this is enough BUT we have some special cases where the SQL data alone is not enough and is enriched by a GridDataFactory decorator Example for the product list https://github.com/PrestaShop/PrestaShop/blob/3ec94d7692a5fa7bcec180afedad86be3c14c1af/src/Adapter/Product/Grid/Data/Factory/ProductGridDataFactoryDecorator.php#L185 In this case the decorator computes the price tax included, handles the ecotax, adds the image URL, ... So our listing implementation should probably handle two use cases: - based on a query builder - based on a grid data factory Unless we decide that it should ALWAYS be based on a grid data factory which would not be more complex than the current solution we just need to target a different service, maybe this way it's less confusing because we always rely on grid data factory instead of query builders The drawback is that for new/independent listing endpoint we'll have to create/define two services (the grid data factory + the query builder) although most of the time it's just adding a service definition in yaml And as long as we use the same as the ones in migrated pages they are already available anyway ### Solution Be based on a grid data factory

Make the API based on the grid data instead of the query builder

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Make the API based on the grid data instead of the query builder Issue date: --- start body --- ### Issue The initial listing implemented by @tleon in https://github.com/PrestaShop/PrestaShop/pull/35630 is based on the QueryBuilder interface services that perform SQL queries and return raw data from the DB For 90% of our grids, and so four the listing API, this is enough BUT we have some special cases where the SQL data alone is not enough and is enriched by a GridDataFactory decorator Example for the product list https://github.com/PrestaShop/PrestaShop/blob/3ec94d7692a5fa7bcec180afedad86be3c14c1af/src/Adapter/Product/Grid/Data/Factory/ProductGridDataFactoryDecorator.php#L185 In this case the decorator computes the price tax included, handles the ecotax, adds the image URL, ... So our listing implementation should probably handle two use cases: - based on a query builder - based on a grid data factory Unless we decide that it should ALWAYS be based on a grid data factory which would not be more complex than the current solution we just need to target a different service, maybe this way it's less confusing because we always rely on grid data factory instead of query builders The drawback is that for new/independent listing endpoint we'll have to create/define two services (the grid data factory + the query builder) although most of the time it's just adding a service definition in yaml And as long as we use the same as the ones in migrated pages they are already available anyway ### Solution Be based on a grid data factory --- end body --- comments : --- start comments --- --- end comments ---

### Issue Some of the integration will require external authentification serveur ### Steps to make it work 1. Run Keycloak module (external auth server) 2. To be able to run Keycloak and native PrestaShop in parallel 3. Persist with an external API id client 4. Display the auth server in the list and see how to adapt the form. 5. Validate UI tests

Make keycloak great again !

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Make keycloak great again ! Issue date: --- start body --- ### Issue Some of the integration will require external authentification serveur ### Steps to make it work 1. Run Keycloak module (external auth server) 2. To be able to run Keycloak and native PrestaShop in parallel 3. Persist with an external API id client 4. Display the auth server in the list and see how to adapt the form. 5. Validate UI tests --- end body --- comments : --- start comments --- --- end comments ---

### Issue For an endpoint to be considered fully completed, it needs to be tested, documented, and accessible in the interface. The issue arises when some endpoints are still a work in progress during a release, causing delays in development. Committers are then required to either complete the pending work or backport it. ### Solutions To streamline the development and contribution process, it would be beneficial to hide the experimental/work-in-progress endpoints. ### Specs Implement a feature flag for endpoints; when an endpoint is marked as experimental, If the feature flag is disabled, the experimental endpoints will not be accessible. Endpoints won't be display on the doc swagger If all the endpoints from one scope are experimental, then hide the scope on the API Client form ### Acceptance test When an endpoint is marked as experimental... ### Technical solution Add a parameter on our CQRS operations: ```php #[ApiResource( operations: [ new CQRSUpdate( uriTemplate: '/cart-rule', CQRSCommand: EditCartRuleCommand::class, // This is optional and false by default experimental: true, ), ], )] ``` When the experimental config is true endpoint is not visible in prod nor in dev Add a feature flag `Show hidden API endpoints` to ignore this config, then the endpoints become visible in both prod and dev Scopes that are assigned ONLY to experimental endpoints should be filtered out To implement this feature we need to override/decorate the scanning mechanism of ApiPlatform and filter some operations (hint look into the `ResourceMetadataCollectionFactoryInterface` that was already decorated) Hint: Look into this old decorator https://github.com/PrestaShop/PrestaShop/blob/b2dbfdeddff99112b68d0744606fe87d1f6d670c/src/PrestaShopBundle/ApiPlatform/Metadata/ScopesToSecurityMetadataCollectionFactoryDecorator.php The principle should be similar but instead of adding some extra properties we remove the operation from the collection

Hide Endpoint on the endpoint list when the endpoint is not fully finished

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Hide Endpoint on the endpoint list when the endpoint is not fully finished Issue date: --- start body --- ### Issue For an endpoint to be considered fully completed, it needs to be tested, documented, and accessible in the interface. The issue arises when some endpoints are still a work in progress during a release, causing delays in development. Committers are then required to either complete the pending work or backport it. ### Solutions To streamline the development and contribution process, it would be beneficial to hide the experimental/work-in-progress endpoints. ### Specs Implement a feature flag for endpoints; when an endpoint is marked as experimental, If the feature flag is disabled, the experimental endpoints will not be accessible. Endpoints won't be display on the doc swagger If all the endpoints from one scope are experimental, then hide the scope on the API Client form ### Acceptance test When an endpoint is marked as experimental... ### Technical solution Add a parameter on our CQRS operations: ```php #[ApiResource( operations: [ new CQRSUpdate( uriTemplate: '/cart-rule', CQRSCommand: EditCartRuleCommand::class, // This is optional and false by default experimental: true, ), ], )] ``` When the experimental config is true endpoint is not visible in prod nor in dev Add a feature flag `Show hidden API endpoints` to ignore this config, then the endpoints become visible in both prod and dev Scopes that are assigned ONLY to experimental endpoints should be filtered out To implement this feature we need to override/decorate the scanning mechanism of ApiPlatform and filter some operations (hint look into the `ResourceMetadataCollectionFactoryInterface` that was already decorated) Hint: Look into this old decorator https://github.com/PrestaShop/PrestaShop/blob/b2dbfdeddff99112b68d0744606fe87d1f6d670c/src/PrestaShopBundle/ApiPlatform/Metadata/ScopesToSecurityMetadataCollectionFactoryDecorator.php The principle should be similar but instead of adding some extra properties we remove the operation from the collection --- 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 selected Venipak courier, it shows all the payment methods: Pay when picked up in store, Bank transfer, Paysera payment. The Venipak Pickup point courier works normally, shows Bank transfer and Paysera payment. For some reason it only affects Pickup Point courier. Venipak courier payment methods:  Venipak pickup point payment methods:  ### Expected behavior It should only show Bank transfer and Paysera payment methods like the Venipak Pickup Point courier. ### Steps to reproduce 1. Select desired products 2. Go to shopping cart to pay for them 3. Select Venipak courier 4. See all 3 Payment methods ### PrestaShop version(s) where the bug happened 1.7.8.6 ### PHP version(s) where the bug happened 8.0.28 ### If your bug is related to a module, specify its name and its version venipakcarrier v1.0.3 ### Your company or customer's name goes here (if applicable). _No response_

Venipak Carrier shows all payment methods

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Venipak Carrier shows all payment methods 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 selected Venipak courier, it shows all the payment methods: Pay when picked up in store, Bank transfer, Paysera payment. The Venipak Pickup point courier works normally, shows Bank transfer and Paysera payment. For some reason it only affects Pickup Point courier. Venipak courier payment methods:  Venipak pickup point payment methods:  ### Expected behavior It should only show Bank transfer and Paysera payment methods like the Venipak Pickup Point courier. ### Steps to reproduce 1. Select desired products 2. Go to shopping cart to pay for them 3. Select Venipak courier 4. See all 3 Payment methods ### PrestaShop version(s) where the bug happened 1.7.8.6 ### PHP version(s) where the bug happened 8.0.28 ### If your bug is related to a module, specify its name and its version venipakcarrier v1.0.3 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments All tinymce fields on product page get randomly broken after some time of inactivity, or going to another tab and doing some actions. Sometimes they break completely, sometimes they work, sometimes they shrink to some min size. You have to type inside to make them work again. https://github.com/PrestaShop/PrestaShop/assets/6097524/65a6be73-6bd6-4552-9e77-12c984adbad5 ### Expected behavior It should work properly. ### Steps to reproduce See video in issue description. ### PrestaShop version(s) where the bug happened 8.1.5

Textarea fields randomly broken on product page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Textarea fields randomly broken on product page Issue date: --- start body --- ### Describe the bug and add attachments All tinymce fields on product page get randomly broken after some time of inactivity, or going to another tab and doing some actions. Sometimes they break completely, sometimes they work, sometimes they shrink to some min size. You have to type inside to make them work again. https://github.com/PrestaShop/PrestaShop/assets/6097524/65a6be73-6bd6-4552-9e77-12c984adbad5 ### Expected behavior It should work properly. ### Steps to reproduce See video in issue description. ### PrestaShop version(s) where the bug happened 8.1.5 --- 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 Faceted Search module filters the price based on the base sales price instead of the action (specific) price. So for example, if you sell a bike for 1899 with a discount of 400, so the actual price will be 1499, the Faceted Search won't show this product in the list when you set the maximum price on, for example, 1600. ### Expected behavior The Faceted Search should have the abillity to filter the list based on the action price of the product. ### Steps to reproduce Don't need reproduction steps, it's quite clear. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_facetedsearch 3.15.1 ### Your company or customer's name goes here (if applicable). _No response_

Faceted Search price filter not based on action prices

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Faceted Search price filter not based on action prices 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 Faceted Search module filters the price based on the base sales price instead of the action (specific) price. So for example, if you sell a bike for 1899 with a discount of 400, so the actual price will be 1499, the Faceted Search won't show this product in the list when you set the maximum price on, for example, 1600. ### Expected behavior The Faceted Search should have the abillity to filter the list based on the action price of the product. ### Steps to reproduce Don't need reproduction steps, it's quite clear. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_facetedsearch 3.15.1 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments After upgrade to 8.1.5, some strings cannot be translated at all. For example, a translation of a custom theme string - `Your password must be at least %min% characters long.` You save it, you get green alert, but nothing gets saved.  ### Expected behavior All strings should be saved, or some error thrown. ### Steps to reproduce 1. Install any custom theme, hummingbird for example. 2. Make sure that there is `{l s='Your blabla password must be at least %min% characters long.' d='Shop.Forms.Help' sprintf=['%min%' => 5]}` in any tpl file. 3. Go to Translations > Front office > Hummingbird, try to translate it. ### PrestaShop version(s) where the bug happened 8.1.5

Certain strings can't be translated at all

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Certain strings can't be translated at all Issue date: --- start body --- ### Describe the bug and add attachments After upgrade to 8.1.5, some strings cannot be translated at all. For example, a translation of a custom theme string - `Your password must be at least %min% characters long.` You save it, you get green alert, but nothing gets saved.  ### Expected behavior All strings should be saved, or some error thrown. ### Steps to reproduce 1. Install any custom theme, hummingbird for example. 2. Make sure that there is `{l s='Your blabla password must be at least %min% characters long.' d='Shop.Forms.Help' sprintf=['%min%' => 5]}` in any tpl file. 3. Go to Translations > Front office > Hummingbird, try to translate it. ### PrestaShop version(s) where the bug happened 8.1.5 --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments Translations in backoffice are displaying error page "security compromised". ### Expected behavior No error should be displayed. ### Steps to reproduce 1. Install 8.1.5. I upgraded from 1.7.6. 2. Go to Translations. 3. Select anything - backoffice for example. 4. Click translate. 5. Error page - security compromised. ### PrestaShop version(s) where the bug happened 8.1.5

Translations throwing invalid token all the time

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Translations throwing invalid token all the time Issue date: --- start body --- ### Describe the bug and add attachments Translations in backoffice are displaying error page "security compromised". ### Expected behavior No error should be displayed. ### Steps to reproduce 1. Install 8.1.5. I upgraded from 1.7.6. 2. Go to Translations. 3. Select anything - backoffice for example. 4. Click translate. 5. Error page - security compromised. ### PrestaShop version(s) where the bug happened 8.1.5 --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments SEO preview on product page shows the short description including html tags, which are not in the final result. ### Expected behavior SEO preview should be stripped of html tags. ### Steps to reproduce 1. Open any product in new product page. 2. Make sure there is a summary. 3. Go to SEO tab, see the preview displays html tags, which are not there in front office.  ### PrestaShop version(s) where the bug happened 8.1.5

SEO preview displays HTML tags, which are not in the final description

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : SEO preview displays HTML tags, which are not in the final description Issue date: --- start body --- ### Describe the bug and add attachments SEO preview on product page shows the short description including html tags, which are not in the final result. ### Expected behavior SEO preview should be stripped of html tags. ### Steps to reproduce 1. Open any product in new product page. 2. Make sure there is a summary. 3. Go to SEO tab, see the preview displays html tags, which are not there in front office.  ### PrestaShop version(s) where the bug happened 8.1.5 --- 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 ``` version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: ``` This is the initial container configuration of the docker-compose.yml file in the root directory of the website in the D:\dockerpro\prestashop root directory of my window host, and I have already successfully installed the prestashop website by executing docker compose up from that directory with the terminal tool. I can now access the frontend and backend of prestashop successfully. Then I added the following parameters for the MySQL persistent bindings volume: ``` ... mysql: container_name: some-mysql volumes: - dbdata:/var/lib/mysql ... volumes: dbdata: ``` **The final configuration is as follows: (mainly for mysql container persistence)：** ``` version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop volumes: - dbdata:/var/lib/mysql networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: volumes: dbdata: ``` In order to make the docker-compose.yml configuration file take effect, I executed the following commands one after the other: docker compose down //Stop and delete existing containers docker compose up -d //Start the container using the updated docker-compose.yml file Then, **I visit http://localhost:8080/ again and the site goes to the installation screen again.** **Question 1:** Can the official prestashop guys, please help me to see, what is the cause of this? **Question 2:** Is there any error in the procedure I have stated above? **Question 3**: Prestashop officials, after you make changes to the docker-compose.yml file, what actions do you usually perform to make the container configuration file take effect? ### Expected behavior Whenever I update the docker-compose.yml file, instead of prompting me to reinstall, the site allows me to access the frontend and backend of the site normally. ### Steps to reproduce **1.** In the D:\dockerpro\prestashop directory, create a docker-compose.yml manifest. version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: **2.In the D:\dockerpro\prestashop directory, through the terminal, execute docker compose up. According to the prompts successfully installed prestashop** **3. Bind a volume for MySQL persisting, Added the following code：** ... mysql: container_name: some-mysql volumes: - dbdata:/var/lib/mysql ... volumes: dbdata: **4. Run the following commands：** docker-compose down docker-compose up -d When finished executing these two commands, the home page (http://localhost:8080/zh/) of the prestashop website that has just been installed will not open, and the page automatically jumps to the very beginning of the installation interface. ### PrestaShop version(s) where the bug happened See the docker configuration file ### PHP version(s) where the bug happened See the docker configuration file ### If your bug is related to a module, specify its name and its version no ### Your company or customer's name goes here (if applicable). _No response_

#After adding a volume for mysql persistence and executing the rebuild container command, going to the home page of the site again takes me to the installation page again, why?

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : #After adding a volume for mysql persistence and executing the rebuild container command, going to the home page of the site again takes me to the installation page again, why? 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 ``` version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: ``` This is the initial container configuration of the docker-compose.yml file in the root directory of the website in the D:\dockerpro\prestashop root directory of my window host, and I have already successfully installed the prestashop website by executing docker compose up from that directory with the terminal tool. I can now access the frontend and backend of prestashop successfully. Then I added the following parameters for the MySQL persistent bindings volume: ``` ... mysql: container_name: some-mysql volumes: - dbdata:/var/lib/mysql ... volumes: dbdata: ``` **The final configuration is as follows: (mainly for mysql container persistence)：** ``` version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop volumes: - dbdata:/var/lib/mysql networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: volumes: dbdata: ``` In order to make the docker-compose.yml configuration file take effect, I executed the following commands one after the other: docker compose down //Stop and delete existing containers docker compose up -d //Start the container using the updated docker-compose.yml file Then, **I visit http://localhost:8080/ again and the site goes to the installation screen again.** **Question 1:** Can the official prestashop guys, please help me to see, what is the cause of this? **Question 2:** Is there any error in the procedure I have stated above? **Question 3**: Prestashop officials, after you make changes to the docker-compose.yml file, what actions do you usually perform to make the container configuration file take effect? ### Expected behavior Whenever I update the docker-compose.yml file, instead of prompting me to reinstall, the site allows me to access the frontend and backend of the site normally. ### Steps to reproduce **1.** In the D:\dockerpro\prestashop directory, create a docker-compose.yml manifest. version: '3' services: mysql: container_name: some-mysql image: mysql:5.7 restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: admin MYSQL_DATABASE: prestashop networks: - prestashop_network prestashop: container_name: prestashop image: prestashop/prestashop:latest restart: unless-stopped depends_on: - mysql ports: - 8080:80 environment: DB_SERVER: some-mysql DB_NAME: prestashop DB_USER: root DB_PASSWD: admin PS_DOMAIN: localhost:8080 networks: - prestashop_network networks: prestashop_network: **2.In the D:\dockerpro\prestashop directory, through the terminal, execute docker compose up. According to the prompts successfully installed prestashop** **3. Bind a volume for MySQL persisting, Added the following code：** ... mysql: container_name: some-mysql volumes: - dbdata:/var/lib/mysql ... volumes: dbdata: **4. Run the following commands：** docker-compose down docker-compose up -d When finished executing these two commands, the home page (http://localhost:8080/zh/) of the prestashop website that has just been installed will not open, and the page automatically jumps to the very beginning of the installation interface. ### PrestaShop version(s) where the bug happened See the docker configuration file ### PHP version(s) where the bug happened See the docker configuration file ### If your bug is related to a module, specify its name and its version no ### 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 If you add a carrier and add second range for shipping and save it, it is impossible to edit this carrier. When you go to editing carrier, it stops on the first step "General settings" and the "Next" button is not active, and when you try to click next step "Shipping locations and costs" it stays on the first step showing error "Ranges are overlapping" at the same time not allowing you to change those overlapping ranges.  ### Expected behavior It should let me press the button "Next" to edit the "Shipping locations and costs". ### Steps to reproduce 1. Go to Shipping > Carriers > Add New Carrier 2. Add name, and transit time and go to next step "Shipipng locations and costs". 3. Set "billing" to weight. 4. In the field "will be applied when the weight is <" type 10000 5. Select one of the areas (eg. Europe) and type 20 6. Click the button "Add new range" (it should automatically put 10000 in the "Will be applied when the weight is >=" field of the new range). 7. Click "Finish" 8. On the list of carriers click on the newly created carrier (to edit it). 9. Go to the second tab "Shipping locations and costs" - it is impossible, prestashop doesn't allow you to fix the error it displays "Ranges are overlapping". ### PrestaShop version(s) where the bug happened 1.7.8.6 ### PHP version(s) where the bug happened 8.0.28 ### If your bug is related to a module, specify its name and its version venipakcarrier v1.0.3 ### Your company or customer's name goes here (if applicable). _No response_

Can't edit carrier if the ranges are overlapping.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Can't edit carrier if the ranges are overlapping. 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 If you add a carrier and add second range for shipping and save it, it is impossible to edit this carrier. When you go to editing carrier, it stops on the first step "General settings" and the "Next" button is not active, and when you try to click next step "Shipping locations and costs" it stays on the first step showing error "Ranges are overlapping" at the same time not allowing you to change those overlapping ranges.  ### Expected behavior It should let me press the button "Next" to edit the "Shipping locations and costs". ### Steps to reproduce 1. Go to Shipping > Carriers > Add New Carrier 2. Add name, and transit time and go to next step "Shipipng locations and costs". 3. Set "billing" to weight. 4. In the field "will be applied when the weight is <" type 10000 5. Select one of the areas (eg. Europe) and type 20 6. Click the button "Add new range" (it should automatically put 10000 in the "Will be applied when the weight is >=" field of the new range). 7. Click "Finish" 8. On the list of carriers click on the newly created carrier (to edit it). 9. Go to the second tab "Shipping locations and costs" - it is impossible, prestashop doesn't allow you to fix the error it displays "Ranges are overlapping". ### PrestaShop version(s) where the bug happened 1.7.8.6 ### PHP version(s) where the bug happened 8.0.28 ### If your bug is related to a module, specify its name and its version venipakcarrier v1.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 Since https://github.com/PrestaShop/PrestaShop/pull/26239 there's no information about new version available on admin dashboard. Removed section was hijacked by https://github.com/PrestaShopCorp/ps_mbo which now only serves blog news and addons connect feature. No info about new version ☹️ ### Expected behavior PS 1.7:  ### Steps to reproduce Install the shop (any version from range 8.0.0 - 8.1.3) and check if you have info about version 8.1.4 available anywhere. ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version https://github.com/PrestaShopCorp/ps_mbo ### Your company or customer's name goes here (if applicable). _No response_

No info about new version available since PS 8.0.0

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : No info about new version available since PS 8.0.0 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 https://github.com/PrestaShop/PrestaShop/pull/26239 there's no information about new version available on admin dashboard. Removed section was hijacked by https://github.com/PrestaShopCorp/ps_mbo which now only serves blog news and addons connect feature. No info about new version ☹️ ### Expected behavior PS 1.7:  ### Steps to reproduce Install the shop (any version from range 8.0.0 - 8.1.3) and check if you have info about version 8.1.4 available anywhere. ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version https://github.com/PrestaShopCorp/ps_mbo ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

## Issue Example: Module actions that depend on ModuleManager and more specifically https://github.com/PrestaShop/PrestaShop/blob/efb6aa7a6492d6533ecdbaa4a9477135a52eb973/src/Adapter/Module/AdminModuleDataProvider.php#L170 The check is only performed on a logged in employee, we need to allow checking access based on an API client as well, this implies thinking about what scope we'd use, do we introduce core scopes manually? Do we think of a way to convert legacy permissions into scopes? We need to search in the core what other part are similar to this and could be blocked so we anticipate the solution before v9 release. Employe::can  Also check `Profile::getProfileAccesses` and `Profile::getProfileAccess` ## Investigation - List endpoints impacted (17 endpoints) - Can we find a generic solution ? POC

Some core services have internal manual check of permission, this is not compatible with the API at all

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Some core services have internal manual check of permission, this is not compatible with the API at all Issue date: --- start body --- ## Issue Example: Module actions that depend on ModuleManager and more specifically https://github.com/PrestaShop/PrestaShop/blob/efb6aa7a6492d6533ecdbaa4a9477135a52eb973/src/Adapter/Module/AdminModuleDataProvider.php#L170 The check is only performed on a logged in employee, we need to allow checking access based on an API client as well, this implies thinking about what scope we'd use, do we introduce core scopes manually? Do we think of a way to convert legacy permissions into scopes? We need to search in the core what other part are similar to this and could be blocked so we anticipate the solution before v9 release. Employe::can  Also check `Profile::getProfileAccesses` and `Profile::getProfileAccess` ## Investigation - List endpoints impacted (17 endpoints) - Can we find a generic solution ? POC --- end body --- comments : --- start comments --- --- end comments ---

### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/35609 <div type='discussions-op-text'> ^{Originally posted by **Angar90** March 11, 2024} ### 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 Go to the "Module Manager" tab and disable one module. After that the "Configure" button should be changed to "Enable", but Prestashop still displays the "Configure" button. ### Expected behavior The "Configure" button should be changed to "Enable" like in the PrestaShop 1.7 Without this option is it hard to find which modules are disabled in the backoffice. ### Steps to reproduce 1.Go to the "Module Manager" tab. 2.Disable one module, for example the "Cross-selling" module: https://prnt.sc/X4wVZC-uaLbq 3.After that the "Configure" text should be changed to "Enable" (in PrestaShop 1.7 it works correctly), but it still shows the text "Configure". Screenshot from PrestaShop 8.1.4: https://prnt.sc/xcrm_Bf--998 Screenshot from PrestaShop 1.7.8: https://prnt.sc/QvuUMH3fKizV Without this option is it hard to find which modules are disabled in the backoffice. I have this problem in all PrestaShop 8.x versions. Also, sometimes I have a similar problem with the module's upgrade, after the upgrade, the old version number of the module is still displayed in the backoffice. ### PrestaShop version(s) where the bug happened 8.1.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). _No response_</div>

PrestaShop 8.1.4 - Problem with the "disabled" modules on the "Module Manager" page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop 8.1.4 - Problem with the "disabled" modules on the "Module Manager" page Issue date: --- start body --- ### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/35609 <div type='discussions-op-text'> ^{Originally posted by **Angar90** March 11, 2024} ### 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 Go to the "Module Manager" tab and disable one module. After that the "Configure" button should be changed to "Enable", but Prestashop still displays the "Configure" button. ### Expected behavior The "Configure" button should be changed to "Enable" like in the PrestaShop 1.7 Without this option is it hard to find which modules are disabled in the backoffice. ### Steps to reproduce 1.Go to the "Module Manager" tab. 2.Disable one module, for example the "Cross-selling" module: https://prnt.sc/X4wVZC-uaLbq 3.After that the "Configure" text should be changed to "Enable" (in PrestaShop 1.7 it works correctly), but it still shows the text "Configure". Screenshot from PrestaShop 8.1.4: https://prnt.sc/xcrm_Bf--998 Screenshot from PrestaShop 1.7.8: https://prnt.sc/QvuUMH3fKizV Without this option is it hard to find which modules are disabled in the backoffice. I have this problem in all PrestaShop 8.x versions. Also, sometimes I have a similar problem with the module's upgrade, after the upgrade, the old version number of the module is still displayed in the backoffice. ### PrestaShop version(s) where the bug happened 8.1.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). _No response_</div> --- 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 importing a new theme, the theme page does not look as it should. And modal functions are not working (Activate theme, Delete theme, etc). ### Expected behavior _No response_ ### Steps to reproduce 1. Go to backoffice Customization > Themes 2. Import new theme from computer 3. Enable new theme added from computer 4. Theme Page views changed and theme actions didn't work (Enable theme, delete theme, etc.) ### PrestaShop version(s) where the bug happened 8.1.4 ### 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). PrestaConnect

BO > Customization > Themes Stop Working After importing a new theme, the theme page does not look as it should. And modal functions are not working #8.1.4 #Bug

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Customization > Themes Stop Working After importing a new theme, the theme page does not look as it should. And modal functions are not working #8.1.4 #Bug 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 importing a new theme, the theme page does not look as it should. And modal functions are not working (Activate theme, Delete theme, etc). ### Expected behavior _No response_ ### Steps to reproduce 1. Go to backoffice Customization > Themes 2. Import new theme from computer 3. Enable new theme added from computer 4. Theme Page views changed and theme actions didn't work (Enable theme, delete theme, etc.) ### PrestaShop version(s) where the bug happened 8.1.4 ### 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). PrestaConnect --- 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 Signing up for notification of product availability does not transfer the selected size. Product attribute id is undefined because backward compatibility should set "productAttributeId" instead of "productIdAttribute". HTML `<input class="input-radio" type="radio" data-product-attribute="7" name="group[7]" value="152" checked="checked">` POST request `id_product=1644&id_product_attribute=undefined&customer_email=example@go2.pl` JS: https://github.com/PrestaShop/ps_emailalerts/blob/v3.0.0/js/mailalerts.js#L25 `function addNotification(productId, productAttributeId) { // to keep backward compatibility if (typeof productId === 'undefined') { var ids = $('div.js-mailalert > input[type=hidden]'); productId = ids.eq(0).val(); productIdAttribute = ids.eq(1).val(); }` ### Expected behavior Backward compatibility should set variable "productAttributeId" instead of "productIdAttribute". POST request: `id_product=1644&id_product_attribute=7&customer_email=example@go2.pl` JS: https://github.com/PrestaShop/ps_emailalerts/blob/v3.0.0/js/mailalerts.js#L25 `function addNotification(productId, productAttributeId) { // to keep backward compatibility if (typeof productId === 'undefined') { var ids = $('div.js-mailalert > input[type=hidden]'); productId = ids.eq(0).val(); productAttributeId = ids.eq(1).val(); }` ### Steps to reproduce 1. Find product with soldout size 2. Sign for stock notificiation 3. Sent POST request has id_product_attribute with "undefined" value ### PrestaShop version(s) where the bug happened 1.7.6.7 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version ps_emailalerts ### Your company or customer's name goes here (if applicable). Blim

Module ps_emailalerts - problem with product attribute

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module ps_emailalerts - problem with product 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 Signing up for notification of product availability does not transfer the selected size. Product attribute id is undefined because backward compatibility should set "productAttributeId" instead of "productIdAttribute". HTML `<input class="input-radio" type="radio" data-product-attribute="7" name="group[7]" value="152" checked="checked">` POST request `id_product=1644&id_product_attribute=undefined&customer_email=example@go2.pl` JS: https://github.com/PrestaShop/ps_emailalerts/blob/v3.0.0/js/mailalerts.js#L25 `function addNotification(productId, productAttributeId) { // to keep backward compatibility if (typeof productId === 'undefined') { var ids = $('div.js-mailalert > input[type=hidden]'); productId = ids.eq(0).val(); productIdAttribute = ids.eq(1).val(); }` ### Expected behavior Backward compatibility should set variable "productAttributeId" instead of "productIdAttribute". POST request: `id_product=1644&id_product_attribute=7&customer_email=example@go2.pl` JS: https://github.com/PrestaShop/ps_emailalerts/blob/v3.0.0/js/mailalerts.js#L25 `function addNotification(productId, productAttributeId) { // to keep backward compatibility if (typeof productId === 'undefined') { var ids = $('div.js-mailalert > input[type=hidden]'); productId = ids.eq(0).val(); productAttributeId = ids.eq(1).val(); }` ### Steps to reproduce 1. Find product with soldout size 2. Sign for stock notificiation 3. Sent POST request has id_product_attribute with "undefined" value ### PrestaShop version(s) where the bug happened 1.7.6.7 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version ps_emailalerts ### Your company or customer's name goes here (if applicable). Blim --- 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 am using PRESTASHOP version 8.0.4, hosted on an OVH server with PHP version 7.4. I wanted to change the PHP version to 8, but unfortunately, I am having trouble with this. If I change the PHP version to any above 8 (8.0, 8.1, 8.2, 8.3), the website stops working. Instead of the page loading, strange characters appear. I have attached a screenshot. If I revert to version 7.4, the website starts working normally again. Please help. ### Expected behavior Changing the server version to PHP 8 ### Steps to reproduce 1. Log in to my OVH account. 2. In the server configuration, in the PHP version window, click "Change configuration." 3. Select PHP version: 8.0, stable64. 4. Confirm the configuration change. 5. After receiving confirmation of the PHP version change, go to the website. 6. Instead of the website, strange characters appear.  ### PrestaShop version(s) where the bug happened 8.0.4 ### 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). meblino.nl

Problem with changing php version to 8

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem with changing php version to 8 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 am using PRESTASHOP version 8.0.4, hosted on an OVH server with PHP version 7.4. I wanted to change the PHP version to 8, but unfortunately, I am having trouble with this. If I change the PHP version to any above 8 (8.0, 8.1, 8.2, 8.3), the website stops working. Instead of the page loading, strange characters appear. I have attached a screenshot. If I revert to version 7.4, the website starts working normally again. Please help. ### Expected behavior Changing the server version to PHP 8 ### Steps to reproduce 1. Log in to my OVH account. 2. In the server configuration, in the PHP version window, click "Change configuration." 3. Select PHP version: 8.0, stable64. 4. Confirm the configuration change. 5. After receiving confirmation of the PHP version change, go to the website. 6. Instead of the website, strange characters appear.  ### PrestaShop version(s) where the bug happened 8.0.4 ### 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). meblino.nl --- 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 disable a parent category, the child categories should still be displayed because these are not disabled. https://github.com/PrestaShop/PrestaShop/assets/16019289/b081b344-b079-4e3d-a1fa-2fa3b59b17ce ### Expected behavior When I disable a parent category, their children should still accessible in the sitemap. ### Steps to reproduce 1. Go to BO > Categories > Disable Accessories 2. Go to FO > Scroll down to Footer > Click on Sitemap 3. See that the Parent category Accessories is not displayed anymore 4. See that the children are not displayed anymore : Stationary and Home Accessories :x: ### 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_

sitemap - If I disable a parent category, the children categories are not displayed anymore

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : sitemap - If I disable a parent category, the children categories are not displayed 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 When I disable a parent category, the child categories should still be displayed because these are not disabled. https://github.com/PrestaShop/PrestaShop/assets/16019289/b081b344-b079-4e3d-a1fa-2fa3b59b17ce ### Expected behavior When I disable a parent category, their children should still accessible in the sitemap. ### Steps to reproduce 1. Go to BO > Categories > Disable Accessories 2. Go to FO > Scroll down to Footer > Click on Sitemap 3. See that the Parent category Accessories is not displayed anymore 4. See that the children are not displayed anymore : Stationary and Home Accessories :x: ### 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 Hi there is a problem with the module ps_facetedsearch about product sorts in front-office this problem is present on many websites normally in those with many products, perhaps because it is more easily noticed the problem is present in every type of ordering, and accentuated if the "Show unavailable, out of stock last" option is activated the problem does not depend on the graphics used, in this case it is developed by me. taking a random category from this site https://www.lampadaribartalini.it/7-plafoniere-lampade-soffitto when "Show unavailable, out of stock last" is enabled  when "Show unavailable, out of stock last" is not enabled  this also happens on the best-selling products page, with a product at €5.66 https://www.lampadaribartalini.it/vendite-migliori?order=product.price.asc on this site the problem is even more evident in general it seems that the order is correct but then it makes a mistake on some products https://www.mondialshop.it/it/piatti-doccia-in-marmo-resina-339 I can provide other sites with the same problem. obviously on a demo site with 20 products you won't notice it here is another example, at the end of this page https://www.stilebagno.com/it/63-box-doccia-2-lati here another error on the first row https://www.velliniilluminazione.com/it/49-lampade-da-tavolo-abat-jour  I can provide access to a copy of the site if you need verification bye ### Expected behavior _No response_ ### Steps to reproduce 1. it is necessary to check on a real website ### 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 ps_facetedsearch v3.15.1 ### Your company or customer's name goes here (if applicable). _No response_

ps_facetedsearch wrong product sorts in front-office

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_facetedsearch wrong product sorts in front-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 Hi there is a problem with the module ps_facetedsearch about product sorts in front-office this problem is present on many websites normally in those with many products, perhaps because it is more easily noticed the problem is present in every type of ordering, and accentuated if the "Show unavailable, out of stock last" option is activated the problem does not depend on the graphics used, in this case it is developed by me. taking a random category from this site https://www.lampadaribartalini.it/7-plafoniere-lampade-soffitto when "Show unavailable, out of stock last" is enabled  when "Show unavailable, out of stock last" is not enabled  this also happens on the best-selling products page, with a product at €5.66 https://www.lampadaribartalini.it/vendite-migliori?order=product.price.asc on this site the problem is even more evident in general it seems that the order is correct but then it makes a mistake on some products https://www.mondialshop.it/it/piatti-doccia-in-marmo-resina-339 I can provide other sites with the same problem. obviously on a demo site with 20 products you won't notice it here is another example, at the end of this page https://www.stilebagno.com/it/63-box-doccia-2-lati here another error on the first row https://www.velliniilluminazione.com/it/49-lampade-da-tavolo-abat-jour  I can provide access to a copy of the site if you need verification bye ### Expected behavior _No response_ ### Steps to reproduce 1. it is necessary to check on a real website ### 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 ps_facetedsearch v3.15.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 Error details: _Create file parameters An error occurred during installation... You can use the links on the left column to go back to the previous steps, or restart the installation process by [clicking here](http://localhost:8081/prestashop/install/index.php?restart=true). 1: HTTP 0 - error - undefined_ Screenshot:  Question 1: What usually causes this issue? Question 2: What can I do to fix this issue? My OS and server info is below: ------ OS: Windows 10 IoT Enterprise LTSC Version number: 21H2 IDE: wampserver3.3.2-64bit apache version: 2.4.58 php version: 8.3.0 mysql version: 8.2.0 phpmyadmin version: 5.2.1 ### Expected behavior Looking forward to successfully installing prestashop in win10! ### Steps to reproduce 1. During installation, it prompted me to enable SSL, I chose not to enable SSL. 2. Everything else is set up correctly, and the mysql database can be connected normally. 3. In the first step of installation, it prompts: To avoid internationalization data inconsistencies upgrade the symfony/intl component. I didn't solve this problem and just went to the next step! ### PrestaShop version(s) where the bug happened I don't know if there is any relation! ### PHP version(s) where the bug happened 8.3.0 ### If your bug is related to a module, specify its name and its version I don't know if there is any relation! ### Your company or customer's name goes here (if applicable). _No response_

Installing prestashop locally on win10, last step reported error

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Installing prestashop locally on win10, last step reported 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 Error details: _Create file parameters An error occurred during installation... You can use the links on the left column to go back to the previous steps, or restart the installation process by [clicking here](http://localhost:8081/prestashop/install/index.php?restart=true). 1: HTTP 0 - error - undefined_ Screenshot:  Question 1: What usually causes this issue? Question 2: What can I do to fix this issue? My OS and server info is below: ------ OS: Windows 10 IoT Enterprise LTSC Version number: 21H2 IDE: wampserver3.3.2-64bit apache version: 2.4.58 php version: 8.3.0 mysql version: 8.2.0 phpmyadmin version: 5.2.1 ### Expected behavior Looking forward to successfully installing prestashop in win10! ### Steps to reproduce 1. During installation, it prompted me to enable SSL, I chose not to enable SSL. 2. Everything else is set up correctly, and the mysql database can be connected normally. 3. In the first step of installation, it prompts: To avoid internationalization data inconsistencies upgrade the symfony/intl component. I didn't solve this problem and just went to the next step! ### PrestaShop version(s) where the bug happened I don't know if there is any relation! ### PHP version(s) where the bug happened 8.3.0 ### If your bug is related to a module, specify its name and its version I don't know if there is any relation! ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---