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 function TaxRulesGroupCore::getIdByName() is used (at least) in localization to return the id associated with a Tax Rule (Group), however it doesn't take account of disabled or deleted entries and instead returns the first (LIMIT 1) result. This means that the function can return an invalid id, most likely in older stores that have had successive upgrades. While its use in localization perhaps has little to no overall effect on a store, the use of this function by any community-generated content could cause incorrect behaviour in the front office. A select query on the relevant table (found in the wild and used by an active store) including all rows which match the tax rule group name (only one - with the id 19 - is active and therefor valid).  The result of simulating the sql used by the function. It returns the id 1 (and not 19 as would be expected). This record is marked active but deleted.  It could, of course, be any of the records in that list that is active and not deleted that is the value which *should* be returned not just the highest id as in this case. The back office user interface will not display deleted records, so the issue may even be completely transparent to the user if the duplicates have been deleted. It should also be noted that it is possible even in 8.1.4 to add multiple entries to this table via the back office all with the same name and all enabled (which, in itself, is a quality/usability issue). ### Expected behavior It is expected that this function returns a valid id of an active and enabled tax rules group. Either the name should be enforced as unique (likely a BC) or at the very least the enable/disable and deleted properties should be taken into account in the underlying sql. ### Steps to reproduce 1. Add several tax rules groups with the same name as the existing one 2. Delete and/or disable one or more of the "duplicate" tax rules groups 3. The function will return only the id of the first matching record. ### PrestaShop version(s) where the bug happened All ### PHP version(s) where the bug happened All ### 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_

TaxRulesGroupCore::getIdByName() can return an invalid result

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : TaxRulesGroupCore::getIdByName() can return an invalid result 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 function TaxRulesGroupCore::getIdByName() is used (at least) in localization to return the id associated with a Tax Rule (Group), however it doesn't take account of disabled or deleted entries and instead returns the first (LIMIT 1) result. This means that the function can return an invalid id, most likely in older stores that have had successive upgrades. While its use in localization perhaps has little to no overall effect on a store, the use of this function by any community-generated content could cause incorrect behaviour in the front office. A select query on the relevant table (found in the wild and used by an active store) including all rows which match the tax rule group name (only one - with the id 19 - is active and therefor valid).  The result of simulating the sql used by the function. It returns the id 1 (and not 19 as would be expected). This record is marked active but deleted.  It could, of course, be any of the records in that list that is active and not deleted that is the value which *should* be returned not just the highest id as in this case. The back office user interface will not display deleted records, so the issue may even be completely transparent to the user if the duplicates have been deleted. It should also be noted that it is possible even in 8.1.4 to add multiple entries to this table via the back office all with the same name and all enabled (which, in itself, is a quality/usability issue). ### Expected behavior It is expected that this function returns a valid id of an active and enabled tax rules group. Either the name should be enforced as unique (likely a BC) or at the very least the enable/disable and deleted properties should be taken into account in the underlying sql. ### Steps to reproduce 1. Add several tax rules groups with the same name as the existing one 2. Delete and/or disable one or more of the "duplicate" tax rules groups 3. The function will return only the id of the first matching record. ### PrestaShop version(s) where the bug happened All ### PHP version(s) where the bug happened All ### 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 don’t know if it’s a bug or not. I installed a new PS 8.1.4 ( downloaded here) and imported all the data from a PS 1.7.4. So there are commands. But the Best seller block does not display any products. ### Expected behavior Display best sellers ### Steps to reproduce 1. The Theme is Panda. it has its own module to display best sellers. But it doesn't display anything. On the PS 1.7, best sellers are displayed. 2. I try with the native module of Prestashop. But it's the same ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version bestsellers ### Your company or customer's name goes here (if applicable). _No response_

No best seller products

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : No best seller 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 I don’t know if it’s a bug or not. I installed a new PS 8.1.4 ( downloaded here) and imported all the data from a PS 1.7.4. So there are commands. But the Best seller block does not display any products. ### Expected behavior Display best sellers ### Steps to reproduce 1. The Theme is Panda. it has its own module to display best sellers. But it doesn't display anything. On the PS 1.7, best sellers are displayed. 2. I try with the native module of Prestashop. But it's the same ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version bestsellers ### 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, i'm trying to update manually from PrestaShop 1.7.6.7 to PrestaShop 8.1.4 using the CLI method outlined here: https://github.com/PrestaShop/docs/blob/131c273ba2b5b162206673298fb0c3c182fd1147/basics/keeping-up-to-date/upgrade-module/upgrade-cli.md The upgrade module v5.0.1 has been installed via shop backend (module manager). How can i avoid this error which comes from "Symfony" obviously?  All previous steps were running fine. (Linux Debian 12.5 / Plesk Obsidian 18.0.59 / PHP 7.4.33, also used for CLI) Thanks! ### Expected behavior A smooth update of the PrestaShop database structure. ### Steps to reproduce cd /var/www/vhosts/xxx/httpdocs/ rm -rf var/cache/prod/ rm -rf var/cache/dev/ curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.4/prestashop_8.1.4.zip -o adminxxx/autoupgrade/download/prestashop.zip curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.4/prestashop_8.1.4.xml -o adminxxx/autoupgrade/download/prestashop.xml echo "{\"channel\":\"archive\",\"archive_prestashop\":\"prestashop.zip\",\"archive_num\":\"8.1.4\", \"archive_xml\":\"prestashop.xml\", \"PS_AUTOUP_CHANGE_DEFAULT_THEME\":0, \"skip_backup\": 1}" > modules/autoupgrade/config.json php modules/autoupgrade/cli-updateconfig.php --from=modules/autoupgrade/config.json --dir=adminxxx php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=unzip php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=removeSamples php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=upgradeFiles php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=upgradeDb ### PrestaShop version(s) where the bug happened 1.7.6.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 upgrade-module 5.0.1 ### Your company or customer's name goes here (if applicable). _No response_

Manual update from PrestaShop 1.7.6.7 to PrestaShop 8.1.4 using CLI method fails - Symfony ClassNotFoundError

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Manual update from PrestaShop 1.7.6.7 to PrestaShop 8.1.4 using CLI method fails - Symfony ClassNotFoundError 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'm trying to update manually from PrestaShop 1.7.6.7 to PrestaShop 8.1.4 using the CLI method outlined here: https://github.com/PrestaShop/docs/blob/131c273ba2b5b162206673298fb0c3c182fd1147/basics/keeping-up-to-date/upgrade-module/upgrade-cli.md The upgrade module v5.0.1 has been installed via shop backend (module manager). How can i avoid this error which comes from "Symfony" obviously?  All previous steps were running fine. (Linux Debian 12.5 / Plesk Obsidian 18.0.59 / PHP 7.4.33, also used for CLI) Thanks! ### Expected behavior A smooth update of the PrestaShop database structure. ### Steps to reproduce cd /var/www/vhosts/xxx/httpdocs/ rm -rf var/cache/prod/ rm -rf var/cache/dev/ curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.4/prestashop_8.1.4.zip -o adminxxx/autoupgrade/download/prestashop.zip curl -L https://github.com/PrestaShop/PrestaShop/releases/download/8.1.4/prestashop_8.1.4.xml -o adminxxx/autoupgrade/download/prestashop.xml echo "{\"channel\":\"archive\",\"archive_prestashop\":\"prestashop.zip\",\"archive_num\":\"8.1.4\", \"archive_xml\":\"prestashop.xml\", \"PS_AUTOUP_CHANGE_DEFAULT_THEME\":0, \"skip_backup\": 1}" > modules/autoupgrade/config.json php modules/autoupgrade/cli-updateconfig.php --from=modules/autoupgrade/config.json --dir=adminxxx php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=unzip php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=removeSamples php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=upgradeFiles php modules/autoupgrade/cli-upgrade.php --dir=adminxxx --channel=archive --action=upgradeDb ### PrestaShop version(s) where the bug happened 1.7.6.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 upgrade-module 5.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 a user adds product X to the cart on February 10th but leaves the store before completing the order. Two days later, they return to the store and still find their product in the cart. Upon accessing the cart page, they encounter an error message stating "Product X is no longer available." However, if the user directly accesses the checkout URL without visiting the cart page first, they can proceed to finalize the order without any validation of product availability in the cart. ### Expected behavior Upon clicking the "Finalize Order" button, it should be verified that all products are still active to prevent a user from purchasing deactivated products. ### Steps to reproduce 1. Add a product to the cart. 2. Go to the checkout page. 3. Disable the product from the backoffice. 4. Come back to the checkout page. Click the "Finish order" button. The order will be finished instead of show a message notifying "Product is not available". 5. After my pull request changes, this problem has been fixed. ### PrestaShop version(s) where the bug happened 8.0.x ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). csoon1992

Check all product are still active to set orderable cart

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Check all product are still active to set orderable 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 a user adds product X to the cart on February 10th but leaves the store before completing the order. Two days later, they return to the store and still find their product in the cart. Upon accessing the cart page, they encounter an error message stating "Product X is no longer available." However, if the user directly accesses the checkout URL without visiting the cart page first, they can proceed to finalize the order without any validation of product availability in the cart. ### Expected behavior Upon clicking the "Finalize Order" button, it should be verified that all products are still active to prevent a user from purchasing deactivated products. ### Steps to reproduce 1. Add a product to the cart. 2. Go to the checkout page. 3. Disable the product from the backoffice. 4. Come back to the checkout page. Click the "Finish order" button. The order will be finished instead of show a message notifying "Product is not available". 5. After my pull request changes, this problem has been fixed. ### PrestaShop version(s) where the bug happened 8.0.x ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). csoon1992 --- 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 have a volume discount for a product, the shopping cart is not well updated with the right information. The discount tag is not always displayed. It is only displayed when I have the first product in the cart reaching the volume discount. https://github.com/PrestaShop/PrestaShop/assets/16019289/099690e5-5ea5-448f-908b-2fd8b0ab26e6 ### Expected behavior The discount tag should always be displayed on the shopping cart ### Steps to reproduce In BO : 1. Go to BO > Create a product > Add a title, stock and a price = 100€ 2. In Details Tab > Add a required customization 3. Go to Pricing Tab > Add a specific price 4. Minimum number of units purchased = 3 5. Enable : Apply a discount to the initial price > Set to 5% > Save In FO : 1. Preview your product 2. Add a customization > Add to cart 3. Do that 2 more times, so you have 3 products with 3 different custom in your cart 4. Proceed to checkout > The shopping cart page is displayed 5. You have 3 products at 95€ each :x: 6. It should display the initial price `100`, the discounted price `95` and the discount `5%` 7. Increase the first product in cart to 3 8. See the discount tag is displayed 9. Decrease the first product to 1, increase the second product to 3 10. No discount tag is displayed :x: ### 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 - Volume discounts on Shopping cart page are not well displayed

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO - Volume discounts on Shopping cart page are not well 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 have a volume discount for a product, the shopping cart is not well updated with the right information. The discount tag is not always displayed. It is only displayed when I have the first product in the cart reaching the volume discount. https://github.com/PrestaShop/PrestaShop/assets/16019289/099690e5-5ea5-448f-908b-2fd8b0ab26e6 ### Expected behavior The discount tag should always be displayed on the shopping cart ### Steps to reproduce In BO : 1. Go to BO > Create a product > Add a title, stock and a price = 100€ 2. In Details Tab > Add a required customization 3. Go to Pricing Tab > Add a specific price 4. Minimum number of units purchased = 3 5. Enable : Apply a discount to the initial price > Set to 5% > Save In FO : 1. Preview your product 2. Add a customization > Add to cart 3. Do that 2 more times, so you have 3 products with 3 different custom in your cart 4. Proceed to checkout > The shopping cart page is displayed 5. You have 3 products at 95€ each :x: 6. It should display the initial price `100`, the discounted price `95` and the discount `5%` 7. Increase the first product in cart to 3 8. See the discount tag is displayed 9. Decrease the first product to 1, increase the second product to 3 10. No discount tag is displayed :x: ### 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 When installing Prestashop 8.1.4 I get the following error: Warning: rename([]index.php.tmp,[]index.php): Access denied (code:5) in index.php on line 1338 ("error":false,"numfiles":28574,"lastId":29000)  This is rather strange as some time ago I installed PS 8.1.1 without problems under PHP 7.4. That is the same install file. So there must be something strange with PHP 8.1. Following that I rename the file manually and then I start /install/index.php. This starts the proper installation. Unfortunately this installation only goes until 56%. Then I get a rather vague message: 1: HTTP 500 - error - {"success":true,"message":""}  When I look in the error log of the server I an error about Swiftmailer: PHP Fatal error: Uncaught Error: Failed opening required 'D:\\xampp814\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\getSwiftmailer_EmailSender_ListenerService.php' When I check this "ContainerHxgZQPu" no longer exists. The complete error message is very long. What is happening here? > [Tue Mar 12 14:32:32.251574 2024] [php:error] [pid 36576:tid 1956] [client ::1:59935] PHP Fatal error: Uncaught Error: Failed opening required 'D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\getSwiftmailer_EmailSender_ListenerService.php' (include_path='D:\\xampp81\\htdocs\\_ps814\\vendor/pear/pear_exception;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/console_getopt;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/pear-core-minimal/src;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/archive_tar;D:\\xampp81\\php\\PEAR') in D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php:2224\nStack trace:\n#0 D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php(2631): ContainerHxgZQPu\\appAppKernelProdContainer->load('getSwiftmailer_...')\n#1 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(301): ContainerHxgZQPu\\appAppKernelProdContainer->ContainerHxgZQPu\\{closure}()\n#2 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(264): Symfony\\Component\\EventDispatcher\\EventDispatcher::Symfony\\Component\\EventDispatcher\\{closure}(Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent), 'console.error', Object(Symfony\\Component\\EventDispatcher\\EventDispatcher))\n#3 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(239): Symfony\\Component\\EventDispatcher\\EventDispatcher->doDispatch(Array, 'console.error', Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent))\n#4 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(73): Symfony\\Component\\EventDispatcher\\EventDispatcher->callListeners(Array, 'console.error', Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent))\n#5 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\Console\\Application.php(242): Symfony\\Component\\EventDispatcher\\EventDispatcher->dispatch(Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent), 'console.error')\n#6 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Bundle\\FrameworkBundle\\Console\\Application.php(83): Symfony\\Component\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArrayInput), Object(Symfony\\Component\\Console\\Output\\NullOutput))\n#7 D:\\xampp81\\htdocs\\_ps814\\src\\Adapter\\Cache\\Clearer\\SymfonyCacheClearer.php(103): Symfony\\Bundle\\FrameworkBundle\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArrayInput), Object(Symfony\\Component\\Console\\Output\\NullOutput))\n#8 [internal function]: PrestaShop\\PrestaShop\\Adapter\\Cache\\Clearer\\SymfonyCacheClearer->PrestaShop\\PrestaShop\\Adapter\\Cache\\Clearer\\{closure}()\n#9 {main}\n thrown in D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php on line 2224, referer: http://localhost/_ps814/install/index.php ### Expected behavior correct installation ### Steps to reproduce Install under Windows and Xampp with PHP 8.1. ### 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). _No response_

Installation trouble

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Installation trouble 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 installing Prestashop 8.1.4 I get the following error: Warning: rename([]index.php.tmp,[]index.php): Access denied (code:5) in index.php on line 1338 ("error":false,"numfiles":28574,"lastId":29000)  This is rather strange as some time ago I installed PS 8.1.1 without problems under PHP 7.4. That is the same install file. So there must be something strange with PHP 8.1. Following that I rename the file manually and then I start /install/index.php. This starts the proper installation. Unfortunately this installation only goes until 56%. Then I get a rather vague message: 1: HTTP 500 - error - {"success":true,"message":""}  When I look in the error log of the server I an error about Swiftmailer: PHP Fatal error: Uncaught Error: Failed opening required 'D:\\xampp814\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\getSwiftmailer_EmailSender_ListenerService.php' When I check this "ContainerHxgZQPu" no longer exists. The complete error message is very long. What is happening here? > [Tue Mar 12 14:32:32.251574 2024] [php:error] [pid 36576:tid 1956] [client ::1:59935] PHP Fatal error: Uncaught Error: Failed opening required 'D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\getSwiftmailer_EmailSender_ListenerService.php' (include_path='D:\\xampp81\\htdocs\\_ps814\\vendor/pear/pear_exception;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/console_getopt;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/pear-core-minimal/src;D:\\xampp81\\htdocs\\_ps814\\vendor/pear/archive_tar;D:\\xampp81\\php\\PEAR') in D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php:2224\nStack trace:\n#0 D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php(2631): ContainerHxgZQPu\\appAppKernelProdContainer->load('getSwiftmailer_...')\n#1 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(301): ContainerHxgZQPu\\appAppKernelProdContainer->ContainerHxgZQPu\\{closure}()\n#2 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(264): Symfony\\Component\\EventDispatcher\\EventDispatcher::Symfony\\Component\\EventDispatcher\\{closure}(Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent), 'console.error', Object(Symfony\\Component\\EventDispatcher\\EventDispatcher))\n#3 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(239): Symfony\\Component\\EventDispatcher\\EventDispatcher->doDispatch(Array, 'console.error', Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent))\n#4 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\EventDispatcher\\EventDispatcher.php(73): Symfony\\Component\\EventDispatcher\\EventDispatcher->callListeners(Array, 'console.error', Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent))\n#5 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\Console\\Application.php(242): Symfony\\Component\\EventDispatcher\\EventDispatcher->dispatch(Object(Symfony\\Component\\Console\\Event\\ConsoleErrorEvent), 'console.error')\n#6 D:\\xampp81\\htdocs\\_ps814\\vendor\\symfony\\symfony\\src\\Symfony\\Bundle\\FrameworkBundle\\Console\\Application.php(83): Symfony\\Component\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArrayInput), Object(Symfony\\Component\\Console\\Output\\NullOutput))\n#7 D:\\xampp81\\htdocs\\_ps814\\src\\Adapter\\Cache\\Clearer\\SymfonyCacheClearer.php(103): Symfony\\Bundle\\FrameworkBundle\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArrayInput), Object(Symfony\\Component\\Console\\Output\\NullOutput))\n#8 [internal function]: PrestaShop\\PrestaShop\\Adapter\\Cache\\Clearer\\SymfonyCacheClearer->PrestaShop\\PrestaShop\\Adapter\\Cache\\Clearer\\{closure}()\n#9 {main}\n thrown in D:\\xampp81\\htdocs\\_ps814\\var\\cache\\prod\\ContainerHxgZQPu\\appAppKernelProdContainer.php on line 2224, referer: http://localhost/_ps814/install/index.php ### Expected behavior correct installation ### Steps to reproduce Install under Windows and Xampp with PHP 8.1. ### 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). _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 request a `PATCH /api/product/{productId}` with data, type is not updated ### Expected behavior When I request a `PATCH /api/product/{productId}` with data, type is updated ### Steps to reproduce 1. Auth with the API (scope : `product_write`) 2. Request the endpoint 'api/product/{productId}' with method `PATCH` : ```json { type: 'virtual' } ``` 3. The reponse has not updated type : ```json {"productId":34,"type":"standard","active":true,"names":{"1":"Unbranded Granite Chair","2":"Unbranded Granite Chair"},"descriptions":{"1":"<p>Sint aro defungo cultellus audentia talio corrupti stabilis abstergo unus.<\/p>","2":""}} ``` 4. The product page has not updated type ### PrestaShop version(s) where the bug happened 9.0.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). @PrestaShopCorp

Endpoint `PATCH /api/product/{productId}` : Type is not updated

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Endpoint `PATCH /api/product/{productId}` : Type is not updated 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 request a `PATCH /api/product/{productId}` with data, type is not updated ### Expected behavior When I request a `PATCH /api/product/{productId}` with data, type is updated ### Steps to reproduce 1. Auth with the API (scope : `product_write`) 2. Request the endpoint 'api/product/{productId}' with method `PATCH` : ```json { type: 'virtual' } ``` 3. The reponse has not updated type : ```json {"productId":34,"type":"standard","active":true,"names":{"1":"Unbranded Granite Chair","2":"Unbranded Granite Chair"},"descriptions":{"1":"<p>Sint aro defungo cultellus audentia talio corrupti stabilis abstergo unus.<\/p>","2":""}} ``` 4. The product page has not updated type ### PrestaShop version(s) where the bug happened 9.0.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). @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 The `Specific delivery time for this product` is not displayed if my product has a Required Customization. With a non required customization, it is OK. https://github.com/PrestaShop/PrestaShop/assets/16019289/44418339-9e18-4f79-87a6-935731c52f65 ### Expected behavior The `Specific delivery time for this product` for Out-of-Stock product should always be displayed, whether or not there's a Required customization. ### Steps to reproduce 1. Go to BO > Add a product > Add a title > Enable the product 2. In Tab Stock > When out of stock > Select Allow orders 3. Go to Shipping > Select Specific delivery time for this product 4. Add a text to the option : Delivery time of out-of-stock products with allowed orders: 5. Save 6. Preview product > See the text displayed ✅ 7. Go back to BO > Product page > Tab Details 8. Add a Required Customization 9. Save 10. Go to FO > See the Delivery time for OOS product is not displayed anymore :x: ### 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 > Product page - Products with required customization do not display the Specific delivery time for OOS products

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO > Product page - Products with required customization do not display the Specific delivery time for OOS 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 The `Specific delivery time for this product` is not displayed if my product has a Required Customization. With a non required customization, it is OK. https://github.com/PrestaShop/PrestaShop/assets/16019289/44418339-9e18-4f79-87a6-935731c52f65 ### Expected behavior The `Specific delivery time for this product` for Out-of-Stock product should always be displayed, whether or not there's a Required customization. ### Steps to reproduce 1. Go to BO > Add a product > Add a title > Enable the product 2. In Tab Stock > When out of stock > Select Allow orders 3. Go to Shipping > Select Specific delivery time for this product 4. Add a text to the option : Delivery time of out-of-stock products with allowed orders: 5. Save 6. Preview product > See the text displayed ✅ 7. Go back to BO > Product page > Tab Details 8. Add a Required Customization 9. Save 10. Go to FO > See the Delivery time for OOS product is not displayed anymore :x: ### 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 Whether I click on top or at the bottom of the quickview modal, it should close it. Now, it depends on where exactly I click. https://github.com/PrestaShop/PrestaShop/assets/16019289/404b85d7-6705-4175-b500-fa0671666964 ### Expected behavior I should be able to click anywhere outside of the modal and it should close it. ### Steps to reproduce 1. Go to FO > Open quickview of a product 2. Click anywhere on the greyed out area outside of the modal on top or at the bottom 3. The module won't close :x: ### 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 > Quick view - I can't close the quickview modal if I click outside of the modal on the top/bottom

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO > Quick view - I can't close the quickview modal if I click outside of the modal on the top/bottom 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 Whether I click on top or at the bottom of the quickview modal, it should close it. Now, it depends on where exactly I click. https://github.com/PrestaShop/PrestaShop/assets/16019289/404b85d7-6705-4175-b500-fa0671666964 ### Expected behavior I should be able to click anywhere outside of the modal and it should close it. ### Steps to reproduce 1. Go to FO > Open quickview of a product 2. Click anywhere on the greyed out area outside of the modal on top or at the bottom 3. The module won't close :x: ### 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 When I add a file with a wrong format in the custom area, my product page will be broken. https://github.com/PrestaShop/PrestaShop/assets/16019289/3134bf98-3e68-49e8-aaf0-51cf1f7fc1ec When I enable the debug mode, I have the following errors :  https://github.com/PrestaShop/PrestaShop/assets/16019289/e743d103-9352-4385-be60-157139056f14 ### Expected behavior I should see the red alert "Image format not recognized, allowed formats are: gif, jpg, jpeg, jpe, png, webp", but the page should still be displayed as before (with title, price, details, description, etc) ### Steps to reproduce 1. BO > Create a product > Add a title and a price 2. Add a required custom file > Save 3. Go to the product page in FO 4. In the custom area > Add a .mov file 5. Save customization 6. See alert is displayed 7. See the page is broken, no title, no price, can't refresh the page to see the details of the product :x: ### 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 > Product Page - Add a file in the wrong format in the customization area breaks the page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO > Product Page - Add a file in the wrong format in the customization area breaks the 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 When I add a file with a wrong format in the custom area, my product page will be broken. https://github.com/PrestaShop/PrestaShop/assets/16019289/3134bf98-3e68-49e8-aaf0-51cf1f7fc1ec When I enable the debug mode, I have the following errors :  https://github.com/PrestaShop/PrestaShop/assets/16019289/e743d103-9352-4385-be60-157139056f14 ### Expected behavior I should see the red alert "Image format not recognized, allowed formats are: gif, jpg, jpeg, jpe, png, webp", but the page should still be displayed as before (with title, price, details, description, etc) ### Steps to reproduce 1. BO > Create a product > Add a title and a price 2. Add a required custom file > Save 3. Go to the product page in FO 4. In the custom area > Add a .mov file 5. Save customization 6. See alert is displayed 7. See the page is broken, no title, no price, can't refresh the page to see the details of the product :x: ### 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 During restoration of a backup I found some problems with a table connected to a third party module that contained lots of non-Latin characters. This led me to do some investigation and then I saw that Prestashop isn't doing any conversion when storing the data in the backup file. This probably worked when UTF8 was used, as the backup file uses UTF8. But I wonder whether that still always works with UTF8mb4. Also note that third party modules sometimes still use pre-UTF8 collations like latin1_swedish for their tables. The Export class of phpMyAdmin does use conversion. ### Expected behavior Correct conversion ### Steps to reproduce Backup and retrieve a database with many non-Latin characters. ### PrestaShop version(s) where the bug happened 8 ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Data conversion in backup

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Data conversion in backup 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 restoration of a backup I found some problems with a table connected to a third party module that contained lots of non-Latin characters. This led me to do some investigation and then I saw that Prestashop isn't doing any conversion when storing the data in the backup file. This probably worked when UTF8 was used, as the backup file uses UTF8. But I wonder whether that still always works with UTF8mb4. Also note that third party modules sometimes still use pre-UTF8 collations like latin1_swedish for their tables. The Export class of phpMyAdmin does use conversion. ### Expected behavior Correct conversion ### Steps to reproduce Backup and retrieve a database with many non-Latin characters. ### PrestaShop version(s) where the bug happened 8 ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _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 request a `POST /api/product` with data, descriptions are not used. ### Expected behavior When I request a `POST /api/product` with data, descriptions are used. ### Steps to reproduce 1. Auth with the API (scope : `product_write`) 2. Request the endpoint 'api/product' with method `POST` : ```json { type: 'standard', active: true, names: { '1': 'Unbranded Plastic Keyboard', '2': 'Unbranded Plastic Keyboard in FRENCH' }, descriptions: { '1': 'Similique antea compono summa est.', '2': 'Similique antea compono summa est. in FRENCH' } } ``` 3. The reponse has empty description : ```json {"productId":23,"type":"standard","active":false,"names":{"1":"Unbranded Plastic Keyboard","2":"Unbranded Plastic Keyboard in FRENCH"},"descriptions":{"1":"","2":""}} ``` 4. The product page has empty description ### PrestaShop version(s) where the bug happened 9.0.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). @PrestaShopCorp

Endpoint `POST /api/product` : Descriptions are not updated

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Endpoint `POST /api/product` : Descriptions are not updated 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 request a `POST /api/product` with data, descriptions are not used. ### Expected behavior When I request a `POST /api/product` with data, descriptions are used. ### Steps to reproduce 1. Auth with the API (scope : `product_write`) 2. Request the endpoint 'api/product' with method `POST` : ```json { type: 'standard', active: true, names: { '1': 'Unbranded Plastic Keyboard', '2': 'Unbranded Plastic Keyboard in FRENCH' }, descriptions: { '1': 'Similique antea compono summa est.', '2': 'Similique antea compono summa est. in FRENCH' } } ``` 3. The reponse has empty description : ```json {"productId":23,"type":"standard","active":false,"names":{"1":"Unbranded Plastic Keyboard","2":"Unbranded Plastic Keyboard in FRENCH"},"descriptions":{"1":"","2":""}} ``` 4. The product page has empty description ### PrestaShop version(s) where the bug happened 9.0.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). @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 The endpoint /api/hooks returns a bad count of hooks (or the BO doesn't display all hooks). ### Expected behavior The endpoint /api/hooks has the same count of hooks that in the BO. ### Steps to reproduce 1. Auth with the API (scope : `hook_read`) 2. Request the endpoint 'api/hooks' : It returns **947** hooks  3. Go in the BO > Design > Positions 4. Display non-positionable hooks: It returns **124** hooks  ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version ps_apiresources `dev-fix/34852` ### Your company or customer's name goes here (if applicable). @PrestaShopCorp

Endpoint /api/hooks & List of Hooks : Incorrect count of hooks

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Endpoint /api/hooks & List of Hooks : Incorrect count of hooks 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 endpoint /api/hooks returns a bad count of hooks (or the BO doesn't display all hooks). ### Expected behavior The endpoint /api/hooks has the same count of hooks that in the BO. ### Steps to reproduce 1. Auth with the API (scope : `hook_read`) 2. Request the endpoint 'api/hooks' : It returns **947** hooks  3. Go in the BO > Design > Positions 4. Display non-positionable hooks: It returns **124** hooks  ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version ps_apiresources `dev-fix/34852` ### 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 For example : - Total order price : 100€ - Total discount : 30€ The credit slip should be 70€ but it's actually 100€. ### Expected behavior In my Document Block, the Amount should be 70€, instead of 100€ ### Steps to reproduce 1. Go to BO > Orders > Discounts > Create a discount 30€ 2. Create a product 100€ 3. In FO > Add the product to your cart > Proceed checkout, make sure the discount is taken into account 4. Go to BO > Change status to Paiement accepted 5. Click Partial Refund 6. Select > `Generate a credit slip` & `Product(s) price, excluding amount of initial voucher: €70.00` > Click Partial Refund 7. See in Document Block > the Amount column is incorrect. It displayed €30.00, it should be €70.00 ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

BO > Order details page - Amount displayed on Document tab for Credit slip is incorrect when made on an order with discount

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Order details page - Amount displayed on Document tab for Credit slip is incorrect when made on an order with discount 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 example : - Total order price : 100€ - Total discount : 30€ The credit slip should be 70€ but it's actually 100€. ### Expected behavior In my Document Block, the Amount should be 70€, instead of 100€ ### Steps to reproduce 1. Go to BO > Orders > Discounts > Create a discount 30€ 2. Create a product 100€ 3. In FO > Add the product to your cart > Proceed checkout, make sure the discount is taken into account 4. Go to BO > Change status to Paiement accepted 5. Click Partial Refund 6. Select > `Generate a credit slip` & `Product(s) price, excluding amount of initial voucher: €70.00` > Click Partial Refund 7. See in Document Block > the Amount column is incorrect. It displayed €30.00, it should be €70.00 ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _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 console error appeared ### Expected behavior No console errors ### Steps to reproduce 1. Go to BO 2. Go to Module > Module Manager 3. Check the JS Console   ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version ps_faviconnotificationbo 2.1.3 ### Your company or customer's name goes here (if applicable). @PrestaShopCorp

Uncaught ReferenceError: ps_faviconnotificationbo is not defined

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Uncaught ReferenceError: ps_faviconnotificationbo is not defined 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 console error appeared ### Expected behavior No console errors ### Steps to reproduce 1. Go to BO 2. Go to Module > Module Manager 3. Check the JS Console   ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened 8.2 ### If your bug is related to a module, specify its name and its version ps_faviconnotificationbo 2.1.3 ### 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 The list of hooks was available in 8.1.x but not on develop. `develop` :  `8.1.4` :  ### Expected behavior The list of hooks is available. ### Steps to reproduce 1. Go to BO 2. Design > Positions 3. Click on "Hook a module" 4. Choose a module like "Bank transfer" 5. List of hooks is not available ### PrestaShop version(s) where the bug happened 9.0.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). @PrestaShopCorp

BO > Design > Positions : Can't hook a module

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Design > Positions : Can't hook a 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 The list of hooks was available in 8.1.x but not on develop. `develop` :  `8.1.4` :  ### Expected behavior The list of hooks is available. ### Steps to reproduce 1. Go to BO 2. Design > Positions 3. Click on "Hook a module" 4. Choose a module like "Bank transfer" 5. List of hooks is not available ### PrestaShop version(s) where the bug happened 9.0.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). @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 the stats module pagesnotfound is missing pagination, so if you try to access the module when there is a huge amount of data (800k+ rows for instance) either the server goes out of memory trying to render the list, or the browser will. ### Expected behavior The list should have pagination. ### Steps to reproduce 1. fill the database with lots unique rows in ps_pagenotfound 2. visit the page not found stats page. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version pagenotfound 2.0.3 ### Your company or customer's name goes here (if applicable). Prestaworks AB

pagesnotfound is missing pagination

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : pagesnotfound is missing pagination 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 stats module pagesnotfound is missing pagination, so if you try to access the module when there is a huge amount of data (800k+ rows for instance) either the server goes out of memory trying to render the list, or the browser will. ### Expected behavior The list should have pagination. ### Steps to reproduce 1. fill the database with lots unique rows in ps_pagenotfound 2. visit the page not found stats page. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version pagenotfound 2.0.3 ### Your company or customer's name goes here (if applicable). Prestaworks AB --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When upgrade module Faceted Search from v3.15.0 > v3.15.1 it downloads this file: https://api.prestashop-project.org/assets/modules/ps_facetedsearch/v3.15.1/ps_facetedsearch.zip But prestashop keep saying it needs to be upgraded. When i download the file manually and open: config.xml the version is: `<version><![CDATA[3.15.0]]></version>` And not `<version><![CDATA[3.15.1]]></version>` As you can see, v3.15.1 is in the upgrade url! <img width="899" alt="facetedsearch" src="https://github.com/PrestaShop/PrestaShop/assets/533123/f37182cf-c3d3-497c-bbb8-eb3058d322c2"> Also git doesn't see that the config file is updated. <img width="617" alt="Scherm­afbeelding 2024-03-11 om 13 50 15" src="https://github.com/PrestaShop/PrestaShop/assets/533123/569289b1-35e3-4c49-87a2-64dd3bf02817"> When i download manually the release from github, the config.xml contains the correct version: `<version><![CDATA[3.15.1]]></version>` https://github.com/PrestaShop/ps_facetedsearch/releases So the problem is that prestashop doesn't have the correct file on: https://api.prestashop-project.org/assets/modules/ps_facetedsearch/v3.15.1/ps_facetedsearch.zip ### Expected behavior upgrade succesfull with the correct config.xml with version: <version><![CDATA[3.15.1]]></version> ### Steps to reproduce upgrade module ### 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 ps_facetedsearch v3.15.0 ### Your company or customer's name goes here (if applicable). _No response_

Upgrade module facetedsearch succesfull, but keeps saying it needs an upgrade.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade module facetedsearch succesfull, but keeps saying it needs an upgrade. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When upgrade module Faceted Search from v3.15.0 > v3.15.1 it downloads this file: https://api.prestashop-project.org/assets/modules/ps_facetedsearch/v3.15.1/ps_facetedsearch.zip But prestashop keep saying it needs to be upgraded. When i download the file manually and open: config.xml the version is: `<version><![CDATA[3.15.0]]></version>` And not `<version><![CDATA[3.15.1]]></version>` As you can see, v3.15.1 is in the upgrade url! <img width="899" alt="facetedsearch" src="https://github.com/PrestaShop/PrestaShop/assets/533123/f37182cf-c3d3-497c-bbb8-eb3058d322c2"> Also git doesn't see that the config file is updated. <img width="617" alt="Scherm­afbeelding 2024-03-11 om 13 50 15" src="https://github.com/PrestaShop/PrestaShop/assets/533123/569289b1-35e3-4c49-87a2-64dd3bf02817"> When i download manually the release from github, the config.xml contains the correct version: `<version><![CDATA[3.15.1]]></version>` https://github.com/PrestaShop/ps_facetedsearch/releases So the problem is that prestashop doesn't have the correct file on: https://api.prestashop-project.org/assets/modules/ps_facetedsearch/v3.15.1/ps_facetedsearch.zip ### Expected behavior upgrade succesfull with the correct config.xml with version: <version><![CDATA[3.15.1]]></version> ### Steps to reproduce upgrade module ### 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 ps_facetedsearch v3.15.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 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_

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

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

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

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 --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://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_ --- 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 exception when I create a product with a long title in cyrillic. <img width="1214" alt="Screenshot 2024-03-11 at 12 31 59" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/3d94148d-7ca0-46ca-97a3-7d7125059bd8"> `An unexpected error occurred. [PrestaShop\PrestaShop\Core\Domain\Product\Exception\ProductConstraintException code 310]: Invalid Product localized property "link_rewrite" for language with id "1"` ### Expected behavior Should be saved without exception ### Steps to reproduce 1. Go to BO > Product > Add a product 2. Add title in cyrillic `События, окружающие нас сегодня, часто настолько драматические, что трудно их даже осознать.` (92 characters) 3. Save 4. See Exception :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

BO > Product Page - Add a long title in cyrillic results in an Exception

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Product Page - Add a long title in cyrillic results in an Exception 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 exception when I create a product with a long title in cyrillic. <img width="1214" alt="Screenshot 2024-03-11 at 12 31 59" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/3d94148d-7ca0-46ca-97a3-7d7125059bd8"> `An unexpected error occurred. [PrestaShop\PrestaShop\Core\Domain\Product\Exception\ProductConstraintException code 310]: Invalid Product localized property "link_rewrite" for language with id "1"` ### Expected behavior Should be saved without exception ### Steps to reproduce 1. Go to BO > Product > Add a product 2. Add title in cyrillic `События, окружающие нас сегодня, часто настолько драматические, что трудно их даже осознать.` (92 characters) 3. Save 4. See Exception :x: ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments PrestaShop only support true color png file. ### Expected behavior Support 8 bits png file ### Steps to reproduce 1. Upload a 8 bits png file (256 colors file) 2. Check the uploaded file: it is in true color and size is doubled ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened all ### 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). Creabilis.com

Support palleted PNG file

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Support palleted PNG 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 PrestaShop only support true color png file. ### Expected behavior Support 8 bits png file ### Steps to reproduce 1. Upload a 8 bits png file (256 colors file) 2. Check the uploaded file: it is in true color and size is doubled ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened all ### 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). Creabilis.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 Hi, I installed the module "Newsletter subscription" in my theme but it doesn't work, when I press the subscribe button nothing happens...  ### Expected behavior _No response_ ### Steps to reproduce Go to 'https://themedev.vitastrong.it/en/' Scrool to the footer Enter valid email Checked the checkbox Click the button 'Subscribe' ### 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 Newsletter subscription - Version 2.8.2 ### Your company or customer's name goes here (if applicable). _No response_

Newsletter subscription button doesn't work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Newsletter subscription button doesn't 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 Hi, I installed the module "Newsletter subscription" in my theme but it doesn't work, when I press the subscribe button nothing happens...  ### Expected behavior _No response_ ### Steps to reproduce Go to 'https://themedev.vitastrong.it/en/' Scrool to the footer Enter valid email Checked the checkbox Click the button 'Subscribe' ### 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 Newsletter subscription - Version 2.8.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 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 _No response_ ### 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/35595/comments

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

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 _No response_ ### 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 connected to the closed signal https://github.com/PrestaShop/PrestaShop/issues/29982 ### Expected behavior Hi, I'm having the same problem on a prestashop where the taxes have been changed, @hibatallahAouadni answer doesn't give a solution, prestashop can't have a constraint (id_tax = 1) which we can't even modify by code to solve the problem. therefore, marking it as closed is not a solution. It would be nice to understand when creating a product which class assigns this (id_tax = 1 fixed), so that those who have this problem can solve it, without having to reinstall a new prestashop. Personally, I have been trying to resolve this problem for days by restoring all the tax tables but the problem persists. I hope someone can give comprehensive information on how to solve the problem. Thanks for the support video sent by @hibatallahAouadni ### Steps to reproduce https://private-user-images.githubusercontent.com/100699445/195567908-94bffd04-7925-464c-b717-d60a10465ac2.webm?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDk5Nzc2OTMsIm5iZiI6MTcwOTk3NzM5MywicGF0aCI6Ii8xMDA2OTk0NDUvMTk1NTY3OTA4LTk0YmZmZDA0LTc5MjUtNDY0Yy1iNzE3LWQ2MGExMDQ2NWFjMi53ZWJtP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDMwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDAzMDlUMDk0MzEzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NTBmNGIyMTBmYzhmMTMzMDcyYThmY2FiZWFiMGUxNjkyYjkyY2U4NTNmNzRmMDNkM2Q5OTcwY2JjZWJiMzAxYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.GL4ExC2EIjEYLs0ontcjO5q5deoaddIMVARsVVA4eEU ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.0.30 ### 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_

No more default tax rule when creating new product

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : No more default tax rule when creating new product Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments connected to the closed signal https://github.com/PrestaShop/PrestaShop/issues/29982 ### Expected behavior Hi, I'm having the same problem on a prestashop where the taxes have been changed, @hibatallahAouadni answer doesn't give a solution, prestashop can't have a constraint (id_tax = 1) which we can't even modify by code to solve the problem. therefore, marking it as closed is not a solution. It would be nice to understand when creating a product which class assigns this (id_tax = 1 fixed), so that those who have this problem can solve it, without having to reinstall a new prestashop. Personally, I have been trying to resolve this problem for days by restoring all the tax tables but the problem persists. I hope someone can give comprehensive information on how to solve the problem. Thanks for the support video sent by @hibatallahAouadni ### Steps to reproduce https://private-user-images.githubusercontent.com/100699445/195567908-94bffd04-7925-464c-b717-d60a10465ac2.webm?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDk5Nzc2OTMsIm5iZiI6MTcwOTk3NzM5MywicGF0aCI6Ii8xMDA2OTk0NDUvMTk1NTY3OTA4LTk0YmZmZDA0LTc5MjUtNDY0Yy1iNzE3LWQ2MGExMDQ2NWFjMi53ZWJtP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDMwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDAzMDlUMDk0MzEzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NTBmNGIyMTBmYzhmMTMzMDcyYThmY2FiZWFiMGUxNjkyYjkyY2U4NTNmNzRmMDNkM2Q5OTcwY2JjZWJiMzAxYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.GL4ExC2EIjEYLs0ontcjO5q5deoaddIMVARsVVA4eEU ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.0.30 ### 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 J'essaye d'installer prestashop mais je tombe sur l'erreur ci-dessous, j'ai essayer de creer un environement comme jai vu sur un tuto mai sca marche toujours pas. Merci d'avance <img width="736" alt="Capture d’écran 2024-03-08 163600" src="https://github.com/PrestaShop/PrestaShop/assets/161261845/d9245555-bc37-48a9-b34f-11c34f3afdf7"> ### Expected behavior _No response_ ### Steps to reproduce installation de prestashop ### PrestaShop version(s) where the bug happened prestashop 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_

Impossible de générer de clé privée à partir de openssl_pkey_new.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Impossible de générer de clé privée à partir de openssl_pkey_new. 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 J'essaye d'installer prestashop mais je tombe sur l'erreur ci-dessous, j'ai essayer de creer un environement comme jai vu sur un tuto mai sca marche toujours pas. Merci d'avance <img width="736" alt="Capture d’écran 2024-03-08 163600" src="https://github.com/PrestaShop/PrestaShop/assets/161261845/d9245555-bc37-48a9-b34f-11c34f3afdf7"> ### Expected behavior _No response_ ### Steps to reproduce installation de prestashop ### PrestaShop version(s) where the bug happened prestashop 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 ! First of all, thank you for your work on this project :) I'm sorry if this issue has been solved somewhere, I've found other similar problems but not one that seems to be fixing what I experience. As you can see in the video attached, everytime I try to update PrestaShop Marketplace, it seems to be failing. I'm not refreshing the page or touching anything, I first get a pop up saying that the upgrade went well but then the notification saying that PS Marketplace should be updated appears again. When I check the logs I can see some errors too (that's what led me to some similar issues) but can't figure them out. Record of my screen : https://www.awesomescreenshot.com/video/25646679?key=4a555ad2ba3eed21c11da549c36f7137 Do you have any idea of what can cause this ? Let me know if you need more information of course. Thanks a lot ! Sasha ### Expected behavior I expect the upgrade to be taken into account ### Steps to reproduce 1. Go in the admin page 2. Try to update PS Marketplace ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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_

PrestaShop Marketplace update impossible

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop Marketplace update impossible 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 ! First of all, thank you for your work on this project :) I'm sorry if this issue has been solved somewhere, I've found other similar problems but not one that seems to be fixing what I experience. As you can see in the video attached, everytime I try to update PrestaShop Marketplace, it seems to be failing. I'm not refreshing the page or touching anything, I first get a pop up saying that the upgrade went well but then the notification saying that PS Marketplace should be updated appears again. When I check the logs I can see some errors too (that's what led me to some similar issues) but can't figure them out. Record of my screen : https://www.awesomescreenshot.com/video/25646679?key=4a555ad2ba3eed21c11da549c36f7137 Do you have any idea of what can cause this ? Let me know if you need more information of course. Thanks a lot ! Sasha ### Expected behavior I expect the upgrade to be taken into account ### Steps to reproduce 1. Go in the admin page 2. Try to update PS Marketplace ### PrestaShop version(s) where the bug happened 1.7.8.7 ### 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 ---

Tested on PR migration - [x] B1: Wrong color input display - [x] B2: Can't add attribute value from the list - [ ] B3: Attribute value list doesn't adapt itself if the attribute type changes - [x] B4: SQL query not working - [ ] B5: Product doesn't adapt when the type of the attribute group changes - [x] B6: Can't add texture This one is handled by https://github.com/PrestaShop/PrestaShop/pull/36068 - [x] B7: Wrong wording titlte - [x] B8: Missing wording and catch the error for the public name missing - [ ] B9: Can't click on the row to view the attribut value list - [ ] B10: Attribute group list is not by default sorted by position I have found a few issues. ## Bug 1 The block Color used to displayed correctly. Now there's one line in the input instead of the chosen color. **Before:** <img width="1209" alt="Screenshot 2024-03-07 at 14 49 33" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/8a407552-ff2f-4799-a3cf-b6e057264b22"> **After:** <img width="1197" alt="Screenshot 2024-03-07 at 14 48 57" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/54692560-ae0e-4363-b1aa-3155b95ad949"> - [ ] Fixed ? ## Bug 2 On the Attributes pages, I could chose to Add new attribute or Add a new value. Now I only have one choice. **Before:** <img width="1222" alt="Screenshot 2024-03-07 at 14 53 36" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/70733f71-9007-47d1-b4f8-9e316636c6c6"> **After:** <img width="1234" alt="Screenshot 2024-03-07 at 14 53 42" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5320d468-d62d-408c-8df1-9876ec40fffb"> - [ ] Fixed ? ## Bug 3 When I add a new value and change the attribute group, the inputs for that attribute are not displayed. In my case, I have to go to my Color attribute and edit it to add a color manually. Steps to reproduce : - Go to BO > Attributes page > View `Paper Type` - Click Add new value button - In Attribute group > Change it to `Color` - The inputs for the color attributes are not automatically displayed :x: Same case the other way around. - Go to BO > Attributes page > View `Color` - Click Add new value button - In Attribute group > Change it to `Dimension` - The inputs for the color attributes are not automatically removed :x: https://github.com/PrestaShop/PrestaShop/assets/16019289/e6524081-c975-4c07-bfb8-fd58b6b82b52 - [ ] Fixed ? --- ## Bug 4 The options `Show SQL Query` and `Export to SQL manager` do not work as expected. The query is different compared to the old page and the export gives a Bad Query. **Before:** <img width="1219" alt="Screenshot 2024-03-07 at 15 33 12" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/ea31e690-7305-4f0f-8608-044b78c4da4c"> **After:** <img width="1215" alt="Screenshot 2024-03-07 at 15 31 32" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/01fdb037-2be4-436d-80c5-44933bf8695b"> - [x] Fixed ? --- ## Bug 5 When I edit the Attribute Color to a Dropdown list Attribute type, it won't refresh my page with the right Attribute Type. On old page, it was well removed. I tried clearing cache from PS and browser. Steps to reproduce : - Edit Color Attribute - Choose Attribute type = Drop-down list > Save - Click View Color - See all the Color column still displayed on the list https://github.com/PrestaShop/PrestaShop/assets/16019289/9fe825e9-0cbc-44ce-bbf0-367e6c8e5f41 The issue is also present on the Product page. When I create a product with combinations, the attributes Color is displayed with a color, when I deleted it. (this last issue is not related to the PR) <img width="629" alt="Screenshot 2024-03-07 at 15 52 15" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/468cd310-e002-42df-96c1-837a6ef74919"> - [ ] Fixed ? --- ## Bug 6 The texture can't be added. The color Black is automatically added. https://github.com/PrestaShop/PrestaShop/assets/16019289/2618d7b1-c277-4fec-bded-ece4faa7b14d - [x] Fixed ? --- ## Bug 7 I have reproduced all of the issues mentioned by @Hlavtox https://github.com/PrestaShop/PrestaShop/pull/35270#pullrequestreview-1864601308 Indeed, when I edit an attribute value, the title of the page is misleading. In my case, it says `Editing attribute Gray`. It should say `Editing attribute value Gray` or `Editing value Gray`. There's no reference on the old page, as it only says "Attributes". <img width="1227" alt="Screenshot 2024-03-07 at 15 08 14" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/84f12771-37c1-421e-8749-a96d9b8ea24a"> - [x] Fixed ? --- ## Bug 8 If you save a new attribute without Public name, you will have an exception. <img width="1220" alt="Screenshot 2024-03-07 at 15 18 39" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/56fea93f-0b12-4d20-b748-aeac0bac413f"> - [x] Fixed ? --- ## Bug 9 Attribute list is not clickable, you have to click on the small View button to get to the list of values. On the old page, you could click on the name AND on the View button. Same issue with Attributes values. you have to click on the Edit button to edit your value. On the old page, you could click on the name AND on the Edit button. https://github.com/PrestaShop/PrestaShop/assets/16019289/a515741a-86ef-4e4f-a02a-2f157950d096 - [ ] Fixed ? ## Bug10 For some reason, when I open a list of attribute values, it automatically opens "rearrange" mode. It doesn't happen in attribute list. Need to adapt the attribut group list <img width="1187" alt="Screenshot 2024-03-07 at 15 58 35" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/de6e8ae4-85de-40c4-92bb-72f94c1aeb56"> - [ ] Fixed ? --- ## Not really a bug but feedbacks ### feedback 1 There's an option to Import your Attributes and attributes values. But in the import of PrestaShop, you have to import `Products` with Attributes in order to get the attributes created. So I think this is misleading and should not be an option. There's no Import type Attributes. <img width="252" alt="Screenshot 2024-03-07 at 15 24 53" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2e101c6d-742d-493d-8015-69456845b099"> ### feedback 2 --- It is not possible to filter by Position anymore. https://github.com/PrestaShop/PrestaShop/issues/11217#issuecomment-661141039 **Before:** <img width="1211" alt="Screenshot 2024-03-07 at 15 57 20" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d9e97c1a-c18d-4288-a032-03bcb5d42f74"> **After:** <img width="1194" alt="Screenshot 2024-03-07 at 15 57 03" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5826747b-642c-464a-ba4c-0a63065d3654"> @MatShir comment: To order you have to select rearrange ### feedback 3 --- The block URL is misleading. It should not say URL. I'm not sure what it was meant to say 🤔 <img width="741" alt="Screenshot 2024-03-07 at 16 09 54" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/07960451-e900-4d95-8953-a9ae7ba92d3c"> Regarding the block Meta Title, I'm not sure how to use it. I added an element, but in the FO, I don't see it anywhere. <img width="764" alt="Screenshot 2024-03-07 at 16 13 38" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5257214d-7d62-4881-88bf-4d8efe62ac4a"> @MatShir comment: You need to insert a path, maybe to check with the content team. It will be a bonus on this PR (not blocking) Waiting for your feedback 😃 Thanks!

Regression on the migrated Attributes pages

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Regression on the migrated Attributes pages Issue date: --- start body --- Tested on PR migration - [x] B1: Wrong color input display - [x] B2: Can't add attribute value from the list - [ ] B3: Attribute value list doesn't adapt itself if the attribute type changes - [x] B4: SQL query not working - [ ] B5: Product doesn't adapt when the type of the attribute group changes - [x] B6: Can't add texture This one is handled by https://github.com/PrestaShop/PrestaShop/pull/36068 - [x] B7: Wrong wording titlte - [x] B8: Missing wording and catch the error for the public name missing - [ ] B9: Can't click on the row to view the attribut value list - [ ] B10: Attribute group list is not by default sorted by position I have found a few issues. ## Bug 1 The block Color used to displayed correctly. Now there's one line in the input instead of the chosen color. **Before:** <img width="1209" alt="Screenshot 2024-03-07 at 14 49 33" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/8a407552-ff2f-4799-a3cf-b6e057264b22"> **After:** <img width="1197" alt="Screenshot 2024-03-07 at 14 48 57" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/54692560-ae0e-4363-b1aa-3155b95ad949"> - [ ] Fixed ? ## Bug 2 On the Attributes pages, I could chose to Add new attribute or Add a new value. Now I only have one choice. **Before:** <img width="1222" alt="Screenshot 2024-03-07 at 14 53 36" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/70733f71-9007-47d1-b4f8-9e316636c6c6"> **After:** <img width="1234" alt="Screenshot 2024-03-07 at 14 53 42" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5320d468-d62d-408c-8df1-9876ec40fffb"> - [ ] Fixed ? ## Bug 3 When I add a new value and change the attribute group, the inputs for that attribute are not displayed. In my case, I have to go to my Color attribute and edit it to add a color manually. Steps to reproduce : - Go to BO > Attributes page > View `Paper Type` - Click Add new value button - In Attribute group > Change it to `Color` - The inputs for the color attributes are not automatically displayed :x: Same case the other way around. - Go to BO > Attributes page > View `Color` - Click Add new value button - In Attribute group > Change it to `Dimension` - The inputs for the color attributes are not automatically removed :x: https://github.com/PrestaShop/PrestaShop/assets/16019289/e6524081-c975-4c07-bfb8-fd58b6b82b52 - [ ] Fixed ? --- ## Bug 4 The options `Show SQL Query` and `Export to SQL manager` do not work as expected. The query is different compared to the old page and the export gives a Bad Query. **Before:** <img width="1219" alt="Screenshot 2024-03-07 at 15 33 12" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/ea31e690-7305-4f0f-8608-044b78c4da4c"> **After:** <img width="1215" alt="Screenshot 2024-03-07 at 15 31 32" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/01fdb037-2be4-436d-80c5-44933bf8695b"> - [x] Fixed ? --- ## Bug 5 When I edit the Attribute Color to a Dropdown list Attribute type, it won't refresh my page with the right Attribute Type. On old page, it was well removed. I tried clearing cache from PS and browser. Steps to reproduce : - Edit Color Attribute - Choose Attribute type = Drop-down list > Save - Click View Color - See all the Color column still displayed on the list https://github.com/PrestaShop/PrestaShop/assets/16019289/9fe825e9-0cbc-44ce-bbf0-367e6c8e5f41 The issue is also present on the Product page. When I create a product with combinations, the attributes Color is displayed with a color, when I deleted it. (this last issue is not related to the PR) <img width="629" alt="Screenshot 2024-03-07 at 15 52 15" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/468cd310-e002-42df-96c1-837a6ef74919"> - [ ] Fixed ? --- ## Bug 6 The texture can't be added. The color Black is automatically added. https://github.com/PrestaShop/PrestaShop/assets/16019289/2618d7b1-c277-4fec-bded-ece4faa7b14d - [x] Fixed ? --- ## Bug 7 I have reproduced all of the issues mentioned by @Hlavtox https://github.com/PrestaShop/PrestaShop/pull/35270#pullrequestreview-1864601308 Indeed, when I edit an attribute value, the title of the page is misleading. In my case, it says `Editing attribute Gray`. It should say `Editing attribute value Gray` or `Editing value Gray`. There's no reference on the old page, as it only says "Attributes". <img width="1227" alt="Screenshot 2024-03-07 at 15 08 14" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/84f12771-37c1-421e-8749-a96d9b8ea24a"> - [x] Fixed ? --- ## Bug 8 If you save a new attribute without Public name, you will have an exception. <img width="1220" alt="Screenshot 2024-03-07 at 15 18 39" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/56fea93f-0b12-4d20-b748-aeac0bac413f"> - [x] Fixed ? --- ## Bug 9 Attribute list is not clickable, you have to click on the small View button to get to the list of values. On the old page, you could click on the name AND on the View button. Same issue with Attributes values. you have to click on the Edit button to edit your value. On the old page, you could click on the name AND on the Edit button. https://github.com/PrestaShop/PrestaShop/assets/16019289/a515741a-86ef-4e4f-a02a-2f157950d096 - [ ] Fixed ? ## Bug10 For some reason, when I open a list of attribute values, it automatically opens "rearrange" mode. It doesn't happen in attribute list. Need to adapt the attribut group list <img width="1187" alt="Screenshot 2024-03-07 at 15 58 35" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/de6e8ae4-85de-40c4-92bb-72f94c1aeb56"> - [ ] Fixed ? --- ## Not really a bug but feedbacks ### feedback 1 There's an option to Import your Attributes and attributes values. But in the import of PrestaShop, you have to import `Products` with Attributes in order to get the attributes created. So I think this is misleading and should not be an option. There's no Import type Attributes. <img width="252" alt="Screenshot 2024-03-07 at 15 24 53" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/2e101c6d-742d-493d-8015-69456845b099"> ### feedback 2 --- It is not possible to filter by Position anymore. https://github.com/PrestaShop/PrestaShop/issues/11217#issuecomment-661141039 **Before:** <img width="1211" alt="Screenshot 2024-03-07 at 15 57 20" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d9e97c1a-c18d-4288-a032-03bcb5d42f74"> **After:** <img width="1194" alt="Screenshot 2024-03-07 at 15 57 03" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5826747b-642c-464a-ba4c-0a63065d3654"> @MatShir comment: To order you have to select rearrange ### feedback 3 --- The block URL is misleading. It should not say URL. I'm not sure what it was meant to say 🤔 <img width="741" alt="Screenshot 2024-03-07 at 16 09 54" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/07960451-e900-4d95-8953-a9ae7ba92d3c"> Regarding the block Meta Title, I'm not sure how to use it. I added an element, but in the FO, I don't see it anywhere. <img width="764" alt="Screenshot 2024-03-07 at 16 13 38" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5257214d-7d62-4881-88bf-4d8efe62ac4a"> @MatShir comment: You need to insert a path, maybe to check with the content team. It will be a bonus on this PR (not blocking) Waiting for your feedback 😃 Thanks! --- 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 want to remove a product customization, and save the product. It gives me the following error: `An unexpected error occurred. [PrestaShop\PrestaShop\Core\Exception\CoreException code 0]: Error occurred when trying to soft delete CustomizationField #1 [Field "deleted" is missing from definition in object model CustomizationField]` Table: customization_field doesn't have a field called: `'deleted'`, but has: `'is_deleted'` See attached video. https://github.com/PrestaShop/PrestaShop/assets/533123/897aff17-e763-4752-b79f-bb3abe679aa7 ### Expected behavior Removing the customization from product without errors. ### Steps to reproduce 1. add product 2. add product customization 3. save product 4. delete product customization ### 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_

Remove Customization from product unexpected error

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Remove Customization from product unexpected error Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When i want to remove a product customization, and save the product. It gives me the following error: `An unexpected error occurred. [PrestaShop\PrestaShop\Core\Exception\CoreException code 0]: Error occurred when trying to soft delete CustomizationField #1 [Field "deleted" is missing from definition in object model CustomizationField]` Table: customization_field doesn't have a field called: `'deleted'`, but has: `'is_deleted'` See attached video. https://github.com/PrestaShop/PrestaShop/assets/533123/897aff17-e763-4752-b79f-bb3abe679aa7 ### Expected behavior Removing the customization from product without errors. ### Steps to reproduce 1. add product 2. add product customization 3. save product 4. delete product customization ### 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 If we remove all the groups of a customer who had the "select all" checkbox checked. an error is displayed when it should only be a notification. https://www.loom.com/share/4ed05e1152c44c889d131321c1815bf3?sid=3db95e05-3065-4633-a88c-75370220bdc7 ### Expected behavior  ### Steps to reproduce 1. BO > Sell > Customers 2. Edit a customer 3. Click to select all 4. Save 5. Edit again this customer 6. uncheck all groups except "select all" 7. Save 8. Error ### 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_

Error 400 when you uncheck a customer's groups

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error 400 when you uncheck a customer's groups 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 we remove all the groups of a customer who had the "select all" checkbox checked. an error is displayed when it should only be a notification. https://www.loom.com/share/4ed05e1152c44c889d131321c1815bf3?sid=3db95e05-3065-4633-a88c-75370220bdc7 ### Expected behavior  ### Steps to reproduce 1. BO > Sell > Customers 2. Edit a customer 3. Click to select all 4. Save 5. Edit again this customer 6. uncheck all groups except "select all" 7. Save 8. Error ### 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 my first install is 8.1.3. I tried updating to 8.1.4 but the Edition Basic mod doesn't work and can't be uninstalled either. Any experience? what exactly is the difference between Prestashop 8 Edition Basic? Can I switch to the regular version? ### Expected behavior _No response_ ### Steps to reproduce 1 click upadate a and then the non-functionality of the Edition Base module. the main page of the administration has changed the template. ### 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_

Prestashop Edition Basic after update doesn't work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop Edition Basic after update doesn't 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 my first install is 8.1.3. I tried updating to 8.1.4 but the Edition Basic mod doesn't work and can't be uninstalled either. Any experience? what exactly is the difference between Prestashop 8 Edition Basic? Can I switch to the regular version? ### Expected behavior _No response_ ### Steps to reproduce 1 click upadate a and then the non-functionality of the Edition Base module. the main page of the administration has changed the template. ### 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, This is the bug -> if you buy a product with customization and combinations, and then you go to check the history of that order or the order confirmation, the row total it's broken. - Product should be: with combinations and customization.  ### Expected behavior Total should be 3.00 instead of 1.00 ( 1.00 it's the original price of the product, 2.00 it's the impact of the combination) ### Steps to reproduce 1. Buy product with combination and customization. 2. Go to checkout, complete the order 3. Here's the order summary that is broken. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 7.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Order Confirmation Table data broken when buying a product with customization

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Order Confirmation Table data broken when buying a product with customization 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, This is the bug -> if you buy a product with customization and combinations, and then you go to check the history of that order or the order confirmation, the row total it's broken. - Product should be: with combinations and customization.  ### Expected behavior Total should be 3.00 instead of 1.00 ( 1.00 it's the original price of the product, 2.00 it's the impact of the combination) ### Steps to reproduce 1. Buy product with combination and customization. 2. Go to checkout, complete the order 3. Here's the order summary that is broken. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 7.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 It appears there's an error in the logic for calculating available carriers. In the scenario of an order that needs to be split between two carriers due to different products requiring different carriers, it's essential to verify that the weight of the products being delivered falls within the defined weight ranges for each carrier. However, the issue arises from the fact that for a particular carrier, instead of calculating the weight of only the products assigned to that carrier, it's taking ianto account the weight of the entire order. During testing, even though this error in checking available carriers exists, it doesn't seem to affect the calculation of the delivery amount. ## Prestashop Version 1.7.8.9 ## Affected Code: In classes/Carrier.php, method getCarriersForOrder() ``` if ($shipping_method == Carrier::SHIPPING_METHOD_WEIGHT && (!Carrier::checkDeliveryPriceByWeight($row['id_carrier'], $cart->getTotalWeight(), $id_zone))) { $error[$carrier->id] = Carrier::SHIPPING_WEIGHT_EXCEPTION; unset($result[$k]); continue; } ``` As you can see in the code block, checkDeliveryPriceByWeight tests for the total weight of the order instead of the weight of all products shipped with the carrier. ### Expected behavior The getCarriersForOrder() method should check for carrier weight compatibility only for the products shipped by this carrier. ### Steps to reproduce - Create two carriers (with setting Disable carrier if weight out of range) - CarrierA : with ranges 0 to 3kg - 10€ - CarrierB : with ranges 0 to 3kg - 5€ - Create two products : - ProductA : weight 2kg - CarrierA - ProductB : weight 2kg - CarrierB - Create an cart from the front office containing : - 1x ProductA - 1x ProductB In this scenario, $cart->getTotalWeight() = 4kg, however none of the carriers allow shipping weights above 3kg. In the checkout page, when proceeding to the carrier selection step : ### With debug enabled 500 error appears with the following stack : (1/1) ContextErrorExceptionNotice: Trying to access array offset on value of type null in DeliveryOptionsFinder.php line 87 ### With debug disabled The customer is presented with an unammed carrier with the shipping amount equal to only one of the shipping carriers correct price (either 5€ or 10€ depending on the position of products in cart). ## Workaround If we extend both the Carrier's weight ranges to allow 4kg (eg. 0kg to 5kg), then the FO shipping price is correct (15€) ### 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). _No response_

Split orders - Incorrect calculation of carrier availability for weight ranges

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Split orders - Incorrect calculation of carrier availability for weight ranges Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments It appears there's an error in the logic for calculating available carriers. In the scenario of an order that needs to be split between two carriers due to different products requiring different carriers, it's essential to verify that the weight of the products being delivered falls within the defined weight ranges for each carrier. However, the issue arises from the fact that for a particular carrier, instead of calculating the weight of only the products assigned to that carrier, it's taking ianto account the weight of the entire order. During testing, even though this error in checking available carriers exists, it doesn't seem to affect the calculation of the delivery amount. ## Prestashop Version 1.7.8.9 ## Affected Code: In classes/Carrier.php, method getCarriersForOrder() ``` if ($shipping_method == Carrier::SHIPPING_METHOD_WEIGHT && (!Carrier::checkDeliveryPriceByWeight($row['id_carrier'], $cart->getTotalWeight(), $id_zone))) { $error[$carrier->id] = Carrier::SHIPPING_WEIGHT_EXCEPTION; unset($result[$k]); continue; } ``` As you can see in the code block, checkDeliveryPriceByWeight tests for the total weight of the order instead of the weight of all products shipped with the carrier. ### Expected behavior The getCarriersForOrder() method should check for carrier weight compatibility only for the products shipped by this carrier. ### Steps to reproduce - Create two carriers (with setting Disable carrier if weight out of range) - CarrierA : with ranges 0 to 3kg - 10€ - CarrierB : with ranges 0 to 3kg - 5€ - Create two products : - ProductA : weight 2kg - CarrierA - ProductB : weight 2kg - CarrierB - Create an cart from the front office containing : - 1x ProductA - 1x ProductB In this scenario, $cart->getTotalWeight() = 4kg, however none of the carriers allow shipping weights above 3kg. In the checkout page, when proceeding to the carrier selection step : ### With debug enabled 500 error appears with the following stack : (1/1) ContextErrorExceptionNotice: Trying to access array offset on value of type null in DeliveryOptionsFinder.php line 87 ### With debug disabled The customer is presented with an unammed carrier with the shipping amount equal to only one of the shipping carriers correct price (either 5€ or 10€ depending on the position of products in cart). ## Workaround If we extend both the Carrier's weight ranges to allow 4kg (eg. 0kg to 5kg), then the FO shipping price is correct (15€) ### 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). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [x] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After enabling this feature, there's no email / contact field for a customer to leave their email / contact when viewing the product which is out of stock. ### Expected behavior addons.prestashop.com/en/emails-notifications/24547-mail-alerts.html -- > Customer notifications: > > Product Availability: when you enable this setting, a field appears on the product page of your shop when the product is out of stock and if you disallow order of out of stock products. It asks your customers to leave their contact information so that they may be contacted when your shop will have this product back in stock.  ### Steps to reproduce Enable feature in PS administration under IMPROVE (left menu / panel) -- Modules > Module Manager > Mail alerts > Configure > Product availability (1st option) ### 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 ps_emailalerts v3.0.0 ### Your company or customer's name goes here (if applicable). _No response_

Mail alerts - Customer notifications - feature "Product Availability" not working

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Mail alerts - Customer notifications - feature "Product Availability" 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 After enabling this feature, there's no email / contact field for a customer to leave their email / contact when viewing the product which is out of stock. ### Expected behavior addons.prestashop.com/en/emails-notifications/24547-mail-alerts.html -- > Customer notifications: > > Product Availability: when you enable this setting, a field appears on the product page of your shop when the product is out of stock and if you disallow order of out of stock products. It asks your customers to leave their contact information so that they may be contacted when your shop will have this product back in stock.  ### Steps to reproduce Enable feature in PS administration under IMPROVE (left menu / panel) -- Modules > Module Manager > Mail alerts > Configure > Product availability (1st option) ### 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 ps_emailalerts v3.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 There is a hook that is getting run before a Swift message is sent in Mail.php send static class method. The name of the hook is actionMailAlterMessageBeforeSend. After inspecting ps_hook table and then hook.xml installation file, I realised this hook is not there even though it is in the Mail class. For this I have created the following PR: https://github.com/PrestaShop/PrestaShop/pull/35544 Please have a look and let me know if you need anything else from me Best ### Expected behavior When you create and install a module with the method hookActionMailAlterMessageBeforeSend, you expect the body of this function to be run when you are sending an email with prestashop, for instance, in the Order page while sending an email with the updates to the customer ### Steps to reproduce 1,Create a simple module with a method hookActionMailAlterMessageBeforeSend 2.In the body method write something like: die('mehod reached'); 3.Install the module 4.Go to a customer order, or create a new testing order 5.Change the order status or send an email to the customer throughout this form The body of the method (die), is not executed and therefore it works without dying as it should have done ### PrestaShop version(s) where the bug happened develop ### 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_

Missing root hook in hook.xml

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Missing root hook in hook.xml Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There is a hook that is getting run before a Swift message is sent in Mail.php send static class method. The name of the hook is actionMailAlterMessageBeforeSend. After inspecting ps_hook table and then hook.xml installation file, I realised this hook is not there even though it is in the Mail class. For this I have created the following PR: https://github.com/PrestaShop/PrestaShop/pull/35544 Please have a look and let me know if you need anything else from me Best ### Expected behavior When you create and install a module with the method hookActionMailAlterMessageBeforeSend, you expect the body of this function to be run when you are sending an email with prestashop, for instance, in the Order page while sending an email with the updates to the customer ### Steps to reproduce 1,Create a simple module with a method hookActionMailAlterMessageBeforeSend 2.In the body method write something like: die('mehod reached'); 3.Install the module 4.Go to a customer order, or create a new testing order 5.Change the order status or send an email to the customer throughout this form The body of the method (die), is not executed and therefore it works without dying as it should have done ### PrestaShop version(s) where the bug happened develop ### 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 Hi everyone, At the check out, the customer data privacy became a 15px font-sized (instead of 14px) after the module having been modified and registered in translations as well as the color turned into a #7a7a7a instead of #232323.   ### Expected behavior After having modified the text, I expected : font-size : 14 px ; color: #232323 ; (as it is below regarding the sign up of the newsletter) :  ### Steps to reproduce 1. Go to BO -> Module Manager -> Customer data privacy block  2. Click on 'Configure' 3. Modify any text and click on 'Save' 4. Go to FO : it changed the font size (15px) and color (#7a7a7a) Then, restart to the step 1 at BO, 2. click on 'Reset' and 3. go check the FO : it's font-sized 14px and colored #232323 again :  ### PrestaShop version(s) where the bug happened 8.1.4 (but maybe before) ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version ps_dataprivacy ### Your company or customer's name goes here (if applicable). Thanks a lot in advance, Regards - Dom

Module ps_dataprivacy - Customer Data Privacy wrong display font-size and color at checkout after customization.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module ps_dataprivacy - Customer Data Privacy wrong display font-size and color at checkout after customization. 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 everyone, At the check out, the customer data privacy became a 15px font-sized (instead of 14px) after the module having been modified and registered in translations as well as the color turned into a #7a7a7a instead of #232323.   ### Expected behavior After having modified the text, I expected : font-size : 14 px ; color: #232323 ; (as it is below regarding the sign up of the newsletter) :  ### Steps to reproduce 1. Go to BO -> Module Manager -> Customer data privacy block  2. Click on 'Configure' 3. Modify any text and click on 'Save' 4. Go to FO : it changed the font size (15px) and color (#7a7a7a) Then, restart to the step 1 at BO, 2. click on 'Reset' and 3. go check the FO : it's font-sized 14px and colored #232323 again :  ### PrestaShop version(s) where the bug happened 8.1.4 (but maybe before) ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version ps_dataprivacy ### Your company or customer's name goes here (if applicable). Thanks a lot in advance, Regards - Dom --- 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 are about to upgrade from 1.6 to 8.1. Right now running a test site (version 8.1) parallel to the production site (version 1.6). Both sites have cache enabled. We have the specials block (ps_specials) active on our homepage. Each month some products have discounts. On the production site old specials are taken off and new specials are displayed. But on the test site it still shows old specials. If you click on "All specials" it shows the new specials. If you return to the homepage it displays the old specials again. If we turn off cache on the test site you can see the new specials on the homepage. But if you reactivate cache it shows the old specials again.  ### Expected behavior We expect behavior like on the old site. When a new special is valid it should show it on the homepage and if a special is no longer valid it should disappear. ### Steps to reproduce 1. Make sure cache is on. 2. Check homepage and special products. 3. Go to products and create a valid special for a product. For example, 10% discount for the month March. 4. Check homepage. No valid special. Click all specials and see the valid special. 5. Turn off caching and check homepage. Valid special should appear. 6. Turn on caching and check homepage. There is no valid special. ### 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 ps_specials v.1.0.2 ### Your company or customer's name goes here (if applicable). _No response_

Specials on homepage are not updated when they are changed with cache on

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Specials on homepage are not updated when they are changed with cache on 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 are about to upgrade from 1.6 to 8.1. Right now running a test site (version 8.1) parallel to the production site (version 1.6). Both sites have cache enabled. We have the specials block (ps_specials) active on our homepage. Each month some products have discounts. On the production site old specials are taken off and new specials are displayed. But on the test site it still shows old specials. If you click on "All specials" it shows the new specials. If you return to the homepage it displays the old specials again. If we turn off cache on the test site you can see the new specials on the homepage. But if you reactivate cache it shows the old specials again.  ### Expected behavior We expect behavior like on the old site. When a new special is valid it should show it on the homepage and if a special is no longer valid it should disappear. ### Steps to reproduce 1. Make sure cache is on. 2. Check homepage and special products. 3. Go to products and create a valid special for a product. For example, 10% discount for the month March. 4. Check homepage. No valid special. Click all specials and see the valid special. 5. Turn off caching and check homepage. Valid special should appear. 6. Turn on caching and check homepage. There is no valid special. ### 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 ps_specials v.1.0.2 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello I have tried to Upgrade my shop with 1click Upgrade. And now i have the message when i try to connect to my admin Unknown locale code: fr-FR [PrestaShop\PrestaShop\Core\Localization\Exception\LocalizationException 0] I have seen past (closed issue) but I haven't found any solution. ### Expected behavior Connect to my admin ### Steps to reproduce 1-Go to 1click Upgrade 2-Made the upgrade from 1.7.5.1 to 8.1 using Major Version Chanel 3-Reconnect to my admin after Update. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version 1 Click Upgrade ### Your company or customer's name goes here (if applicable). _No response_

Unknown locale code: fr-FR [PrestaShop\PrestaShop\Core\Localization\Exception\LocalizationException 0] - Update 1.7.5.1 -> 8.1

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unknown locale code: fr-FR [PrestaShop\PrestaShop\Core\Localization\Exception\LocalizationException 0] - Update 1.7.5.1 -> 8.1 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 have tried to Upgrade my shop with 1click Upgrade. And now i have the message when i try to connect to my admin Unknown locale code: fr-FR [PrestaShop\PrestaShop\Core\Localization\Exception\LocalizationException 0] I have seen past (closed issue) but I haven't found any solution. ### Expected behavior Connect to my admin ### Steps to reproduce 1-Go to 1click Upgrade 2-Made the upgrade from 1.7.5.1 to 8.1 using Major Version Chanel 3-Reconnect to my admin after Update. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version 1 Click Upgrade ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Error page when configuring autoupgrade  ### Expected behavior No errors in configuration display ### Steps to reproduce On a fresh store: 1. Install 1-Click Upgrade module 2. Go to configure 3. See error ### 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 autoupgrade 5.0.1 ### Your company or customer's name goes here (if applicable). _No response_

Error page when configuring autoupgrade

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error page when configuring 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 Error page when configuring autoupgrade  ### Expected behavior No errors in configuration display ### Steps to reproduce On a fresh store: 1. Install 1-Click Upgrade module 2. Go to configure 3. See error ### 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 autoupgrade 5.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 The form rejects any input with error message "Invalid e-mail address" (Adresse e-mail invalide. in French) even though the given e-mail address exists. ### Expected behavior A proper e-mail address should be accepted by the form. ### Steps to reproduce 1. Go to https://www.anjea-skincare.fr/fr 2. Scroll to the footer 3. Try to insert your e-mail address ### PrestaShop version(s) where the bug happened 1.7.8.8 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version ps_emailsubscription v2.8.1 ### Your company or customer's name goes here (if applicable). Anjea Skincare

Inappropriate "Invalid e-mail address" error message

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Inappropriate "Invalid e-mail address" error message 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 form rejects any input with error message "Invalid e-mail address" (Adresse e-mail invalide. in French) even though the given e-mail address exists. ### Expected behavior A proper e-mail address should be accepted by the form. ### Steps to reproduce 1. Go to https://www.anjea-skincare.fr/fr 2. Scroll to the footer 3. Try to insert your e-mail address ### PrestaShop version(s) where the bug happened 1.7.8.8 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version ps_emailsubscription v2.8.1 ### Your company or customer's name goes here (if applicable). Anjea Skincare --- 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'm creating this issue for @Hlavtox. What's wrong? - When you want to download an invoice via a standardized link `https://www.domain.com/index.php?controller=pdf-invoice&id_order=XXXX&secure_key=XXXX`, it doesn't work sometimes. - The condition now says this: `if there is a customer in context and it doesn't match the order customer OR the secure key doesn't match`, die. - So now if you have a perfectly legit link with secure_key, but you are logged in as different customer or start a guest checkout, the link won't work. - So the fix is easy, die only if both of these fail: - If there is a customer in context and it's not the customer of the order. - If there isn't a secure key in the link. ### Expected behavior I should be able to download the invoice. ### Steps to reproduce - Make sure that some guest order exists in a shop and invoice is available for it. - Go to FO, make sure you are logged out. Start a checkout as a guest (without password), no need to fill any addresses. - Now go to guest tracking and try to track the order and try to download an invoice. - You will get white screen and `The invoice was not found.`. - Same situation is when you are logged in in FO as a different customer and you have the link to the invoice in the mail for example. ### 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). _No response_

Impossible to download PDF invoice for guest order

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Impossible to download PDF invoice for guest order 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'm creating this issue for @Hlavtox. What's wrong? - When you want to download an invoice via a standardized link `https://www.domain.com/index.php?controller=pdf-invoice&id_order=XXXX&secure_key=XXXX`, it doesn't work sometimes. - The condition now says this: `if there is a customer in context and it doesn't match the order customer OR the secure key doesn't match`, die. - So now if you have a perfectly legit link with secure_key, but you are logged in as different customer or start a guest checkout, the link won't work. - So the fix is easy, die only if both of these fail: - If there is a customer in context and it's not the customer of the order. - If there isn't a secure key in the link. ### Expected behavior I should be able to download the invoice. ### Steps to reproduce - Make sure that some guest order exists in a shop and invoice is available for it. - Go to FO, make sure you are logged out. Start a checkout as a guest (without password), no need to fill any addresses. - Now go to guest tracking and try to track the order and try to download an invoice. - You will get white screen and `The invoice was not found.`. - Same situation is when you are logged in in FO as a different customer and you have the link to the invoice in the mail for example. ### 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). _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 UI Tests (`tests/UI/campaigns/functional/BO/03_catalog/04_attributesAndFeatures/01_attributes/02_changePosition.ts`), * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the third element on the first, the third become the second :red_circle: It's the same thing on Attribute Value page. (and all other of migrated page with dragndrop rows except for Categories page which works but doesn't use the same component in the grid). ### Expected behavior Adapt all the grid * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the first element on the second, the first becomes the first :heavy_check_mark: ### Steps to reproduce 1. Go to BO 2. Go to "Catalog > Attributes & Features" page (migrated) 3. => * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the third element on the first, the third become the second :red_circle: ### PrestaShop version(s) where the bug happened 9.0.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). @PrestaShopCorp

DragNDrop and Tests UI on the migrated page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : DragNDrop and Tests UI on the migrated 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 In UI Tests (`tests/UI/campaigns/functional/BO/03_catalog/04_attributesAndFeatures/01_attributes/02_changePosition.ts`), * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the third element on the first, the third become the second :red_circle: It's the same thing on Attribute Value page. (and all other of migrated page with dragndrop rows except for Categories page which works but doesn't use the same component in the grid). ### Expected behavior Adapt all the grid * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the first element on the second, the first becomes the first :heavy_check_mark: ### Steps to reproduce 1. Go to BO 2. Go to "Catalog > Attributes & Features" page (migrated) 3. => * when I drag the first element on the third, the first becomes the third :heavy_check_mark: * when I drag the third element on the first, the third become the second :red_circle: ### PrestaShop version(s) where the bug happened 9.0.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). @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 Hi, When using the **"Import" .csv** file system **to update products who are virtual products** with file attachment already uploaded. It result that **the downloadable file datas are updated even if we don't choose to update the related columns** (file_url, nb_downloadable, date_expiration, nb_days_accessible) by reseting the according datas (that are stocked in ps_product_download), including deleting the file in /download/. I think there is nothing that check if we want or not update thoses columns in controllers/admin/AdminImportController.php Observed behavior on Prestashop 1.7.8.10 in a production shop ; reproduced on a new install of 1.7.8.10 in localhost. May do the same on Prestashop 8 as AdminImportController.php has not been modified since concerning the products download related datas. Thanks, Regards ### Expected behavior If you don't select the product download related colum, those informations should not be updated. ### Steps to reproduce 1) create a product as virtual product - with "Does this product have an associated file?" yes - upload a file - put something different than 0 in "Number of allowed downloads", "Expiration date" and/or "Number of days". 2) create a .csv file to update this product. Not all coulmns are needed : same "id" and "name" are enough 3) import that file with the "Advanced Parameters/Import" 4) check you product, the file is deleted, "Number of allowed downloads", "Expiration date" and/or "Number of days" are set back to 0 ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

import virtual products with .csv reset ps_product_download datas

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : import virtual products with .csv reset ps_product_download datas 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, When using the **"Import" .csv** file system **to update products who are virtual products** with file attachment already uploaded. It result that **the downloadable file datas are updated even if we don't choose to update the related columns** (file_url, nb_downloadable, date_expiration, nb_days_accessible) by reseting the according datas (that are stocked in ps_product_download), including deleting the file in /download/. I think there is nothing that check if we want or not update thoses columns in controllers/admin/AdminImportController.php Observed behavior on Prestashop 1.7.8.10 in a production shop ; reproduced on a new install of 1.7.8.10 in localhost. May do the same on Prestashop 8 as AdminImportController.php has not been modified since concerning the products download related datas. Thanks, Regards ### Expected behavior If you don't select the product download related colum, those informations should not be updated. ### Steps to reproduce 1) create a product as virtual product - with "Does this product have an associated file?" yes - upload a file - put something different than 0 in "Number of allowed downloads", "Expiration date" and/or "Number of days". 2) create a .csv file to update this product. Not all coulmns are needed : same "id" and "name" are enough 3) import that file with the "Advanced Parameters/Import" 4) check you product, the file is deleted, "Number of allowed downloads", "Expiration date" and/or "Number of days" are set back to 0 ### PrestaShop version(s) where the bug happened 1.7.8.10 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Image, you have big customer with 200 000 products and there are 2 queries from module ps_facetedsearch. (They are taking 80% of performance -> loading time) I understand usage of two queries, but there is possibility to do it with ONE query and then parse results with PHP. I already tested this in "plain php" and results were great. Now is website category with filter loading 4 seconds, but after this change 2.2 seconds, very big difference. I have only one problem, I don't know how to edit ps_facetedsearch and change behaviour and from 2 queries make one and then from results one query parse results for 2 "use cases". Already consulted with @Hlavtox last year. This edit can be HUGE performance improvement for EVERYONE. Especially for big eshop or PrestaShop on poor hostings. Any expert, who is able to edit funcionality of this module? (I am not able to do this, already tried, but I am not familiar with this module) Query one: `SELECT SQL_NO_CACHE p.id_product, sa.out_of_stock FROM (SELECT p.id_product, p.id_manufacturer, SUM(sa.quantity) as quantity, p.condition, p.weight, p.price, psales.quantity as sales, cp.position FROM ps_product p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) LEFT JOIN ps_product_sale psales ON (psales.id_product = p.id_product) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) INNER JOIN ps_product_shop ps ON (p.id_product = ps.id_product AND ps.id_shop = 1 AND ps.active = TRUE) INNER JOIN ps_category c ON (cp.id_category = c.id_category AND c.active=1) LEFT JOIN ps_category_group cg ON (cg.id_category = c.id_category) WHERE ps.id_shop='1' AND p.visibility IN ('both', 'catalog') AND cg.id_group='1' AND c.nleft&gt;=292 AND c.nright&lt;=293 GROUP BY p.id_product) p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) GROUP BY p.id_product ORDER BY IFNULL(p.quantity, 0) &lt;= 0, IFNULL(p.quantity, 0) &lt;= 0 AND FIELD(sa.out_of_stock, 0) ASC, p.position DESC, p.id_product DESC LIMIT 0, 39 ` Query two: `SELECT SQL_NO_CACHE COUNT(DISTINCT p.id_product) c FROM (SELECT p.id_product, p.id_manufacturer, SUM(sa.quantity) as quantity, p.condition, p.weight, p.price, psales.quantity as sales, cp.position FROM ps_product p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) LEFT JOIN ps_product_sale psales ON (psales.id_product = p.id_product) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) INNER JOIN ps_product_shop ps ON (p.id_product = ps.id_product AND ps.id_shop = 1 AND ps.active = TRUE) INNER JOIN ps_category c ON (cp.id_category = c.id_category AND c.active=1) LEFT JOIN ps_category_group cg ON (cg.id_category = c.id_category) WHERE ps.id_shop='1' AND p.visibility IN ('both', 'catalog') AND cg.id_group='1' AND c.nleft&gt;=292 AND c.nright&lt;=293 GROUP BY p.id_product) p` As you can see, this 2 queries is possible to merge to one query and we need limit 39 there, so we will use than PHP way: array_slice($bla, 0, 39) and we get what we need and save nearly 2 seconds of mysql query + other small changes in query. This queries are nearly same This "feature" is problem X years, nothing new. Same for all module version, php version, prestashop version. Tested on more hostings and PrestaShops - still same results. Not related to any specific enviroment, global problem(feature). **Now can be good time to fix this and make PrestaShop category listing smoother.** ### Expected behavior Only one mysql query with php parsing of results for 2 usage cases. Huge performance improvement. ### Steps to reproduce 1) enable filter for module 2) go to any category 3) enable profiling 4) you will see "duplicite" query ### 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 3.15.0 ### Your company or customer's name goes here (if applicable). openservis.cz

ps_facetedsearch - "duplicite" query - performance killer for e-shop with 200 000 products and for smaller as well

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_facetedsearch - "duplicite" query - performance killer for e-shop with 200 000 products and for smaller as well 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 Image, you have big customer with 200 000 products and there are 2 queries from module ps_facetedsearch. (They are taking 80% of performance -> loading time) I understand usage of two queries, but there is possibility to do it with ONE query and then parse results with PHP. I already tested this in "plain php" and results were great. Now is website category with filter loading 4 seconds, but after this change 2.2 seconds, very big difference. I have only one problem, I don't know how to edit ps_facetedsearch and change behaviour and from 2 queries make one and then from results one query parse results for 2 "use cases". Already consulted with @Hlavtox last year. This edit can be HUGE performance improvement for EVERYONE. Especially for big eshop or PrestaShop on poor hostings. Any expert, who is able to edit funcionality of this module? (I am not able to do this, already tried, but I am not familiar with this module) Query one: `SELECT SQL_NO_CACHE p.id_product, sa.out_of_stock FROM (SELECT p.id_product, p.id_manufacturer, SUM(sa.quantity) as quantity, p.condition, p.weight, p.price, psales.quantity as sales, cp.position FROM ps_product p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) LEFT JOIN ps_product_sale psales ON (psales.id_product = p.id_product) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) INNER JOIN ps_product_shop ps ON (p.id_product = ps.id_product AND ps.id_shop = 1 AND ps.active = TRUE) INNER JOIN ps_category c ON (cp.id_category = c.id_category AND c.active=1) LEFT JOIN ps_category_group cg ON (cg.id_category = c.id_category) WHERE ps.id_shop='1' AND p.visibility IN ('both', 'catalog') AND cg.id_group='1' AND c.nleft&gt;=292 AND c.nright&lt;=293 GROUP BY p.id_product) p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) GROUP BY p.id_product ORDER BY IFNULL(p.quantity, 0) &lt;= 0, IFNULL(p.quantity, 0) &lt;= 0 AND FIELD(sa.out_of_stock, 0) ASC, p.position DESC, p.id_product DESC LIMIT 0, 39 ` Query two: `SELECT SQL_NO_CACHE COUNT(DISTINCT p.id_product) c FROM (SELECT p.id_product, p.id_manufacturer, SUM(sa.quantity) as quantity, p.condition, p.weight, p.price, psales.quantity as sales, cp.position FROM ps_product p LEFT JOIN ps_product_attribute pa ON (p.id_product = pa.id_product) LEFT JOIN ps_product_attribute_combination pac ON (pa.id_product_attribute = pac.id_product_attribute) LEFT JOIN ps_stock_available sa ON (p.id_product = sa.id_product AND IFNULL(pac.id_product_attribute, 0) = sa.id_product_attribute AND sa.id_shop = 1 AND sa.id_shop_group = 0 ) LEFT JOIN ps_product_sale psales ON (psales.id_product = p.id_product) INNER JOIN ps_category_product cp ON (p.id_product = cp.id_product) INNER JOIN ps_product_shop ps ON (p.id_product = ps.id_product AND ps.id_shop = 1 AND ps.active = TRUE) INNER JOIN ps_category c ON (cp.id_category = c.id_category AND c.active=1) LEFT JOIN ps_category_group cg ON (cg.id_category = c.id_category) WHERE ps.id_shop='1' AND p.visibility IN ('both', 'catalog') AND cg.id_group='1' AND c.nleft&gt;=292 AND c.nright&lt;=293 GROUP BY p.id_product) p` As you can see, this 2 queries is possible to merge to one query and we need limit 39 there, so we will use than PHP way: array_slice($bla, 0, 39) and we get what we need and save nearly 2 seconds of mysql query + other small changes in query. This queries are nearly same This "feature" is problem X years, nothing new. Same for all module version, php version, prestashop version. Tested on more hostings and PrestaShops - still same results. Not related to any specific enviroment, global problem(feature). **Now can be good time to fix this and make PrestaShop category listing smoother.** ### Expected behavior Only one mysql query with php parsing of results for 2 usage cases. Huge performance improvement. ### Steps to reproduce 1) enable filter for module 2) go to any category 3) enable profiling 4) you will see "duplicite" query ### 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 3.15.0 ### Your company or customer's name goes here (if applicable). openservis.cz --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrading to PS 8.1.4 and productcomments 6.0.2, upgrade the database schema with doctrine. In the BO, productcomments, it is no longer possible to delete a comment. Why? Docrtine created incorrect foreign keys (run `php bin/console doctrine:schema:update --dump-sql` to see the script that is executed): ``` ALTER TABLE ps_product_comment_report ADD CONSTRAINT FK_C2608AB0ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_usefulness ADD CONSTRAINT FK_49A8F246ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_grade ADD CONSTRAINT FK_A0128571ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_grade ADD CONSTRAINT FK_A01285718375853C FOREIGN KEY (id_product_comment_criterion) REFERENCES ps_product_comment_criterion (id_product_comment_criterion); ``` The first three foreign keys should include `on delete cascade` to allow deletion of a comment (every comment has a related comment_grade, and if someone reported a spam comment, it will probably have a related comment_usefulness and / or comment_report). ### Expected behavior Updating the database schema must not break a backend functionality. Here: it must not break the possibility to delete a comment in the BO ### Steps to reproduce 1. Install PS with productcomments 6.0.2 2. In the BO test if it is possible to delete a comment. If yes: 3. on the command line run `php bin/console doctrine:schema:update --dump-sql` 4. Execute the queries related to productcomments 5. In the BO test if it is possible to delete a comment. It is no longer possible ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1.27 (not related to PHP) ### If your bug is related to a module, specify its name and its version productcomments 6.0.2 ### Your company or customer's name goes here (if applicable). Société Biblique de Genève

productcomments: Incorrect declaration of foreign keys in Doctrine ORM Entity annotations

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : productcomments: Incorrect declaration of foreign keys in Doctrine ORM Entity annotations Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrading to PS 8.1.4 and productcomments 6.0.2, upgrade the database schema with doctrine. In the BO, productcomments, it is no longer possible to delete a comment. Why? Docrtine created incorrect foreign keys (run `php bin/console doctrine:schema:update --dump-sql` to see the script that is executed): ``` ALTER TABLE ps_product_comment_report ADD CONSTRAINT FK_C2608AB0ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_usefulness ADD CONSTRAINT FK_49A8F246ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_grade ADD CONSTRAINT FK_A0128571ACF38A54 FOREIGN KEY (id_product_comment) REFERENCES ps_product_comment (id_product_comment); ALTER TABLE ps_product_comment_grade ADD CONSTRAINT FK_A01285718375853C FOREIGN KEY (id_product_comment_criterion) REFERENCES ps_product_comment_criterion (id_product_comment_criterion); ``` The first three foreign keys should include `on delete cascade` to allow deletion of a comment (every comment has a related comment_grade, and if someone reported a spam comment, it will probably have a related comment_usefulness and / or comment_report). ### Expected behavior Updating the database schema must not break a backend functionality. Here: it must not break the possibility to delete a comment in the BO ### Steps to reproduce 1. Install PS with productcomments 6.0.2 2. In the BO test if it is possible to delete a comment. If yes: 3. on the command line run `php bin/console doctrine:schema:update --dump-sql` 4. Execute the queries related to productcomments 5. In the BO test if it is possible to delete a comment. It is no longer possible ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.1.27 (not related to PHP) ### If your bug is related to a module, specify its name and its version productcomments 6.0.2 ### Your company or customer's name goes here (if applicable). Société Biblique de Genève --- 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 <img width="970" alt="Capture d’écran 2024-02-28 à 17 16 15" src="https://github.com/PrestaShop/PrestaShop/assets/11886419/8649b5fc-2db3-46bf-bbdb-bd757a72c42a"> Hi, on a prestashop 8.1.0 with php 8.1.26 on Infomaniak web hosting server, the dashboard activity is not displaying datas. Informations du serveur : Linux #1 SMP Debian 4.9.210-1+deb9u1~deb8u1 (2020-06-09) x86_64 Version du logiciel serveur : Apache Version de PHP : 8.1.26 Limite de mémoire : 512M Temps maximal d'exécution : 300 Taille max. pour envoi de fichiers : 300M Version de MySQL : 10.4.25-MariaDB-1:10.4.25+maria~stretch-log I check everyhting but nothing explain this. Can you please help me ? Thanks ### Expected behavior Normally we are supposed to see online visitors, carts... ### Steps to reproduce 1. login to backoffice 2. go to dashboard. 3. check left column of dashboard ( Online activity ) ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened 8.0 and 8.1.26 ### If your bug is related to a module, specify its name and its version Dashactivity ### Your company or customer's name goes here (if applicable). bluewave

BO - DashActivity not loading datas

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - DashActivity not loading datas 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 <img width="970" alt="Capture d’écran 2024-02-28 à 17 16 15" src="https://github.com/PrestaShop/PrestaShop/assets/11886419/8649b5fc-2db3-46bf-bbdb-bd757a72c42a"> Hi, on a prestashop 8.1.0 with php 8.1.26 on Infomaniak web hosting server, the dashboard activity is not displaying datas. Informations du serveur : Linux #1 SMP Debian 4.9.210-1+deb9u1~deb8u1 (2020-06-09) x86_64 Version du logiciel serveur : Apache Version de PHP : 8.1.26 Limite de mémoire : 512M Temps maximal d'exécution : 300 Taille max. pour envoi de fichiers : 300M Version de MySQL : 10.4.25-MariaDB-1:10.4.25+maria~stretch-log I check everyhting but nothing explain this. Can you please help me ? Thanks ### Expected behavior Normally we are supposed to see online visitors, carts... ### Steps to reproduce 1. login to backoffice 2. go to dashboard. 3. check left column of dashboard ( Online activity ) ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened 8.0 and 8.1.26 ### If your bug is related to a module, specify its name and its version Dashactivity ### Your company or customer's name goes here (if applicable). bluewave --- 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 updating the database scema to the latest installed version, `php bin/console doctrine:schema:update --dump-sql` showed these lines related to the psgdpr module: ``` ALTER TABLE ps_psgdpr_consent_lang MODIFY id_gdpr_consent INT UNSIGNED NOT NULL; ALTER TABLE ps_psgdpr_consent_lang DROP PRIMARY KEY; ALTER TABLE ps_psgdpr_consent_lang CHANGE id_gdpr_consent id_gdpr_consent INT NOT NULL, CHANGE id_lang id_lang INT NOT NULL, CHANGE id_shop id_shop INT NOT NULL, CHANGE message message VARCHAR(255) NOT NULL; ALTER TABLE ps_psgdpr_consent_lang ADD CONSTRAINT FK_9C2246C9BEB78BEF FOREIGN KEY (id_gdpr_consent) REFERENCES ps_psgdpr_consent (id_gdpr_consent); ALTER TABLE ps_psgdpr_consent_lang ADD CONSTRAINT FK_9C2246C9BA299860 FOREIGN KEY (id_lang) REFERENCES ps_lang (id_lang) ON DELETE CASCADE; CREATE INDEX IDX_9C2246C9BEB78BEF ON ps_psgdpr_consent_lang (id_gdpr_consent); CREATE INDEX IDX_9C2246C9BA299860 ON ps_psgdpr_consent_lang (id_lang); # Bug in psgdpr : id_shop must be included ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang); ``` The last line is incorrect. The table `ps_psgdpr_consent_lang` contains a column `id_shop` that must be part of the primary key. The SQL command will fail, with an error `duplicate key`, because there is a line for each shop in the table. ### Expected behavior `php bin/console doctrine:schema:update --dump-sql` should produce valid output. This means, it must be `ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang, id_shop);` instead of `ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang);` ### Steps to reproduce 1. Install Prestashop, enable multishop and configure at least 2 shops 2. Install the module psgdpr at version 1.4.3 3. Look at the table `PREFIX_psgdpr_consent_lang`, it has a primary key (id_gdpr_consent, id_lang, id_shop). You can also look at the file `modules/psgdpr/sql/install/psgdpr_consent_lang.sql` both for psgdpr 1.4.3 and psgdpr 2.0.1 and find this same definition 4. Update psgdpr to version 2.0.1 5. On the command line run `php bin/console doctrine:schema:update --dump-sql` and observe the output. It will contain a primary key (id_gdpr_consent, id_lang) with id_shop absent. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.0 / 8.1 ### If your bug is related to a module, specify its name and its version psgdpr 2.0.1 ### Your company or customer's name goes here (if applicable). Société Biblique de Genève

Doctrine ORM annotations in psdgpr are not compatible with multishop activated

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Doctrine ORM annotations in psdgpr are not compatible with multishop 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 When updating the database scema to the latest installed version, `php bin/console doctrine:schema:update --dump-sql` showed these lines related to the psgdpr module: ``` ALTER TABLE ps_psgdpr_consent_lang MODIFY id_gdpr_consent INT UNSIGNED NOT NULL; ALTER TABLE ps_psgdpr_consent_lang DROP PRIMARY KEY; ALTER TABLE ps_psgdpr_consent_lang CHANGE id_gdpr_consent id_gdpr_consent INT NOT NULL, CHANGE id_lang id_lang INT NOT NULL, CHANGE id_shop id_shop INT NOT NULL, CHANGE message message VARCHAR(255) NOT NULL; ALTER TABLE ps_psgdpr_consent_lang ADD CONSTRAINT FK_9C2246C9BEB78BEF FOREIGN KEY (id_gdpr_consent) REFERENCES ps_psgdpr_consent (id_gdpr_consent); ALTER TABLE ps_psgdpr_consent_lang ADD CONSTRAINT FK_9C2246C9BA299860 FOREIGN KEY (id_lang) REFERENCES ps_lang (id_lang) ON DELETE CASCADE; CREATE INDEX IDX_9C2246C9BEB78BEF ON ps_psgdpr_consent_lang (id_gdpr_consent); CREATE INDEX IDX_9C2246C9BA299860 ON ps_psgdpr_consent_lang (id_lang); # Bug in psgdpr : id_shop must be included ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang); ``` The last line is incorrect. The table `ps_psgdpr_consent_lang` contains a column `id_shop` that must be part of the primary key. The SQL command will fail, with an error `duplicate key`, because there is a line for each shop in the table. ### Expected behavior `php bin/console doctrine:schema:update --dump-sql` should produce valid output. This means, it must be `ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang, id_shop);` instead of `ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang);` ### Steps to reproduce 1. Install Prestashop, enable multishop and configure at least 2 shops 2. Install the module psgdpr at version 1.4.3 3. Look at the table `PREFIX_psgdpr_consent_lang`, it has a primary key (id_gdpr_consent, id_lang, id_shop). You can also look at the file `modules/psgdpr/sql/install/psgdpr_consent_lang.sql` both for psgdpr 1.4.3 and psgdpr 2.0.1 and find this same definition 4. Update psgdpr to version 2.0.1 5. On the command line run `php bin/console doctrine:schema:update --dump-sql` and observe the output. It will contain a primary key (id_gdpr_consent, id_lang) with id_shop absent. ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.0 / 8.1 ### If your bug is related to a module, specify its name and its version psgdpr 2.0.1 ### Your company or customer's name goes here (if applicable). Société Biblique de Genève --- 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 updated my PHP version from 8.0.30 to 8.1.27 and started to get errors in my log. Note: I activated geolocation in my Prestashop. ``` Deprecated: Return type of GeoIp2\Model\AbstractModel::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice ``` ### Expected behavior Since PS announces compatibility for PHP 8.1, I expect that there are no deprecation notices, even with geolocation activated. ### Steps to reproduce 1. Configure the server to log deprecation notices 2. Enable geolocation in the BO 3. Upgrade from PHP 8.0 to PHP 8.1 ### 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). Société Biblique de Genève

Geolocation in PS 8.1.4 is not compatible with PHP 8.1

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Geolocation in PS 8.1.4 is not compatible with PHP 8.1 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 updated my PHP version from 8.0.30 to 8.1.27 and started to get errors in my log. Note: I activated geolocation in my Prestashop. ``` Deprecated: Return type of GeoIp2\Model\AbstractModel::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice ``` ### Expected behavior Since PS announces compatibility for PHP 8.1, I expect that there are no deprecation notices, even with geolocation activated. ### Steps to reproduce 1. Configure the server to log deprecation notices 2. Enable geolocation in the BO 3. Upgrade from PHP 8.0 to PHP 8.1 ### 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). Société Biblique de Genève --- 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 install bare prestashop without modules and demo products, error in admin area /admin-dev ### Expected behavior expect to work ### Steps to reproduce try to install bare prestashop without modules and demo products, after install open admin area /admin-dev   ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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 rendering "LegacyHeadTag" component

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error rendering "LegacyHeadTag" component 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 install bare prestashop without modules and demo products, error in admin area /admin-dev ### Expected behavior expect to work ### Steps to reproduce try to install bare prestashop without modules and demo products, after install open admin area /admin-dev   ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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 try to install latest dev version and I receive this error: Fatal error: Uncaught LogicException: The annotation metadata driver cannot be enabled because the "doctrine/annotations" library is not installed. Please run "composer require doctrine/annotations" or choose a different metadata driver. in /var/www/vhosts/mydomain.local/prestashop/public_html/vendor/doctrine/orm/lib/Doctrine/ORM/Configuration.php:1 ### Expected behavior why it ask for doctrine/annotations? it is deprecated long time ago you should replace everywhere annotations with attributes https://www.doctrine-project.org/2022/11/04/annotations-to-attributes.html ### Steps to reproduce try to install latest dev version ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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_

"doctrine/annotations" library is not installed

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : "doctrine/annotations" library is not installed 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 try to install latest dev version and I receive this error: Fatal error: Uncaught LogicException: The annotation metadata driver cannot be enabled because the "doctrine/annotations" library is not installed. Please run "composer require doctrine/annotations" or choose a different metadata driver. in /var/www/vhosts/mydomain.local/prestashop/public_html/vendor/doctrine/orm/lib/Doctrine/ORM/Configuration.php:1 ### Expected behavior why it ask for doctrine/annotations? it is deprecated long time ago you should replace everywhere annotations with attributes https://www.doctrine-project.org/2022/11/04/annotations-to-attributes.html ### Steps to reproduce try to install latest dev version ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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 open installed dev : https://mydomain.local/admin-dev/ I receive this error Compile Error: Declaration of PrestaShopBundle\Service\Log\LogHandler::write(array $record): void must be compatible with Monolog\Handler\AbstractProcessingHandler::write(Monolog\LogRecord $record): void ### Expected behavior expected to work ### Steps to reproduce install fresh dev, go to admin area  ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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_ 

Compile Error:

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Compile Error: Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments when I open installed dev : https://mydomain.local/admin-dev/ I receive this error Compile Error: Declaration of PrestaShopBundle\Service\Log\LogHandler::write(array $record): void must be compatible with Monolog\Handler\AbstractProcessingHandler::write(Monolog\LogRecord $record): void ### Expected behavior expected to work ### Steps to reproduce install fresh dev, go to admin area  ### PrestaShop version(s) where the bug happened dev ### PHP version(s) where the bug happened 8.2.9 ### 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, On a live website with Multishop enabled, 2 shop groups and 2 shops on different domains, we have the same products but we are using different languages. In ps_shop the id's are 1 and 2 for id_shop and for id_shop_group 1 and 2. We are tryng to do a stock update and some other queries that use LEFT JOIN, but we cannot use id_shop or id_shop_group as a key in ps_stock_available, because in this table we also have the 0 value and if we are trying to correct the id's (already tested), Prestashop considers/show stock 0 in backend as well as in frontend. Please see the attachments. Is it a normal behaviour, or why do we have that 0 values? If we leave it as it is now, everything is working fine.   ### Expected behavior In ps_stock_available id_shop=1 and id_shop_group=1 on the first line, and id_shop=2 and id_shop_group=2 ### Steps to reproduce 1. Activate MultiShop 2. Add 2 stores 3. Set different stock values for a product for each store. ### PrestaShop version(s) where the bug happened 1.7.8.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ECOMPRO CONVERSION SRL

v.1.7.8.3 In multishop context, table ps_stock_available uses different id's for id_shop and id_shop_group than I have in ps_shop

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : v.1.7.8.3 In multishop context, table ps_stock_available uses different id's for id_shop and id_shop_group than I have in ps_shop Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello, On a live website with Multishop enabled, 2 shop groups and 2 shops on different domains, we have the same products but we are using different languages. In ps_shop the id's are 1 and 2 for id_shop and for id_shop_group 1 and 2. We are tryng to do a stock update and some other queries that use LEFT JOIN, but we cannot use id_shop or id_shop_group as a key in ps_stock_available, because in this table we also have the 0 value and if we are trying to correct the id's (already tested), Prestashop considers/show stock 0 in backend as well as in frontend. Please see the attachments. Is it a normal behaviour, or why do we have that 0 values? If we leave it as it is now, everything is working fine.   ### Expected behavior In ps_stock_available id_shop=1 and id_shop_group=1 on the first line, and id_shop=2 and id_shop_group=2 ### Steps to reproduce 1. Activate MultiShop 2. Add 2 stores 3. Set different stock values for a product for each store. ### PrestaShop version(s) where the bug happened 1.7.8.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). ECOMPRO CONVERSION SRL --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I " ADD a product" manually from the order details, New product was added at the last row https://prnt.sc/2e3rSRFJ9bxY We expect New products would be added from the last part and easy to manage. But it is adding Randomly to anywhere. Can you please fix the adding rule will be fixed and New products would be added last part? ### Expected behavior _No response_ ### Steps to reproduce 1. Go to Orders 2. from any order 3. From products part, click Add a product button ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

When adding products to order in BO, they are added to the list randomly, not to the end

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : When adding products to order in BO, they are added to the list randomly, not to the end Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I " ADD a product" manually from the order details, New product was added at the last row https://prnt.sc/2e3rSRFJ9bxY We expect New products would be added from the last part and easy to manage. But it is adding Randomly to anywhere. Can you please fix the adding rule will be fixed and New products would be added last part? ### Expected behavior _No response_ ### Steps to reproduce 1. Go to Orders 2. from any order 3. From products part, click Add a product button ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Is your feature request related to a problem? It is a problem for SEO not to have this function add redirection function 301 or 302 on category page I am always frustrated when I see that Prestashop has set up on the product pages the 301 or 302 redirects to another product or category and that this has not been done also for the category pages ### Describe the solution you'd like We could take a large part of the code of the product page to adapt it to the category page and to redirect 301 or 302 to another category page or to choose why not a CMS page in order to keep the SEO referencing of this category ### Specs Below the form group of the **Friendly URL**, add the form group **Redirection when not displayed**. The form group is composed of the label **"Redirection when not displayed"** and a dropdown with 4 options: - Permanent redirection to a category (301) - Temporary redirection to a category (302) - No redirection (404), display error page - No redirection (410), display error page The default value is “Permanent redirection to a category (301)” with default category select ("Home") if it is the root category, only list: - No redirection (404), display error page - No redirection (410), display error page The default value is "No redirection (410)" When “Permanent redirection to a category (301)” or “Temporary redirection to a category (302)” is selected Then **Target category** field is displayed. This search field is displayed if you select in the dropdown Permanent redirection to a category or Temporary redirection to a category. There is a placeholder: `“To which category the page should redirect ?”` If no category is selected, the Home Category is used. You can search by category name. When you start typing, if there are results, they are displayed under and you can click on it. Then, the selected category is displayed under the field. Information message is displayed below the droplist: ``` "Permanent redirection (301) = Permanently display another category instead. Temporary redirection (302) = Temporarily display another category instead. No redirection (404), display error page = Do not redirect anywhere and display a 404 "Not Found" page. No redirection (410), display error page = Do not redirect anywhere and display a 410 "Gone" page." ``` Upgrade to take into account ### Acceptance test When the categories X is not displayed and set at Permanent redirection to a category (301) Then on the FO the category page direct link displays the http error 301 page

Add a redirection function 301 or 302 on Category page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Add a redirection function 301 or 302 on Category page Issue date: --- start body --- ### Is your feature request related to a problem? It is a problem for SEO not to have this function add redirection function 301 or 302 on category page I am always frustrated when I see that Prestashop has set up on the product pages the 301 or 302 redirects to another product or category and that this has not been done also for the category pages ### Describe the solution you'd like We could take a large part of the code of the product page to adapt it to the category page and to redirect 301 or 302 to another category page or to choose why not a CMS page in order to keep the SEO referencing of this category ### Specs Below the form group of the **Friendly URL**, add the form group **Redirection when not displayed**. The form group is composed of the label **"Redirection when not displayed"** and a dropdown with 4 options: - Permanent redirection to a category (301) - Temporary redirection to a category (302) - No redirection (404), display error page - No redirection (410), display error page The default value is “Permanent redirection to a category (301)” with default category select ("Home") if it is the root category, only list: - No redirection (404), display error page - No redirection (410), display error page The default value is "No redirection (410)" When “Permanent redirection to a category (301)” or “Temporary redirection to a category (302)” is selected Then **Target category** field is displayed. This search field is displayed if you select in the dropdown Permanent redirection to a category or Temporary redirection to a category. There is a placeholder: `“To which category the page should redirect ?”` If no category is selected, the Home Category is used. You can search by category name. When you start typing, if there are results, they are displayed under and you can click on it. Then, the selected category is displayed under the field. Information message is displayed below the droplist: ``` "Permanent redirection (301) = Permanently display another category instead. Temporary redirection (302) = Temporarily display another category instead. No redirection (404), display error page = Do not redirect anywhere and display a 404 "Not Found" page. No redirection (410), display error page = Do not redirect anywhere and display a 410 "Gone" page." ``` Upgrade to take into account ### Acceptance test When the categories X is not displayed and set at Permanent redirection to a category (301) Then on the FO the category page direct link displays the http error 301 page --- end body --- comments : --- start comments --- --- end comments ---

**US** As a merchant, I want to be able to sort the feature position to follow a display logic of my product feature. **Specs** - Add position column on the feature value page. New db filed - Add endpoint to update position - Drag and drop row like on feature group page Sort by position is selected by default - Upgrade PR to do - To adadpt the theme classic and HB, the features from the same feature group follows the position orders and place at the end the custom value **Acceptance test** Go on composition Drag Polyester below Wool Check FO Wool is before Polyester cf https://github.com/PrestaShop/PrestaShop/discussions/32267

Add possibility to change position of feature values

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Add possibility to change position of feature values Issue date: --- start body --- **US** As a merchant, I want to be able to sort the feature position to follow a display logic of my product feature. **Specs** - Add position column on the feature value page. New db filed - Add endpoint to update position - Drag and drop row like on feature group page Sort by position is selected by default - Upgrade PR to do - To adadpt the theme classic and HB, the features from the same feature group follows the position orders and place at the end the custom value **Acceptance test** Go on composition Drag Polyester below Wool Check FO Wool is before Polyester cf https://github.com/PrestaShop/PrestaShop/discussions/32267 --- 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 Even though I have the Product Availability option enabled in the Email alerts module, I don't see the address field and submit button on the product tab. We are trying to hook module "Email Alert" for product page position name "displayProductAdditionalInfo" but i can see in store admin panel there is js related console error so, we can not hook module ### Expected behavior Email alert on product page ### Steps to reproduce 1. Go to on product page on [https://www.srubky.sk](url) 2. The field for the email address and the send button are not displayed on the product page ### PrestaShop version(s) where the bug happened 8.0.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_emailalerts ### Your company or customer's name goes here (if applicable). Stealthtech, s.r.o.

Email alert problém

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Email alert problém 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 Even though I have the Product Availability option enabled in the Email alerts module, I don't see the address field and submit button on the product tab. We are trying to hook module "Email Alert" for product page position name "displayProductAdditionalInfo" but i can see in store admin panel there is js related console error so, we can not hook module ### Expected behavior Email alert on product page ### Steps to reproduce 1. Go to on product page on [https://www.srubky.sk](url) 2. The field for the email address and the send button are not displayed on the product page ### PrestaShop version(s) where the bug happened 8.0.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_emailalerts ### Your company or customer's name goes here (if applicable). Stealthtech, s.r.o. --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments During the installation process, if PHP is not compiled with the '--with-jpeg' flag, attempting to install (template step) - results in an HTTP 500 error. This issue poses a significant challenge for regular users who may not be aware of the underlying cause. trace: ``` Attempted to call function "imagecreatefromjpeg" from the global namespace. (1/1) UndefinedFunctionException Attempted to call function "imagecreatefromjpeg" from the global namespace. in ImageManager.php line 619 at ImageManagerCore::create(2, '/www/hidden.pl/install/langs/bs/img/bs.jpg') in ImageManager.php line 318 at ImageManagerCore::resize('/www/hidden.pl/install/langs/bs/img/bs.jpg', '/www/hidden.pl/img/p/bs-default-cart_default.jpg', 125, 125) in Install.php line 712 at Install->copyLanguageImages('bs') in Install.php line 1191 at Install->installTheme('classic') in process.php line 294 at InstallControllerHttpProcess->processInstallTheme() in process.php line 104 at InstallControllerHttpProcess->process() in controllerHttp.php line 277 at InstallControllerHttp::execute() in index.php line 53 ``` ### Expected behavior _No response_ ### Steps to reproduce 1. Begin a fresh installation of the software. 2. Ensure that PHP is not compiled with the '--with-jpeg' flag. 3. Attempt to install ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

UndefinedFunctionException - Attempted to call function "imagecreatefromjpeg" from the global namespace.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : UndefinedFunctionException - Attempted to call function "imagecreatefromjpeg" from the global namespace. Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments During the installation process, if PHP is not compiled with the '--with-jpeg' flag, attempting to install (template step) - results in an HTTP 500 error. This issue poses a significant challenge for regular users who may not be aware of the underlying cause. trace: ``` Attempted to call function "imagecreatefromjpeg" from the global namespace. (1/1) UndefinedFunctionException Attempted to call function "imagecreatefromjpeg" from the global namespace. in ImageManager.php line 619 at ImageManagerCore::create(2, '/www/hidden.pl/install/langs/bs/img/bs.jpg') in ImageManager.php line 318 at ImageManagerCore::resize('/www/hidden.pl/install/langs/bs/img/bs.jpg', '/www/hidden.pl/img/p/bs-default-cart_default.jpg', 125, 125) in Install.php line 712 at Install->copyLanguageImages('bs') in Install.php line 1191 at Install->installTheme('classic') in process.php line 294 at InstallControllerHttpProcess->processInstallTheme() in process.php line 104 at InstallControllerHttpProcess->process() in controllerHttp.php line 277 at InstallControllerHttp::execute() in index.php line 53 ``` ### Expected behavior _No response_ ### Steps to reproduce 1. Begin a fresh installation of the software. 2. Ensure that PHP is not compiled with the '--with-jpeg' flag. 3. Attempt to install ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I installed Prestashop Email Aleart and when admin change order details, I set to notify customers about "order edit" But email is not sent. Even though admin change the order details, "Email NOtification to customer about order edit" does not work ### Expected behavior _No response_ ### Steps to reproduce 1. Go to Module " Email Alert" by prestashop 2. Enable Customer notification about ORder Edit ### PrestaShop version(s) where the bug happened 1.8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Prestashp Email Alert Module - Order Edit email is not sent

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashp Email Alert Module - Order Edit email is not sent 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 installed Prestashop Email Aleart and when admin change order details, I set to notify customers about "order edit" But email is not sent. Even though admin change the order details, "Email NOtification to customer about order edit" does not work ### Expected behavior _No response_ ### Steps to reproduce 1. Go to Module " Email Alert" by prestashop 2. Enable Customer notification about ORder Edit ### PrestaShop version(s) where the bug happened 1.8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments I issued a refund from " Partial Refund" Button from prestashop One of two items is sold out and I issued a paypal refund withint prestashop admin page And I need Corrected / New invoice for customer But I cannot get the new invoice after partial refund ### Expected behavior _No response_ ### Steps to reproduce 1. Orders 2. Choose any order and Partial Refund 3. View Invoice ### PrestaShop version(s) where the bug happened 1.8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). dhglobal

Prestashop 1.8.1 Invoice cannot be issued again with right amount after Partial refund

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 1.8.1 Invoice cannot be issued again with right amount after Partial refund 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 issued a refund from " Partial Refund" Button from prestashop One of two items is sold out and I issued a paypal refund withint prestashop admin page And I need Corrected / New invoice for customer But I cannot get the new invoice after partial refund ### Expected behavior _No response_ ### Steps to reproduce 1. Orders 2. Choose any order and Partial Refund 3. View Invoice ### PrestaShop version(s) where the bug happened 1.8.1 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). dhglobal --- end body --- comments : --- start comments --- --- end comments ---

**Issue encounter** I have not yet discovered the reason behind the loop redirect issue when accessing the BO. This problem seems to be present in the Docker version of PrestaShop from a Nightly image when the Symphony Layout is enabled. **Expected behavior** Nightly docker image should work with the Symphony Layout enabled. **Acceptance test** Docker nightly should work

Symfony Layout with the nightly docker image doesn't work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Symfony Layout with the nightly docker image doesn't work Issue date: --- start body --- **Issue encounter** I have not yet discovered the reason behind the loop redirect issue when accessing the BO. This problem seems to be present in the Docker version of PrestaShop from a Nightly image when the Symphony Layout is enabled. **Expected behavior** Nightly docker image should work with the Symphony Layout enabled. **Acceptance test** Docker nightly should work --- end body --- comments : --- start comments --- --- end comments ---

### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/35484 <div type='discussions-op-text'> ^{Originally posted by **ChronoBrake** February 26, 2024} Hey, where i can find "export" button on the new product page v2 list? It's looks like is missing. How i can add it manually?</div>

Export button missing on new Product Page V2

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Export button missing on new Product Page V2 Issue date: --- start body --- ### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/35484 <div type='discussions-op-text'> ^{Originally posted by **ChronoBrake** February 26, 2024} Hey, where i can find "export" button on the new product page v2 list? It's looks like is missing. How i can add it manually?</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 On my FO, when I click on the color white for the product Hummingbird printed t-shirt, Im redirect to the product page with variants M and White, instead of S and White. https://github.com/PrestaShop/PrestaShop/assets/16019289/eddfb25c-6e75-4c24-ba7c-1decabd5acf1 My default combination is S and White : <img width="1186" alt="Screenshot 2024-02-26 at 16 14 38" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/db88efb7-b362-4d46-8e3b-45ab45f2e98d"> ### Expected behavior The default color and size should be displayed when I click on the variant choice. In my case, S and White. ### Steps to reproduce 1. Go to FO > Homepage > Scroll down to Hummingbird printed t-shirt 2. Click on the color combination "white" 3. See the color combination is white ✅ but the size is M, it should be S :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_

FO > When clicking on a variation, the default combination is not displayed on the product page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO > When clicking on a variation, the default combination is not displayed on the product 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 On my FO, when I click on the color white for the product Hummingbird printed t-shirt, Im redirect to the product page with variants M and White, instead of S and White. https://github.com/PrestaShop/PrestaShop/assets/16019289/eddfb25c-6e75-4c24-ba7c-1decabd5acf1 My default combination is S and White : <img width="1186" alt="Screenshot 2024-02-26 at 16 14 38" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/db88efb7-b362-4d46-8e3b-45ab45f2e98d"> ### Expected behavior The default color and size should be displayed when I click on the variant choice. In my case, S and White. ### Steps to reproduce 1. Go to FO > Homepage > Scroll down to Hummingbird printed t-shirt 2. Click on the color combination "white" 3. See the color combination is white ✅ but the size is M, it should be S :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 When I add a product with customization to an order, when the same customization is added, it should not add another product, but it should increase the quantity of the existing product. https://github.com/PrestaShop/PrestaShop/assets/16019289/e7eb0a1a-5177-44d9-8fbe-d958d37b162c ### Expected behavior Exact same customization should be detected and stacked. ### Steps to reproduce 1. Go to BO > Orders > Add an order > Choose Customer 2. Choose "Customizable mug" > Add a Customization "hello" > Add to cart 3. Click again on Add to cart 4. 2 entities of the same products with the same custom are added :x: ### PrestaShop version(s) where the bug happened 8.1.3, develop ### 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). Symcon GmbH

BO - Order Creation - Customizable product with same customization can be added to an order individually

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - Order Creation - Customizable product with same customization can be added to an order individually Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I add a product with customization to an order, when the same customization is added, it should not add another product, but it should increase the quantity of the existing product. https://github.com/PrestaShop/PrestaShop/assets/16019289/e7eb0a1a-5177-44d9-8fbe-d958d37b162c ### Expected behavior Exact same customization should be detected and stacked. ### Steps to reproduce 1. Go to BO > Orders > Add an order > Choose Customer 2. Choose "Customizable mug" > Add a Customization "hello" > Add to cart 3. Click again on Add to cart 4. 2 entities of the same products with the same custom are added :x: ### PrestaShop version(s) where the bug happened 8.1.3, develop ### 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). Symcon GmbH --- 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 I didn't find an exact Issue Describing it, but some Really close ones: If I want to Order 2 Different Products, one with a Free shipping digital Delivery (With Variations so not a virtual Product) and the Other with DHL Delivery Both Options Are Configured one Item is only Virtual, and the Other is a Physical Product so need to be shipped. After I order the Products, the Order is Spit according to the Carrier Option(DHL and Virtual Product Delivery). And only one Order Overview is showing with only one Product, so the Customer Only Sees the One Product ordered in the Browser. But is Send 2 Emails with the Order Overview. Cart:  Sometimes Displays: "Digital Versand" (Virtual Product Delivery) some time DHL and always Displays the Fee for the Highest Price but with Wrong name.  only one tab with Order Confirmation and only one Product contained:  Next Issue: there is no option as far as I could research To not Split the Order and just use the highest Delivery Option if one is free. ### Expected behavior Both Products Should either be contained in one Order with Product Specific Delivery or split but shows both Order Confirmations, so the Customer is Informed in the Browser that all the Product will be delivered. On top of that, the Delivery Option Should not be displayed one as there are two different Delivery Options (But I can live with one if I can set the name reliably to DHL at the moment I think it's Last added or something like this). ### Steps to reproduce Complicated: 1. Add 2 products with Variants 2. Add 2 Delivery Options one Free, one with Fee 3. Assign the 2 Products Different Delivery Options 4. Add Both Products to the Cart and Order ### PrestaShop version(s) where the bug happened 1.8.3 ### PHP version(s) where the bug happened 8.1.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Symcon GmbH

Multiple Carrier Options, splitting the order even if one option is free shipping only one Order Overview.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Multiple Carrier Options, splitting the order even if one option is free shipping only one Order Overview. 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 I didn't find an exact Issue Describing it, but some Really close ones: If I want to Order 2 Different Products, one with a Free shipping digital Delivery (With Variations so not a virtual Product) and the Other with DHL Delivery Both Options Are Configured one Item is only Virtual, and the Other is a Physical Product so need to be shipped. After I order the Products, the Order is Spit according to the Carrier Option(DHL and Virtual Product Delivery). And only one Order Overview is showing with only one Product, so the Customer Only Sees the One Product ordered in the Browser. But is Send 2 Emails with the Order Overview. Cart:  Sometimes Displays: "Digital Versand" (Virtual Product Delivery) some time DHL and always Displays the Fee for the Highest Price but with Wrong name.  only one tab with Order Confirmation and only one Product contained:  Next Issue: there is no option as far as I could research To not Split the Order and just use the highest Delivery Option if one is free. ### Expected behavior Both Products Should either be contained in one Order with Product Specific Delivery or split but shows both Order Confirmations, so the Customer is Informed in the Browser that all the Product will be delivered. On top of that, the Delivery Option Should not be displayed one as there are two different Delivery Options (But I can live with one if I can set the name reliably to DHL at the moment I think it's Last added or something like this). ### Steps to reproduce Complicated: 1. Add 2 products with Variants 2. Add 2 Delivery Options one Free, one with Fee 3. Assign the 2 Products Different Delivery Options 4. Add Both Products to the Cart and Order ### PrestaShop version(s) where the bug happened 1.8.3 ### PHP version(s) where the bug happened 8.1.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Symcon GmbH --- 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 Screenshots:    ### Expected behavior There should be no error. ### Steps to reproduce 1. Make sure you are using PHP 8.3 2. Browse the back office with debug mode enabled. ### PrestaShop version(s) where the bug happened 9.0.0 ### PHP version(s) where the bug happened 8.3.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Warning: Undefined property across back office with PS 9 and PHP 8.3

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Warning: Undefined property across back office with PS 9 and PHP 8.3 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Screenshots:    ### Expected behavior There should be no error. ### Steps to reproduce 1. Make sure you are using PHP 8.3 2. Browse the back office with debug mode enabled. ### PrestaShop version(s) where the bug happened 9.0.0 ### PHP version(s) where the bug happened 8.3.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments If you enable Symfony layout for the back office in feature flags, the built-in profiler doesn't show up. ### Expected behavior Profiler should work as before because otherwise, it is impossible to easily debug the performance of queries coming from legacy, etc. ### Steps to reproduce 1. Enable Symfony layout in feature flags. 2. Edit config/defines.inc.php and change `_PS_DEBUG_PROFILING_` to `true` 3. See that the profiler doesn't show with Symfony layout, but it is available if Symfony layout is disabled. ### 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). _No response_

PrestaShop debug profiler doesn't work with Symfony layout

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestaShop debug profiler doesn't work with 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 If you enable Symfony layout for the back office in feature flags, the built-in profiler doesn't show up. ### Expected behavior Profiler should work as before because otherwise, it is impossible to easily debug the performance of queries coming from legacy, etc. ### Steps to reproduce 1. Enable Symfony layout in feature flags. 2. Edit config/defines.inc.php and change `_PS_DEBUG_PROFILING_` to `true` 3. See that the profiler doesn't show with Symfony layout, but it is available if Symfony layout is disabled. ### 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). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

**Specs** - Investigation and dev to change api url to "/bo/api" The path is still to be defined. "/bo/api" is path test name for the purpose of the POC. -- Why ? - When change the admin dev name -> easier to maintain - No need to have all the admin name each time a dev/module want to use the API - Security, won't need to communicate the admin path **Acceptance** All the endpoints are reachable from the selected path

Update the URL path of the new API

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Update the URL path of the new API Issue date: --- start body --- **Specs** - Investigation and dev to change api url to "/bo/api" The path is still to be defined. "/bo/api" is path test name for the purpose of the POC. -- Why ? - When change the admin dev name -> easier to maintain - No need to have all the admin name each time a dev/module want to use the API - Security, won't need to communicate the admin path **Acceptance** All the endpoints are reachable from the selected path --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There is a problem with the specific prices. Example : 1. We create a specific price on a variation of a product 2. We create a specific price on all variations of the product, with a minimum of products to purchase: 2 3. in the front office the discounted price does not change if you take 2 quantities. He remains stuck on the specific price of point n°1 <img width="1648" alt="doesnt-work" src="https://github.com/PrestaShop/PrestaShop/assets/5530905/c1819960-bbdb-4b76-8036-6fb56ebf4f19"> ---- Note: Works if you do not put all the variations, but with only one variation of the product <img width="1641" alt="work" src="https://github.com/PrestaShop/PrestaShop/assets/5530905/260d91c9-88dc-4aa1-bc1f-f4b5cb2a30e3"> ### Expected behavior _No response_ ### Steps to reproduce 1. We create a specific price on a variation of a product 2. We create a specific price on all variations of the product, with a minimum of products to purchase: 2 3. in the front office the discounted price does not change if you take 2 quantities. He remains stuck on the specific price of point n°1 https://github.com/PrestaShop/PrestaShop/assets/5530905/ffc9c7a1-5d4d-4c5b-aa81-31aea7784de2 ### PrestaShop version(s) where the bug happened 1.7.8.10 ### 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). Kosmo

Bug with specific prices

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Bug with specific 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 There is a problem with the specific prices. Example : 1. We create a specific price on a variation of a product 2. We create a specific price on all variations of the product, with a minimum of products to purchase: 2 3. in the front office the discounted price does not change if you take 2 quantities. He remains stuck on the specific price of point n°1 <img width="1648" alt="doesnt-work" src="https://github.com/PrestaShop/PrestaShop/assets/5530905/c1819960-bbdb-4b76-8036-6fb56ebf4f19"> ---- Note: Works if you do not put all the variations, but with only one variation of the product <img width="1641" alt="work" src="https://github.com/PrestaShop/PrestaShop/assets/5530905/260d91c9-88dc-4aa1-bc1f-f4b5cb2a30e3"> ### Expected behavior _No response_ ### Steps to reproduce 1. We create a specific price on a variation of a product 2. We create a specific price on all variations of the product, with a minimum of products to purchase: 2 3. in the front office the discounted price does not change if you take 2 quantities. He remains stuck on the specific price of point n°1 https://github.com/PrestaShop/PrestaShop/assets/5530905/ffc9c7a1-5d4d-4c5b-aa81-31aea7784de2 ### PrestaShop version(s) where the bug happened 1.7.8.10 ### 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). Kosmo --- 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 you can see from the image enclosed:  I cannot edit anymore any text in the website since the Text Formatting Bar is not visible anymore. How can i solve that? ### Expected behavior The expected behaviour is the Text Formatting Bar visible as in this image:  ### Steps to reproduce go to Design/Pages and try to edit any page ### 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_

Text Formatting Bar disappeared

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Text Formatting Bar disappeared 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 you can see from the image enclosed:  I cannot edit anymore any text in the website since the Text Formatting Bar is not visible anymore. How can i solve that? ### Expected behavior The expected behaviour is the Text Formatting Bar visible as in this image:  ### Steps to reproduce go to Design/Pages and try to edit any page ### 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 The stock is incorrect when I Re-stock a product + I change the status of the order to Canceled. https://github.com/PrestaShop/PrestaShop/assets/16019289/3d2ef22a-5a84-4f37-9f70-6eb8a1f88d9d ### Expected behavior The stock should be should not exceed the initial quantity ### Steps to reproduce 1. Create a product with stock 100 2. Place an order with of that product 3. Stock is 99 ✅ 4. Change status to "Payment accepted" 5. Partially refund the order > Check “Re-stock products” option 6. Stock is 100 ✅ 7. Change status to “Canceled” 8. See the stock is 101 :x: it should stay at 100 ### PrestaShop version(s) where the bug happened 8.1.3, develop ### PHP version(s) where the bug happened 8.1.18 ### 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 > When I restock a product and Cancel the order, the product stock exceed the initial quantity

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - Orders > When I restock a product and Cancel the order, the product stock exceed the initial quantity 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 stock is incorrect when I Re-stock a product + I change the status of the order to Canceled. https://github.com/PrestaShop/PrestaShop/assets/16019289/3d2ef22a-5a84-4f37-9f70-6eb8a1f88d9d ### Expected behavior The stock should be should not exceed the initial quantity ### Steps to reproduce 1. Create a product with stock 100 2. Place an order with of that product 3. Stock is 99 ✅ 4. Change status to "Payment accepted" 5. Partially refund the order > Check “Re-stock products” option 6. Stock is 100 ✅ 7. Change status to “Canceled” 8. See the stock is 101 :x: it should stay at 100 ### PrestaShop version(s) where the bug happened 8.1.3, develop ### PHP version(s) where the bug happened 8.1.18 ### 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 a problem with displaying product availability in the Faceted search module. Availability is showing correctly for some products. "In stock" and "Unavailable". See image good.png But for some it shows me like this: "In stock" "Available" and "Unavailable" See image bad.png. It should only show "In Stock" or "Available" and "Unavailable". There should only be two options. Some products are displayed with both "In stock" and "Available" filters ### Expected behavior There should only be two options. In Stock and Unavailable ### Steps to reproduce 1. Go to Main Page [https://www.srubky.sk](url) 2. Click on left menu "Srubky" 3. See Faceted filter 4. There are 3 availabilities: In Stock, Available, Unavailable. 5. -- 6. Go to Main Page [https://www.srubky.sk](url) 7. Click on left Menu "Kotvy mechanicke do betonu" 8. See Faceted filter 9. There are 2 availabilities: In Stock and Unavailable. ### PrestaShop version(s) where the bug happened 8,0.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_facetedsearch v.3.15.0 ### Your company or customer's name goes here (if applicable). Stealthtech, s.r.o.

Faceted search problem

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Faceted search 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 I have a problem with displaying product availability in the Faceted search module. Availability is showing correctly for some products. "In stock" and "Unavailable". See image good.png But for some it shows me like this: "In stock" "Available" and "Unavailable" See image bad.png. It should only show "In Stock" or "Available" and "Unavailable". There should only be two options. Some products are displayed with both "In stock" and "Available" filters ### Expected behavior There should only be two options. In Stock and Unavailable ### Steps to reproduce 1. Go to Main Page [https://www.srubky.sk](url) 2. Click on left menu "Srubky" 3. See Faceted filter 4. There are 3 availabilities: In Stock, Available, Unavailable. 5. -- 6. Go to Main Page [https://www.srubky.sk](url) 7. Click on left Menu "Kotvy mechanicke do betonu" 8. See Faceted filter 9. There are 2 availabilities: In Stock and Unavailable. ### PrestaShop version(s) where the bug happened 8,0.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_facetedsearch v.3.15.0 ### Your company or customer's name goes here (if applicable). Stealthtech, s.r.o. --- 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 the module ps_accounts is installed, the login page to the BO is replaced. When clicking on the "connect with another method" to try to login with a regular account, the password reset feature does not work. Clicking on "I forgot my password" will send a link to my email, but when clicking on that link, instead of the password reset form, I get the ps_accounts login page. Thus, I am not able to reset my password any more. ### Expected behavior I expect to be able to reset my password even if ps_accounts is installed. ### Steps to reproduce 1. Install and configure ps_accounts 2. create a new employee 3. log out from your account 4. use the forgot password feature found under "connect with another method" 5. click the link sent to your email. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version ps_accounts 6.3.2 ### Your company or customer's name goes here (if applicable). Prestaworks AB

Ps_accounts make it impossible to reset password

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Ps_accounts make it impossible to reset password 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 the module ps_accounts is installed, the login page to the BO is replaced. When clicking on the "connect with another method" to try to login with a regular account, the password reset feature does not work. Clicking on "I forgot my password" will send a link to my email, but when clicking on that link, instead of the password reset form, I get the ps_accounts login page. Thus, I am not able to reset my password any more. ### Expected behavior I expect to be able to reset my password even if ps_accounts is installed. ### Steps to reproduce 1. Install and configure ps_accounts 2. create a new employee 3. log out from your account 4. use the forgot password feature found under "connect with another method" 5. click the link sent to your email. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.12 ### If your bug is related to a module, specify its name and its version ps_accounts 6.3.2 ### 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 The link Online Visitors redirect to an archived module. https://github.com/PrestaShop/statslive https://github.com/PrestaShop/PrestaShop/assets/16019289/4ce28fdd-9f19-4c1f-ad5f-4d40285f2ef1 ### Expected behavior The link should not be displayed anymore. ### Steps to reproduce 1. Go to BO > In Activity overview > Click on Online Visitors 2. See Module not found ### PrestaShop version(s) where the bug happened 8.0.x, 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 statslive ### Your company or customer's name goes here (if applicable). _No response_

BO - statslive - Activity overview, Online Visitors redirects to an archived module

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - statslive - Activity overview, Online Visitors redirects to an archived 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 The link Online Visitors redirect to an archived module. https://github.com/PrestaShop/statslive https://github.com/PrestaShop/PrestaShop/assets/16019289/4ce28fdd-9f19-4c1f-ad5f-4d40285f2ef1 ### Expected behavior The link should not be displayed anymore. ### Steps to reproduce 1. Go to BO > In Activity overview > Click on Online Visitors 2. See Module not found ### PrestaShop version(s) where the bug happened 8.0.x, 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 statslive ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

#### Describe the solution you'd like be able to modify the creation date of a product so that it appears in new products. When I no longer want to sell a product, what I do is overwrite that with a new one so that I don't have to delete them. but when doing this, prestashop does not put it in the new products section #### Expected solution (by @MatShir) - Create a new date field: Published Date on the product page. - Once the product is created, the first publication date is set to the product creation date. `ps_newproducts` module should base the date to the new field - At the upgrade all the creation date of all the product as copied to the Published Date for the empty value. - The field is datetime. - In the tab option: The field name: "Product as New date from" label: "The date allows you to specify when the product is considered as new. It is used by modules to showcase new products from your catalog or to arrange products by the most recent ones. By default, the date is set to the product creation date for the new date." #### Acceptance test When I go an old product, and edited published date Then the product becomes new on the new product module cf https://github.com/PrestaShop/PrestaShop/discussions/32273

Product as new - date on the product page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Product as new - date on the product page Issue date: --- start body --- #### Describe the solution you'd like be able to modify the creation date of a product so that it appears in new products. When I no longer want to sell a product, what I do is overwrite that with a new one so that I don't have to delete them. but when doing this, prestashop does not put it in the new products section #### Expected solution (by @MatShir) - Create a new date field: Published Date on the product page. - Once the product is created, the first publication date is set to the product creation date. `ps_newproducts` module should base the date to the new field - At the upgrade all the creation date of all the product as copied to the Published Date for the empty value. - The field is datetime. - In the tab option: The field name: "Product as New date from" label: "The date allows you to specify when the product is considered as new. It is used by modules to showcase new products from your catalog or to arrange products by the most recent ones. By default, the date is set to the product creation date for the new date." #### Acceptance test When I go an old product, and edited published date Then the product becomes new on the new product module cf https://github.com/PrestaShop/PrestaShop/discussions/32273 --- 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 am writing because today I found that all my alt tags are filled with the titles of my products instead of the captions I have written. I have the same issue with both the theme I purchased and the classic theme. ### Expected behavior I would like my alt tags to be filled with my captions. ### Steps to reproduce Go to any product page. Inspect an picture. You can see the title of the product. ### 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_

alt tags are filled with the titles

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : alt tags are filled with the titles 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 am writing because today I found that all my alt tags are filled with the titles of my products instead of the captions I have written. I have the same issue with both the theme I purchased and the classic theme. ### Expected behavior I would like my alt tags to be filled with my captions. ### Steps to reproduce Go to any product page. Inspect an picture. You can see the title of the product. ### 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 no carga la validacion del pago contra reembolso, https://casamarsel.es/module/ps_cashondelivery/validation appears the next message The gateway did not receive a timely response from the upstream server or application. It is not allowing the customer to complete the purchase, because the module does not respond ### Expected behavior That the customer can complete the purchase ### Steps to reproduce 1. Go to the store at casamarsel.es then add products to the cart. 2. Fill out customer information. 3. choose shipping method (delivery) 4. Choose cash on delivery payment method. 5. proceed to validate order 6. error ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.2.16 ### If your bug is related to a module, specify its name and its version Cash on delivery (COD) v2.0.1 ### Your company or customer's name goes here (if applicable). Casa marsel

Module error ps_cashondelivery/validation

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Module error ps_cashondelivery/validation Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments no carga la validacion del pago contra reembolso, https://casamarsel.es/module/ps_cashondelivery/validation appears the next message The gateway did not receive a timely response from the upstream server or application. It is not allowing the customer to complete the purchase, because the module does not respond ### Expected behavior That the customer can complete the purchase ### Steps to reproduce 1. Go to the store at casamarsel.es then add products to the cart. 2. Fill out customer information. 3. choose shipping method (delivery) 4. Choose cash on delivery payment method. 5. proceed to validate order 6. error ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.2.16 ### If your bug is related to a module, specify its name and its version Cash on delivery (COD) v2.0.1 ### Your company or customer's name goes here (if applicable). Casa marsel --- 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, when I want to upload a Webp Image on my product, when this one seems to be to big, I have an error message but it's not related to the issue, as we can see : [recording(107).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/d02c4c7a-b52e-4045-8046-6cf2704ed450) ### Expected behavior I wish I could use any Webp Image ### Steps to reproduce 1. GO to BO 2. Go to catalog > Products 3. Create a new simple product 4. On the image, try to put a webp with more than 45 Ko 5. You should have the same error than me ### 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). PS

New Product Page - Image - Webp too big ? and wrong error message

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : New Product Page - Image - Webp too big ? and wrong error message 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, when I want to upload a Webp Image on my product, when this one seems to be to big, I have an error message but it's not related to the issue, as we can see : [recording(107).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/d02c4c7a-b52e-4045-8046-6cf2704ed450) ### Expected behavior I wish I could use any Webp Image ### Steps to reproduce 1. GO to BO 2. Go to catalog > Products 3. Create a new simple product 4. On the image, try to put a webp with more than 45 Ko 5. You should have the same error than me ### 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). 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 Specific prices are applied only to default group and not to another group. I think it's a new feature, but I posted it as bug due to the very old report DOC-99 (August 2015) see attachment. [DOC-99.pdf](https://github.com/PrestaShop/PrestaShop/files/14360894/DOC-99.pdf) ### Expected behavior Specific prices could be applied if a customer is into a group which is not his default group. ### Steps to reproduce 1. Create a group called "A" 2. Create a customer and set "A" as group. Don't change default group. 3. Create specifc prices to "A" group 4. Display the product on frontoffice logged as this customer, you won't see the "A" group price. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened N/A ### 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_

Specific prices for customer groups

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Specific prices for customer groups 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 Specific prices are applied only to default group and not to another group. I think it's a new feature, but I posted it as bug due to the very old report DOC-99 (August 2015) see attachment. [DOC-99.pdf](https://github.com/PrestaShop/PrestaShop/files/14360894/DOC-99.pdf) ### Expected behavior Specific prices could be applied if a customer is into a group which is not his default group. ### Steps to reproduce 1. Create a group called "A" 2. Create a customer and set "A" as group. Don't change default group. 3. Create specifc prices to "A" group 4. Display the product on frontoffice logged as this customer, you won't see the "A" group price. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened N/A ### 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 test ### Expected behavior _No response_ ### Steps to reproduce test ### PrestaShop version(s) where the bug happened test ### 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_

Test for issueBot

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Test for issueBot 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 test ### Expected behavior _No response_ ### Steps to reproduce test ### PrestaShop version(s) where the bug happened test ### 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 2 products: 1. "Dorade heel" with carriers "Delivery NL" and "Delivery local" 2. "Doradefilet" with carrier "Delivery BE" You would expect that no carrier is available as both products have complete different carriers and there is no overlap. Instead you get strange carrier(s).  ### Expected behavior You would expect that no carrier is available as both products have complete different carriers and there is no overlap. ### Steps to reproduce 1. Go to products and select different carriers for 2 products. 2. Order both products. 3. Go to checkout. 4. See result on shipping page. ### 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_

Orders with products with different carriers give strange shipping

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Orders with products with different carriers give strange shipping 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 2 products: 1. "Dorade heel" with carriers "Delivery NL" and "Delivery local" 2. "Doradefilet" with carrier "Delivery BE" You would expect that no carrier is available as both products have complete different carriers and there is no overlap. Instead you get strange carrier(s).  ### Expected behavior You would expect that no carrier is available as both products have complete different carriers and there is no overlap. ### Steps to reproduce 1. Go to products and select different carriers for 2 products. 2. Order both products. 3. Go to checkout. 4. See result on shipping page. ### 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 In PrestaShop\PrestaShop\Core\Util\String\StringModifier class function cutEnd it used strlen and substr functions to calculate and cut strings wich not work correct with UTF-8 strings. To correct this it can be used mb_strlen and mb_substr ### Expected behavior _No response_ ### Steps to reproduce 1. Write 90+ symbols product name in cyrillic 2. Try to duplicate product ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

StringModifier cutEnd function problem with UTF-8

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : StringModifier cutEnd function problem with UTF-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 In PrestaShop\PrestaShop\Core\Util\String\StringModifier class function cutEnd it used strlen and substr functions to calculate and cut strings wich not work correct with UTF-8 strings. To correct this it can be used mb_strlen and mb_substr ### Expected behavior _No response_ ### Steps to reproduce 1. Write 90+ symbols product name in cyrillic 2. Try to duplicate product ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

opgrade prestashop stoped at 85%

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : opgrade prestashop stoped at 85% Issue date: --- start body --- None --- 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, I wanted to update the prestashop version 1.6.1.13 to the most recent one using the 1-Click Upgrade module but despite having updated the 1-click upgrade module (see image) I am unable to update. How come? What could be the problem?  ### Expected behavior update version ### Steps to reproduce I go to form exhaust version module installation ### PrestaShop version(s) where the bug happened 1.6.1.13 ### PHP version(s) where the bug happened 7.1 ### If your bug is related to a module, specify its name and its version 1-click upgrade (la tua versione corrente è la v4.14.2) ### Your company or customer's name goes here (if applicable). Città Immagine snc - SiTimbri

PROBLEM UPGRADE

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PROBLEM UPGRADE Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Good morning, I wanted to update the prestashop version 1.6.1.13 to the most recent one using the 1-Click Upgrade module but despite having updated the 1-click upgrade module (see image) I am unable to update. How come? What could be the problem?  ### Expected behavior update version ### Steps to reproduce I go to form exhaust version module installation ### PrestaShop version(s) where the bug happened 1.6.1.13 ### PHP version(s) where the bug happened 7.1 ### If your bug is related to a module, specify its name and its version 1-click upgrade (la tua versione corrente è la v4.14.2) ### Your company or customer's name goes here (if applicable). Città Immagine snc - SiTimbri --- end body --- comments : --- start comments --- --- end comments ---

Based on this [PR that introduced the `Mutation`](https://github.com/PrestaShop/PrestaShop/pull/35292) entity @kpodemski suggested a more [generic way to display the mutator](https://github.com/PrestaShop/PrestaShop/pull/35292/files#r1492459582) associated to a mutation that could be reused in other places in the future ### Technical implementation We'd introduce a `MutatorFormatter` service that can use a `Mutation` entity as its input like this: ```php public function formatMutator(Mutation $mutationEntity): string; public function formatMutator(MutatorType $mutatoryType, string $mutatorIdentifier): string; ``` It would return a string depending on the parameters like: - `Employee: John Doe` - `API Client: client_id (keycloak)` - `API Client: client_id (PrestaShop)` - `Module: ps_wirepayment` The `MutatorType` and `MutatorAction` enums should be moved from the `Entity` namespace to a more generic one `PrestaShop\PrestaShop\Core\Mutation` ### Integration This new generic formatter should be integrated in the `GetOrderForViewing` CQRS query, it will imply modifying its QueryResult a bit which is a breaking change, but the structure as already modified to integrate the API Client anyway and we are in a major version so we can afford such breaking change. The `OrderStatusForViewing` DTO would go from: ```php public function __construct( int $orderHistoryId, int $orderStatusId, string $name, string $color, DateTimeImmutable $createdAt, bool $withEmail, ?string $employeeFirstName, ?string $employeeLastName, ?string $apiClientId, ) ``` to a more generic ```php public function __construct( int $orderHistoryId, int $orderStatusId, string $name, string $color, DateTimeImmutable $createdAt, bool $withEmail, ?Mutator, ) ``` The mutator DTO itself could be reused more easily then and would look like: ```php class Mutator { public function __construct( private readonly MutatorType $mutatorType, private readonly string $mutatorIdentifier, private readonly ?string $formattedMutator ) { } // Public getters } ``` This generic DTO should also be in the `PrestaShop\PrestaShop\Core\Mutation` namespace The structure still contains the DB details to identify the mutator relationship, and an additional/option formatted text used for display and generated by the `MutatorFormatter` Ultimately this mutator formatted text will be integrated in the Order status history view in the BO and this will finalize the first implementation that can be used as a reference in the future.

Generic Mutator formatting

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Generic Mutator formatting Issue date: --- start body --- Based on this [PR that introduced the `Mutation`](https://github.com/PrestaShop/PrestaShop/pull/35292) entity @kpodemski suggested a more [generic way to display the mutator](https://github.com/PrestaShop/PrestaShop/pull/35292/files#r1492459582) associated to a mutation that could be reused in other places in the future ### Technical implementation We'd introduce a `MutatorFormatter` service that can use a `Mutation` entity as its input like this: ```php public function formatMutator(Mutation $mutationEntity): string; public function formatMutator(MutatorType $mutatoryType, string $mutatorIdentifier): string; ``` It would return a string depending on the parameters like: - `Employee: John Doe` - `API Client: client_id (keycloak)` - `API Client: client_id (PrestaShop)` - `Module: ps_wirepayment` The `MutatorType` and `MutatorAction` enums should be moved from the `Entity` namespace to a more generic one `PrestaShop\PrestaShop\Core\Mutation` ### Integration This new generic formatter should be integrated in the `GetOrderForViewing` CQRS query, it will imply modifying its QueryResult a bit which is a breaking change, but the structure as already modified to integrate the API Client anyway and we are in a major version so we can afford such breaking change. The `OrderStatusForViewing` DTO would go from: ```php public function __construct( int $orderHistoryId, int $orderStatusId, string $name, string $color, DateTimeImmutable $createdAt, bool $withEmail, ?string $employeeFirstName, ?string $employeeLastName, ?string $apiClientId, ) ``` to a more generic ```php public function __construct( int $orderHistoryId, int $orderStatusId, string $name, string $color, DateTimeImmutable $createdAt, bool $withEmail, ?Mutator, ) ``` The mutator DTO itself could be reused more easily then and would look like: ```php class Mutator { public function __construct( private readonly MutatorType $mutatorType, private readonly string $mutatorIdentifier, private readonly ?string $formattedMutator ) { } // Public getters } ``` This generic DTO should also be in the `PrestaShop\PrestaShop\Core\Mutation` namespace The structure still contains the DB details to identify the mutator relationship, and an additional/option formatted text used for display and generated by the `MutatorFormatter` Ultimately this mutator formatted text will be integrated in the Order status history view in the BO and this will finalize the first implementation that can be used as a reference in the future. --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There is a duplicate 'Marketplace' and 'Themes Catalog' entry in backend. It started happening after upgrading from 8.1.2 to 8.1.4 using one-click-upgrade. I already tried disabling/enabling Marketplace plugin as well as disabling/clearing caches, and disabling ps_edition_basic but the issue persists. Only when Marketplace plugin is disabled - both menu entries disappear, which is expected.   ### Expected behavior _No response_ ### Steps to reproduce I guess upgrade from 8.1.2 to 8.1.4 ### 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 ps_mbo v4.10.1 ### Your company or customer's name goes here (if applicable). _No response_

Duplicate 'Marketplace' and 'Themes Catalog' entry in backend

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Duplicate 'Marketplace' and 'Themes Catalog' entry in backend Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments There is a duplicate 'Marketplace' and 'Themes Catalog' entry in backend. It started happening after upgrading from 8.1.2 to 8.1.4 using one-click-upgrade. I already tried disabling/enabling Marketplace plugin as well as disabling/clearing caches, and disabling ps_edition_basic but the issue persists. Only when Marketplace plugin is disabled - both menu entries disappear, which is expected.   ### Expected behavior _No response_ ### Steps to reproduce I guess upgrade from 8.1.2 to 8.1.4 ### 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 ps_mbo v4.10.1 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

We should follow the guidelines from ADR 23: https://github.com/PrestaShop/ADR/blob/master/0023-cqrs-api-guidelines.md At the moment, we have paths that don't follow guidelines described in the ADR, like `/hook-status/.` cc @MatShir @jolelievre - I'm not sure what labels would you like to add :)

API: lack of consistency in naming of endpoints

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : API: lack of consistency in naming of endpoints Issue date: --- start body --- We should follow the guidelines from ADR 23: https://github.com/PrestaShop/ADR/blob/master/0023-cqrs-api-guidelines.md At the moment, we have paths that don't follow guidelines described in the ADR, like `/hook-status/.` cc @MatShir @jolelievre - I'm not sure what labels would you like to add :) --- 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'm upgading a Prestashop version from 1.6.1.23. In the control panel it says: You can update to PrestaShop 1.6.1.24. I thought it would be better to upgrade to 1.6.1.24 before going to 8.x, but really don't care IF I could just upgrade to the newest. However, 1 click upgrade wont let me upgrade. It says that the 1 click upgrade module needs to be update (even tho in the same sentence it says its the newest version). So Im stuck in a loop where I can upgrade the module but nothing changes Please see the screen shots. Can you help me "get out of this loop?" so I can upgrade?   ### Expected behavior After I click Upgrade, the 1 click Upgrade module should allow be to upgrade the Prestashop install. ### Steps to reproduce 1. Advanced functions 2. 1 click upgrade 3. Line 1 "1 click upgrade" presss Update 4. After update go to 1. (now the check marks should all be gree) ### PrestaShop version(s) where the bug happened 1.6.1.23 to 1.6.1.24 ### PHP version(s) where the bug happened 1.6.1.23 ### If your bug is related to a module, specify its name and its version 1-click upgrade v4.14.2 - byPrestaShop ### Your company or customer's name goes here (if applicable). KKE Motorer

1 click upgrade won't allow me to update Prestashop

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : 1 click upgrade won't allow me to update Prestashop 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'm upgading a Prestashop version from 1.6.1.23. In the control panel it says: You can update to PrestaShop 1.6.1.24. I thought it would be better to upgrade to 1.6.1.24 before going to 8.x, but really don't care IF I could just upgrade to the newest. However, 1 click upgrade wont let me upgrade. It says that the 1 click upgrade module needs to be update (even tho in the same sentence it says its the newest version). So Im stuck in a loop where I can upgrade the module but nothing changes Please see the screen shots. Can you help me "get out of this loop?" so I can upgrade?   ### Expected behavior After I click Upgrade, the 1 click Upgrade module should allow be to upgrade the Prestashop install. ### Steps to reproduce 1. Advanced functions 2. 1 click upgrade 3. Line 1 "1 click upgrade" presss Update 4. After update go to 1. (now the check marks should all be gree) ### PrestaShop version(s) where the bug happened 1.6.1.23 to 1.6.1.24 ### PHP version(s) where the bug happened 1.6.1.23 ### If your bug is related to a module, specify its name and its version 1-click upgrade v4.14.2 - byPrestaShop ### Your company or customer's name goes here (if applicable). KKE Motorer --- 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 shopping cart in the backend of the store, the search engine works unintuitively. For example, a product with the name "test 12345" does not scrub when you type the phrase "test". The product appears when you type "test 1". We make no secret of the fact that this is problematic, and customers have already commented to us more than once on the way this search engine works. ### Expected behavior We expect the search engine in the shopping cart backend to function intuitively, allowing for efficient and accurate product retrieval based on relevant keywords. ### Steps to reproduce 1. go to the "Orders" tab 2. click "Add new order" 3. search for a customer 4. go to the product search engine ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened 7.4.30 ### 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_

Search engine - creating an order

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Search engine - creating an order 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 shopping cart in the backend of the store, the search engine works unintuitively. For example, a product with the name "test 12345" does not scrub when you type the phrase "test". The product appears when you type "test 1". We make no secret of the fact that this is problematic, and customers have already commented to us more than once on the way this search engine works. ### Expected behavior We expect the search engine in the shopping cart backend to function intuitively, allowing for efficient and accurate product retrieval based on relevant keywords. ### Steps to reproduce 1. go to the "Orders" tab 2. click "Add new order" 3. search for a customer 4. go to the product search engine ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened 7.4.30 ### 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 shop's currency stays as the default currency when IP geolocation is enabled. It seems that the logic for changing the default currency is only triggered if IP geolocation is not used here https://github.com/PrestaShop/PrestaShop/blob/8.1.4-build/classes/controller/FrontController.php#L327-L360 It is probably possible to extract the currency setting part into a common function or code branch. ### Expected behavior Having set the default currency in International -> Locations -> Countries, it will be set when using IP geolocation. ### Steps to reproduce 1. Set the shop's default currency in International -> Localization to Euro 2. In International -> Locations -> Countries, set the default currency of United Kingdom to British Pound 3. Go into shop from a UK IP address 4. The default currency will be set to Euro, even though it should be GBP ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2.7 ### 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_

Default currency for country does not get set when using IP geolocation

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Default currency for country does not get set when using IP geolocation 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 shop's currency stays as the default currency when IP geolocation is enabled. It seems that the logic for changing the default currency is only triggered if IP geolocation is not used here https://github.com/PrestaShop/PrestaShop/blob/8.1.4-build/classes/controller/FrontController.php#L327-L360 It is probably possible to extract the currency setting part into a common function or code branch. ### Expected behavior Having set the default currency in International -> Locations -> Countries, it will be set when using IP geolocation. ### Steps to reproduce 1. Set the shop's default currency in International -> Localization to Euro 2. In International -> Locations -> Countries, set the default currency of United Kingdom to British Pound 3. Go into shop from a UK IP address 4. The default currency will be set to Euro, even though it should be GBP ### PrestaShop version(s) where the bug happened 8.1.4 ### PHP version(s) where the bug happened 8.2.7 ### 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 an issue with importing products via CSV on the PrestaShop platform version 1.7.0.2. The PHP version is 7.0.33. It keeps showing the same error. I'm attaching screenshots for reference. To make it easier, I've included only the product name and ID in the CSV file.     ### Expected behavior _No response_ ### Steps to reproduce 1.Import CSV ### PrestaShop version(s) where the bug happened 1.7.0.2. ### PHP version(s) where the bug happened 7.0.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.dobreljekarne.com

Import prodcut csv

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Import prodcut csv 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 importing products via CSV on the PrestaShop platform version 1.7.0.2. The PHP version is 7.0.33. It keeps showing the same error. I'm attaching screenshots for reference. To make it easier, I've included only the product name and ID in the CSV file.     ### Expected behavior _No response_ ### Steps to reproduce 1.Import CSV ### PrestaShop version(s) where the bug happened 1.7.0.2. ### PHP version(s) where the bug happened 7.0.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.dobreljekarne.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 when I enable de debug mode my products page not open more, I will see the follow Warnings and product page not open. If I disable the debug mode the product page will open correctly ( ! ) Warning: Undefined array key "available_now" in .../controllers/front/ProductController.php on line 705 ( ! ) Warning: Undefined array key "available_later" in .../controllers/front/ProductController.php on line 706 I am using PS 8.1.2 on dedicated server apache+nginx with php 8.1 ### Expected behavior _No response_ ### Steps to reproduce Open BO Go to performance and enable debug mode Open an product page with debug mode enable ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Warnin in debug mode "available_now" "available_later" in products page on PS 8.1.2

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Warnin in debug mode "available_now" "available_later" in products page on PS 8.1.2 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments when I enable de debug mode my products page not open more, I will see the follow Warnings and product page not open. If I disable the debug mode the product page will open correctly ( ! ) Warning: Undefined array key "available_now" in .../controllers/front/ProductController.php on line 705 ( ! ) Warning: Undefined array key "available_later" in .../controllers/front/ProductController.php on line 706 I am using PS 8.1.2 on dedicated server apache+nginx with php 8.1 ### Expected behavior _No response_ ### Steps to reproduce Open BO Go to performance and enable debug mode Open an product page with debug mode enable ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

This issue tracks the status of the PrestaShop 8.1.4 release # Information Q | A --------------------------------------|--------------- **Type** | Security patch version **Build date** | 2024-02-12 **Milestone** | 8.1.4 **Delivery date** | 2024-02-19 **Release manager tech** | @matks **Release manager product** | **Release manager QA** | _Nota Bene: the release date may vary, if major bugs are identified during the test phase_ RMT = Release manager tech RMQ = Release manager QA # Current status ## 1. Development This is a security-only release: it only contains the version number change, the changelog and the security patch. ## 2. Preparing the source code for release This is a security-only release: it only contains the version number change, the changelog and the security patch. So no source code preparation was needed. ## 3. Build process - [x] Create the new version in Addons Marketplace and update native module compatibility - [x] Prepare communication **Communicator** - [x] Merge security PRs locally if there are some **RMT** - [x] Update the Changelog and Contributors list **RMT** - [x] Build the zip archive. **RMT** - [x] QA validation **RMQ** - [x] Release **RMT** - [x] Merge security PRs on GitHub if there are some - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub. - [x] Provide Communicator with up to date informations (contributors list, changelog...) **RMT** - [x] Communicate - [x] Release note **Communicator** ## 4. After release steps - [x] Make new version available for upgrade - [x] Publish Docker image - [x] Close milestone

Release 8.1.4

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Release 8.1.4 Issue date: --- start body --- This issue tracks the status of the PrestaShop 8.1.4 release # Information Q | A --------------------------------------|--------------- **Type** | Security patch version **Build date** | 2024-02-12 **Milestone** | 8.1.4 **Delivery date** | 2024-02-19 **Release manager tech** | @matks **Release manager product** | **Release manager QA** | _Nota Bene: the release date may vary, if major bugs are identified during the test phase_ RMT = Release manager tech RMQ = Release manager QA # Current status ## 1. Development This is a security-only release: it only contains the version number change, the changelog and the security patch. ## 2. Preparing the source code for release This is a security-only release: it only contains the version number change, the changelog and the security patch. So no source code preparation was needed. ## 3. Build process - [x] Create the new version in Addons Marketplace and update native module compatibility - [x] Prepare communication **Communicator** - [x] Merge security PRs locally if there are some **RMT** - [x] Update the Changelog and Contributors list **RMT** - [x] Build the zip archive. **RMT** - [x] QA validation **RMQ** - [x] Release **RMT** - [x] Merge security PRs on GitHub if there are some - [x] Merge the updated Changelog and Contributors list on GitHub. - [x] Tag the version using Git and publish the release on GitHub. - [x] Provide Communicator with up to date informations (contributors list, changelog...) **RMT** - [x] Communicate - [x] Release note **Communicator** ## 4. After release steps - [x] Make new version available for upgrade - [x] Publish Docker image - [x] Close milestone --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi if you try to do the password reset steps, you will get the reset page where to set a new password two times from this page is not present the new password verification, in fact it is possible to set weak password  bye ### Expected behavior _No response_ ### Steps to reproduce 1. go at login 2. push on the link "I don't remember the password" 3. set an email to get the reset link 4. push on the reset link 5. set a new password, but weak like "casetta" 6. Password verification will not appear ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

The new password policy is not present in the reset password page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : The new password policy is not present in the reset password 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 Hi if you try to do the password reset steps, you will get the reset page where to set a new password two times from this page is not present the new password verification, in fact it is possible to set weak password  bye ### Expected behavior _No response_ ### Steps to reproduce 1. go at login 2. push on the link "I don't remember the password" 3. set an email to get the reset link 4. push on the reset link 5. set a new password, but weak like "casetta" 6. Password verification will not appear ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Describe the bug and add attachments Customer discount section shows all vouchers without code that even if not highlighted. The problem is caused by this PR - https://github.com/PrestaShop/PrestaShop/pull/22518, which added `cr.highlight = 1 OR cr.code = ""`. Also, it hides the posibility to set voucher highlighted when it has no code. The result is following. ### 1.7.6 - no vouchers  ### 8.1.3 - all of the business logic is exposed  | Voucher | My account zone | Cart page | Cart page logged out | Backoffice customer detail | --- | --- | --- | --- | --- | | This page should show only vouchers specific to this single customer. | This case should show only rules highlighted and either for current customer or for everyone. | This case should show only rules highlighted and for everyone. | This page should show only vouchers specific to this single customer. | Code, highlight, for everyone | 🔴 YES - not a disaster, but wrong, it's not his specific voucher | 🟢YES | 🟢YES | 🔴YES - wrong, it's not his specific voucher | Code, highlight, specific customer | 🟢 YES | 🟢YES | 🟢NO | 🟢YES | Code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | Code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES | No code, highlight, for everyone | 🔴YES - not a disaster, but wrong, it's not his specific voucher | 🟢YES | 🟢YES | 🔴YES - wrong, it's not his specific voucher | No code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | No code, no highlight, for everyone | 🔴YES - VERY WRONG, nobody should see this logic | 🟢NO | 🟢NO | 🔴YES - wrong, it's not his specific voucher | No code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES ### Expected behavior The change must be reverted and in the customer zone, only vouchers **FOR THAT SPECIFIC CUSTOMER** or **HIGHLIGHTED** should be displayed. The only thing that the PR did was to prevent people configuring if they want people to see this voucher or not. | Voucher | My account zone | Cart page | Cart page logged out | Backoffice customer detail | --- | --- | --- | --- | --- | | This page should show only vouchers specific to this single customer. | This case should show only rules highlighted and either for current customer or for everyone. | This case should show only rules highlighted and for everyone. | This page should show only vouchers specific to this single customer. | Code, highlight, for everyone | 🟢NO | 🟢YES | 🟢YES | 🟢NO | Code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | Code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | Code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES | No code, highlight, for everyone | 🟢NO | 🟢YES | 🟢YES | 🟢NO | No code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | No code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | No code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES ### Steps to reproduce 1. Create cart rule with no code, valid for all customers, with infinte quantity. 2. Login as a customer in FO, see that you can see the voucher even if you did not highlight it. ### 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_

FO discount section shows all vouchers without code that even if not highlighted

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FO discount section shows all vouchers without code that even if not highlighted Issue date: --- start body --- ### Describe the bug and add attachments Customer discount section shows all vouchers without code that even if not highlighted. The problem is caused by this PR - https://github.com/PrestaShop/PrestaShop/pull/22518, which added `cr.highlight = 1 OR cr.code = ""`. Also, it hides the posibility to set voucher highlighted when it has no code. The result is following. ### 1.7.6 - no vouchers  ### 8.1.3 - all of the business logic is exposed  | Voucher | My account zone | Cart page | Cart page logged out | Backoffice customer detail | --- | --- | --- | --- | --- | | This page should show only vouchers specific to this single customer. | This case should show only rules highlighted and either for current customer or for everyone. | This case should show only rules highlighted and for everyone. | This page should show only vouchers specific to this single customer. | Code, highlight, for everyone | 🔴 YES - not a disaster, but wrong, it's not his specific voucher | 🟢YES | 🟢YES | 🔴YES - wrong, it's not his specific voucher | Code, highlight, specific customer | 🟢 YES | 🟢YES | 🟢NO | 🟢YES | Code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | Code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES | No code, highlight, for everyone | 🔴YES - not a disaster, but wrong, it's not his specific voucher | 🟢YES | 🟢YES | 🔴YES - wrong, it's not his specific voucher | No code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | No code, no highlight, for everyone | 🔴YES - VERY WRONG, nobody should see this logic | 🟢NO | 🟢NO | 🔴YES - wrong, it's not his specific voucher | No code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES ### Expected behavior The change must be reverted and in the customer zone, only vouchers **FOR THAT SPECIFIC CUSTOMER** or **HIGHLIGHTED** should be displayed. The only thing that the PR did was to prevent people configuring if they want people to see this voucher or not. | Voucher | My account zone | Cart page | Cart page logged out | Backoffice customer detail | --- | --- | --- | --- | --- | | This page should show only vouchers specific to this single customer. | This case should show only rules highlighted and either for current customer or for everyone. | This case should show only rules highlighted and for everyone. | This page should show only vouchers specific to this single customer. | Code, highlight, for everyone | 🟢NO | 🟢YES | 🟢YES | 🟢NO | Code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | Code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | Code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES | No code, highlight, for everyone | 🟢NO | 🟢YES | 🟢YES | 🟢NO | No code, highlight, specific customer | 🟢YES | 🟢YES | 🟢NO | 🟢YES | No code, no highlight, for everyone | 🟢NO | 🟢NO | 🟢NO | 🟢NO | No code, no highlight, specific customer | 🟢YES | 🟢NO | 🟢NO | 🟢YES ### Steps to reproduce 1. Create cart rule with no code, valid for all customers, with infinte quantity. 2. Login as a customer in FO, see that you can see the voucher even if you did not highlight it. ### 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 Hello, I have a problem with a prestashop. The customer insert the cost price with decimals, but when some time passes (we do not know days or weeks) the price is automatically rounded by itself. What can be happening? ### Expected behavior The price should be kept to decimal places, otherwise the profit statistics are not real. ### Steps to reproduce Insert price with decimals and wait (days or weeks). We do not know the estimated time. ### PrestaShop version(s) where the bug happened 1.7.8.0 ### 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_

Problem with product cost prices

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem with product cost 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 Hello, I have a problem with a prestashop. The customer insert the cost price with decimals, but when some time passes (we do not know days or weeks) the price is automatically rounded by itself. What can be happening? ### Expected behavior The price should be kept to decimal places, otherwise the profit statistics are not real. ### Steps to reproduce Insert price with decimals and wait (days or weeks). We do not know the estimated time. ### PrestaShop version(s) where the bug happened 1.7.8.0 ### 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  I want it to chose this one EVERY TIME and not the "No Tax". ### Expected behavior _No response_ ### Steps to reproduce Create a new product ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Create a new product, it does not select the correct VAT group.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Create a new product, it does not select the correct VAT group. 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 want it to chose this one EVERY TIME and not the "No Tax". ### Expected behavior _No response_ ### Steps to reproduce Create a new product ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4.33 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

Retrieve the data from the BDD Same acceptance test as [MOCCT-005_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35400)

[US-Pricing][MOC][Without rounding][B_to_C] : MOCCT-005_B_to_C : Connection to the BDD#34166

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [US-Pricing][MOC][Without rounding][B_to_C] : MOCCT-005_B_to_C : Connection to the BDD#34166 Issue date: --- start body --- Retrieve the data from the BDD Same acceptance test as [MOCCT-005_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35400) --- end body --- comments : --- start comments --- --- end comments ---

User Story : As a merchant I need to be able to correctly calculate the total price of several items depending of the combination of the product. for quantity greater than 1 adding shipping cost for B to B For several items, Quantity parametrable, Without Ecotax, Price without decimal point, without reduction, VAT parametrable, **mono shipping including** **Reste à ajouter le shipping dans les steps** **Business rules**: Look at [specification](https://app.gitbook.com/o/-MAz0PPl5s9ulE9xyliu/s/eRh5ljXXvELkmmdiRmg8/functional-documentation/business-rules/pricing/method-of-calculating-a-cart-total-mocct) **Acceptance test** : Consider five products (3 combinations of one product on combination of another product and one standard product) 1) 3 combinations of balloon Standard price :  Impact price :  Quantity : 10 for black, 3 for white,4 for grey in the chart 2) 1 combination of skipping rope : Standard price :  Impact price :  Quantity 2 in the chart 3) Yoyo Standard price :  Impact price : NA Quantity 6 in the chart Result step by step : Step 1 - Standard Price and impact price : Black balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 1.20 = 7.20 White Balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 114 = 120 Grey balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 0 = 6 Skipping rope : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 26.40 + 1,10 = 27,50 Yoyo : Price_of_product_tax_included_step1 = Retail price (tax incl.) = 6 Step 6 - Total price included of products Black balloon : Total_cost_included_product_X1 = 7.2 * 10 = 72 White Balloon : Total_cost_included_product_X2 = 120 * 3 = 360 Grey balloon : Total_cost_included_product_X3 = 6 * 4 = 24 Skipping rope Total_cost_included_product_X4 = 27.5 * 2 = 55 Yoyo : Total_cost_included_product_X5 = 6 * 6 = 36 Total_cost_excluded_products =Total_cost_excluded_product_X1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 + Total_cost_excluded_product_X4 + Total_cost_excluded_product_X5 = 72+360+24+55+36 = 547 Step 7 - Calculation of VAT to correct Total_cost_included_ rate20 = Total_cost_excluded_productX1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 +Total_cost_excluded_product_X5 = 72+360+24+36 = 492 Price tax excluded of product with rate 20% 492/1.2 = 410 VAT_rate_20 = 492 - 410 = 82 Total_cost_included_ rate10 = Total_cost_excluded_productX4 = 55 Price tax excluded of product with rate 10% 55/1.1 = 50 VAT_rate_10 = 55 - 50 = 5 Step 8 VAT of shipping The shipping and handling tax is added Consider : Cost_of_carrier_tax_excluded = 20 euros and Carrier's_tax = 10 % Handling_charges_tax_excluded = 2 euros Shipping_cost_tax_excluded = Cost_of_carrier_tax_excluded + Handling_charges_tax_excluded = 20 + 2 = 22 We calculate the shipping VAT: Carrier_VAT = Cost_of_carrier_tax_excluded * Carrier's_tax = 0,1 * 20 = 2 We calculate the handling VAT: Handling_VAT = Handling_charges_tax_excluded * Carrier's_tax = 0,1 * 2 = 0,2 For a total tax of : Total_Shipping_VAT = Carrier_VAT + Handling_VAT 2 + 0,2 = 2.2 Step 9 Display of the chart Shopping cart result B to C : 2 - Price_of_product_tax_included_step1 3 - Total_cost_included_productX (step 6) 4 - Total_cost_included_products (step 6) 7 - Shipping_cost_tax_included 8- Total_tax_included = Total_cost_included_products (step 6) + Shipping_cost_tax_included 9 - Taxes = VAT_rate_20 + VAT_rate_10 + Total_Shipping_VAT Shopping cart result B to C :  Invoice : 5 - VAT_rate_10 (step 7) VAT_rate_20 (step 7) Total_Shipping_VAT (step 8) 

[US-Pricing][MOC][Without rounding][B to C] : MOCCT-005_B_to_C : Buy several articles with shipping

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [US-Pricing][MOC][Without rounding][B to C] : MOCCT-005_B_to_C : Buy several articles with shipping Issue date: --- start body --- User Story : As a merchant I need to be able to correctly calculate the total price of several items depending of the combination of the product. for quantity greater than 1 adding shipping cost for B to B For several items, Quantity parametrable, Without Ecotax, Price without decimal point, without reduction, VAT parametrable, **mono shipping including** **Reste à ajouter le shipping dans les steps** **Business rules**: Look at [specification](https://app.gitbook.com/o/-MAz0PPl5s9ulE9xyliu/s/eRh5ljXXvELkmmdiRmg8/functional-documentation/business-rules/pricing/method-of-calculating-a-cart-total-mocct) **Acceptance test** : Consider five products (3 combinations of one product on combination of another product and one standard product) 1) 3 combinations of balloon Standard price :  Impact price :  Quantity : 10 for black, 3 for white,4 for grey in the chart 2) 1 combination of skipping rope : Standard price :  Impact price :  Quantity 2 in the chart 3) Yoyo Standard price :  Impact price : NA Quantity 6 in the chart Result step by step : Step 1 - Standard Price and impact price : Black balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 1.20 = 7.20 White Balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 114 = 120 Grey balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 0 = 6 Skipping rope : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 26.40 + 1,10 = 27,50 Yoyo : Price_of_product_tax_included_step1 = Retail price (tax incl.) = 6 Step 6 - Total price included of products Black balloon : Total_cost_included_product_X1 = 7.2 * 10 = 72 White Balloon : Total_cost_included_product_X2 = 120 * 3 = 360 Grey balloon : Total_cost_included_product_X3 = 6 * 4 = 24 Skipping rope Total_cost_included_product_X4 = 27.5 * 2 = 55 Yoyo : Total_cost_included_product_X5 = 6 * 6 = 36 Total_cost_excluded_products =Total_cost_excluded_product_X1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 + Total_cost_excluded_product_X4 + Total_cost_excluded_product_X5 = 72+360+24+55+36 = 547 Step 7 - Calculation of VAT to correct Total_cost_included_ rate20 = Total_cost_excluded_productX1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 +Total_cost_excluded_product_X5 = 72+360+24+36 = 492 Price tax excluded of product with rate 20% 492/1.2 = 410 VAT_rate_20 = 492 - 410 = 82 Total_cost_included_ rate10 = Total_cost_excluded_productX4 = 55 Price tax excluded of product with rate 10% 55/1.1 = 50 VAT_rate_10 = 55 - 50 = 5 Step 8 VAT of shipping The shipping and handling tax is added Consider : Cost_of_carrier_tax_excluded = 20 euros and Carrier's_tax = 10 % Handling_charges_tax_excluded = 2 euros Shipping_cost_tax_excluded = Cost_of_carrier_tax_excluded + Handling_charges_tax_excluded = 20 + 2 = 22 We calculate the shipping VAT: Carrier_VAT = Cost_of_carrier_tax_excluded * Carrier's_tax = 0,1 * 20 = 2 We calculate the handling VAT: Handling_VAT = Handling_charges_tax_excluded * Carrier's_tax = 0,1 * 2 = 0,2 For a total tax of : Total_Shipping_VAT = Carrier_VAT + Handling_VAT 2 + 0,2 = 2.2 Step 9 Display of the chart Shopping cart result B to C : 2 - Price_of_product_tax_included_step1 3 - Total_cost_included_productX (step 6) 4 - Total_cost_included_products (step 6) 7 - Shipping_cost_tax_included 8- Total_tax_included = Total_cost_included_products (step 6) + Shipping_cost_tax_included 9 - Taxes = VAT_rate_20 + VAT_rate_10 + Total_Shipping_VAT Shopping cart result B to C :  Invoice : 5 - VAT_rate_10 (step 7) VAT_rate_20 (step 7) Total_Shipping_VAT (step 8)  --- end body --- comments : --- start comments --- --- end comments ---

Retrieve the data from the BDD Same acceptance test as [MOCCT-004_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35398)

[US-Pricing][MOC][Without rounding][B_to_C] : MOCCT-004_B_to_C : Buy several articles - Connection to the BDD

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [US-Pricing][MOC][Without rounding][B_to_C] : MOCCT-004_B_to_C : Buy several articles - Connection to the BDD Issue date: --- start body --- Retrieve the data from the BDD Same acceptance test as [MOCCT-004_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35398) --- end body --- comments : --- start comments --- --- end comments ---

User Story : As a merchant I need to be able to correctly calculate the total price of several items depending of the combination of the product for B to C For **several** items, Quantity parametrable, Without Ecotax, Price without decimal point, without reduction, VAT parametrable, no shipping **Business rules**: Look at [specification](https://app.gitbook.com/o/-MAz0PPl5s9ulE9xyliu/s/eRh5ljXXvELkmmdiRmg8/functional-documentation/business-rules/pricing/method-of-calculating-a-cart-total-mocct) **Acceptance test** : Consider five products (3 combinations of one product on combination of another product and one standard product) 1) 3 combinations of balloon Standard price :  Impact price :  Quantity : 10 for black, 3 for white,4 for grey in the chart 2) 1 combination of skipping rope : Standard price :  Impact price :  Quantity 2 in the chart 3) Yoyo Standard price :  Impact price : NA Quantity 6 in the chart Result step by step : Step 1 - Standard Price and impact price : Black balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 1.20 = 7.20 White Balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 114 = 120 Grey balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 0 = 6 Skipping rope : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 26.40 + 1,10 = 27,50 Yoyo : Price_of_product_tax_included_step1 = Retail price (tax incl.) = 6 Step 6 - Total price included of products Black balloon : Total_cost_included_product_X1 = 7.2 * 10 = 72 White Balloon : Total_cost_included_product_X2 = 120 * 3 = 360 Grey balloon : Total_cost_included_product_X3 = 6 * 4 = 24 Skipping rope Total_cost_included_product_X4 = 27.5 * 2 = 55 Yoyo : Total_cost_included_product_X5 = 6 * 6 = 36 Total_cost_excluded_products =Total_cost_excluded_product_X1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 + Total_cost_excluded_product_X4 + Total_cost_excluded_product_X5 = 72+360+24+55+36 = 547 Step 7 - Calculation of VAT to correct Total_cost_included_ rate20 = Total_cost_excluded_productX1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 +Total_cost_excluded_product_X5 = 72+360+24+36 = 492 Price tax excluded of product with rate 20% 492/1.2 = 410 VAT_rate_20 = 492 - 410 = 82 Total_cost_included_ rate10 = Total_cost_excluded_productX4 = 55 Price tax excluded of product with rate 10% 55/1.1 = 50 VAT_rate_10 = 55 - 50 = 5 Step 9 Display of the chart Shopping cart result B to C : 2 - Price_of_product_tax_included_step1 3 - Total_cost_included_productX (step 6) 4 - Total_cost_included_products (step 6) 7 - Shipping_cost_tax_included : 0 8- Total_tax_included = Total_cost_included_products (step 6) + Shipping_cost_tax_included 9 - Taxes = VAT_rate_20 + VAT_rate_10 Shopping cart result B to C :  Invoice : 5 - VAT_rate_10 (step 7) VAT_rate_20 (step 7) ![Uploading image.png…]()

[US-Pricing][MOC][Without rounding] [B to C]: MOCCT-004_B_to_C : Buy several articles

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [US-Pricing][MOC][Without rounding] [B to C]: MOCCT-004_B_to_C : Buy several articles Issue date: --- start body --- User Story : As a merchant I need to be able to correctly calculate the total price of several items depending of the combination of the product for B to C For **several** items, Quantity parametrable, Without Ecotax, Price without decimal point, without reduction, VAT parametrable, no shipping **Business rules**: Look at [specification](https://app.gitbook.com/o/-MAz0PPl5s9ulE9xyliu/s/eRh5ljXXvELkmmdiRmg8/functional-documentation/business-rules/pricing/method-of-calculating-a-cart-total-mocct) **Acceptance test** : Consider five products (3 combinations of one product on combination of another product and one standard product) 1) 3 combinations of balloon Standard price :  Impact price :  Quantity : 10 for black, 3 for white,4 for grey in the chart 2) 1 combination of skipping rope : Standard price :  Impact price :  Quantity 2 in the chart 3) Yoyo Standard price :  Impact price : NA Quantity 6 in the chart Result step by step : Step 1 - Standard Price and impact price : Black balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 1.20 = 7.20 White Balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 114 = 120 Grey balloon : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 6 + 0 = 6 Skipping rope : Price_of_product_tax_included_step1 = Retail price (tax incl.) + impact price (tax incl) = 26.40 + 1,10 = 27,50 Yoyo : Price_of_product_tax_included_step1 = Retail price (tax incl.) = 6 Step 6 - Total price included of products Black balloon : Total_cost_included_product_X1 = 7.2 * 10 = 72 White Balloon : Total_cost_included_product_X2 = 120 * 3 = 360 Grey balloon : Total_cost_included_product_X3 = 6 * 4 = 24 Skipping rope Total_cost_included_product_X4 = 27.5 * 2 = 55 Yoyo : Total_cost_included_product_X5 = 6 * 6 = 36 Total_cost_excluded_products =Total_cost_excluded_product_X1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 + Total_cost_excluded_product_X4 + Total_cost_excluded_product_X5 = 72+360+24+55+36 = 547 Step 7 - Calculation of VAT to correct Total_cost_included_ rate20 = Total_cost_excluded_productX1 + Total_cost_excluded_product_X2 + Total_cost_excluded_product_X3 +Total_cost_excluded_product_X5 = 72+360+24+36 = 492 Price tax excluded of product with rate 20% 492/1.2 = 410 VAT_rate_20 = 492 - 410 = 82 Total_cost_included_ rate10 = Total_cost_excluded_productX4 = 55 Price tax excluded of product with rate 10% 55/1.1 = 50 VAT_rate_10 = 55 - 50 = 5 Step 9 Display of the chart Shopping cart result B to C : 2 - Price_of_product_tax_included_step1 3 - Total_cost_included_productX (step 6) 4 - Total_cost_included_products (step 6) 7 - Shipping_cost_tax_included : 0 8- Total_tax_included = Total_cost_included_products (step 6) + Shipping_cost_tax_included 9 - Taxes = VAT_rate_20 + VAT_rate_10 Shopping cart result B to C :  Invoice : 5 - VAT_rate_10 (step 7) VAT_rate_20 (step 7) ![Uploading image.png…]() --- end body --- comments : --- start comments --- --- end comments ---

Retrieve the data from the BDD Same acceptance test as [MOCCT-003_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35395)

[US-Pricing][MOC][Without rounding][B to C] : MOCCT-003_B_to_C : Buy one article with variable VAT - Connection to the BDD

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [US-Pricing][MOC][Without rounding][B to C] : MOCCT-003_B_to_C : Buy one article with variable VAT - Connection to the BDD Issue date: --- start body --- Retrieve the data from the BDD Same acceptance test as [MOCCT-003_B_to_C](https://github.com/PrestaShop/PrestaShop/issues/35395) --- end body --- comments : --- start comments --- --- end comments ---