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 I'm on the categories page, I want to filter my categories by displayed = YES My page filters all the categories and subcategories present on the shop. https://github.com/PrestaShop/PrestaShop/assets/16019289/5ff6f899-f52d-4478-b35d-ce80cc370a7b ### Expected behavior I just want to see that categories of the page I'm looking at. ### Steps to reproduce 1. Go to BO > Catalog > Categories 2. Filter Displayed = YES > Search 3. See that you have more categories displayed that there were before filtering ❌ ### 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 _No response_ ### Your company or customer's name goes here (if applicable). _No response_

BO > Categories page - Filter by "Displayed" shows all the categories AND subcategories instead of just the category displayed on the page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO > Categories page - Filter by "Displayed" shows all the categories AND subcategories instead of just the category displayed on 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 I'm on the categories page, I want to filter my categories by displayed = YES My page filters all the categories and subcategories present on the shop. https://github.com/PrestaShop/PrestaShop/assets/16019289/5ff6f899-f52d-4478-b35d-ce80cc370a7b ### Expected behavior I just want to see that categories of the page I'm looking at. ### Steps to reproduce 1. Go to BO > Catalog > Categories 2. Filter Displayed = YES > Search 3. See that you have more categories displayed that there were before filtering ❌ ### 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 _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 Before : <img width="1216" alt="Screenshot 2024-01-26 at 10 27 00" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/a816b5ec-d472-4d37-ac74-63f5e51530e8"> Now : <img width="978" alt="Screenshot 2024-01-26 at 10 20 11" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/15c08239-d1f7-4e64-8023-8d6fd9b04dce"> ### Expected behavior I should have an outline around the color field. ### Steps to reproduce 1. Go to BO > Shop parameters > Order Settings > Statuses > Click Add a new order status 2. See there's no outline on the color field :x: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Order status return - There's no outline on the color field

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Order status return - There's no outline on the color field Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Before : <img width="1216" alt="Screenshot 2024-01-26 at 10 27 00" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/a816b5ec-d472-4d37-ac74-63f5e51530e8"> Now : <img width="978" alt="Screenshot 2024-01-26 at 10 20 11" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/15c08239-d1f7-4e64-8023-8d6fd9b04dce"> ### Expected behavior I should have an outline around the color field. ### Steps to reproduce 1. Go to BO > Shop parameters > Order Settings > Statuses > Click Add a new order status 2. See there's no outline on the color field :x: ### PrestaShop version(s) where the bug happened develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _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 a new [PR on the `blockwishlist` module](https://github.com/PrestaShop/blockwishlist/pull/236), we use this docker compose file : ```yml version: '3.7' services: prestashop: image: prestashop/prestashop:${PS_VERSION}-apache container_name: prestashop depends_on: - mysql environment: - PS_DEV_MODE=1 - PS_DOMAIN=localhost - PS_LANGUAGE=en - PS_COUNTRY=fr - PS_INSTALL_AUTO=1 - PS_FOLDER_ADMIN=admin-dev - PS_FOLDER_INSTALL=install-dev - ADMIN_MAIL=admin@prestashop.com - ADMIN_PASSWD=prestashop - DB_SERVER=mysql - DB_USER=prestashop - DB_PASSWD=prestashop - DB_NAME=prestashop volumes: - type: bind # Local Path source: ../../ # Mount Path target: /var/www/html/modules/blockwishlist ports: - 80:80 mysql: image: mariadb:lts container_name: prestashop-mysql healthcheck: test: [ 'CMD', 'mysqladmin', 'ping', '--host=localhost', '--user=prestashop', '--password=prestashop', ] interval: 5s timeout: 10s retries: 5 environment: - MYSQL_HOST=mysql - MYSQL_USER=prestashop - MYSQL_PASSWORD=prestashop - MYSQL_ROOT_PASSWORD=prestashop - MYSQL_PORT=3306 - MYSQL_DATABASE=prestashop ``` Only the nightly have a white page in BackOffice. With 8.0.5 & 8.1.3 we have no problems. ### Expected behavior _No response_ ### Steps to reproduce 1. Use the `prestashop/prestashop:nightly-apache` image 2. Go to BO 3. The page is white  ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version docker ### Your company or customer's name goes here (if applicable). @PrestaShopCorp

Docker Nightly : White page (for the BackOffice)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Docker Nightly : White page (for the BackOffice) 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 a new [PR on the `blockwishlist` module](https://github.com/PrestaShop/blockwishlist/pull/236), we use this docker compose file : ```yml version: '3.7' services: prestashop: image: prestashop/prestashop:${PS_VERSION}-apache container_name: prestashop depends_on: - mysql environment: - PS_DEV_MODE=1 - PS_DOMAIN=localhost - PS_LANGUAGE=en - PS_COUNTRY=fr - PS_INSTALL_AUTO=1 - PS_FOLDER_ADMIN=admin-dev - PS_FOLDER_INSTALL=install-dev - ADMIN_MAIL=admin@prestashop.com - ADMIN_PASSWD=prestashop - DB_SERVER=mysql - DB_USER=prestashop - DB_PASSWD=prestashop - DB_NAME=prestashop volumes: - type: bind # Local Path source: ../../ # Mount Path target: /var/www/html/modules/blockwishlist ports: - 80:80 mysql: image: mariadb:lts container_name: prestashop-mysql healthcheck: test: [ 'CMD', 'mysqladmin', 'ping', '--host=localhost', '--user=prestashop', '--password=prestashop', ] interval: 5s timeout: 10s retries: 5 environment: - MYSQL_HOST=mysql - MYSQL_USER=prestashop - MYSQL_PASSWORD=prestashop - MYSQL_ROOT_PASSWORD=prestashop - MYSQL_PORT=3306 - MYSQL_DATABASE=prestashop ``` Only the nightly have a white page in BackOffice. With 8.0.5 & 8.1.3 we have no problems. ### Expected behavior _No response_ ### Steps to reproduce 1. Use the `prestashop/prestashop:nightly-apache` image 2. Go to BO 3. The page is white  ### PrestaShop version(s) where the bug happened 9.0.x ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version docker ### 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 When I create a block with any image and I delete that block later, I'm having a warning in the FO as well a an empty image on one of my block. https://github.com/PrestaShop/PrestaShop/assets/16019289/e2da0c26-1af5-4747-80ef-4830b6c29cbc <img width="844" alt="Screenshot 2024-01-26 at 10 01 05" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/b4915191-cb88-4e90-9d5a-9a27be3fe513"> ``` Warning: finfo_file(/Users/fHea/Desktop/develop/modules/blockreassurance/views/img/img_perso/Screenshot 2024-01-22 at 17.04.31.png): Failed to open stream: No such file or directory in /Users/Desktop/develop/modules/blockreassurance/classes/ReassuranceActivity.php on line 187 Warning: mime_content_type(/Users/fHea/Desktop/develop/modules/blockreassurance/views/img/img_perso/Screenshot 2024-01-22 at 17.04.31.png): Failed to open stream: No such file or directory in /Users/Desktop/develop/modules/blockreassurance/classes/ReassuranceActivity.php on line 192 ``` ### Expected behavior I shouldn't have any warning, my other blocks shouldn't be impacted. ### Steps to reproduce 1. go to BO > modules > blockreassurance > Configure module 2. edit an existing block with a png image 3. create 1 new block with the same png image as the previous one 4. go to FO ✅ 5. delete the block you created 6. go to FO, see warning and the existing block's image has disappeared ❌ ### 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 blockreassurance v5.1.4 ### Your company or customer's name goes here (if applicable). _No response_

blockreassurance - warning and empty image when I delete a block with the same image as another block

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : blockreassurance - warning and empty image when I delete a block with the same image as another block 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 create a block with any image and I delete that block later, I'm having a warning in the FO as well a an empty image on one of my block. https://github.com/PrestaShop/PrestaShop/assets/16019289/e2da0c26-1af5-4747-80ef-4830b6c29cbc <img width="844" alt="Screenshot 2024-01-26 at 10 01 05" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/b4915191-cb88-4e90-9d5a-9a27be3fe513"> ``` Warning: finfo_file(/Users/fHea/Desktop/develop/modules/blockreassurance/views/img/img_perso/Screenshot 2024-01-22 at 17.04.31.png): Failed to open stream: No such file or directory in /Users/Desktop/develop/modules/blockreassurance/classes/ReassuranceActivity.php on line 187 Warning: mime_content_type(/Users/fHea/Desktop/develop/modules/blockreassurance/views/img/img_perso/Screenshot 2024-01-22 at 17.04.31.png): Failed to open stream: No such file or directory in /Users/Desktop/develop/modules/blockreassurance/classes/ReassuranceActivity.php on line 192 ``` ### Expected behavior I shouldn't have any warning, my other blocks shouldn't be impacted. ### Steps to reproduce 1. go to BO > modules > blockreassurance > Configure module 2. edit an existing block with a png image 3. create 1 new block with the same png image as the previous one 4. go to FO ✅ 5. delete the block you created 6. go to FO, see warning and the existing block's image has disappeared ❌ ### 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 blockreassurance v5.1.4 ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments prestashop 8 can not show sample data product category on the main menu when i resave the sample data product category with no updated on this product category, i see the main menu module on backend, it has the product category    ### Expected behavior _No response_ ### Steps to reproduce 1, Install Project whth sample data 2, login the backend 3, resave one product category 4, missed on front main menu ### PrestaShop version(s) where the bug happened 8.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_

prestashop 8 can not show sample data product category on the main menu when i resave the sample data product category

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : prestashop 8 can not show sample data product category on the main menu when i resave the sample data product category 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 8 can not show sample data product category on the main menu when i resave the sample data product category with no updated on this product category, i see the main menu module on backend, it has the product category    ### Expected behavior _No response_ ### Steps to reproduce 1, Install Project whth sample data 2, login the backend 3, resave one product category 4, missed on front main menu ### PrestaShop version(s) where the bug happened 8.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 hello frineds In prestashop 8.1.3, hooks not enabled or disabled. After I enable a hook (or disable) and refreshing the page I see that it is disabled (enabled) again. ### Expected behavior It should be activated and remain in that state. ### Steps to reproduce 1. in prestashop 8.1.3, Go to "Designs" > "Positions" 2. for example search for "displayProductAdditionalInfo" and enable it. 3. in browser refresh the page, 4. I see it goes to "disable" https://github.com/PrestaShop/PrestaShop/assets/11363195/d49e9a56-880c-4ce5-8294-b23cb6799f96 ### 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_

hooks not enable or disable at all.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : hooks not enable or disable at all. 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 frineds In prestashop 8.1.3, hooks not enabled or disabled. After I enable a hook (or disable) and refreshing the page I see that it is disabled (enabled) again. ### Expected behavior It should be activated and remain in that state. ### Steps to reproduce 1. in prestashop 8.1.3, Go to "Designs" > "Positions" 2. for example search for "displayProductAdditionalInfo" and enable it. 3. in browser refresh the page, 4. I see it goes to "disable" https://github.com/PrestaShop/PrestaShop/assets/11363195/d49e9a56-880c-4ce5-8294-b23cb6799f96 ### 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 ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Trying to translate front-office with PS 9.0.0 gets a fatal error page  ### Expected behavior It should open the Translation Edit page without error ### Steps to reproduce 1. Install PrestaShop using `develop` branch, in French 2. Go to back-office, open Translation menu 3. Select the following options (see below the screenshot) 4. Click on "Modify"  ### 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_

Trying to translate front-office with PS 9.0.0 gets a fatal error page

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Trying to translate front-office with PS 9.0.0 gets a fatal error 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 Trying to translate front-office with PS 9.0.0 gets a fatal error page  ### Expected behavior It should open the Translation Edit page without error ### Steps to reproduce 1. Install PrestaShop using `develop` branch, in French 2. Go to back-office, open Translation menu 3. Select the following options (see below the screenshot) 4. Click on "Modify"  ### 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 ---

SPIKE CU : incermental db migration ( php into SQL vs SQL into php vs other ...) ?

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : SPIKE CU : incermental db migration ( php into SQL vs SQL into php vs other ...) ? 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 The module ps_edition_basic on file src->Presetner->SetupGuideDataPresenter.php line 168 is pointing to a route that does not exist 'href' => $router->generate('admin_logos_index'), This is causing an error 500 on BO as such route does not exist  ### Expected behavior _No response_ ### Steps to reproduce Enter to BO with debug on ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_edition_basic ### Your company or customer's name goes here (if applicable). Multiservicios Austral (PS partner)

Error on ps_edition_basic Route error:500

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error on ps_edition_basic Route error:500 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The module ps_edition_basic on file src->Presetner->SetupGuideDataPresenter.php line 168 is pointing to a route that does not exist 'href' => $router->generate('admin_logos_index'), This is causing an error 500 on BO as such route does not exist  ### Expected behavior _No response_ ### Steps to reproduce Enter to BO with debug on ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_edition_basic ### Your company or customer's name goes here (if applicable). Multiservicios Austral (PS partner) --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to upgrade prestashop so I can have an up2date software This is part of [CLI : ps-upgrade:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) upgrade files is a step of the upgrade ## Description **\<FILE_ORIGINAL\>** : a file (ex: a php file ) of what the prestashop installed should have (extract from the xml file , example from prestashop-8.1.3.xml if prestashop-8.1.3 is currently installed ) **\<FILE_CURRENT\>** : a file (ex: a php file ) of prestashop **currently installed (real)** **\<FILE_TARGET\>** : a file (ex: a php file ) of prestashop **to install** should have (extract from the xml file , example from prestashop-8.1.3.xml if prestashop-8.1.3 is currently installed ) **\<MD5_FILE_ORIGINAL\>** : md5sum of \<FILE_ORIGINAL\> extract form xml file **\<MD5_FILE_CURRENT\>** : md5sum of \<FILE_CURRENT\> , compute from with the current installation (at --prestashop-path \<PATH\> ) **\<MD5_FILE_TARGET\>** : md5sum of \<FILE_TARGET\> extract form xml file ( prestashop to install ) xml file (SOURCE & TARGET xml file ) should be download if not available on the disk / filesystem ( see TS ) --- ### if \<MD5_FILE_ORIGINAL\> == \<MD5_FILE_CURRENT\> #### if \<MD5_FILE_TARGET\> == \<MD5_FILE_ORIGINAL\> Then do nothing ( means let the file as is ) #### if \<MD5_FILE_TARGET\> ( or \<FILE_TARGET\> ? ) does not exist Then delete \<FILE_CURRENT\> ---- ### if \<MD5_FILE_ORIGINAL\> != \<MD5_FILE_CURRENT\> #### . if \<MD5_CURRENT\> == \<MD5_TARGET\> Does nothing #### . if \<MD5_CURRENT\> != \<MD5_TARGET\> Suivant ce qui a été vu en check Message : You have modified \<FILE_CURRENT> of your current installation : what do you want to do here ? [1] Backup it & Replace it by our new implementation [2] Replace it by our new implementation without backup ( WARNING you will loose your modifications ) [3] Keep your modified file ? ( WARNING this could make your new installation unusable ) ---- ( revoir messages Fabien / @Julievrz ? ) ### if \<FILE_TARGET> is a new file #### if it does not exists into current : \<FILE_CURRENT\> Then add it #### if it exists into current \<FILE_CURRENT\> Message : ``` You have a <FILE_CURRENT> in your current installation : what to do here ? [1] Backup it & Replace it by our new implementation [2] Replace it by our new implementation without backup ( WARNING you will loose your modifications ) [3] Keep your modified file ? ( WARNING this could make your new installation unusable ) ``` ### if ORIGINAL_PACKAGE.xml is not available 1 . Download xml file for \<ORIGINAL PACKAGE\> Message: ``` Dowloading <ORIGINAL_PACKAGE.xml> file .....<STATUS> ``` if download is ok \<STATUS\> = OK if download is ko \<STATUS\> = KO + Message \<ERROR\> 2. Download ask md5 check for xml file for \<SOURCE PACKAGE\> through API Verify integrity for \<SOURCE_PACKAGE.xml.M\> file .....\<STATUS\> if md5sum is ok \<STATUS\> = OK if md5sum is ko \<STATUS\> = KO: integrity check failed ## Acceptance tests ### Acceptance test : OK - Without Download ``` Upgrading files ....OK ``` ### Acceptance test : KO - Without Download ``` Upgrading files ....KO <ERRORS> ``` See with dev for \<ERRORS\> ### Acceptance test : OK - With Download ``` Dowloading <ORIGINAL_PACKAGE.xml> file ....OK Upgrading files ....OK ``` ### Acceptance test : KO - With Download KO ``` Dowloading <ORIGINAL_PACKAGE.xml> file ....KO ``` ( TODO ) ### Technical specs - [ ] #35159 - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command.

EPIC - CLI : ps-upgrade:upgrade - implement upgrade files

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:upgrade - implement upgrade files Issue date: --- start body --- As a user I want to upgrade prestashop so I can have an up2date software This is part of [CLI : ps-upgrade:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) upgrade files is a step of the upgrade ## Description **\<FILE_ORIGINAL\>** : a file (ex: a php file ) of what the prestashop installed should have (extract from the xml file , example from prestashop-8.1.3.xml if prestashop-8.1.3 is currently installed ) **\<FILE_CURRENT\>** : a file (ex: a php file ) of prestashop **currently installed (real)** **\<FILE_TARGET\>** : a file (ex: a php file ) of prestashop **to install** should have (extract from the xml file , example from prestashop-8.1.3.xml if prestashop-8.1.3 is currently installed ) **\<MD5_FILE_ORIGINAL\>** : md5sum of \<FILE_ORIGINAL\> extract form xml file **\<MD5_FILE_CURRENT\>** : md5sum of \<FILE_CURRENT\> , compute from with the current installation (at --prestashop-path \<PATH\> ) **\<MD5_FILE_TARGET\>** : md5sum of \<FILE_TARGET\> extract form xml file ( prestashop to install ) xml file (SOURCE & TARGET xml file ) should be download if not available on the disk / filesystem ( see TS ) --- ### if \<MD5_FILE_ORIGINAL\> == \<MD5_FILE_CURRENT\> #### if \<MD5_FILE_TARGET\> == \<MD5_FILE_ORIGINAL\> Then do nothing ( means let the file as is ) #### if \<MD5_FILE_TARGET\> ( or \<FILE_TARGET\> ? ) does not exist Then delete \<FILE_CURRENT\> ---- ### if \<MD5_FILE_ORIGINAL\> != \<MD5_FILE_CURRENT\> #### . if \<MD5_CURRENT\> == \<MD5_TARGET\> Does nothing #### . if \<MD5_CURRENT\> != \<MD5_TARGET\> Suivant ce qui a été vu en check Message : You have modified \<FILE_CURRENT> of your current installation : what do you want to do here ? [1] Backup it & Replace it by our new implementation [2] Replace it by our new implementation without backup ( WARNING you will loose your modifications ) [3] Keep your modified file ? ( WARNING this could make your new installation unusable ) ---- ( revoir messages Fabien / @Julievrz ? ) ### if \<FILE_TARGET> is a new file #### if it does not exists into current : \<FILE_CURRENT\> Then add it #### if it exists into current \<FILE_CURRENT\> Message : ``` You have a <FILE_CURRENT> in your current installation : what to do here ? [1] Backup it & Replace it by our new implementation [2] Replace it by our new implementation without backup ( WARNING you will loose your modifications ) [3] Keep your modified file ? ( WARNING this could make your new installation unusable ) ``` ### if ORIGINAL_PACKAGE.xml is not available 1 . Download xml file for \<ORIGINAL PACKAGE\> Message: ``` Dowloading <ORIGINAL_PACKAGE.xml> file .....<STATUS> ``` if download is ok \<STATUS\> = OK if download is ko \<STATUS\> = KO + Message \<ERROR\> 2. Download ask md5 check for xml file for \<SOURCE PACKAGE\> through API Verify integrity for \<SOURCE_PACKAGE.xml.M\> file .....\<STATUS\> if md5sum is ok \<STATUS\> = OK if md5sum is ko \<STATUS\> = KO: integrity check failed ## Acceptance tests ### Acceptance test : OK - Without Download ``` Upgrading files ....OK ``` ### Acceptance test : KO - Without Download ``` Upgrading files ....KO <ERRORS> ``` See with dev for \<ERRORS\> ### Acceptance test : OK - With Download ``` Dowloading <ORIGINAL_PACKAGE.xml> file ....OK Upgrading files ....OK ``` ### Acceptance test : KO - With Download KO ``` Dowloading <ORIGINAL_PACKAGE.xml> file ....KO ``` ( TODO ) ### Technical specs - [ ] #35159 - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command. --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to upgrade prestashop so I can have an up2date software This is part of This is part of [CLI : ps-upgrade:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) ## Description Verify everything is ok 1. Disable maintenance 2. Diagnostic ### Disable maintenance See [maintenance](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44044496) ### Tasks post installation #### Caches #### Images ? #### Natives Modules ? ### Diagnostic See doctor ? ### Technical specs - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command.

EPIC - CLI : ps-upgrade:upgrade - implement post installation

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:upgrade - implement post installation Issue date: --- start body --- As a user I want to upgrade prestashop so I can have an up2date software This is part of This is part of [CLI : ps-upgrade:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) ## Description Verify everything is ok 1. Disable maintenance 2. Diagnostic ### Disable maintenance See [maintenance](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44044496) ### Tasks post installation #### Caches #### Images ? #### Natives Modules ? ### Diagnostic See doctor ? ### Technical specs - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command. --- 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 have a problem with the faceted search module. When I go to enable filters in my view model, they don't activate. What could be the problem? ### Expected behavior Impossibile to enable filters in faceted module. ### Steps to reproduce - Go to faceted search module - Edit the the view model - Enable at least one filter - Save - Refresh the page - All filter are disabled again https://github.com/PrestaShop/PrestaShop/assets/113089629/d2e47f0e-5de7-42f5-b3ec-00e4ea33d761 ### 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 ps_facetedsearch 3.14.1 ### Your company or customer's name goes here (if applicable). Promydea Srls

Faceted Search issue

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Faceted Search issue 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 have a problem with the faceted search module. When I go to enable filters in my view model, they don't activate. What could be the problem? ### Expected behavior Impossibile to enable filters in faceted module. ### Steps to reproduce - Go to faceted search module - Edit the the view model - Enable at least one filter - Save - Refresh the page - All filter are disabled again https://github.com/PrestaShop/PrestaShop/assets/113089629/d2e47f0e-5de7-42f5-b3ec-00e4ea33d761 ### 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 ps_facetedsearch 3.14.1 ### Your company or customer's name goes here (if applicable). Promydea Srls --- end body --- comments : --- start comments --- --- end comments ---

CliApp: Create this step in `ps-upgrade:shop:compatibility-check` command.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create this step in `ps-upgrade:shop:compatibility-check` command. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: Create `VersionCompatibilityChecker` aim to check the compatibility with the targeted version of PS against the targeted env ( web / cli )

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: Create `VersionCompatibilityChecker` aim to check the compatibility with the targeted version of PS against the targeted env ( web / cli ) Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to know the my system is compatibile with the new version of PrestaShop so I can upgrade prestashop ## Description Implements **ps-upgrade:check-compatibility - \<TARGET_VERSION\> --checklist \<CHECKLIST\>** Check the compatibility for a TARGET version With \<TARGET_VERSION\> : targeted vesion \<CHECKLIST\> : list of the checks (mem, cpu, swap, disk, php-version, php-ext, php-settings, db-version) ### Help Message _ps-upgrade:check-compatibility , check the compatibility for a prestashop version Usage: ps:upgrade:check-compatibility --checklist [ARGS_LIST] \<TARGET_VERSION\> With \<TARGET_VERSION\> the prestashop version you want to verify --checklist separate by comma : php-version, php-ext, acces-db -verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ### memory (mem) Optional : not in MVP ### cpu (cpu) Optional : not in MVP ### swap (swap) Optional : not in MVP ### disk space (disk) Optional : not in MVP ### php-version (php-version) Check PHP compatibility ### php-ext (php-ext) Check php-ext version compatibility ### php-settings (php-settings) Check php-settings (such as memory_limit) compatibility ### database version (db-version) Optional : not in MVP ### database access (db-access) Check DB access ### Message (STDOUT) For each test (specify by checklist or all ) one per line \<TEST NAME\> .....\<OK|KO\> : \<DESCRIPTION if KO\> Examples `php-version ....OK ` `php-version ....KO : prestashop-9.0.1 required PHP >= 8.1 ` A full example ``` $ check-compatibility --check-list=mem,cpu,php-version,db,db-access /--package=/somewhere/prestashop-9.0.1.zip mem....SKIP : Can not be test cpu: OK php-version: KO - please upgrade your system to PHP >= 8.1 php-ext : OK ``` ## Acceptances tests ### Accestance test : help ``` $ ps-upgrade:check-compatibility --help ps-upgrade:check-compatibility , check the compatibility for a prestashop version Usage: ps:upgrade:check-compatibility --checklist [ARGS_LIST] \<TARGET_VERSION\> With \<TARGET_VERSION\> the prestashop version you want to verify --checklist separate by comma : php-version, php-ext, acces-db -verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output ``` ### Acceptance test : OK TODO jeu de tests ``` $ ps-upgrade:check-compatibility --check-list=php-version,php-ext,db-access 9.0.0 php-version: OK php-ext : OK db-access: OK ``` ### Acceptance test : KO TODO per test ``` $ ps-upgrade:check-compatibility --check-list=php-version,php-ext,db-access 9.0.0 php-version: KO <ERROR> php-ext : OK <ERROR> db-access: OK <ERROR> ``` | Check type| Errors | |----------------|----------| | php-version | please upgrade your system to PHP >= A.B and <= C.D | | php-version | please downgrade your system to PHP >= A.B and <= C.D | | php-ext | please upgrade your <EXT> to >= A.B and <= C.D | | php-ext * | please downgrade your <EXT> to >= A.B and <= C.D | | php-ext | please downgrade your <EXT> to >= A.B and <= C.D | | php-settings * | <SETTINGS> Should be <MESSAGE> | | db-access * | TODO | * You could have multiple error = multiple extension / settings (multiline) ### Technical specs - [ ] #35163 - [ ] #35164

EPIC - CLI : ps-upgrade:check-compatibility - implement check-compatibility

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:check-compatibility - implement check-compatibility Issue date: --- start body --- As a user I want to know the my system is compatibile with the new version of PrestaShop so I can upgrade prestashop ## Description Implements **ps-upgrade:check-compatibility - \<TARGET_VERSION\> --checklist \<CHECKLIST\>** Check the compatibility for a TARGET version With \<TARGET_VERSION\> : targeted vesion \<CHECKLIST\> : list of the checks (mem, cpu, swap, disk, php-version, php-ext, php-settings, db-version) ### Help Message _ps-upgrade:check-compatibility , check the compatibility for a prestashop version Usage: ps:upgrade:check-compatibility --checklist [ARGS_LIST] \<TARGET_VERSION\> With \<TARGET_VERSION\> the prestashop version you want to verify --checklist separate by comma : php-version, php-ext, acces-db -verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ### memory (mem) Optional : not in MVP ### cpu (cpu) Optional : not in MVP ### swap (swap) Optional : not in MVP ### disk space (disk) Optional : not in MVP ### php-version (php-version) Check PHP compatibility ### php-ext (php-ext) Check php-ext version compatibility ### php-settings (php-settings) Check php-settings (such as memory_limit) compatibility ### database version (db-version) Optional : not in MVP ### database access (db-access) Check DB access ### Message (STDOUT) For each test (specify by checklist or all ) one per line \<TEST NAME\> .....\<OK|KO\> : \<DESCRIPTION if KO\> Examples `php-version ....OK ` `php-version ....KO : prestashop-9.0.1 required PHP >= 8.1 ` A full example ``` $ check-compatibility --check-list=mem,cpu,php-version,db,db-access /--package=/somewhere/prestashop-9.0.1.zip mem....SKIP : Can not be test cpu: OK php-version: KO - please upgrade your system to PHP >= 8.1 php-ext : OK ``` ## Acceptances tests ### Accestance test : help ``` $ ps-upgrade:check-compatibility --help ps-upgrade:check-compatibility , check the compatibility for a prestashop version Usage: ps:upgrade:check-compatibility --checklist [ARGS_LIST] \<TARGET_VERSION\> With \<TARGET_VERSION\> the prestashop version you want to verify --checklist separate by comma : php-version, php-ext, acces-db -verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output ``` ### Acceptance test : OK TODO jeu de tests ``` $ ps-upgrade:check-compatibility --check-list=php-version,php-ext,db-access 9.0.0 php-version: OK php-ext : OK db-access: OK ``` ### Acceptance test : KO TODO per test ``` $ ps-upgrade:check-compatibility --check-list=php-version,php-ext,db-access 9.0.0 php-version: KO <ERROR> php-ext : OK <ERROR> db-access: OK <ERROR> ``` | Check type| Errors | |----------------|----------| | php-version | please upgrade your system to PHP >= A.B and <= C.D | | php-version | please downgrade your system to PHP >= A.B and <= C.D | | php-ext | please upgrade your <EXT> to >= A.B and <= C.D | | php-ext * | please downgrade your <EXT> to >= A.B and <= C.D | | php-ext | please downgrade your <EXT> to >= A.B and <= C.D | | php-settings * | <SETTINGS> Should be <MESSAGE> | | db-access * | TODO | * You could have multiple error = multiple extension / settings (multiline) ### Technical specs - [ ] #35163 - [ ] #35164 --- end body --- comments : --- start comments --- --- end comments ---

Depends #35171

CU: Create `DbMigrator` aim to migrate the database.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: Create `DbMigrator` aim to migrate the database. Issue date: --- start body --- Depends #35171 --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to upgrade prestashop so I can have an up2date software This is part of "CLI: ps-upgrade:uprade command line upgrade db is a step of the upgrade ## Description **\<DB_STRUCT_SOURCE\>** : the file describing the DB structure of **what the current installation SHOULD have** **\<DB_STRUCT_CURRENT\>** : the current DB structure **currently installed (real)** **\<DB_STRUCT_TARGET\>** : the file describing the DB structure of **what the current installation WILL have** ( after installation and if no alteration ) db struct files (\<DB_STRUCT_SOURCE\> and \<DB_STRUCT_TARGET\> ) should have been download if not available on the disk / filesystem ( see TS ) ### if \<DB_STRUCT_SOURCE\> != \<DB_STRUCT_CURRENT\> Message _WARNING : the database have been alterated using prestashop tables ; it breaks ou guidellines and could make prestashop unusable_ \<List of tables / rows altered> Do you want to continue ? [N/y] ## Acceptance test ### Acceptance test OK Case current prestashop ( and \<DB_STUCT_CURRENT\> ) has not been modified ``` Upgrading database ....OK ``` ### Acceptance test KO Case current prestashop ( and \<DB_STUCT_CURRENT\> ) has been modified ``` Upgrading database ....KO \<ERROR\> ``` See with devs for \<ERRORS\> ### Technical specs - [ ] #35161 - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command.

EPIC - CLI : ps-upgrade:upgrade - implement upgrade db

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:upgrade - implement upgrade db Issue date: --- start body --- As a user I want to upgrade prestashop so I can have an up2date software This is part of "CLI: ps-upgrade:uprade command line upgrade db is a step of the upgrade ## Description **\<DB_STRUCT_SOURCE\>** : the file describing the DB structure of **what the current installation SHOULD have** **\<DB_STRUCT_CURRENT\>** : the current DB structure **currently installed (real)** **\<DB_STRUCT_TARGET\>** : the file describing the DB structure of **what the current installation WILL have** ( after installation and if no alteration ) db struct files (\<DB_STRUCT_SOURCE\> and \<DB_STRUCT_TARGET\> ) should have been download if not available on the disk / filesystem ( see TS ) ### if \<DB_STRUCT_SOURCE\> != \<DB_STRUCT_CURRENT\> Message _WARNING : the database have been alterated using prestashop tables ; it breaks ou guidellines and could make prestashop unusable_ \<List of tables / rows altered> Do you want to continue ? [N/y] ## Acceptance test ### Acceptance test OK Case current prestashop ( and \<DB_STUCT_CURRENT\> ) has not been modified ``` Upgrading database ....OK ``` ### Acceptance test KO Case current prestashop ( and \<DB_STUCT_CURRENT\> ) has been modified ``` Upgrading database ....KO \<ERROR\> ``` See with devs for \<ERRORS\> ### Technical specs - [ ] #35161 - [ ] CliApp: Create this step in `ps-upgrade:shop:upgrade` command. --- end body --- comments : --- start comments --- --- end comments ---

CU: Create `ArchiveExtractor` aim to unzip the PS downloaded archive and add/replace/remove files on the fly.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: Create `ArchiveExtractor` aim to unzip the PS downloaded archive and add/replace/remove files on the fly. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to upgrade prestashop so I can have an up2date software This is part of [CLI: ps-upgrade:uprade command line ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) unzip is a step of the upgrade ( see [Miro](https://miro.com/app/board/uXjVNO6-Gq8=/?share_link_id=888804706864) ) TODO Voir les questions de filesystem ( avec @jolelievre , @boherm ) ## Description Unzip the package at \<PATH TARGET\> ( zip file ) ### Message STDOUT Progress bar ? Format _Unzip \<PACKAGE\>...._ _\<STATUS\>_ If unzip succeeded Then STATUS = _Done. File unzip into \<PATH_UNZIPPED\>_ If unzip failed Then \<STATUS\> = _Failed ;: error message_ Examples ``` Unzip prestashop-9.0.0.zip .... ============================== Done. File unzip into /var/www/prestashop/tmp/ ``` ``` Unzip prestashop-9.0.0.zip .... ============================== Failed. Not enough space on you filesystem ``` ## Acceptance tests ### Acceptance test : OK Test with a valid prestashop package ``` $ps-upgrade:upgrade --unzip /path/to/prestashop-X.Y.Z.zip Done. File unzip into /var/www/prestashop/tmp/ ``` and verify into /var/www/prestashop/tmp/ ### Acceptance test : KO Corrupt a prestashop archive : Example : ``` $dd bs=1024 count=1048576 </dev/urandom >/path/to/prestashop-X.Y.Z.zip ``` Then test it : ``` $ps-upgrade:upgrade --unzip /path/to/prestashop-X.Y.Z.zip Failed . file corrupted ``` See with dev all \<ERROR\> Example : - File Corrupted - Not enough disk space ### Technical specs - [ ] #35159 - [ ] CliApp: Create this step in [ps-upgrade:shop:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) command.

CLI : ps-upgrade:upgrade - implement unzip

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CLI : ps-upgrade:upgrade - implement unzip Issue date: --- start body --- As a user I want to upgrade prestashop so I can have an up2date software This is part of [CLI: ps-upgrade:uprade command line ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) unzip is a step of the upgrade ( see [Miro](https://miro.com/app/board/uXjVNO6-Gq8=/?share_link_id=888804706864) ) TODO Voir les questions de filesystem ( avec @jolelievre , @boherm ) ## Description Unzip the package at \<PATH TARGET\> ( zip file ) ### Message STDOUT Progress bar ? Format _Unzip \<PACKAGE\>...._ _\<STATUS\>_ If unzip succeeded Then STATUS = _Done. File unzip into \<PATH_UNZIPPED\>_ If unzip failed Then \<STATUS\> = _Failed ;: error message_ Examples ``` Unzip prestashop-9.0.0.zip .... ============================== Done. File unzip into /var/www/prestashop/tmp/ ``` ``` Unzip prestashop-9.0.0.zip .... ============================== Failed. Not enough space on you filesystem ``` ## Acceptance tests ### Acceptance test : OK Test with a valid prestashop package ``` $ps-upgrade:upgrade --unzip /path/to/prestashop-X.Y.Z.zip Done. File unzip into /var/www/prestashop/tmp/ ``` and verify into /var/www/prestashop/tmp/ ### Acceptance test : KO Corrupt a prestashop archive : Example : ``` $dd bs=1024 count=1048576 </dev/urandom >/path/to/prestashop-X.Y.Z.zip ``` Then test it : ``` $ps-upgrade:upgrade --unzip /path/to/prestashop-X.Y.Z.zip Failed . file corrupted ``` See with dev all \<ERROR\> Example : - File Corrupted - Not enough disk space ### Technical specs - [ ] #35159 - [ ] CliApp: Create this step in [ps-upgrade:shop:upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44108684) command. --- end body --- comments : --- start comments --- --- end comments ---

TODO : Workflow ( @fabienvallon )

CliApp: Create this step in `ps-upgrade:shop:upgrade` command.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create this step in `ps-upgrade:shop:upgrade` command. Issue date: --- start body --- TODO : Workflow ( @fabienvallon ) --- end body --- comments : --- start comments --- --- end comments ---

Spike à prévoir

CU : Persistance of upgrade process

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU : Persistance of upgrade process Issue date: --- start body --- Spike à prévoir --- 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 log appears when I leave a legacy page `[Thu Jan 25 09:44:44.235126 2024] [php:error] [pid 1529] [client 172.21.0.1:38970] PHP Fatal error: Uncaught ErrorException: Warning: Undefined property: Symfony\\Component\\VarDumper\\Caster\\CutStub::$cache_locking in /var/www/html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php:737\nStack trace:\n#0 [internal function]: Smarty_Internal_Template->__destruct()\n#1 {main}\n thrown in /var/www/html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php on line 737` I think this is related to debug mode, to be confirmed. This happened in a docker environment. ### Expected behavior No php:error in logs ### Steps to reproduce 1. Set up a fresh store (in debug mode, to be sure) 2. Login and go to the BO dashboard 3. Navigated to another page, like orders for example 4. See logs ### 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_

PHP Fatal error in logs

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PHP Fatal error in logs Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments A log appears when I leave a legacy page `[Thu Jan 25 09:44:44.235126 2024] [php:error] [pid 1529] [client 172.21.0.1:38970] PHP Fatal error: Uncaught ErrorException: Warning: Undefined property: Symfony\\Component\\VarDumper\\Caster\\CutStub::$cache_locking in /var/www/html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php:737\nStack trace:\n#0 [internal function]: Smarty_Internal_Template->__destruct()\n#1 {main}\n thrown in /var/www/html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php on line 737` I think this is related to debug mode, to be confirmed. This happened in a docker environment. ### Expected behavior No php:error in logs ### Steps to reproduce 1. Set up a fresh store (in debug mode, to be sure) 2. Login and go to the BO dashboard 3. Navigated to another page, like orders for example 4. See logs ### 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 ---

Check doctor implementation and services.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Check doctor implementation and services. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to upgrade prestashop so I can have an up2date software This is part of "CLI: ps-upgrade:uprade command line upgrade pre-installation is a step of the upgrade ## Description The pre-installation is split in this steps : 1. Verify md5sum for the \<TARGET_PACKAGE\>, the \<TARGET_XML_FILE\>, the \<TARGET_DBSTRUCT_FILE\> and, optionally check the md5sum of all files into \<TARGET_PACKAGE\> 2. Verify it BO & FO are in maintenance mode 3. Verify consistency between \<ORGINAL_FILES\> and \<CURRENT_FILES\> 4. Verify consistency between \<ORIGINAL_DBSTRUCT\> and \<CURRENT_DBSTRUC\> 5. Snapshot ( if specified ) ### Verify md5sum See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Verify maintenance mode See[ ps-upgrade:maintenance ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44044496) ### Verify files consistency See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Verify db consistency See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Snapshot See ps-snapshot:snapshot ( TODO ) ## Acceptance tests TODO ### Technical specs - [ ] #35156 - [ ] CliApp: Check targeted version compatibility with current system, before to upgrade. - [ ] #35157

EPIC - ps-upgrade:upgrade - implement pre-installation

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - ps-upgrade:upgrade - implement pre-installation Issue date: --- start body --- As a user I want to upgrade prestashop so I can have an up2date software This is part of "CLI: ps-upgrade:uprade command line upgrade pre-installation is a step of the upgrade ## Description The pre-installation is split in this steps : 1. Verify md5sum for the \<TARGET_PACKAGE\>, the \<TARGET_XML_FILE\>, the \<TARGET_DBSTRUCT_FILE\> and, optionally check the md5sum of all files into \<TARGET_PACKAGE\> 2. Verify it BO & FO are in maintenance mode 3. Verify consistency between \<ORGINAL_FILES\> and \<CURRENT_FILES\> 4. Verify consistency between \<ORIGINAL_DBSTRUCT\> and \<CURRENT_DBSTRUC\> 5. Snapshot ( if specified ) ### Verify md5sum See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Verify maintenance mode See[ ps-upgrade:maintenance ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44044496) ### Verify files consistency See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Verify db consistency See [ps-upgrade:doctor ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44721119) ### Snapshot See ps-snapshot:snapshot ( TODO ) ## Acceptance tests TODO ### Technical specs - [ ] #35156 - [ ] CliApp: Check targeted version compatibility with current system, before to upgrade. - [ ] #35157 --- end body --- comments : --- start comments --- --- end comments ---

CliApp: Create the `ps-upgrade:shop:maintenance` command.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create the `ps-upgrade:shop:maintenance` command. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

If .ps-upgrade.maintenance.html file with maintenant page content doesn't exist, we create this file in root project of PS. For Enable: - We edit the index.php to include the maintenance page at first then exit with http code 503 with retry after some time. (for BO and FO !) For Disable: - We edit the index.php te move the inclusion of the maintenance page. (for BO and FO !) For status: - We need to check index.php for BO and FO. UX => Maintenance for BO / icon

CU: aim to enable or disable BO and FO at the same time

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: aim to enable or disable BO and FO at the same time Issue date: --- start body --- If .ps-upgrade.maintenance.html file with maintenant page content doesn't exist, we create this file in root project of PS. For Enable: - We edit the index.php to include the maintenance page at first then exit with http code 503 with retry after some time. (for BO and FO !) For Disable: - We edit the index.php te move the inclusion of the maintenance page. (for BO and FO !) For status: - We need to check index.php for BO and FO. UX => Maintenance for BO / icon --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to enable or disable the maintenance of Prestashop so I can safety upgrade PrestaShop ## Description AJOUTER WebServices (Potentiel) AND API Pour MVP Webservices seulement Pour MVP API : pour l'instant derrière admin => A voir si on change (alpha ) ### Help Message : _--verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ## Behaviour **ps-upgrade:maintenance --prestashop-path \<PATH\> \<ENABLE|DISABLE|STATUS\>** With \<PATH\> prestashop directory for the current (installed) prestashop ( or current directory of \<PATH\> is not specify ) --force : optional force the maintenance without interaction ( same as -no-interaction) ### Case ENABLE Once validated by the user (except if --force or --no-interaction is specified ) the tool 1. Enable maintenance in FO if the FO is not in maintenance mode or let the FO in maintenance if the FO is already in maintenance mode 2. Enable maintenance in BO if the FO is not in maintenance mode or let the BO in maintenance if the BO is already in maintenance mode 3. Exit See also Message STDOUT table & messages ### Case DISABLE Once validated by the user (except if --force or --no-interaction is specified ) the tool ( est-ce vraiment nécessaire ????) 1. Disable maintenance in FO if the FO is in maintenance mode or let the FO as is if the FO is not in maintenance mode 2.Disable maintenance in BO if the BO is in maintenance mode or let the BO as is if the BO is not in maintenance mode 3. Exit See also Message STDOUT table & messages ### Case STATUS 1. Display the maintenance status of FO ( Enabled or Disabled) 2. Display the maintenance status of BO ( Enabled or Disabled) 3. Exit ### Message STDOUT SAUF STATUS If --force (or --no-interaction) not specifiy _WARNING : BackOffice & FrontOffice vont être mis en /sortir du mode maintenance Are you sure : y/N_ Default NO Except if the user type __y__ or __yes__ (case insensitiv) the the ## Message (STDOUT) This is the outputs of the tool For BO  For FO  ### Message (STDERR) Errors messages (voir avec Boris / jo ) #### Error : Can not enable maintenance If on _maintenance ENABLE_ if the tool can not enable the maintenance (except if already enable : see Message (STDOUT) `Error : Can not enable FO maintenance ( use --vv or --vvv for more informations) ` ( for FO ) `Error : Can not enable BO maintenance ( use --vv or --vvv for more informations) ` ( for BO ) #### Error : Can not disable maintenance If on _DISABLE_ if the tool can not enable the maintenance (except if already disable : see Message (STDOUT) ) `Error : Can not disable FO maintenance ( use --vv or --vvv for more informations) ` (for FO ) `Error : Can not disable BO maintenance ( use --vv or --vvv for more informations) ` ( for BO ) #### Error: Can not get status If on _STATUS_ if the tool can not get the maintenance status `Error : Can not get the FO maintenance status ( use --vv or --vvv for more informations) ` ( for FO ) `Error : Can not get the BO maintenance status ( use --vv or --vvv for more informations) ` ( for BO ) ### Acceptances tests #### Acceptance test : help ``` $ ps-upgrade:maintenance --help --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output ``` #### Acceptance test ENABLE OK BO & FO are up & running ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enable maintenance mode ....OK BO : Enabling maintenance mode...OK ``` #### Acceptance test DISABLE OK BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....OK BO : Disabling maintenance mode...OK ``` ### Acceptance test ENABLE : BO KO BO & FO are up & running `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....OK BO : Enabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ` ## Acceptance test ENABLE : FO KO BO & FO are up & running `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Enabling maintenance mode...OK ` ## Acceptance test ENABLE : FO+BO KO BO & FO are up & running ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Enabling maintenance mode... KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test DISABLE BO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....OK BO : Disabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test DISABLE FO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Disabling maintenance mode...OK ``` #### Acceptance test DISABLE FO + BO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Disabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test STATUS OK (FO is maintenance / BO is maintenance) BO & FO are in maintenance mode `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is in maintenance mode BO : Is in maintenance mode ` #### Acceptance test STATUS OK (FO is maintenance / BO is NOT maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is in maintenance mode BO : Is NOT in maintenance mode ``` #### Acceptance test STATUS OK (FO is NOT maintenance / BO is in maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is NOT in maintenance mode BO : Is in maintenance mode ``` #### Acceptance test STATUS OK (FO is NOT maintenance / BO is NOT in maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is NOT in maintenance mode BO : Is NOT in maintenance mode ``` Add Failed case ? @fabienvallon ### Technical specs - [ ] #35151 - If `.ps-upgrade.maintenance.html` file with maintenant page content doesn't exist, we create this file in root project of PS. - For Enable: - We edit the `index.php` to include the maintenance page at first then exit with http code 503 with retry after some time. (for BO and FO !) - For Disable: - We edit the `index.php` te move the inclusion of the maintenance page. (for BO and FO !) - For status: - We need to check `index.php` for BO and FO. - [ ] #35152 ### Reflexion Fabien / Boris A voir si on ajoute BO et FO en séparé / avec comportement par défaut les 2

EPIC - CLI : ps-upgrade:maintenance - implement maintenance

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:maintenance - implement maintenance Issue date: --- start body --- As a user I want to enable or disable the maintenance of Prestashop so I can safety upgrade PrestaShop ## Description AJOUTER WebServices (Potentiel) AND API Pour MVP Webservices seulement Pour MVP API : pour l'instant derrière admin => A voir si on change (alpha ) ### Help Message : _--verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ## Behaviour **ps-upgrade:maintenance --prestashop-path \<PATH\> \<ENABLE|DISABLE|STATUS\>** With \<PATH\> prestashop directory for the current (installed) prestashop ( or current directory of \<PATH\> is not specify ) --force : optional force the maintenance without interaction ( same as -no-interaction) ### Case ENABLE Once validated by the user (except if --force or --no-interaction is specified ) the tool 1. Enable maintenance in FO if the FO is not in maintenance mode or let the FO in maintenance if the FO is already in maintenance mode 2. Enable maintenance in BO if the FO is not in maintenance mode or let the BO in maintenance if the BO is already in maintenance mode 3. Exit See also Message STDOUT table & messages ### Case DISABLE Once validated by the user (except if --force or --no-interaction is specified ) the tool ( est-ce vraiment nécessaire ????) 1. Disable maintenance in FO if the FO is in maintenance mode or let the FO as is if the FO is not in maintenance mode 2.Disable maintenance in BO if the BO is in maintenance mode or let the BO as is if the BO is not in maintenance mode 3. Exit See also Message STDOUT table & messages ### Case STATUS 1. Display the maintenance status of FO ( Enabled or Disabled) 2. Display the maintenance status of BO ( Enabled or Disabled) 3. Exit ### Message STDOUT SAUF STATUS If --force (or --no-interaction) not specifiy _WARNING : BackOffice & FrontOffice vont être mis en /sortir du mode maintenance Are you sure : y/N_ Default NO Except if the user type __y__ or __yes__ (case insensitiv) the the ## Message (STDOUT) This is the outputs of the tool For BO  For FO  ### Message (STDERR) Errors messages (voir avec Boris / jo ) #### Error : Can not enable maintenance If on _maintenance ENABLE_ if the tool can not enable the maintenance (except if already enable : see Message (STDOUT) `Error : Can not enable FO maintenance ( use --vv or --vvv for more informations) ` ( for FO ) `Error : Can not enable BO maintenance ( use --vv or --vvv for more informations) ` ( for BO ) #### Error : Can not disable maintenance If on _DISABLE_ if the tool can not enable the maintenance (except if already disable : see Message (STDOUT) ) `Error : Can not disable FO maintenance ( use --vv or --vvv for more informations) ` (for FO ) `Error : Can not disable BO maintenance ( use --vv or --vvv for more informations) ` ( for BO ) #### Error: Can not get status If on _STATUS_ if the tool can not get the maintenance status `Error : Can not get the FO maintenance status ( use --vv or --vvv for more informations) ` ( for FO ) `Error : Can not get the BO maintenance status ( use --vv or --vvv for more informations) ` ( for BO ) ### Acceptances tests #### Acceptance test : help ``` $ ps-upgrade:maintenance --help --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output ``` #### Acceptance test ENABLE OK BO & FO are up & running ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enable maintenance mode ....OK BO : Enabling maintenance mode...OK ``` #### Acceptance test DISABLE OK BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....OK BO : Disabling maintenance mode...OK ``` ### Acceptance test ENABLE : BO KO BO & FO are up & running `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....OK BO : Enabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ` ## Acceptance test ENABLE : FO KO BO & FO are up & running `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Enabling maintenance mode...OK ` ## Acceptance test ENABLE : FO+BO KO BO & FO are up & running ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ ENABLE FO : Enabling maintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Enabling maintenance mode... KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test DISABLE BO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....OK BO : Disabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test DISABLE FO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Disabling maintenance mode...OK ``` #### Acceptance test DISABLE FO + BO KO BO & FO are in maintenance mode ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ DISABLE FO : Disabling aintenance mode ....KO ...<ERROR> ( use -vv -vvv for more information) BO : Disabling maintenance mode...KO ...<ERROR> ( use -vv -vvv for more information) ``` #### Acceptance test STATUS OK (FO is maintenance / BO is maintenance) BO & FO are in maintenance mode `$ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is in maintenance mode BO : Is in maintenance mode ` #### Acceptance test STATUS OK (FO is maintenance / BO is NOT maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is in maintenance mode BO : Is NOT in maintenance mode ``` #### Acceptance test STATUS OK (FO is NOT maintenance / BO is in maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is NOT in maintenance mode BO : Is in maintenance mode ``` #### Acceptance test STATUS OK (FO is NOT maintenance / BO is NOT in maintenance) ``` $ ps-upgrade:maintenance --prestashop-path=/path/to/current/ps/ STATUS FO : Is NOT in maintenance mode BO : Is NOT in maintenance mode ``` Add Failed case ? @fabienvallon ### Technical specs - [ ] #35151 - If `.ps-upgrade.maintenance.html` file with maintenant page content doesn't exist, we create this file in root project of PS. - For Enable: - We edit the `index.php` to include the maintenance page at first then exit with http code 503 with retry after some time. (for BO and FO !) - For Disable: - We edit the `index.php` te move the inclusion of the maintenance page. (for BO and FO !) - For status: - We need to check `index.php` for BO and FO. - [ ] #35152 ### Reflexion Fabien / Boris A voir si on ajoute BO et FO en séparé / avec comportement par défaut les 2 --- 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 An employee is not able to access the product edit page if he has only the permission to edit a product but no to add a new product. He is redirected to the dashboard instead. The issue happens because of this check in /src/PrestaShopBundle/Controller/Admin/ProductController.php on line 461: ```php foreach ([PageVoter::READ, PageVoter::UPDATE, PageVoter::CREATE] as $permission) { ``` I think the CREATE permission check should be removed: ```php foreach ([PageVoter::READ, PageVoter::UPDATE] as $permission) { ``` ### Expected behavior The "Edit" permission should be enough to be able to access the product edit page. ### Steps to reproduce 1. Use an employee login with a profile that has only the permission to edit a product but not to add a new product. 2. Go to the product list. 3. Try to edit a product. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Admin product edit page permission issue

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Admin product edit page permission issue 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 An employee is not able to access the product edit page if he has only the permission to edit a product but no to add a new product. He is redirected to the dashboard instead. The issue happens because of this check in /src/PrestaShopBundle/Controller/Admin/ProductController.php on line 461: ```php foreach ([PageVoter::READ, PageVoter::UPDATE, PageVoter::CREATE] as $permission) { ``` I think the CREATE permission check should be removed: ```php foreach ([PageVoter::READ, PageVoter::UPDATE] as $permission) { ``` ### Expected behavior The "Edit" permission should be enough to be able to access the product edit page. ### Steps to reproduce 1. Use an employee login with a profile that has only the permission to edit a product but not to add a new product. 2. Go to the product list. 3. Try to edit a product. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When an url like product page with extra query params used by a third-party module (mainly functional tracking on our case) is add to the URL and the URL isn't canonical the page is redirect by the good one but the query params is removed. Example : We have product link like this path /555-my-product.html?queryParams=1 and we rename that product so now each access to the previous URL will be redirect to the new canonical but the query param is removed. I try in the demo website (demo.prestashop.com) but the version is in 8.1.0 I see a change with this PR : https://github.com/PrestaShop/PrestaShop/pull/33885 but not sure it's the one create that bug ### Expected behavior The url is redirected with the query params even if they are not part of the controller route params ### Steps to reproduce Get a product url with pretty url Add a query param like ?toto=1 type enter That is ok Change the slug in the URL redirection happen to be in the canonical the query params is removed ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.2 ### If your bug is related to a module, specify its name and its version no ### Your company or customer's name goes here (if applicable). Jolimoi

Canonical redirection removed query params

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Canonical redirection removed query params 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 an url like product page with extra query params used by a third-party module (mainly functional tracking on our case) is add to the URL and the URL isn't canonical the page is redirect by the good one but the query params is removed. Example : We have product link like this path /555-my-product.html?queryParams=1 and we rename that product so now each access to the previous URL will be redirect to the new canonical but the query param is removed. I try in the demo website (demo.prestashop.com) but the version is in 8.1.0 I see a change with this PR : https://github.com/PrestaShop/PrestaShop/pull/33885 but not sure it's the one create that bug ### Expected behavior The url is redirected with the query params even if they are not part of the controller route params ### Steps to reproduce Get a product url with pretty url Add a query param like ?toto=1 type enter That is ok Change the slug in the URL redirection happen to be in the canonical the query params is removed ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.2 ### If your bug is related to a module, specify its name and its version no ### Your company or customer's name goes here (if applicable). Jolimoi --- 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 need help with a problem I have when enabling multi-language on my website. It turns out that in the default language of my site (in my case Spanish) everything works correctly. The problem arises with the attributes of the products when using them as combinations because in the default version of my site works perfectly but in the English, French or German version of my website when I want to select a combination of the product and add it to the cart, I get an error 404 undefined. I have already investigated what could be and I saw in forums that if you do not have translated the names of the combinations can generate this error. However I have everything translated to the corresponding language and still I get the error undefined. ### Expected behavior You should be able to add the product combination to the cart when you are visiting the site in English, German, French or any other language. ### Steps to reproduce 1- Go to intermaquinas.es 2- Search for a product with combinations ( here you have one to see the failure: https://intermaquinas.es/motobombas-generadores-tractor/motobomba-pto-zeppelin-125-hp-258491-259134#/258993-motobomba_pto_zeppelin_125_hp-motobomba_pto_60m3_h_caudal_es70609 ) 3- Check that in the spanish version (default) of the site the combinations work well. 4- Select the english, french or german language of the flags in the header. 5- Select again a combination of the product to add to the cart the product in the english version. 6- See the undefined error that occurs when selecting the combination and see that you can not finalize the purchase. ### 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). Spainlex Global Center SL

Href Lang tag issue with attribute id

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Href Lang tag issue with attribute id 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 need help with a problem I have when enabling multi-language on my website. It turns out that in the default language of my site (in my case Spanish) everything works correctly. The problem arises with the attributes of the products when using them as combinations because in the default version of my site works perfectly but in the English, French or German version of my website when I want to select a combination of the product and add it to the cart, I get an error 404 undefined. I have already investigated what could be and I saw in forums that if you do not have translated the names of the combinations can generate this error. However I have everything translated to the corresponding language and still I get the error undefined. ### Expected behavior You should be able to add the product combination to the cart when you are visiting the site in English, German, French or any other language. ### Steps to reproduce 1- Go to intermaquinas.es 2- Search for a product with combinations ( here you have one to see the failure: https://intermaquinas.es/motobombas-generadores-tractor/motobomba-pto-zeppelin-125-hp-258491-259134#/258993-motobomba_pto_zeppelin_125_hp-motobomba_pto_60m3_h_caudal_es70609 ) 3- Check that in the spanish version (default) of the site the combinations work well. 4- Select the english, french or german language of the flags in the header. 5- Select again a combination of the product to add to the cart the product in the english version. 6- See the undefined error that occurs when selecting the combination and see that you can not finalize the purchase. ### 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). Spainlex Global Center SL --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  ### Expected behavior _No response_ ### Steps to reproduce default ### PrestaShop version(s) where the bug happened 1.8.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_

bug design

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : bug design Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments  ### Expected behavior _No response_ ### Steps to reproduce default ### PrestaShop version(s) where the bug happened 1.8.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 The env var to define an admin password is not honored. ### Expected behavior Able to login with that password. ### Steps to reproduce 1. Run docker compose up 2. Try to login and cant ### PrestaShop version(s) where the bug happened 9.0.0 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version none ### Your company or customer's name goes here (if applicable). none

Docker Compose Up - Admin account password not honored by env var

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Docker Compose Up - Admin account password not honored by env var 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 env var to define an admin password is not honored. ### Expected behavior Able to login with that password. ### Steps to reproduce 1. Run docker compose up 2. Try to login and cant ### PrestaShop version(s) where the bug happened 9.0.0 ### PHP version(s) where the bug happened 8.0 ### If your bug is related to a module, specify its name and its version none ### Your company or customer's name goes here (if applicable). 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 When there are no Quick pages created and debug mode is enabled, you get an warning message in almost every page of Backoffice. This could be easily fixed by modifying these two .tpl files: - admin-dev/themes/new-theme/template/components/layout/mobile_quickaccess.tpl - admin-dev/themes/new-theme/template/components/layout/quick_access.tpl and by wrapping the foreach loops within an if statement, so this: `{foreach $quick_access as $quick} ...... {/foreach}` becomes: ` {if $quick_access} {foreach $quick_access as $quick} .... {/foreach} {/if}` ### Expected behavior bo pages load correctly ### Steps to reproduce 1. Click on "Manage quick accesses" under the Quick Access menu available on every Backoffice page  2. Delete every entry in there 3. Enable debug mode 4. Go to another Backoffice page, eg. Orders 5. See error:  ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Hostinato

Warning on every Backoffice page when there are no Quick Access pages created

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Warning on every Backoffice page when there are no Quick Access pages created 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 there are no Quick pages created and debug mode is enabled, you get an warning message in almost every page of Backoffice. This could be easily fixed by modifying these two .tpl files: - admin-dev/themes/new-theme/template/components/layout/mobile_quickaccess.tpl - admin-dev/themes/new-theme/template/components/layout/quick_access.tpl and by wrapping the foreach loops within an if statement, so this: `{foreach $quick_access as $quick} ...... {/foreach}` becomes: ` {if $quick_access} {foreach $quick_access as $quick} .... {/foreach} {/if}` ### Expected behavior bo pages load correctly ### Steps to reproduce 1. Click on "Manage quick accesses" under the Quick Access menu available on every Backoffice page  2. Delete every entry in there 3. Enable debug mode 4. Go to another Backoffice page, eg. Orders 5. See error:  ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Hostinato --- end body --- comments : --- start comments --- --- end comments ---

### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/34408 <div type='discussions-op-text'> ^{Originally posted by **AnnRise** October 27, 2023} To reproduce the situation: 1) Create product 1 with price 30 (tax included 20%) 2) Create product 2 with price 100 (tax included 20%) 3) Create carrier with free delivery over 50 (tax 20%) 4) Create cart rule with free gift "Product 1" if the amount is more than 100 with 1 priority 5) Create cart rule with 40% discount with 2 priority If I add "product 2" to cart, rule with free gift will be applied. After that I apply promocode for 40% discount. Thus, I get the total in the cart 130, a discount of 70, i.e. the total order amount is 60. But the shipping cost is calculated as paid. It looks like after applying a discount promo code, it calculates the order amount without tax (that is, 48 if tax is 20%, not 60). I tried a promotional code for exactly 40 euros, in this case the delivery is correctly calculated as free. What could be the reason for this behavior?  </div>

Incorrect shipping cost calculation with cart rule free gift and percent promocode

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Incorrect shipping cost calculation with cart rule free gift and percent promocode Issue date: --- start body --- ### Discussed in https://github.com/PrestaShop/PrestaShop/discussions/34408 <div type='discussions-op-text'> ^{Originally posted by **AnnRise** October 27, 2023} To reproduce the situation: 1) Create product 1 with price 30 (tax included 20%) 2) Create product 2 with price 100 (tax included 20%) 3) Create carrier with free delivery over 50 (tax 20%) 4) Create cart rule with free gift "Product 1" if the amount is more than 100 with 1 priority 5) Create cart rule with 40% discount with 2 priority If I add "product 2" to cart, rule with free gift will be applied. After that I apply promocode for 40% discount. Thus, I get the total in the cart 130, a discount of 70, i.e. the total order amount is 60. But the shipping cost is calculated as paid. It looks like after applying a discount promo code, it calculates the order amount without tax (that is, 48 if tax is 20%, not 60). I tried a promotional code for exactly 40 euros, in this case the delivery is correctly calculated as free. What could be the reason for this behavior?  </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 Hi I've seen that the homepage is without the canonical url. I think it is very useful to prevent duplication issues using this code into head.tpl the problem is fixed  the better solution should be using Controller::getCanonicalURL() method to assign it to $page.canonical canonical URLs are used to protect pages from duplication, both internal to the site and external if they made a copy of the site on other servers. at an SEO level, in this way Google would only index the reported page. you can see it on Google Search Console, for example with sites that have multiple languages and currencies, you would see that Google reports duplication errors because it sees duplications without a canonical URL. A bit like what happens with pagination bye ### Expected behavior _No response_ ### Steps to reproduce 1. go to the homepage 2. open the source code of your browser 3. search for canonical url ### 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_

Canonical Url is missing from the homepage

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Canonical Url is missing from the homepage Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi I've seen that the homepage is without the canonical url. I think it is very useful to prevent duplication issues using this code into head.tpl the problem is fixed  the better solution should be using Controller::getCanonicalURL() method to assign it to $page.canonical canonical URLs are used to protect pages from duplication, both internal to the site and external if they made a copy of the site on other servers. at an SEO level, in this way Google would only index the reported page. you can see it on Google Search Console, for example with sites that have multiple languages and currencies, you would see that Google reports duplication errors because it sees duplications without a canonical URL. A bit like what happens with pagination bye ### Expected behavior _No response_ ### Steps to reproduce 1. go to the homepage 2. open the source code of your browser 3. search for canonical url ### 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 ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://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 this is my first post (thanks for google traduction from french to english), My problem is that the unit price on PS 8.1.2 does not change on Prestashop when I update the price via the webservice. I first create an item which has a price of €25 excluding tax and I add in the 'Price' tab the price per meter which is €1 excluding tax Then I modify the price in my commercial management to €50 excluding tax With the e-Connector using the Webservice the price of the article and well updated To be sure that this is not an unchecked option, I created a profile in which I checked ALL the boxes in the webservice! Once the update has been carried out, the price has increased to €50 excluding tax but the unit price remains at €1 per meter    ### Expected behavior Normally the unit price should change when the price of the product changes, in this case the price per meter should increase to €2 excluding VAT per meter since the price for 25 meters has doubled ### Steps to reproduce 1 Create an item with a unit price 2 modify the price via the webservice 3 note that the unit price does not change while the price of the item has changed ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.25 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). AMMERLAAN Ronald

Unit sales price (excluding tax) does not update when changing prices via webservice

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Unit sales price (excluding tax) does not update when changing prices via webservice Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Good morning this is my first post (thanks for google traduction from french to english), My problem is that the unit price on PS 8.1.2 does not change on Prestashop when I update the price via the webservice. I first create an item which has a price of €25 excluding tax and I add in the 'Price' tab the price per meter which is €1 excluding tax Then I modify the price in my commercial management to €50 excluding tax With the e-Connector using the Webservice the price of the article and well updated To be sure that this is not an unchecked option, I created a profile in which I checked ALL the boxes in the webservice! Once the update has been carried out, the price has increased to €50 excluding tax but the unit price remains at €1 per meter    ### Expected behavior Normally the unit price should change when the price of the product changes, in this case the price per meter should increase to €2 excluding VAT per meter since the price for 25 meters has doubled ### Steps to reproduce 1 Create an item with a unit price 2 modify the price via the webservice 3 note that the unit price does not change while the price of the item has changed ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 7.4.25 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). AMMERLAAN Ronald --- end body --- comments : --- start comments --- --- end comments ---

**Specs:** Here's all that's left of the test modules: - update the API resources module (with all endpoints now in it - CartRule, CustomerGroup, FoundProduct, Product) - delete the ApiResource classes you've moved, delete the associated tests - https://github.com/PrestaShop/PrestaShop/issues/35208 **Acceptance test** Green CI

Add missing tests CI on module apiressources

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Add missing tests CI on module apiressources Issue date: --- start body --- **Specs:** Here's all that's left of the test modules: - update the API resources module (with all endpoints now in it - CartRule, CustomerGroup, FoundProduct, Product) - delete the ApiResource classes you've moved, delete the associated tests - https://github.com/PrestaShop/PrestaShop/issues/35208 **Acceptance test** Green CI --- 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 update the name of a product. The name is well updated in the product page but is uptaded nor in the list of products nor in the FO (but you can find it looking for it with the new name but is displayed with the old name) ### Expected behavior The product name is updated ### Steps to reproduce In a multistore shop (not tested in not multistore) 1 - Go in Catalog product 2 - Choose an existing product or a new product 3 - Edit the name of the product 4 - Check in the list of products (name not updated) 5 - open the product the name is updated 6 - Go in the FO Look for the product with the new name. The product is found with the old name displayed ### 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_

Update product name in multishop

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Update product name in multishop 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 update the name of a product. The name is well updated in the product page but is uptaded nor in the list of products nor in the FO (but you can find it looking for it with the new name but is displayed with the old name) ### Expected behavior The product name is updated ### Steps to reproduce In a multistore shop (not tested in not multistore) 1 - Go in Catalog product 2 - Choose an existing product or a new product 3 - Edit the name of the product 4 - Check in the list of products (name not updated) 5 - open the product the name is updated 6 - Go in the FO Look for the product with the new name. The product is found with the old name displayed ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I create a new API access (or when I generate a new client secret), I can't copy the secret by clicking on the `content_copy` icon. It only works by clicking on `Copy` text (`Copier` in the below screenshot). <img width="514" alt="Capture d’écran 2024-01-22 à 14 51 29" src="https://github.com/PrestaShop/PrestaShop/assets/121870/21978697-62cb-48d3-aed2-e7fbacb4542a"> ### Expected behavior When I click on the icon, the client secret should be stored in the clipboard. ### Steps to reproduce 1. Enable the authorization server experimental feature 2. Create a new API access 3. The client secret will be displayed. Click on the icon to copy it. ### 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). PrestaShop SA

Click on the `content_copy` icon don't copy the client secret

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Click on the `content_copy` icon don't copy the client secret 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 create a new API access (or when I generate a new client secret), I can't copy the secret by clicking on the `content_copy` icon. It only works by clicking on `Copy` text (`Copier` in the below screenshot). <img width="514" alt="Capture d’écran 2024-01-22 à 14 51 29" src="https://github.com/PrestaShop/PrestaShop/assets/121870/21978697-62cb-48d3-aed2-e7fbacb4542a"> ### Expected behavior When I click on the icon, the client secret should be stored in the clipboard. ### Steps to reproduce 1. Enable the authorization server experimental feature 2. Create a new API access 3. The client secret will be displayed. Click on the icon to copy it. ### 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). PrestaShop SA --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments In my store, I allow local and international orders. For both cases, I offer free shipping and logistics costs are included in the price. Since international logistics prices are higher than local logistics prices, I set the base price of my products globally (where international logistics costs are included) and then add "specific prices" for local buyers on a country-specific basis. The problem is; I wanted to define a discount for a customer group. I added the catalog price rule. So far everything is normal. This is what I noticed when I checked with my test customer account. If more than one address is registered in the customer's account (in the current case, there was one local address and one international address), the catalog price rule does not calculate correctly. For example; If the "specific price" is $10 (for local buyers) and the base price is $20 (for international buyers), it calculates the price at $20 even if the local address is selected in the shopping cart. In short, when the product is added to the cart, it should be 10$, but since I have defined a 10 percent discount for purchases of 2 or more items, it should be calculated as 9x2=18$, but it is calculated as 18x2=36$ ### Expected behavior _No response_ ### Steps to reproduce Add a catalog price rule with 10% discount for 2 or more items. Add a specific price rule in a product for specific country. Add one local and another international address to customer account. Check discounts on cart. ### 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_

Catalog price rules are not behaving as expected

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Catalog price rules are not behaving as expected 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 my store, I allow local and international orders. For both cases, I offer free shipping and logistics costs are included in the price. Since international logistics prices are higher than local logistics prices, I set the base price of my products globally (where international logistics costs are included) and then add "specific prices" for local buyers on a country-specific basis. The problem is; I wanted to define a discount for a customer group. I added the catalog price rule. So far everything is normal. This is what I noticed when I checked with my test customer account. If more than one address is registered in the customer's account (in the current case, there was one local address and one international address), the catalog price rule does not calculate correctly. For example; If the "specific price" is $10 (for local buyers) and the base price is $20 (for international buyers), it calculates the price at $20 even if the local address is selected in the shopping cart. In short, when the product is added to the cart, it should be 10$, but since I have defined a 10 percent discount for purchases of 2 or more items, it should be calculated as 9x2=18$, but it is calculated as 18x2=36$ ### Expected behavior _No response_ ### Steps to reproduce Add a catalog price rule with 10% discount for 2 or more items. Add a specific price rule in a product for specific country. Add one local and another international address to customer account. Check discounts on cart. ### 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 ---

This ticket follow this one https://github.com/PrestaShop/PrestaShop/issues/34271 who looks for new translations only in the main directory. We would like to extend the research of new wording in native modules too.

PrestonBot-CheckForNewTranslations - Main directory + native modules

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PrestonBot-CheckForNewTranslations - Main directory + native modules Issue date: --- start body --- This ticket follow this one https://github.com/PrestaShop/PrestaShop/issues/34271 who looks for new translations only in the main directory. We would like to extend the research of new wording in native modules too. --- 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 ever i log in no matter what option i select it logs me back out ### Expected behavior I would expect to go to the option i have selected so i can configure my store. ### Steps to reproduce Logged in Whent to settings option Got logged straight out ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Logging in error

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Logging in 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 ever i log in no matter what option i select it logs me back out ### Expected behavior I would expect to go to the option i have selected so i can configure my store. ### Steps to reproduce Logged in Whent to settings option Got logged straight out ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi it is necessary to add webmanifest extension into /themes/.htaccess if not I get 403 error  thanks ### Expected behavior _No response_ ### Steps to reproduce 1. go to /themes/.htaccess 2. try to add a file site.webmanifest into the theme 3. add a line into the head.tpl to load it ### 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_

[Fix] Missing webmanifest extension in the file /themes/.htaccess

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [Fix] Missing webmanifest extension in the file /themes/.htaccess 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 it is necessary to add webmanifest extension into /themes/.htaccess if not I get 403 error  thanks ### Expected behavior _No response_ ### Steps to reproduce 1. go to /themes/.htaccess 2. try to add a file site.webmanifest into the theme 3. add a line into the head.tpl to load it ### 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 ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://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 setup a plain Prestashop 8.1.0 site locally (Windows / Laragaon) and then upload the site to my linux server (dumping the files and DB), however the following error appears: Warning: require_once(/home/webgener/sb.webgeneration.co.uk/classes\Tools.php): Failed to open stream: No such file or directory in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php on line 86 Fatal error: Uncaught Error: Failed opening required '/home/webgener/sb.webgeneration.co.uk/classes\Tools.php' (include_path='/home/webgener/sb.webgeneration.co.uk/vendor/pear/pear_exception:/home/webgener/sb.webgeneration.co.uk/vendor/pear/console_getopt:/home/webgener/sb.webgeneration.co.uk/vendor/pear/pear-core-minimal/src:/home/webgener/sb.webgeneration.co.uk/vendor/pear/archive_tar:.:/opt/cpanel/ea-php81/root/usr/share/pear') in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php:86 Stack trace: #0 /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php(96) : eval()'d code(1): PrestaShop\Autoload\Autoloader->load('ToolsCore') #1 /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php(96): eval() #2 /home/webgener/sb.webgeneration.co.uk/config/config.inc.php(83): PrestaShop\Autoload\Autoloader->load('Tools') #3 /home/webgener/sb.webgeneration.co.uk/index.php(27): require('/home/webgener/...') #4 {main} thrown in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php on line 86 I've done this in the past without issues (Prestashop 1.7) It looks like it may have something to do with the directory separator but I can't see how this can be changed. ### Expected behavior _No response_ ### Steps to reproduce Setup a fresh Prestashop site locally on Windows Migrate site by dumping the DB and files across to a unix server ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Problem migrating site from localhost to live

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Problem migrating site from localhost to live 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 setup a plain Prestashop 8.1.0 site locally (Windows / Laragaon) and then upload the site to my linux server (dumping the files and DB), however the following error appears: Warning: require_once(/home/webgener/sb.webgeneration.co.uk/classes\Tools.php): Failed to open stream: No such file or directory in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php on line 86 Fatal error: Uncaught Error: Failed opening required '/home/webgener/sb.webgeneration.co.uk/classes\Tools.php' (include_path='/home/webgener/sb.webgeneration.co.uk/vendor/pear/pear_exception:/home/webgener/sb.webgeneration.co.uk/vendor/pear/console_getopt:/home/webgener/sb.webgeneration.co.uk/vendor/pear/pear-core-minimal/src:/home/webgener/sb.webgeneration.co.uk/vendor/pear/archive_tar:.:/opt/cpanel/ea-php81/root/usr/share/pear') in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php:86 Stack trace: #0 /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php(96) : eval()'d code(1): PrestaShop\Autoload\Autoloader->load('ToolsCore') #1 /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php(96): eval() #2 /home/webgener/sb.webgeneration.co.uk/config/config.inc.php(83): PrestaShop\Autoload\Autoloader->load('Tools') #3 /home/webgener/sb.webgeneration.co.uk/index.php(27): require('/home/webgener/...') #4 {main} thrown in /home/webgener/sb.webgeneration.co.uk/vendor/prestashop/autoload/src/Autoloader.php on line 86 I've done this in the past without issues (Prestashop 1.7) It looks like it may have something to do with the directory separator but I can't see how this can be changed. ### Expected behavior _No response_ ### Steps to reproduce Setup a fresh Prestashop site locally on Windows Migrate site by dumping the DB and files across to a unix server ### PrestaShop version(s) where the bug happened 8.1.0 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Same issue on Old Product Page and New Product Page. I can't add a unit value for different language. If I add "per kilo", il will always be "per kilo" for all the languages enables on my shop. <img width="925" alt="Screenshot 2024-01-19 at 17 14 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d0f67203-39b4-4ef4-81ca-05e7d01b98f1"> ### Expected behavior I should be able to translate this element for all my languages. ### Steps to reproduce 1. Make sure you have at least 2 active languages 2. Go to BO > Products > Edit any product 3. Go to Pricing tab > Enable Display retail price per unit 4. See that you can only add a unique value for the Unit element :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_

BO Product page - Unit price is not translatable

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO Product page - Unit price is not translatable 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 Same issue on Old Product Page and New Product Page. I can't add a unit value for different language. If I add "per kilo", il will always be "per kilo" for all the languages enables on my shop. <img width="925" alt="Screenshot 2024-01-19 at 17 14 16" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/d0f67203-39b4-4ef4-81ca-05e7d01b98f1"> ### Expected behavior I should be able to translate this element for all my languages. ### Steps to reproduce 1. Make sure you have at least 2 active languages 2. Go to BO > Products > Edit any product 3. Go to Pricing tab > Enable Display retail price per unit 4. See that you can only add a unique value for the Unit element :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 The logo and name of Twitter/X is obsolete, it should be changed to X <img width="750" alt="Screenshot 2024-01-19 at 15 16 37" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/9f51094a-3408-4c8e-8ae6-ac63ffe17bb5"> <img width="261" alt="Screenshot 2024-01-19 at 15 22 00" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5b3501d0-ceb2-436a-b438-3fab413dad3f"> ### Expected behavior Everything should be changed by X ### Steps to reproduce 1. Go to BO > Modules > Configure social follow module 2. See Twitter -> should be X :x: 3. Add a link 4. Go to FO > See old logo :x: ### PrestaShop version(s) where the bug happened 8.1.0, develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version socialfollow v2.3.2 ### Your company or customer's name goes here (if applicable). _No response_

socialfollow - Twitter old logo should be changed by X logo

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : socialfollow - Twitter old logo should be changed by X logo 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 logo and name of Twitter/X is obsolete, it should be changed to X <img width="750" alt="Screenshot 2024-01-19 at 15 16 37" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/9f51094a-3408-4c8e-8ae6-ac63ffe17bb5"> <img width="261" alt="Screenshot 2024-01-19 at 15 22 00" src="https://github.com/PrestaShop/PrestaShop/assets/16019289/5b3501d0-ceb2-436a-b438-3fab413dad3f"> ### Expected behavior Everything should be changed by X ### Steps to reproduce 1. Go to BO > Modules > Configure social follow module 2. See Twitter -> should be X :x: 3. Add a link 4. Go to FO > See old logo :x: ### PrestaShop version(s) where the bug happened 8.1.0, develop ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version socialfollow v2.3.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 There is a SQL error when there is at least a refunded product in a validated order: > SQLSTATE[22003]: Numeric value out of range: 1690 BIGINT UNSIGNED value is out of range in '(((`dbname`.`od`.`product_quantity` - `dbname`.`od`.`product_quantity_refunded`) - `dbname`.`od`.`product_quantity_return`) - `dbname`.`od`.`product_quantity_reinjected`)' And the hook does not show anything:  ### Expected behavior the hook shows data:  ### Steps to reproduce 1. Create a validated order (payment by credit card) 2. go to BO and in the order 3. Create a refunding 4. go to dashboard 5. see there isn't any data in dashproducts hook ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version dashproducts ### Your company or customer's name goes here (if applicable). _No response_

dashproducts module - SQL error with refunded product in validated order

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : dashproducts module - SQL error with refunded product in validated 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 There is a SQL error when there is at least a refunded product in a validated order: > SQLSTATE[22003]: Numeric value out of range: 1690 BIGINT UNSIGNED value is out of range in '(((`dbname`.`od`.`product_quantity` - `dbname`.`od`.`product_quantity_refunded`) - `dbname`.`od`.`product_quantity_return`) - `dbname`.`od`.`product_quantity_reinjected`)' And the hook does not show anything:  ### Expected behavior the hook shows data:  ### Steps to reproduce 1. Create a validated order (payment by credit card) 2. go to BO and in the order 3. Create a refunding 4. go to dashboard 5. see there isn't any data in dashproducts hook ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version dashproducts ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hello everyone, I'm having a problem with promotional codes. Some promotional codes have been used and validated even though their end date has passed. How is it possible ? Additionally, some codes stopped working for a few days and then worked again... very strange. Thank you for your help and have a nice day everyone! ### Expected behavior _No response_ ### Steps to reproduce promotional code problem. ### PrestaShop version(s) where the bug happened 1.7.8.6 ### 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_

Coupons problem

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Coupons 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 Hello everyone, I'm having a problem with promotional codes. Some promotional codes have been used and validated even though their end date has passed. How is it possible ? Additionally, some codes stopped working for a few days and then worked again... very strange. Thank you for your help and have a nice day everyone! ### Expected behavior _No response_ ### Steps to reproduce promotional code problem. ### PrestaShop version(s) where the bug happened 1.7.8.6 ### 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 ---

CliApp: Create command `ps-upgrade:shop:download`.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create command `ps-upgrade:shop:download`. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CliApp: Create hidden command `ps-upgrade:shop:make-db-structure-xml` and use DBStructureGenerator service to generate db struct xml file.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create hidden command `ps-upgrade:shop:make-db-structure-xml` and use DBStructureGenerator service to generate db struct xml file. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: `DistributionApiDownloader` service.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: `DistributionApiDownloader` service. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to download a new package of PrestaShop so I can install it now or later As a user I want to verify the integrity of PrestaShop so I can be sure that my package (and xml file) is safe ## Description TBD : filesystem ' WHERE SHOULD I Download my packages " `ps-upgrade:download <package name>` This command 1. Donwload through distrib API the package named \<package name\>.zip 2. Download through distrib API the xml file name \<package name\>.xml 3. Download through distrib API the xml file name \<package name\>.dbstruct ? 4. Verify integrity of this 3 files through distrib API ### Messages #### Global options See [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands #### Help _ps-upgrade:download : download a PrestaShop package Usage: ps:upgrade:download \<package\> or \<version number\> With \<package\> as package name (such as prestashop-8.1.3 ) and \<version number\> the prestashop version (such as 8.1.3) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ #### Usage `ps-upgrade:download <package name>` #### Step 1 : Download For each \<file\> ( \<package_name\>.zip , \<package_name\>.xml, \<package_name\>.dbstuct ) Message : _Downloading \<file\>_ (TODO progress bar ou pas ? ) if OK : Message : _\<file\> donwloaded into \<Downloaded_Repository\>_ and go to the next \<file\> or to the next step ( verify package integrity ) if all files have been downloaded if KO Message : _KO: \<file\> donwloaded failed : use -vv for more information_ ( est ce que je met plujs d'info ici ? ) TODO voir si un fail , est-ce que l'on test les autres ou on exit ? #### Step 2 : Perform chek through disrib API Endpoint For each \<file\> ( \<package_name\>.zip , \<package_name\>.xml, \<package_name\>.dbstuct ) _Verify \<file\> integrity...\<STATUS\>_ If KO ( end point check ) \<STATUS\> = _Integrity verification failed + err Message (see TS) _ ( for errors Messages (see TS) ) If KO (md5sum \<file\> != md5sum provide by the endpoints ) \<STATUS\> = _Bad integrity (message pourri) _ TODO voir si un fail , est-ce que l'on test les autres ou on exit ? ### Acceptances tests - Set up a distrib server with prestashop-8.1.3 & prestashop-9.0.0 & news versions of PrestaShop and a current version prestashop-8.1.2 #### Acceptance test : Help _$ps-upgrade:download --help ps-upgrade:download : download a PrestaShop package Usage: ps:upgrade:download \<package\> or \<version number\> With \<package\> as package name (such as prestashop-8.1.3 ) and \<version number\> the prestashop version (such as 8.1.3) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ #### Acceptance test : Global options See also See [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands and #### Acceptance test 1 : OK Run ( example , see above ) ``` $ ps-upgrade:download prestashop-8.1.3 Downloading prestashop-8.1.3.zip ...OK Downloading prestashop-8.1.3.xml ...OK Downloading prestashop-8.1.3.dbstruct ...OK Verify integrity prestashop-8.1.3.zip ...OK Verify integrity prestashop-8.1.3.xml ...OK Verify integrity prestashop-8.1.3.dbstruct ...OK ``` #### Acceptance test 2 : KO - wrong package name ``` $ ps-upgrade:download prestashop-42.1.1 Prestashop-42.1.1 does not exist - wrong package name ``` #### Acceptance test 3 : KO - network local ``` $ ps-upgrade:download prestashop-8.1.3 Could not download prestashop-8.1.3 : Check your network ``` #### Acceptance test 4 : KO - Problem with distrib API ``` $ ps-upgrade:download prestashop-8.1.3 Could not download : <ERROR> ``` See \<ERROR\> with dev afterward and write new ACs #### Acceptance test 5 : KO - wrong integrity package.zip - Set up a distrib server with prestashop-8.1.3 & prestashop-9.0.0 & news versions of PrestaShop and a current version prestashop-8.1.2 - Modify prestashop-8.1.3.zip ( fort example `echo "Moo" >> prestashop-8.1.3.zip` into the server ``` $ ps-upgrade:download prestashop-8.1.3 Downloading prestashop-8.1.3.zip ...OK Downloading prestashop-8.1.3.xml ...OK Downloading prestashop-8.1.3.dbstruct ...OK Verify integrity prestashop-8.1.3.zip ...KO Bad integrity Verify integrity prestashop-8.1.3.xml ...OK Verify integrity prestashop-8.1.3.dbstruct ...OK ``` Do the same for restashop-8.1.3.xml / prestashop-8.1.3.dbstruct ( should I write new ACs ? @florine2623 ) ### Technical specs - [ ] CU: Create DBStructureGenerator service to create db struct xml files. - [ ] #35100 - [ ] DistributionApi: Add md5 checksums for archive, files checksum xml and db struct xml. (and add DB struct too 😇) - [ ] #35099 - [ ] CU: Check integrity with `ChecksumComparator` service. - [ ] #35101

EPIC - CLI : ps-upgrade:download - implement download

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:download - implement download Issue date: --- start body --- As a user I want to download a new package of PrestaShop so I can install it now or later As a user I want to verify the integrity of PrestaShop so I can be sure that my package (and xml file) is safe ## Description TBD : filesystem ' WHERE SHOULD I Download my packages " `ps-upgrade:download <package name>` This command 1. Donwload through distrib API the package named \<package name\>.zip 2. Download through distrib API the xml file name \<package name\>.xml 3. Download through distrib API the xml file name \<package name\>.dbstruct ? 4. Verify integrity of this 3 files through distrib API ### Messages #### Global options See [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands #### Help _ps-upgrade:download : download a PrestaShop package Usage: ps:upgrade:download \<package\> or \<version number\> With \<package\> as package name (such as prestashop-8.1.3 ) and \<version number\> the prestashop version (such as 8.1.3) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ #### Usage `ps-upgrade:download <package name>` #### Step 1 : Download For each \<file\> ( \<package_name\>.zip , \<package_name\>.xml, \<package_name\>.dbstuct ) Message : _Downloading \<file\>_ (TODO progress bar ou pas ? ) if OK : Message : _\<file\> donwloaded into \<Downloaded_Repository\>_ and go to the next \<file\> or to the next step ( verify package integrity ) if all files have been downloaded if KO Message : _KO: \<file\> donwloaded failed : use -vv for more information_ ( est ce que je met plujs d'info ici ? ) TODO voir si un fail , est-ce que l'on test les autres ou on exit ? #### Step 2 : Perform chek through disrib API Endpoint For each \<file\> ( \<package_name\>.zip , \<package_name\>.xml, \<package_name\>.dbstuct ) _Verify \<file\> integrity...\<STATUS\>_ If KO ( end point check ) \<STATUS\> = _Integrity verification failed + err Message (see TS) _ ( for errors Messages (see TS) ) If KO (md5sum \<file\> != md5sum provide by the endpoints ) \<STATUS\> = _Bad integrity (message pourri) _ TODO voir si un fail , est-ce que l'on test les autres ou on exit ? ### Acceptances tests - Set up a distrib server with prestashop-8.1.3 & prestashop-9.0.0 & news versions of PrestaShop and a current version prestashop-8.1.2 #### Acceptance test : Help _$ps-upgrade:download --help ps-upgrade:download : download a PrestaShop package Usage: ps:upgrade:download \<package\> or \<version number\> With \<package\> as package name (such as prestashop-8.1.3 ) and \<version number\> the prestashop version (such as 8.1.3) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ #### Acceptance test : Global options See also See [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands and #### Acceptance test 1 : OK Run ( example , see above ) ``` $ ps-upgrade:download prestashop-8.1.3 Downloading prestashop-8.1.3.zip ...OK Downloading prestashop-8.1.3.xml ...OK Downloading prestashop-8.1.3.dbstruct ...OK Verify integrity prestashop-8.1.3.zip ...OK Verify integrity prestashop-8.1.3.xml ...OK Verify integrity prestashop-8.1.3.dbstruct ...OK ``` #### Acceptance test 2 : KO - wrong package name ``` $ ps-upgrade:download prestashop-42.1.1 Prestashop-42.1.1 does not exist - wrong package name ``` #### Acceptance test 3 : KO - network local ``` $ ps-upgrade:download prestashop-8.1.3 Could not download prestashop-8.1.3 : Check your network ``` #### Acceptance test 4 : KO - Problem with distrib API ``` $ ps-upgrade:download prestashop-8.1.3 Could not download : <ERROR> ``` See \<ERROR\> with dev afterward and write new ACs #### Acceptance test 5 : KO - wrong integrity package.zip - Set up a distrib server with prestashop-8.1.3 & prestashop-9.0.0 & news versions of PrestaShop and a current version prestashop-8.1.2 - Modify prestashop-8.1.3.zip ( fort example `echo "Moo" >> prestashop-8.1.3.zip` into the server ``` $ ps-upgrade:download prestashop-8.1.3 Downloading prestashop-8.1.3.zip ...OK Downloading prestashop-8.1.3.xml ...OK Downloading prestashop-8.1.3.dbstruct ...OK Verify integrity prestashop-8.1.3.zip ...KO Bad integrity Verify integrity prestashop-8.1.3.xml ...OK Verify integrity prestashop-8.1.3.dbstruct ...OK ``` Do the same for restashop-8.1.3.xml / prestashop-8.1.3.dbstruct ( should I write new ACs ? @florine2623 ) ### Technical specs - [ ] CU: Create DBStructureGenerator service to create db struct xml files. - [ ] #35100 - [ ] DistributionApi: Add md5 checksums for archive, files checksum xml and db struct xml. (and add DB struct too 😇) - [ ] #35099 - [ ] CU: Check integrity with `ChecksumComparator` service. - [ ] #35101 --- end body --- comments : --- start comments --- --- end comments ---

CliApp: Create command and compile all the informations for the user in the output.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create command and compile all the informations for the user in the output. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: DistributionApiExtractor to retrieve all PS versions availabled and > current version.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: DistributionApiExtractor to retrieve all PS versions availabled and > current version. Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to know the new versions of PrestaShop available so I can be aware of updates ## Description ### Implement Golbal options See : [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) #### Help message _ps-upgrade:shop:check-new-version check if new versions are available and display them Usage: ps-upgrade:shop:check-new-version ---prestashop-path \<PATH\> --prestashop-path \<PATH\> : with \<PATH\> the root directory of the current prestashop installation or current directory (.) if this option is not specified --version --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ **TODO : ajouter que il y a de nouvelles versions mais pas gérable par l'outils d'upgrade ( à mettre à jour )** Implement **ps-upgrade:shop:check-new-version --prestashop-path \<PATH\>** 1. Determine the current version 2. Through distrib API list new versions of PrestaShop with a Release Note and display them ### Message (stdout) _Check new version with current prestashop \<ABSOLUTE_PATH\>_ List of new (and only new) versions available one version per line. _\<VERSION_REF\> : \<RELEASE_NOTE_LINK\>_ With \<VERSION_REF\> : prestashop-X.Y.Z-OPT ( for prestashop >= 8 ) or \<VERSION_REF\> : prestashop-1.X.Y.Z-OPT ( for prestashop < 8 ) with X: integer - major number ; mandatory Y: integer - minor number ; mandatory Z: integer : patch number ; mandatory -OPT : OPT naming (such as beta , rc1 ....). -OPT , this is not currently available / implemented ( TO REMOVE / BACKUP) Versions MUST always be > to the current installed prestashop With <RELEASE_NOTE_URL> = \<a href="......"\>Release Note - X-Y-Z\</a\> With X,Y,Z same as above If no new version available the message is : _There is no new version available_ Example ``` ps-upgrade:shop:check-new-version --prestashop-path /var/www/prestashop/ prestashop-8.1.5 : [Release Note-8.1.5](http://www.build.prestashop.org) prestashop-9.0.0 : [Release Note-9.0.0](http://www.build.prestashop.org) ``` ### Message (stderr) #### Error : Wrong <PATH> If the <PATH> (specified by prestahop-path or '.'' if not specified) is a wrong path. Display _Could not determine current prestashop version. Wrong path ( \<PATH\> )_ #### Error : Could not determine version Probably same message as doctor dialglist=ps-version #### Error : Can not list new version through distrib API See all error messages \+ add (concatenation with error message) _use -vv or -vvv for more information_ #### Error: Release note See all error messages with dev \+ add (concatenation with error message) _use -vv or -vvv for more information_ ## Acceptances tests ### Acceptance test : Global options Help message _$ps-upgrade:shop:check-new-version --help ps-upgrade:shop:check-new-version check if new versions are available and display them Usage: ps-upgrade:shop:check-new-version ---prestashop-path \<PATH\> --prestashop-path \<PATH\> : with \<PATH\> the root directory of the current prestashop installation or current directory (.) if this option is not specified --version --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ See also #### Acceptance test 1 : OK - no new version - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run ( example , see above ) In the current prestashop root directory execute ``` $ ps-upgrade:shop:check-new-version There is no new version available ``` #### Acceptance test 2 : OK - new versions - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2, 8.1.3, 9.0.0 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run ( example , see above ) In the current prestashop root directory execute ``` $ ps-upgrade:shop:check-new-version prestashop-8.1.3 : Release Note-8.1.3 prestashop-9.0.0 : Release Note-9.0.0 ``` #### Acceptance test 3 : OK - new version with path arguments for the current version - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2, 8.1.3, 9.0.0 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run the command with --prestashop-path argument ``` $ ps-upgrade:shop:check-new-version --prestashop-path=/var/www/prestashop prestashop-8.1.3 : Release Note-8.1.3 prestashop-9.0.0 : Release Note-9.0.0 ``` Note /var/www/prestashop could be a different path depending on your current installation #### Acceptance test 4 : KO - wirh wrong path (--prestashop-path) - Set up a distrib server with (2) news versions of prestashop Example : current prestashop (to upgrade) is prestashop 8.1.8 New versions available are 8.1.9 & 9.0.0 Run ( example , see above ) ``` $ ps-upgrade:shop:check-new-version --prestashop-path=/tmp Can not find the current prestashop root directory ``` See other acceptance test KO from TS + add message with -vv -vvv #### Acceptance test 4 : KO - with wrong path (.) - Set up a distrib server with (2) news versions of prestashop Example : current prestashop (to upgrade) is prestashop 8.1.8 New versions available are 8.1.9 & 9.0.0 Run ( example , see above ) In your **home directory** (i.e. not into the prestashop root directory) ``` $ ps-upgrade:shop:check-new-version Can not find the current prestashop root directory ( please use --prestashop-path) ``` #### Acceptance test 5 : KO - Can not retrieves information : network local problem - Shutdown network from your local computer Run ( example , see above ) ( /tmp should not contains prestashop current installation ) ``` $ ps-upgrade:shop:check-new-version Repository is not available: no network , check your connexion ( use --vv or --vvv for more informations) ``` #### Acceptance test 3 : KO - Distrib API problem Run ( example , see above ) ``` $ ps-upgrade:shop:check-new-version Error: <ERROR> (use --vv or --vvv for more informations) ``` See all errors with dev ( and create new ACs ) ### Technical specs - [ ] CU: Use PrestaShopInfoExtractor to retrieve the PS version. (look at ps-upgrade:doctor implement doctor) - [ ] #35096 - [ ] #35097

EPIC - CLI : ps-upgrade:shop:check-new-version - implement check new version

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:shop:check-new-version - implement check new version Issue date: --- start body --- As a user I want to know the new versions of PrestaShop available so I can be aware of updates ## Description ### Implement Golbal options See : [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) #### Help message _ps-upgrade:shop:check-new-version check if new versions are available and display them Usage: ps-upgrade:shop:check-new-version ---prestashop-path \<PATH\> --prestashop-path \<PATH\> : with \<PATH\> the root directory of the current prestashop installation or current directory (.) if this option is not specified --version --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ **TODO : ajouter que il y a de nouvelles versions mais pas gérable par l'outils d'upgrade ( à mettre à jour )** Implement **ps-upgrade:shop:check-new-version --prestashop-path \<PATH\>** 1. Determine the current version 2. Through distrib API list new versions of PrestaShop with a Release Note and display them ### Message (stdout) _Check new version with current prestashop \<ABSOLUTE_PATH\>_ List of new (and only new) versions available one version per line. _\<VERSION_REF\> : \<RELEASE_NOTE_LINK\>_ With \<VERSION_REF\> : prestashop-X.Y.Z-OPT ( for prestashop >= 8 ) or \<VERSION_REF\> : prestashop-1.X.Y.Z-OPT ( for prestashop < 8 ) with X: integer - major number ; mandatory Y: integer - minor number ; mandatory Z: integer : patch number ; mandatory -OPT : OPT naming (such as beta , rc1 ....). -OPT , this is not currently available / implemented ( TO REMOVE / BACKUP) Versions MUST always be > to the current installed prestashop With <RELEASE_NOTE_URL> = \<a href="......"\>Release Note - X-Y-Z\</a\> With X,Y,Z same as above If no new version available the message is : _There is no new version available_ Example ``` ps-upgrade:shop:check-new-version --prestashop-path /var/www/prestashop/ prestashop-8.1.5 : [Release Note-8.1.5](http://www.build.prestashop.org) prestashop-9.0.0 : [Release Note-9.0.0](http://www.build.prestashop.org) ``` ### Message (stderr) #### Error : Wrong <PATH> If the <PATH> (specified by prestahop-path or '.'' if not specified) is a wrong path. Display _Could not determine current prestashop version. Wrong path ( \<PATH\> )_ #### Error : Could not determine version Probably same message as doctor dialglist=ps-version #### Error : Can not list new version through distrib API See all error messages \+ add (concatenation with error message) _use -vv or -vvv for more information_ #### Error: Release note See all error messages with dev \+ add (concatenation with error message) _use -vv or -vvv for more information_ ## Acceptances tests ### Acceptance test : Global options Help message _$ps-upgrade:shop:check-new-version --help ps-upgrade:shop:check-new-version check if new versions are available and display them Usage: ps-upgrade:shop:check-new-version ---prestashop-path \<PATH\> --prestashop-path \<PATH\> : with \<PATH\> the root directory of the current prestashop installation or current directory (.) if this option is not specified --version --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ See also #### Acceptance test 1 : OK - no new version - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run ( example , see above ) In the current prestashop root directory execute ``` $ ps-upgrade:shop:check-new-version There is no new version available ``` #### Acceptance test 2 : OK - new versions - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2, 8.1.3, 9.0.0 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run ( example , see above ) In the current prestashop root directory execute ``` $ ps-upgrade:shop:check-new-version prestashop-8.1.3 : Release Note-8.1.3 prestashop-9.0.0 : Release Note-9.0.0 ``` #### Acceptance test 3 : OK - new version with path arguments for the current version - Set up a distrib server with 2 new versions of prestashop with 8.1.0, 8.1.1 , 8.1.2, 8.1.3, 9.0.0 on the distrib_api server With current prestashop (to upgrade) is prestashop 8.1.2 Run the command with --prestashop-path argument ``` $ ps-upgrade:shop:check-new-version --prestashop-path=/var/www/prestashop prestashop-8.1.3 : Release Note-8.1.3 prestashop-9.0.0 : Release Note-9.0.0 ``` Note /var/www/prestashop could be a different path depending on your current installation #### Acceptance test 4 : KO - wirh wrong path (--prestashop-path) - Set up a distrib server with (2) news versions of prestashop Example : current prestashop (to upgrade) is prestashop 8.1.8 New versions available are 8.1.9 & 9.0.0 Run ( example , see above ) ``` $ ps-upgrade:shop:check-new-version --prestashop-path=/tmp Can not find the current prestashop root directory ``` See other acceptance test KO from TS + add message with -vv -vvv #### Acceptance test 4 : KO - with wrong path (.) - Set up a distrib server with (2) news versions of prestashop Example : current prestashop (to upgrade) is prestashop 8.1.8 New versions available are 8.1.9 & 9.0.0 Run ( example , see above ) In your **home directory** (i.e. not into the prestashop root directory) ``` $ ps-upgrade:shop:check-new-version Can not find the current prestashop root directory ( please use --prestashop-path) ``` #### Acceptance test 5 : KO - Can not retrieves information : network local problem - Shutdown network from your local computer Run ( example , see above ) ( /tmp should not contains prestashop current installation ) ``` $ ps-upgrade:shop:check-new-version Repository is not available: no network , check your connexion ( use --vv or --vvv for more informations) ``` #### Acceptance test 3 : KO - Distrib API problem Run ( example , see above ) ``` $ ps-upgrade:shop:check-new-version Error: <ERROR> (use --vv or --vvv for more informations) ``` See all errors with dev ( and create new ACs ) ### Technical specs - [ ] CU: Use PrestaShopInfoExtractor to retrieve the PS version. (look at ps-upgrade:doctor implement doctor) - [ ] #35096 - [ ] #35097 --- 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 Employee that does not exist on ps_employee_shop table are not listed on PS backoffice employees list.   NOTE: if this employee is superadmin can do log in too.  ### Expected behavior All employee that can log in to the backoffice should be listed properly on the backoffice employees list. ### Steps to reproduce 1. Go to ps_employee table. 2. Duplicate any superadmin employee row. 3. The employee is not listed on backoffice list. 4. The employee can sucessfully log in the backoffice. ### PrestaShop version(s) where the bug happened 1.7.x to 8.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_

All employees are not listed on the backoffice list when does not have a shop association

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : All employees are not listed on the backoffice list when does not have a shop association 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 Employee that does not exist on ps_employee_shop table are not listed on PS backoffice employees list.   NOTE: if this employee is superadmin can do log in too.  ### Expected behavior All employee that can log in to the backoffice should be listed properly on the backoffice employees list. ### Steps to reproduce 1. Go to ps_employee table. 2. Duplicate any superadmin employee row. 3. The employee is not listed on backoffice list. 4. The employee can sucessfully log in the backoffice. ### PrestaShop version(s) where the bug happened 1.7.x to 8.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 ---

CliApp: Create doctor command and integrate piece by piece the information when the core services are ready

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CliApp: Create doctor command and integrate piece by piece the information when the core services are ready Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

Spike : -> Define rules for the DB tests -> API Distrib -> Serialization / UnSerialization ( xml) -> QA tests

CU: DbComparator: compares current structure with original one (define from where the default structure is retrieved)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: DbComparator: compares current structure with original one (define from where the default structure is retrieved) Issue date: --- start body --- Spike : -> Define rules for the DB tests -> API Distrib -> Serialization / UnSerialization ( xml) -> QA tests --- end body --- comments : --- start comments --- --- end comments ---

CU: ChecksumComparator: compares checksum from API with the current ones

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: ChecksumComparator: compares checksum from API with the current ones Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: ChecksumDownloader: downloads checksum list for files from the API

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: ChecksumDownloader: downloads checksum list for files from the API Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: PermissionChecker: check permissions of important folders (mostly write permissions probably)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: PermissionChecker: check permissions of important folders (mostly write permissions probably) Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: SystemCompatibilityChecker: check compatibility of specified shop with the system

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: SystemCompatibilityChecker: check compatibility of specified shop with the system Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: DbExtractor: return the DB structure

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: DbExtractor: return the DB structure Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU: ChecsumExtractor return the list of files with their XML checksum

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU: ChecsumExtractor return the list of files with their XML checksum Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

CU (core upgrade): PrestaShopInfoExtractor that based on a path to a shop can extract some data (PS version, DB parameters, admin folder name)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CU (core upgrade): PrestaShopInfoExtractor that based on a path to a shop can extract some data (PS version, DB parameters, admin folder name) Issue date: --- start body --- None --- end body --- comments : --- start comments --- --- end comments ---

As a user/integrator/support I want to know the status/diagnostic of my shop so I can know .... ## Description Execute a set of diagnostic for prestashop installation 1. check the current ps version 2. check the md5sum of files of the current installation vs the \<ORIGINAL\> 3. check the database structure of the current installation vs the \<ORIGINAL\> 4. check the permissions of several directory, files of the current installation 5. check the db info 6. check the compatibility of the current installation ### Options Implement [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) #### Help message For --help option : _ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation ( current directory by default) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Check Prestashop version Display PS version currently installed ( \<ORIGINAL\> ) ### Check the md5sum of files of the current installation vs the ORIGINAL 1. If the \<ORIGINAL_XML_FILE\> is not available then download it and perform a md5sum check of \<ORIGINAL_XML_FILE\> 2. Perform a md5sum check for all files 3. Display modified files ( if needed ) ( TODO progress bar ? ) ### Check the dbstuct of the CURRENT installation vs the ORIGINAL 1. If the \<ORIGINAL_DBSTUCT_FILE\>is not available then download it and perform a md5sum check of \<ORIGINAL_DBSTUCT_FILE\> 2. Perform a dbstruc check 3. Display issue (if needed ) ( TODO progress bar ? ) ### Check database info Check the database access. ### Check Permisssions Check the permissions of directories : TODO : list files/dir + htacesss ? @jo / @boris ? how to maintain what prmision should be ? ### Check the compatibility of the current version See [ps-upgrade:compatibility ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44113169) ## Acceptance tests ### Accteptance test : Display help message _$ps-upgrade:doctor --help ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation ( current directory by default) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Acceptance test : other Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ### Display the current version of current PrestaShop : OK ``` $ ps-upgrade:doctor --diaglist=ps-version Current version is X.Y.Z̀ ``` for PS version >= 8 or ``` $ ps-upgrade:doctor --diaglist=ps-version Current version is 1.X.Y.Z̀ ``` for PS version < 8 ## Display the current version of current PrestaShop : Can not perform diagnostic (version) How to test it ? (for QA ) : afterwards : see all cases with dev ``` $ ps-upgrade:doctor --diaglist=ps-version Can not detect PrestaShop version : \<ERROR\> ``` --- ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> OK & md5sum of all files OK ``` $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : OK Perform check for all files : OK ``` ## Check md5sum : if \<ORIGINAL_XML_FILE\> not available (should be download) & md5sum of \<ORIGINAL_XML_FILE\> OK & md5sum of all files OK ``` $ ps-upgrade:doctor --diaglist=files-md5sum Download <ORIGINAL_XML_FILE> : OK Check <ORIGINAL_XML_FILE> : OK Perform check : OK ``` ## Check md5sum : if \<ORIGINAL_XML_FILE\> not available (should be download) & download KO ``` $ ps-upgrade:doctor --diaglist=files-md5sum Download <ORIGINAL_XML_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS : ChecksumDownloader ) ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> KO ```\ $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS ) ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> OK & Diff with Files ``` $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : OK Perform check <WARNINGS> Some file(s) have been modified , please check your installation (voir avec Julie ? ) ``` With \<WARNINGS\> : **for each file (one per line)** with different md5sum _\<PATH\> : Wrong md5sum_ With \<PATH\>: file path that have been modified (wrong checksum) Note : _Some file(s) have been modified , please check your installation (voir avec Julie ? )_ is **display only once** --- ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> OK & dbstruct OK ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : OK Perform check of the database : OK ``` ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> not available (should be download) & md5sum of \\<ORIGINAL_DBSTUCT_FILE\> OK & dbstruct OK ``` $ ps-upgrade:doctor --diaglist=dbstruct Download <ORIGINAL_DBSTUCT_FILE> : OK Check <ORIGINAL_DBSTUCT_FILE>: OK Perform check of the database: OK ``` ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> not available (should be download) & download KO ``` $ ps-upgrade:doctor --diaglist=dbstruct Download <ORIGINAL_DBSTUCT_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS : ChecksumDownloader ) ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\>available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> KO ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> OK & Diff with db struct ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : OK Perform check of database <WARNINGS> Database has been modified , please check your installation ``` With \<WARNINGS\> : **for each table (one per line)** with difference _\<TABLE\> : list of fields modified_ With \<TABLE\>: TABLE modified TODO : Check with dev hot to test it Note : _Database has been modified , please check your installation (voir avec Julie ? )_ is **display only once** --- ### Permissions Checks : OK ``` $ ps-upgrade:doctor --diaglist=access-managment Check permissions : OK ``` ### Permissions Checks : KO ``` $ ps-upgrade:doctor --diaglist=access-managment, Check permissions : <FILE_OR_DIR_PATH> : Incorect permission : expected permissions <EXPECTED_FILE_PERMISSIONS> Wrong permissions : Please check your installation ``` With ( **for each warning** ) - \<FILE_OR_DIR_PATH\>: file or directory path - \<EXPECTED_FILE_PERMISSIONS\> : The expected permissions - \<HTACCESS_PATH\> : htaccess file path - <EXPECTED_HTACCESS> : expected hatacess ( TODO ) Note : _Wrong permissions : Please check your installation (voir avec Julie ? )_ is **display only once --- ### DB info check : OK ``` $ ps-upgrade:doctor --diaglist=db-info Check Database informations : OK ``` ### DB info check : KO ``` $ ps-upgrade:doctor --diaglist=db-info Check Database informations : KO <ERRORS> ``` With \<ERROS\> : list of errors ( check with dev ) **one per line** --- ### Check the compatibility of the current installation : OK ``` $ ps-upgrade:doctor --diaglist=compatibility Check Compatibility informations : OK ``` ### Check the compatibility of the current installation : KO ``` $ ps-upgrade:doctor --diaglist=comptibility Check compatibility informations : KO <ERRORS> ``` With \<ERROS\> : list of errors ( check with dev ) **one per line** TODO See how to test : ( we need a list here ) - php version - mysSQL version - php-ext version ( + list ) - php config --- ### Technical specs - [ ] #35085 - [ ] #35086 - [ ] #35087 - [ ] #35088 - [ ] #35089 - [ ] #35090 - [ ] #35091 - [ ] #35092 - [ ] #35093

EPIC - CLI : ps-upgrade:doctor - implement doctor

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : EPIC - CLI : ps-upgrade:doctor - implement doctor Issue date: --- start body --- As a user/integrator/support I want to know the status/diagnostic of my shop so I can know .... ## Description Execute a set of diagnostic for prestashop installation 1. check the current ps version 2. check the md5sum of files of the current installation vs the \<ORIGINAL\> 3. check the database structure of the current installation vs the \<ORIGINAL\> 4. check the permissions of several directory, files of the current installation 5. check the db info 6. check the compatibility of the current installation ### Options Implement [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) #### Help message For --help option : _ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation ( current directory by default) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Check Prestashop version Display PS version currently installed ( \<ORIGINAL\> ) ### Check the md5sum of files of the current installation vs the ORIGINAL 1. If the \<ORIGINAL_XML_FILE\> is not available then download it and perform a md5sum check of \<ORIGINAL_XML_FILE\> 2. Perform a md5sum check for all files 3. Display modified files ( if needed ) ( TODO progress bar ? ) ### Check the dbstuct of the CURRENT installation vs the ORIGINAL 1. If the \<ORIGINAL_DBSTUCT_FILE\>is not available then download it and perform a md5sum check of \<ORIGINAL_DBSTUCT_FILE\> 2. Perform a dbstruc check 3. Display issue (if needed ) ( TODO progress bar ? ) ### Check database info Check the database access. ### Check Permisssions Check the permissions of directories : TODO : list files/dir + htacesss ? @jo / @boris ? how to maintain what prmision should be ? ### Check the compatibility of the current version See [ps-upgrade:compatibility ](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44113169) ## Acceptance tests ### Accteptance test : Display help message _$ps-upgrade:doctor --help ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation ( current directory by default) --verbose: sets the verbosity level (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --quiet: disables output and interaction --no-interaction: disables interaction --version: outputs the version number of the console application --help: displays the command help --ansi|--no-ansi: whether to force of disable coloring the output_ ### Acceptance test : other Global options See [Global options](https://symfony.com/doc/current/console/input.html#command-global-options) ### Display the current version of current PrestaShop : OK ``` $ ps-upgrade:doctor --diaglist=ps-version Current version is X.Y.Z̀ ``` for PS version >= 8 or ``` $ ps-upgrade:doctor --diaglist=ps-version Current version is 1.X.Y.Z̀ ``` for PS version < 8 ## Display the current version of current PrestaShop : Can not perform diagnostic (version) How to test it ? (for QA ) : afterwards : see all cases with dev ``` $ ps-upgrade:doctor --diaglist=ps-version Can not detect PrestaShop version : \<ERROR\> ``` --- ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> OK & md5sum of all files OK ``` $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : OK Perform check for all files : OK ``` ## Check md5sum : if \<ORIGINAL_XML_FILE\> not available (should be download) & md5sum of \<ORIGINAL_XML_FILE\> OK & md5sum of all files OK ``` $ ps-upgrade:doctor --diaglist=files-md5sum Download <ORIGINAL_XML_FILE> : OK Check <ORIGINAL_XML_FILE> : OK Perform check : OK ``` ## Check md5sum : if \<ORIGINAL_XML_FILE\> not available (should be download) & download KO ``` $ ps-upgrade:doctor --diaglist=files-md5sum Download <ORIGINAL_XML_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS : ChecksumDownloader ) ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> KO ```\ $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS ) ## Check md5sum : if \<ORIGINAL_XML_FILE\> available & md5sum of \<ORIGINAL_XML_FILE\> OK & Diff with Files ``` $ ps-upgrade:doctor --diaglist=files-md5sum Check md5sum for <ORIGINAL_XML_FILE> : OK Perform check <WARNINGS> Some file(s) have been modified , please check your installation (voir avec Julie ? ) ``` With \<WARNINGS\> : **for each file (one per line)** with different md5sum _\<PATH\> : Wrong md5sum_ With \<PATH\>: file path that have been modified (wrong checksum) Note : _Some file(s) have been modified , please check your installation (voir avec Julie ? )_ is **display only once** --- ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> OK & dbstruct OK ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : OK Perform check of the database : OK ``` ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> not available (should be download) & md5sum of \\<ORIGINAL_DBSTUCT_FILE\> OK & dbstruct OK ``` $ ps-upgrade:doctor --diaglist=dbstruct Download <ORIGINAL_DBSTUCT_FILE> : OK Check <ORIGINAL_DBSTUCT_FILE>: OK Perform check of the database: OK ``` ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> not available (should be download) & download KO ``` $ ps-upgrade:doctor --diaglist=dbstruct Download <ORIGINAL_DBSTUCT_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ( depends on TS : ChecksumDownloader ) ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\>available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> KO ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : KO <ERROR> ``` Check aferwards with dev \<ERROR\> Messages + how to test it ## Check md5sum : if \<ORIGINAL_DBSTUCT_FILE\> available & md5sum of \<ORIGINAL_DBSTUCT_FILE\> OK & Diff with db struct ``` $ ps-upgrade:doctor --diaglist=dbstruct Check md5sum for <ORIGINAL_DBSTUCT_FILE> : OK Perform check of database <WARNINGS> Database has been modified , please check your installation ``` With \<WARNINGS\> : **for each table (one per line)** with difference _\<TABLE\> : list of fields modified_ With \<TABLE\>: TABLE modified TODO : Check with dev hot to test it Note : _Database has been modified , please check your installation (voir avec Julie ? )_ is **display only once** --- ### Permissions Checks : OK ``` $ ps-upgrade:doctor --diaglist=access-managment Check permissions : OK ``` ### Permissions Checks : KO ``` $ ps-upgrade:doctor --diaglist=access-managment, Check permissions : <FILE_OR_DIR_PATH> : Incorect permission : expected permissions <EXPECTED_FILE_PERMISSIONS> Wrong permissions : Please check your installation ``` With ( **for each warning** ) - \<FILE_OR_DIR_PATH\>: file or directory path - \<EXPECTED_FILE_PERMISSIONS\> : The expected permissions - \<HTACCESS_PATH\> : htaccess file path - <EXPECTED_HTACCESS> : expected hatacess ( TODO ) Note : _Wrong permissions : Please check your installation (voir avec Julie ? )_ is **display only once --- ### DB info check : OK ``` $ ps-upgrade:doctor --diaglist=db-info Check Database informations : OK ``` ### DB info check : KO ``` $ ps-upgrade:doctor --diaglist=db-info Check Database informations : KO <ERRORS> ``` With \<ERROS\> : list of errors ( check with dev ) **one per line** --- ### Check the compatibility of the current installation : OK ``` $ ps-upgrade:doctor --diaglist=compatibility Check Compatibility informations : OK ``` ### Check the compatibility of the current installation : KO ``` $ ps-upgrade:doctor --diaglist=comptibility Check compatibility informations : KO <ERRORS> ``` With \<ERROS\> : list of errors ( check with dev ) **one per line** TODO See how to test : ( we need a list here ) - php version - mysSQL version - php-ext version ( + list ) - php config --- ### Technical specs - [ ] #35085 - [ ] #35086 - [ ] #35087 - [ ] #35088 - [ ] #35089 - [ ] #35090 - [ ] #35091 - [ ] #35092 - [ ] #35093 --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to know how this tool is working so I can use it efficiently As a user or developer I want to have more information of what is happening so I can be debug As a devops or sysadmin I want a quiet mode so I will not be annoyed by verbosity to integrate tools into my automation tools As a user I want fancy output of this tool so I can understand easily what is happening ## Description his option are part of the [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands ### help Display help message on STDOUT and exit TODO Version files vu en réu avec jo & boris ( c'est quoi déjà ? ) #### Message _ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation --verbose <NUMBER> or -v or -vv or -vvv : sets the verbosity level with <NUMBER> (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --no-interaction: disables interaction --ansi|--no-ansi : whether to force of disable coloring the output --help: displays the command help --quiet: disables output and interaction_ ### verbosity Same as [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) (See --verbosity -v, -vv, -vvv ) See also [verbosity](https://symfony.com/doc/current/logging/monolog_console.html)  For each User Story : stdout , stderr (error) warning will be describe Debug will be add afterwards ( TODO demander à la QA si ils veulent tester les message des débug ) ### quiet disables output and interaction ### no-interaction disables interaction ### --ansi|--no-ansi whether to force of disable coloring the output ## Acceptances tests ### Help acceptance test ``` $ ps-upgrade:doctor , diagnostic of a prestashop shop Usage: ps:upgrade:docctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default --version --verbose <NUMBER> or -v or -vv or -vvv : sets the verbosity level with <NUMBER> (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --no-interaction: TODO --ansi|--no-ansi : TODO --help: displays this help --quiet : disables output and interaction ``` ### Verbosity acceptance test Go into the current prestashop directory ( ex: /var/www/prestashop/ ) and execute ``` $ ps-upgrade::doctor --verbosity 3 ... ``` You shoud see (dev) Debug message Same for ``` $ ps-upgrade:doctor --vvv ... ``` ### Quiet acceptance test Go into the current prestashop directory ( ex: /var/www/prestashop/ ) and execute ``` $ ps-upgrade:doctor --quiet ``` You should not see any output Voir avec jo / Boris : même les Err ??? ### Ansi / no ansi acceptance test ? A tester ? ### Version acceptance test for _ps-upgrade:doctor --version_ Same as [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) ## Not cover (yet) Multi-source / repositories

CLI - ps-upgrade:doctor - implement command global options

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CLI - ps-upgrade:doctor - implement command global options Issue date: --- start body --- As a user I want to know how this tool is working so I can use it efficiently As a user or developer I want to have more information of what is happening so I can be debug As a devops or sysadmin I want a quiet mode so I will not be annoyed by verbosity to integrate tools into my automation tools As a user I want fancy output of this tool so I can understand easily what is happening ## Description his option are part of the [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) for Symfony commands ### help Display help message on STDOUT and exit TODO Version files vu en réu avec jo & boris ( c'est quoi déjà ? ) #### Message _ps-upgrade:doctor: diagnostic of a prestashop shop Usage: ps:upgrade:doctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default -prestashop-path \<CURRENT_PATH\> ( optional) Path to your current installation --verbose <NUMBER> or -v or -vv or -vvv : sets the verbosity level with <NUMBER> (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --no-interaction: disables interaction --ansi|--no-ansi : whether to force of disable coloring the output --help: displays the command help --quiet: disables output and interaction_ ### verbosity Same as [Global Command options](https://symfony.com/doc/current/console/input.html#command-global-options) (See --verbosity -v, -vv, -vvv ) See also [verbosity](https://symfony.com/doc/current/logging/monolog_console.html)  For each User Story : stdout , stderr (error) warning will be describe Debug will be add afterwards ( TODO demander à la QA si ils veulent tester les message des débug ) ### quiet disables output and interaction ### no-interaction disables interaction ### --ansi|--no-ansi whether to force of disable coloring the output ## Acceptances tests ### Help acceptance test ``` $ ps-upgrade:doctor , diagnostic of a prestashop shop Usage: ps:upgrade:docctor --diaglist [ARGS] --prestashop-path \<CURRENT_PATH\> --diaglist (optional) different diagnostic to execute separate by comma ( files-md5sum,dbstuct,db-info,ps-version,access-managment, compat) ; all by default --version --verbose <NUMBER> or -v or -vv or -vvv : sets the verbosity level with <NUMBER> (e.g. 1 the default, 2 and 3, or you can use respective shortcuts -v, -vv and -vvv) --no-interaction: TODO --ansi|--no-ansi : TODO --help: displays this help --quiet : disables output and interaction ``` ### Verbosity acceptance test Go into the current prestashop directory ( ex: /var/www/prestashop/ ) and execute ``` $ ps-upgrade::doctor --verbosity 3 ... ``` You shoud see (dev) Debug message Same for ``` $ ps-upgrade:doctor --vvv ... ``` ### Quiet acceptance test Go into the current prestashop directory ( ex: /var/www/prestashop/ ) and execute ``` $ ps-upgrade:doctor --quiet ``` You should not see any output Voir avec jo / Boris : même les Err ??? ### Ansi / no ansi acceptance test ? A tester ? ### Version acceptance test for _ps-upgrade:doctor --version_ Same as [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) ## Not cover (yet) Multi-source / repositories --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to know the version of this tool so I can be sure to use the good one ## Description Implement **ps-upgrade:version** option Display the version message on STDOUT and exit ### Message If this is the latest version ``` ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z ``` And If this is NOT the latest version ``` ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Warning you are not using the latest version ( x.y.z ) ``` With X and x : an integer for major release Y and y: an integer for minor release Z:and z an integer for patch release See also : [Check version of ps-upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=47551762) ## Acceptances tests ### Acceptance test : OK If you have the latest version of ps-upgrade ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z ``` ### Acceptance test : New version available If you have a new version of ps-upgrade available ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Warning you are not using the latest version ( x.y.z ) ``` ### Acceptance test : Can not check new version ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Can not check new version of ps upgrade : \<ERROR\> ``` If server not available ( ex: shutdown the network ) : <ERROR> = TODO See with dev other errors ( depending on : [Check version of ps-upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=47551762) ) ### Technical specs - [ ] See Init TS, create two base repository structure and implement this version command - [ ] Its own version should be stored in a const set on the Application/Kernel class

CLI : ps-upgrade:version - implement version

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : CLI : ps-upgrade:version - implement version Issue date: --- start body --- As a user I want to know the version of this tool so I can be sure to use the good one ## Description Implement **ps-upgrade:version** option Display the version message on STDOUT and exit ### Message If this is the latest version ``` ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z ``` And If this is NOT the latest version ``` ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Warning you are not using the latest version ( x.y.z ) ``` With X and x : an integer for major release Y and y: an integer for minor release Z:and z an integer for patch release See also : [Check version of ps-upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=47551762) ## Acceptances tests ### Acceptance test : OK If you have the latest version of ps-upgrade ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z ``` ### Acceptance test : New version available If you have a new version of ps-upgrade available ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Warning you are not using the latest version ( x.y.z ) ``` ### Acceptance test : Can not check new version ``` $ ps-upgrade:version ps-upgrade Core Upgrade X.Y.Z ps-upgrade CLI X.Y.Z Can not check new version of ps upgrade : \<ERROR\> ``` If server not available ( ex: shutdown the network ) : <ERROR> = TODO See with dev other errors ( depending on : [Check version of ps-upgrade](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=47551762) ) ### Technical specs - [ ] See Init TS, create two base repository structure and implement this version command - [ ] Its own version should be stored in a const set on the Application/Kernel class --- end body --- comments : --- start comments --- --- end comments ---

As a user I want to know the latest version of this tool so I can be sure the tool is up to date ## Description See also [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) This TS check if this is the latest version ## Acceptances Tests See [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) ### Technical specs - [ ] In core upgrade: add a tool class/service VersionChecker able to retrieve the list of tags from a defined repository (one method getLatestTag) - [ ] In CLI App: integrate this tool with repository configured as https://github.com/PrestaShop/CLIUpgrade and compare current version with latest one, display warning when they don't match

TS : ps-upgrade:version - check latest version

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : TS : ps-upgrade:version - check latest version Issue date: --- start body --- As a user I want to know the latest version of this tool so I can be sure the tool is up to date ## Description See also [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) This TS check if this is the latest version ## Acceptances Tests See [Display version](https://github.com/orgs/PrestaShop/projects/7/views/43?layout=board&pane=issue&itemId=44019924) ### Technical specs - [ ] In core upgrade: add a tool class/service VersionChecker able to retrieve the list of tags from a defined repository (one method getLatestTag) - [ ] In CLI App: integrate this tool with repository configured as https://github.com/PrestaShop/CLIUpgrade and compare current version with latest one, display warning when they don't match --- end body --- comments : --- start comments --- --- end comments ---

## Description To start the autoupgrade project we need to initialize two repositories: - [ ] https://github.com/PrestaShop/CoreUpgradeBundle This is the bundle (SF 6.4) that will contain all the upgrade services, all the business logic, all the upgrade scripts and SQLs (it will be used by the CLI app and the Web app) - [ ] https://github.com/PrestaShop/CLIUpgrade This is a Symfony application (SF 6.4) that contains CLI commands (symfony commands) relying on the core upgrade bundle This app is mostly an empty shell, but it will introduce the Symfony commands, it should create an internal bundle for these commands (this will ease the work in case someday we need to extract this bundle and these commands into a dedicated repository) The two projects should respect the Autoupgrade ADR (add link to ADR) The purpose of this issue/task is not to fully implement them, just to get the basic project structure (a simple command like version can be integrated to validate the architecture). Note after this first init PR on the two repositories they can be switched to public. ## Acceptance tests ( dev ) - Repository CoreUpgradeBundle up & running + switch to public - Repository CLI SF upgrade up & running + switch to public

TS - Init Autoupgrade project

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : TS - Init Autoupgrade project Issue date: --- start body --- ## Description To start the autoupgrade project we need to initialize two repositories: - [ ] https://github.com/PrestaShop/CoreUpgradeBundle This is the bundle (SF 6.4) that will contain all the upgrade services, all the business logic, all the upgrade scripts and SQLs (it will be used by the CLI app and the Web app) - [ ] https://github.com/PrestaShop/CLIUpgrade This is a Symfony application (SF 6.4) that contains CLI commands (symfony commands) relying on the core upgrade bundle This app is mostly an empty shell, but it will introduce the Symfony commands, it should create an internal bundle for these commands (this will ease the work in case someday we need to extract this bundle and these commands into a dedicated repository) The two projects should respect the Autoupgrade ADR (add link to ADR) The purpose of this issue/task is not to fully implement them, just to get the basic project structure (a simple command like version can be integrated to validate the architecture). Note after this first init PR on the two repositories they can be switched to public. ## Acceptance tests ( dev ) - Repository CoreUpgradeBundle up & running + switch to public - Repository CLI SF upgrade up & running + switch to public --- 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 variants tab of the product view, variants are not loading... I can see a shopId=NaN in the Ajax calls... <img width="1505" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/5221349/cdbe2a04-d5ab-4a08-87c8-ac6bad2e51fb"> ### Expected behavior Just loading of this tab correctly ### Steps to reproduce 1. Create a new product 2. Open variant tab ### 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_

Issue with variants in product creation (shopId=NaN)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Issue with variants in product creation (shopId=NaN) 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 variants tab of the product view, variants are not loading... I can see a shopId=NaN in the Ajax calls... <img width="1505" alt="image" src="https://github.com/PrestaShop/PrestaShop/assets/5221349/cdbe2a04-d5ab-4a08-87c8-ac6bad2e51fb"> ### Expected behavior Just loading of this tab correctly ### Steps to reproduce 1. Create a new product 2. Open variant tab ### PrestaShop version(s) where the bug happened 8.1.2 ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Product list (using V2 product page) n BO does not show final (selling) price with tax. Same problem also in multistore(in actual 8.1.3). Made few screens (PS 8.1.2)-sorry, it´s in czech, only lang installed. Product list - all prices are the same, the last one should be different  This is that last product config with added special price, you can see it is applied on everything and without time limitation:  And here is price how it is shown in FO  There is this pull: https://github.com/PrestaShop/PrestaShop/pull/11484 It states as solved, but it is actually not. Just like the last comment in there says - https://github.com/PrestaShop/PrestaShop/pull/11484#issuecomment-1407725230 ### Expected behavior The price with tax should be showing the final, actual, selling price of the product. Like it did in old PS 1.6. Price with tax, that is not actual selling price of that product is completely useless. ### Steps to reproduce 1. Go to product-list (V2) 2. Set up new product, set tax, add price with tax(let PS count tax excluded price) and save 3. Add some special price applied to everyone and everywhere 4. Check product-list in BO ### PrestaShop version(s) where the bug happened 8.1.2, 8.1.3 ### PHP version(s) where the bug happened 7.4, 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

BO product-list V2 (both single and multistore) - final price with tax missing applied special prices

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO product-list V2 (both single and multistore) - final price with tax missing applied special 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 Product list (using V2 product page) n BO does not show final (selling) price with tax. Same problem also in multistore(in actual 8.1.3). Made few screens (PS 8.1.2)-sorry, it´s in czech, only lang installed. Product list - all prices are the same, the last one should be different  This is that last product config with added special price, you can see it is applied on everything and without time limitation:  And here is price how it is shown in FO  There is this pull: https://github.com/PrestaShop/PrestaShop/pull/11484 It states as solved, but it is actually not. Just like the last comment in there says - https://github.com/PrestaShop/PrestaShop/pull/11484#issuecomment-1407725230 ### Expected behavior The price with tax should be showing the final, actual, selling price of the product. Like it did in old PS 1.6. Price with tax, that is not actual selling price of that product is completely useless. ### Steps to reproduce 1. Go to product-list (V2) 2. Set up new product, set tax, add price with tax(let PS count tax excluded price) and save 3. Add some special price applied to everyone and everywhere 4. Check product-list in BO ### PrestaShop version(s) where the bug happened 8.1.2, 8.1.3 ### PHP version(s) where the bug happened 7.4, 8.0 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

Upgrade from Symfony 6.3 to Symfony 6.4 - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.4.md We must prevent the usage of already deprecated methods/code as much as possible. > [!NOTE] > This hunt on deprecated code can be done in separated PRs if the upgrade PR is already too big

Upgrade to Symfony 6.4

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade to Symfony 6.4 Issue date: --- start body --- Upgrade from Symfony 6.3 to Symfony 6.4 - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.4.md We must prevent the usage of already deprecated methods/code as much as possible. > [!NOTE] > This hunt on deprecated code can be done in separated PRs if the upgrade PR is already too big --- end body --- comments : --- start comments --- --- end comments ---

Upgrade from Symfony 6.0 to Symfony 6.3 Also we should keep in mind what Symfony recommends in its step by step migration guide for each version: - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.1.md - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.2.md - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.3.md We must prevent the usage of already deprecated methods/code as much as possible. > [!NOTE] > This hunt on deprecated code can be done in separated PRs if the upgrade PR is already too big

Upgrade to Symfony 6.3

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade to Symfony 6.3 Issue date: --- start body --- Upgrade from Symfony 6.0 to Symfony 6.3 Also we should keep in mind what Symfony recommends in its step by step migration guide for each version: - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.1.md - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.2.md - https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.3.md We must prevent the usage of already deprecated methods/code as much as possible. > [!NOTE] > This hunt on deprecated code can be done in separated PRs if the upgrade PR is already too big --- 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 Turn off token from Advanced Parameters -> Security and admin search will start giving error. ### Expected behavior Show search results. ### Steps to reproduce 1. Advanced Parameters 2. Security 3. Back office token protection turn this off 4. Search with any number 5. It will give error ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Admin Search error when token disabled

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Admin Search error when token disabled 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 Turn off token from Advanced Parameters -> Security and admin search will start giving error. ### Expected behavior Show search results. ### Steps to reproduce 1. Advanced Parameters 2. Security 3. Back office token protection turn this off 4. Search with any number 5. It will give error ### PrestaShop version(s) where the bug happened 8.1.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When a product is physically removed from the shop, and then the order details are edited (e.g., changing customer address or carrier), the invoice calculation recalculates the total product amount to 0. ### Expected behavior The invoice total should remain unchanged after editing order details. ### Steps to reproduce 1. Place an order with at least one product. 2. Generate the invoice. 3. Physically delete the product from the shop. 4. Edit the order details (e.g., change customer address or carrier). ### PrestaShop version(s) where the bug happened 1.7.8.3 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_

Bug in Invoice Calculation when Editing Order Details

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Bug in Invoice Calculation when Editing Order Details Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When a product is physically removed from the shop, and then the order details are edited (e.g., changing customer address or carrier), the invoice calculation recalculates the total product amount to 0. ### Expected behavior The invoice total should remain unchanged after editing order details. ### Steps to reproduce 1. Place an order with at least one product. 2. Generate the invoice. 3. Physically delete the product from the shop. 4. Edit the order details (e.g., change customer address or carrier). ### PrestaShop version(s) where the bug happened 1.7.8.3 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 I have an issue with the basic Cash on delivery (COD) v2.0.1 - from PrestaShop module in my PrestaShop store. I am using version 8.0.4 on a server with PHP 7.4. Cash On Delivery is the only available option in my store. When a customer placing an order has an account and is logged in, everything works fine. Unfortunately, if a customer wants to place an order without creating an account as a guest, an error 500 occurs in the order process just before the last screen confirming the order. After refreshing with F5, it proceeds to the order confirmation page (but the guest's email address is not entered there). This happens every time. I have searched for a solution to this problem online, but there is no specific solution available. I've noticed that more people are experiencing this issue.    ### Expected behavior I would like to resolve the 500 error when a guest places an order, and I would also like the guest's email address to appear on the order confirmation page. ### Steps to reproduce 1. I navigate to the product page. 2. I click the "Buy Now" button on the product page. 3. On the shopping cart page, I click the "Proceed to Checkout" button. 4. I fill in the fields for first name, last name, shipping address, email address, and phone number. I leave the password field blank. 5. I agree to the terms and conditions and the privacy policy. I click the "Continue" button. 6. I click the "Continue" button when selecting the Shipping Method. Since I have only one carrier to choose from, I simply confirm by clicking "Continue." 7. In the "Payment" tab, I already have the Cash On Delivery option selected as it is the only payment method available in the store. I check the "I agree to the terms of service as set out by the user agreement" box and click the "Place Order" button. 8. I receive a 500 error. This page is not working. HTTP ERROR 500. 9. I refresh the page with F5 and receive the order confirmation page, but the email information does not include the email address. ### PrestaShop version(s) where the bug happened 8.0.4 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version Cash on delivery (COD) v2.0.1 - from PrestaShop ### Your company or customer's name goes here (if applicable). Martin

Error 500 when placing an order when placing an order as a guest. Cash on delivery (COD) v2.0.1 - from PrestaShop.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error 500 when placing an order when placing an order as a guest. Cash on delivery (COD) v2.0.1 - from 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 I have an issue with the basic Cash on delivery (COD) v2.0.1 - from PrestaShop module in my PrestaShop store. I am using version 8.0.4 on a server with PHP 7.4. Cash On Delivery is the only available option in my store. When a customer placing an order has an account and is logged in, everything works fine. Unfortunately, if a customer wants to place an order without creating an account as a guest, an error 500 occurs in the order process just before the last screen confirming the order. After refreshing with F5, it proceeds to the order confirmation page (but the guest's email address is not entered there). This happens every time. I have searched for a solution to this problem online, but there is no specific solution available. I've noticed that more people are experiencing this issue.    ### Expected behavior I would like to resolve the 500 error when a guest places an order, and I would also like the guest's email address to appear on the order confirmation page. ### Steps to reproduce 1. I navigate to the product page. 2. I click the "Buy Now" button on the product page. 3. On the shopping cart page, I click the "Proceed to Checkout" button. 4. I fill in the fields for first name, last name, shipping address, email address, and phone number. I leave the password field blank. 5. I agree to the terms and conditions and the privacy policy. I click the "Continue" button. 6. I click the "Continue" button when selecting the Shipping Method. Since I have only one carrier to choose from, I simply confirm by clicking "Continue." 7. In the "Payment" tab, I already have the Cash On Delivery option selected as it is the only payment method available in the store. I check the "I agree to the terms of service as set out by the user agreement" box and click the "Place Order" button. 8. I receive a 500 error. This page is not working. HTTP ERROR 500. 9. I refresh the page with F5 and receive the order confirmation page, but the email information does not include the email address. ### PrestaShop version(s) where the bug happened 8.0.4 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version Cash on delivery (COD) v2.0.1 - from PrestaShop ### Your company or customer's name goes here (if applicable). Martin --- 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 running the composer script create-test-db, the dump files generated have the order of the columns mixed up sometimes. This leads to dupplicate primary key when restoring the dump file. Also the error message generated is very misleading. Exception message: ``` Exception: Unable to exec command: `/usr/bin/mysql -u 'root' -P '3306' -h 'mysql' -p'prestashop' 'test_prestashop' < '/tmp/ps_dump_test_prestashop_9.0.0_ps_hook.sql' 2> /dev/null`, missing a binary? in /var/www/html/tests/Resources/DatabaseDump.php:247 ``` ### Expected behavior Don't have any duplicate primary key when restoring a dump file. Change the error message so that it is more explicit. ### Steps to reproduce 1. Install the project 2. run the composer create-test-db command 3. find the dump file generated and inspect it 4. Notice on some tables ( e.g. ps_zone ) the active field is inserted before the id field ### 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). PrestaShop SA

Dump files created by composer create-test-db insert fields in the wrong order.

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Dump files created by composer create-test-db insert fields in the wrong 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 When running the composer script create-test-db, the dump files generated have the order of the columns mixed up sometimes. This leads to dupplicate primary key when restoring the dump file. Also the error message generated is very misleading. Exception message: ``` Exception: Unable to exec command: `/usr/bin/mysql -u 'root' -P '3306' -h 'mysql' -p'prestashop' 'test_prestashop' < '/tmp/ps_dump_test_prestashop_9.0.0_ps_hook.sql' 2> /dev/null`, missing a binary? in /var/www/html/tests/Resources/DatabaseDump.php:247 ``` ### Expected behavior Don't have any duplicate primary key when restoring a dump file. Change the error message so that it is more explicit. ### Steps to reproduce 1. Install the project 2. run the composer create-test-db command 3. find the dump file generated and inspect it 4. Notice on some tables ( e.g. ps_zone ) the active field is inserted before the id field ### 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). PrestaShop SA --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments The modules on the dev branch: - ps_checkpayment - ps_wirepayment - ps_cashondelivery since the new feature displays the logo of the payment method into the cart. The logo can be wrongly displayed, and the merchant would need to adapt the theme. ### Expected behavior To avoid forcing the merchant to adapt the theme, the feature should be configurable. Add a toggle on the module, to be able to display or not the logo on the configuration page. **Label**:Display the payment logo on the payment step <img width="426" alt="Capture d’écran 2024-01-16 à 14 09 12" src="https://github.com/PrestaShop/PrestaShop/assets/43613217/8ee0e053-00b2-46ae-b432-f7d511c46827"> By default disabled the feature ### Steps to reproduce 1. Install the module dev branch 2. go to the checkout page, on the payment step ### PrestaShop version(s) where the bug happened All ### 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_

Payment method logo wrongly displayed

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Payment method logo wrongly 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 The modules on the dev branch: - ps_checkpayment - ps_wirepayment - ps_cashondelivery since the new feature displays the logo of the payment method into the cart. The logo can be wrongly displayed, and the merchant would need to adapt the theme. ### Expected behavior To avoid forcing the merchant to adapt the theme, the feature should be configurable. Add a toggle on the module, to be able to display or not the logo on the configuration page. **Label**:Display the payment logo on the payment step <img width="426" alt="Capture d’écran 2024-01-16 à 14 09 12" src="https://github.com/PrestaShop/PrestaShop/assets/43613217/8ee0e053-00b2-46ae-b432-f7d511c46827"> By default disabled the feature ### Steps to reproduce 1. Install the module dev branch 2. go to the checkout page, on the payment step ### PrestaShop version(s) where the bug happened All ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When attempting to install a fresh copy of Prestashop 8.1.3 (downloaded from Prestashop.com) the attached error occurs:  Also attaching the error log which I hope is helpful. Please advise ### Expected behavior _No response_ ### Steps to reproduce Download Prestashop 8.1.3 from Prestashop.com Install on Windows ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.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_

Cannot install Prestashop 8.1.3 on Windows

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Cannot install Prestashop 8.1.3 on Windows 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 attempting to install a fresh copy of Prestashop 8.1.3 (downloaded from Prestashop.com) the attached error occurs:  Also attaching the error log which I hope is helpful. Please advise ### Expected behavior _No response_ ### Steps to reproduce Download Prestashop 8.1.3 from Prestashop.com Install on Windows ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 8.1.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 two or more modules implement the "filterProductContent" hook, the following error is produced: Fatal error: Uncaught TypeError: HookCore::callHookOn(): Argument #3 ($hookArgs) must be of type array, null given, called in C:\websites\clients\test\www\classes\Hook.php on line 981 and defined in C:\websites\clients\test\www\classes\Hook.php:408 Stack trace: #0 C:\websites\clients\test\www\classes\Hook.php(981): HookCore::callHookOn(Object(PfDownloads), 'filterProductCo...', NULL) #1 C:\websites\clients\test\www\controllers\front\ProductController.php(432): HookCore::exec('filterProductCo...', NULL, NULL, false, true, false, NULL, true) #2 C:\websites\clients\test\www\classes\controller\Controller.php(319): ProductControllerCore->initContent() #3 C:\websites\clients\test\www\classes\Dispatcher.php(510): ControllerCore->run() #4 C:\websites\clients\test\www\index.php(28): DispatcherCore->dispatch() #5 {main} thrown in C:\websites\clients\test\www\classes\Hook.php on line 408 But it seems to work OK when only one module is utilising the hook. ### Expected behavior Any number of modules should be able to utilise this hook. ### Steps to reproduce 1. Create two separate test modules which both implement the "filterProductContent" hook 2. Load the store front and the error should appear ### PrestaShop version(s) where the bug happened 8.0, 8.1.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

filterProductContent hook bug

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : filterProductContent hook bug Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When two or more modules implement the "filterProductContent" hook, the following error is produced: Fatal error: Uncaught TypeError: HookCore::callHookOn(): Argument #3 ($hookArgs) must be of type array, null given, called in C:\websites\clients\test\www\classes\Hook.php on line 981 and defined in C:\websites\clients\test\www\classes\Hook.php:408 Stack trace: #0 C:\websites\clients\test\www\classes\Hook.php(981): HookCore::callHookOn(Object(PfDownloads), 'filterProductCo...', NULL) #1 C:\websites\clients\test\www\controllers\front\ProductController.php(432): HookCore::exec('filterProductCo...', NULL, NULL, false, true, false, NULL, true) #2 C:\websites\clients\test\www\classes\controller\Controller.php(319): ProductControllerCore->initContent() #3 C:\websites\clients\test\www\classes\Dispatcher.php(510): ControllerCore->run() #4 C:\websites\clients\test\www\index.php(28): DispatcherCore->dispatch() #5 {main} thrown in C:\websites\clients\test\www\classes\Hook.php on line 408 But it seems to work OK when only one module is utilising the hook. ### Expected behavior Any number of modules should be able to utilise this hook. ### Steps to reproduce 1. Create two separate test modules which both implement the "filterProductContent" hook 2. Load the store front and the error should appear ### PrestaShop version(s) where the bug happened 8.0, 8.1.x ### PHP version(s) where the bug happened 8 ### If your bug is related to a module, specify its name and its version _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 With my Prestashop 8.0.0 I cannot update many modules, there are more and more. The “Payment by bank transfer” module does not appear in the front office when you want to pay. Someone in the forum advised me to upgrade. I wanted to do that and version 8.0.5 was suggested to me. I then put the shop in maintenance mode and started the upgrade. It didn't end and got stuck. You could see a field with red error messages. I then canceled the matter and contacted Prestashop Helpdesk. They referred me to them. The “Assistance by Prestashop” module is also installed.   How can I upload a video? ### Expected behavior  I thought that an automatic upgrade would fix the errors. Unfortunately that was not the case as this upgrade was not completed      ### Steps to reproduce 1. Set maintenance mode 2. Save 3. Click Upgrade 4. Check if all ticks are green 5. Then start the automatic upgrade ### PrestaShop version(s) where the bug happened 8.0.0 ### PHP version(s) where the bug happened 8.2.14 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). asamex

Prestashop 8.0.0 cannot be upgraded

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop 8.0.0 cannot be upgraded Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments With my Prestashop 8.0.0 I cannot update many modules, there are more and more. The “Payment by bank transfer” module does not appear in the front office when you want to pay. Someone in the forum advised me to upgrade. I wanted to do that and version 8.0.5 was suggested to me. I then put the shop in maintenance mode and started the upgrade. It didn't end and got stuck. You could see a field with red error messages. I then canceled the matter and contacted Prestashop Helpdesk. They referred me to them. The “Assistance by Prestashop” module is also installed.   How can I upload a video? ### Expected behavior  I thought that an automatic upgrade would fix the errors. Unfortunately that was not the case as this upgrade was not completed      ### Steps to reproduce 1. Set maintenance mode 2. Save 3. Click Upgrade 4. Check if all ticks are green 5. Then start the automatic upgrade ### PrestaShop version(s) where the bug happened 8.0.0 ### PHP version(s) where the bug happened 8.2.14 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). asamex --- 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 WhenI have multiple messages that I want to answer, I click on the button "Reply to the next unanswered message in this thread", but I'm not redirected to the next unanswered message. The page is just refreshed. ### Expected behavior I should be redirected to the next new unanswered message. ### Steps to reproduce 1. Go to FO > Contact Us > Send a message with email address : test@test.com 2. The message is sent 3. Send another message from the contactform with email address : hello@world.com 4. The message is sent 5. Go to BO > Customer service > Open the thread from test@test.com 6. Click on Reply to the next unanswered message in this thread > You are not redirected to the second message :x: ### PrestaShop version(s) where the bug happened 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Customer Service - Button "Reply to the next unanswered message in this thread" doesn't work

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Customer Service - Button "Reply to the next unanswered message in this thread" 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 WhenI have multiple messages that I want to answer, I click on the button "Reply to the next unanswered message in this thread", but I'm not redirected to the next unanswered message. The page is just refreshed. ### Expected behavior I should be redirected to the next new unanswered message. ### Steps to reproduce 1. Go to FO > Contact Us > Send a message with email address : test@test.com 2. The message is sent 3. Send another message from the contactform with email address : hello@world.com 4. The message is sent 5. Go to BO > Customer service > Open the thread from test@test.com 6. Click on Reply to the next unanswered message in this thread > You are not redirected to the second message :x: ### PrestaShop version(s) where the bug happened 8.1.x, 9.0.x ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When the order has been processed and for some reason it needs to be picked up at the store, the following error is generated in the exchange. PS 8.1.1 PHP 7.3 I attach a video with the generation of the error. Thank you. ### Expected behavior _No response_ ### Steps to reproduce https://github.com/PrestaShop/PrestaShop/assets/31345705/74aa8c8f-9d48-402e-91b1-355798509e1f ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Error when selecting a carrier change when the order has been processed by editing the shipping options?

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Error when selecting a carrier change when the order has been processed by editing the shipping options? Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When the order has been processed and for some reason it needs to be picked up at the store, the following error is generated in the exchange. PS 8.1.1 PHP 7.3 I attach a video with the generation of the error. Thank you. ### Expected behavior _No response_ ### Steps to reproduce https://github.com/PrestaShop/PrestaShop/assets/31345705/74aa8c8f-9d48-402e-91b1-355798509e1f ### PrestaShop version(s) where the bug happened 8.1.x ### PHP version(s) where the bug happened 7.3 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Upgrade to develop branch is broken, ending in an error `Cannot instantiate abstract class AppKernel`. It's caused by https://github.com/PrestaShop/autoupgrade/blob/dev/classes/UpgradeTools/SymfonyAdapter.php doing `$kernel = new \AppKernel($env, _PS_MODE_DEV_);` This worked in the past, but recently the class has been changed in https://github.com/PrestaShop/PrestaShop/pull/32719/files to `abstract` and two new children has been made - `FrontKernel` and `AdminKernel`.  Reproduced by @florine2623 ### Expected behavior There are two solutions. - Removing the abstract keyword. I tried it and all works OK. There are no abstract methods in that class so the keyword is not needed. - Instantiate AdminKernel instead, but that would need to bring some conditions into play and some other stuff. ### Steps to reproduce Upgrade from 8.1.x to develop branch. ### PrestaShop version(s) where the bug happened upgrade from any version to 9.0.0

Upgrade to develop branch broken because of AppKernel

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Upgrade to develop branch broken because of AppKernel 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 Upgrade to develop branch is broken, ending in an error `Cannot instantiate abstract class AppKernel`. It's caused by https://github.com/PrestaShop/autoupgrade/blob/dev/classes/UpgradeTools/SymfonyAdapter.php doing `$kernel = new \AppKernel($env, _PS_MODE_DEV_);` This worked in the past, but recently the class has been changed in https://github.com/PrestaShop/PrestaShop/pull/32719/files to `abstract` and two new children has been made - `FrontKernel` and `AdminKernel`.  Reproduced by @florine2623 ### Expected behavior There are two solutions. - Removing the abstract keyword. I tried it and all works OK. There are no abstract methods in that class so the keyword is not needed. - Instantiate AdminKernel instead, but that would need to bring some conditions into play and some other stuff. ### Steps to reproduce Upgrade from 8.1.x to develop branch. ### PrestaShop version(s) where the bug happened upgrade from any version to 9.0.0 --- 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="1216" alt="Screenshot 2024-01-11 at 15 19 53" src="https://github.com/PrestaShop/PrestaShop/assets/10567881/04544a1f-fbc7-4a5d-ae5c-fcaec340211d"> ### Expected behavior _No response_ ### Steps to reproduce 1) Configure two products with: - 18.56 - 28.03 TAX 21 2) Create a cart with these productos 3) Check the price is incorrect ### PrestaShop version(s) where the bug happened 1.7.8.X 1.8.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_

Rounding problem in cart page (1.7.8.X - 8.X)

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Rounding problem in cart page (1.7.8.X - 8.X) 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="1216" alt="Screenshot 2024-01-11 at 15 19 53" src="https://github.com/PrestaShop/PrestaShop/assets/10567881/04544a1f-fbc7-4a5d-ae5c-fcaec340211d"> ### Expected behavior _No response_ ### Steps to reproduce 1) Configure two products with: - 18.56 - 28.03 TAX 21 2) Create a cart with these productos 3) Check the price is incorrect ### PrestaShop version(s) where the bug happened 1.7.8.X 1.8.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 Updating a product combination's location used to be possible by PUTing a product combination object with the `<location></location>` field populated to the API via `https://www.example.com/api/combinations/ID` Currently you can send an update to this path which returns an `200 OK` response. However when you GET this combination path again the field is no longer populated. The back office UI also does not show the location. To show visually, below is an example of a call to the API to return a combination. e.g. https://www.example.co.uk/api/combinations/209 You can see the **`<location>`** element. The same query on the current Prestashop version will not show this element  On investigation it seems PUTing an object to the path above does update the `location` field in the `ps_product_attribute` table however it does not update the `location` field in the `ps_stock_available` table. When you use the back office UI to update a product combination's location, Prestashop updates both the `ps_product_attribute` & `ps_stock_available` tables which seems to be the correct behaviour. ### Expected behavior Updating a combination object via the API should also update the `ps_stock_available` table with a product location. This way it will show to API requests and via the Admin area. Alternately GETing a product combination via the API should at least get the `location` field from the `ps_product_attribute` Note: I have not tried it the other way by setting the `https://www.example.com/api/stock_availables/ID` object and seeing the results. It would be worth checking how this affects the database. ### Steps to reproduce 1. Update a product combination using the API. Set the `<location></location>` field 2. Get this combination - no location will be shown 3. Check the back office UI - no location will be shown 4. Check the `ps_product_attribute` table, the updated location **will** be shown 5. Check the `ps_stock_available` table, the updated location will **not** ben shown ### PrestaShop version(s) where the bug happened 1.7.8.7 - 1.8 ### PHP version(s) where the bug happened 7.4 - 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_

Updating a product combination location via API no longer is possible now

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Updating a product combination location via API no longer is possible now 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 Updating a product combination's location used to be possible by PUTing a product combination object with the `<location></location>` field populated to the API via `https://www.example.com/api/combinations/ID` Currently you can send an update to this path which returns an `200 OK` response. However when you GET this combination path again the field is no longer populated. The back office UI also does not show the location. To show visually, below is an example of a call to the API to return a combination. e.g. https://www.example.co.uk/api/combinations/209 You can see the **`<location>`** element. The same query on the current Prestashop version will not show this element  On investigation it seems PUTing an object to the path above does update the `location` field in the `ps_product_attribute` table however it does not update the `location` field in the `ps_stock_available` table. When you use the back office UI to update a product combination's location, Prestashop updates both the `ps_product_attribute` & `ps_stock_available` tables which seems to be the correct behaviour. ### Expected behavior Updating a combination object via the API should also update the `ps_stock_available` table with a product location. This way it will show to API requests and via the Admin area. Alternately GETing a product combination via the API should at least get the `location` field from the `ps_product_attribute` Note: I have not tried it the other way by setting the `https://www.example.com/api/stock_availables/ID` object and seeing the results. It would be worth checking how this affects the database. ### Steps to reproduce 1. Update a product combination using the API. Set the `<location></location>` field 2. Get this combination - no location will be shown 3. Check the back office UI - no location will be shown 4. Check the `ps_product_attribute` table, the updated location **will** be shown 5. Check the `ps_stock_available` table, the updated location will **not** ben shown ### PrestaShop version(s) where the bug happened 1.7.8.7 - 1.8 ### PHP version(s) where the bug happened 7.4 - 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 After upgrade from 8.1.1 to 8.1.3 front office don't work. Back office work. Fatal error: Uncaught PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php:149 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php(149): PDO->query() #1 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(377): DbPDOCore->_query() #2 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(744): DbCore->query() #3 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(477): DbCore->q() #4 /home/saqzmqei/shop.terpin.it/classes/ObjectModel.php(622): DbCore->insert() #5 /home/saqzmqei/shop.terpin.it/classes/ConnectionsSource.php(105): ObjectModelCore->add() #6 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(119): ConnectionsSourceCore::logHttpReferer() #7 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(74): statsdata->getScriptCustomerPagesViews() #8 /home/saqzmqei/shop.terpin.it/classes/Hook.php(1043): statsdata->hookDisplayBeforeBodyClosingTag() #9 /home/saqzmqei/shop.terpin.it/classes/Hook.php(418): HookCore::coreCallHook() #10 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #11 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #12 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #13 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #16 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #17 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #19 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #22 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #23 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #25 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #28 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #29 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #31 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #32 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #33 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #34 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #35 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #36 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #37 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #38 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #39 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #40 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #41 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #42 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #43 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #44 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #45 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #46 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #47 {main} Next PrestaShopException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php:151 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(377): DbPDOCore->_query() #1 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(744): DbCore->query() #2 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(477): DbCore->q() #3 /home/saqzmqei/shop.terpin.it/classes/ObjectModel.php(622): DbCore->insert() #4 /home/saqzmqei/shop.terpin.it/classes/ConnectionsSource.php(105): ObjectModelCore->add() #5 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(119): ConnectionsSourceCore::logHttpReferer() #6 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(74): statsdata->getScriptCustomerPagesViews() #7 /home/saqzmqei/shop.terpin.it/classes/Hook.php(1043): statsdata->hookDisplayBeforeBodyClosingTag() #8 /home/saqzmqei/shop.terpin.it/classes/Hook.php(418): HookCore::coreCallHook() #9 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #10 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #11 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #12 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #13 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #16 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #17 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #19 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #22 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #23 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #25 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #28 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #29 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #31 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #32 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #33 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #34 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #35 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #36 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #37 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #38 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #39 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #40 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #41 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #42 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #43 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #44 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #45 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #46 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/Hook.php:431 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #1 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #2 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #3 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #4 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #5 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #6 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #7 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #8 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #9 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #10 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #11 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #12 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #13 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #16 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #17 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #19 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #22 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #23 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #25 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #28 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #29 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #31 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #32 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #33 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #34 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #35 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #36 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #37 {main} thrown in /home/saqzmqei/shop.terpin.it/classes/Hook.php on line 431 ### Expected behavior _No response_ ### Steps to reproduce 1. upgrade with 1 click upgrade 2. front office don't work ### PrestaShop version(s) where the bug happened 8.1.1 to 8.1.3 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Front office error after update 8.1.1 to 8.1.3

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Front office error after update 8.1.1 to 8.1.3 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrade from 8.1.1 to 8.1.3 front office don't work. Back office work. Fatal error: Uncaught PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php:149 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php(149): PDO->query() #1 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(377): DbPDOCore->_query() #2 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(744): DbCore->query() #3 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(477): DbCore->q() #4 /home/saqzmqei/shop.terpin.it/classes/ObjectModel.php(622): DbCore->insert() #5 /home/saqzmqei/shop.terpin.it/classes/ConnectionsSource.php(105): ObjectModelCore->add() #6 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(119): ConnectionsSourceCore::logHttpReferer() #7 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(74): statsdata->getScriptCustomerPagesViews() #8 /home/saqzmqei/shop.terpin.it/classes/Hook.php(1043): statsdata->hookDisplayBeforeBodyClosingTag() #9 /home/saqzmqei/shop.terpin.it/classes/Hook.php(418): HookCore::coreCallHook() #10 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #11 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #12 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #13 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #16 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #17 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #19 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #22 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #23 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #25 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #28 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #29 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #31 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #32 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #33 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #34 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #35 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #36 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #37 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #38 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #39 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #40 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #41 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #42 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #43 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #44 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #45 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #46 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #47 {main} Next PrestaShopException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/db/DbPDO.php:151 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(377): DbPDOCore->_query() #1 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(744): DbCore->query() #2 /home/saqzmqei/shop.terpin.it/classes/db/Db.php(477): DbCore->q() #3 /home/saqzmqei/shop.terpin.it/classes/ObjectModel.php(622): DbCore->insert() #4 /home/saqzmqei/shop.terpin.it/classes/ConnectionsSource.php(105): ObjectModelCore->add() #5 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(119): ConnectionsSourceCore::logHttpReferer() #6 /home/saqzmqei/shop.terpin.it/modules/statsdata/statsdata.php(74): statsdata->getScriptCustomerPagesViews() #7 /home/saqzmqei/shop.terpin.it/classes/Hook.php(1043): statsdata->hookDisplayBeforeBodyClosingTag() #8 /home/saqzmqei/shop.terpin.it/classes/Hook.php(418): HookCore::coreCallHook() #9 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #10 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #11 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #12 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #13 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #16 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #17 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #19 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #22 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #23 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #25 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #28 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #29 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #31 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #32 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #33 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #34 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #35 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #36 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #37 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #38 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #39 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #40 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #41 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #42 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #43 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #44 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #45 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #46 {main} Next PrestaShop\PrestaShop\Core\Exception\CoreException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'saqzmqei_terpinshop.ps_connections_source' doesn't exist in /home/saqzmqei/shop.terpin.it/classes/Hook.php:431 Stack trace: #0 /home/saqzmqei/shop.terpin.it/classes/Hook.php(981): HookCore::callHookOn() #1 /home/saqzmqei/shop.terpin.it/config/smarty.config.inc.php(198): HookCore::exec() #2 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyLazyRegister.php(81): smartyHook() #3 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(381): SmartyLazyRegister->__call() #4 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(248): Block_174328677659efb4065e4f1_14211261->callBlock() #5 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(184): Smarty_Internal_Runtime_Inheritance->callBlock() #6 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(156): Smarty_Internal_Runtime_Inheritance->process() #7 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/ea/d1/b5/ead1b51c988034cc14e3ea5987e9a758d12a3005_2.file.layout-both-columns.tpl.php(125): Smarty_Internal_Runtime_Inheritance->instanceBlock() #8 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4065f398_42427690() #9 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #10 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #11 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #12 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #13 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/9f/7d/a5/9f7da5bd54ab81496b712ceab3fd31e68d2c076e_2.file.layout-full-width.tpl.php(42): Smarty_Internal_Runtime_Inheritance->endChild() #14 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40645229_85144033() #15 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #16 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #17 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #18 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #19 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/26/15/ea/2615eaf2dfdb0695b81c366f6261b1602538b2be_2.file.page.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #20 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb4063d894_31081681() #21 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #22 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #23 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(386): Smarty_Internal_Template->render() #24 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_inheritance.php(116): Smarty_Internal_Template->_subTemplateRender() #25 /home/saqzmqei/shop.terpin.it/var/cache/dev/smarty/compile/Bigstore_Layout2layouts_layout_full_width_tpl/c1/dc/0b/c1dc0b7dcca56b54112ba90606ee59df60bec798_2.file.index.tpl.php(33): Smarty_Internal_Runtime_Inheritance->endChild() #26 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_659efb40631a95_36112358() #27 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode() #28 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render() #29 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render() #30 /home/saqzmqei/shop.terpin.it/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(116): Smarty_Internal_TemplateBase->_execute() #31 /home/saqzmqei/shop.terpin.it/classes/Smarty/SmartyDev.php(40): Smarty_Internal_TemplateBase->fetch() #32 /home/saqzmqei/shop.terpin.it/override/classes/controller/FrontController.php(50): SmartyDev->fetch() #33 /home/saqzmqei/shop.terpin.it/classes/controller/FrontController.php(735): FrontController->smartyOutputContent() #34 /home/saqzmqei/shop.terpin.it/classes/controller/Controller.php(339): FrontControllerCore->display() #35 /home/saqzmqei/shop.terpin.it/classes/Dispatcher.php(510): ControllerCore->run() #36 /home/saqzmqei/shop.terpin.it/index.php(28): DispatcherCore->dispatch() #37 {main} thrown in /home/saqzmqei/shop.terpin.it/classes/Hook.php on line 431 ### Expected behavior _No response_ ### Steps to reproduce 1. upgrade with 1 click upgrade 2. front office don't work ### PrestaShop version(s) where the bug happened 8.1.1 to 8.1.3 ### PHP version(s) where the bug happened 8.1.26 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

List of US: https://github.com/PrestaShop/PrestaShop/issues/35369 https://github.com/PrestaShop/PrestaShop/issues/35374 https://github.com/PrestaShop/PrestaShop/issues/35375 https://github.com/PrestaShop/PrestaShop/issues/35377 https://github.com/PrestaShop/PrestaShop/issues/35378

[Epic][Pricing][MOC][B to C] : Method Of Calculating a cart total without discount

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : [Epic][Pricing][MOC][B to C] : Method Of Calculating a cart total without discount Issue date: --- start body --- List of US: https://github.com/PrestaShop/PrestaShop/issues/35369 https://github.com/PrestaShop/PrestaShop/issues/35374 https://github.com/PrestaShop/PrestaShop/issues/35375 https://github.com/PrestaShop/PrestaShop/issues/35377 https://github.com/PrestaShop/PrestaShop/issues/35378 --- 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 today I've found this bug in the classic theme (probably it is due from the core code) the address form doesn't show the fields present in its country, it is only partially done the problem is present for address already done, for nations that are not the default ones, it shows the default country fields, instead of showing only those selected for the chosen country I've done this video https://watch.screencastify.com/v/VgpRhU2QgZ7GwVf4HJon for the default Italy country I use these fields: `firstname lastname company vat_number dni address1 address2 postcode city State:name Country:name phone phone_mobile` for the France these fields: `firstname lastname company vat_number address1 address2 postcode city Country:name phone` bye ### Expected behavior _No response_ ### Steps to reproduce 1. Italy is the default country (but you can use France) 2. choose a second country to do the test (select less fields) like France in my case 3. go to the front-office 4. create an account 5. create a new French address (in my case is not the default country and it has less fields) 6. for now all is ok 7. now look at the error 8. from the user account go to the addresses section 9. select the previous France address 10. now I see all previous data but all Italy fields with dni and state fields not set also for France address 11. if you try to set something for dni and State fields and save, then you return into this address, you get the same problem  ### 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_

Big problem in the Address form - front-office side with Prestashop 8.1.3

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Big problem in the Address form - front-office side with Prestashop 8.1.3 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Hi today I've found this bug in the classic theme (probably it is due from the core code) the address form doesn't show the fields present in its country, it is only partially done the problem is present for address already done, for nations that are not the default ones, it shows the default country fields, instead of showing only those selected for the chosen country I've done this video https://watch.screencastify.com/v/VgpRhU2QgZ7GwVf4HJon for the default Italy country I use these fields: `firstname lastname company vat_number dni address1 address2 postcode city State:name Country:name phone phone_mobile` for the France these fields: `firstname lastname company vat_number address1 address2 postcode city Country:name phone` bye ### Expected behavior _No response_ ### Steps to reproduce 1. Italy is the default country (but you can use France) 2. choose a second country to do the test (select less fields) like France in my case 3. go to the front-office 4. create an account 5. create a new French address (in my case is not the default country and it has less fields) 6. for now all is ok 7. now look at the error 8. from the user account go to the addresses section 9. select the previous France address 10. now I see all previous data but all Italy fields with dni and state fields not set also for France address 11. if you try to set something for dni and State fields and save, then you return into this address, you get the same problem  ### 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 ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Following a manual update of PrestaShop from version 8.1 to 8.1.3, I am encountering an Autoloader error related to the BulkActionInterface class. The error is as follows: `The autoloader expected class "PrestaShop\PrestaShop\Core\Grid\Action\Bulk\BulkActionInterface" to be defined in file "/home/kmqr1611/public_html/vendor/composer/../../src/Core/Grid/Action/Bulk/BulkActionInterface.php". The file was found but the class was not in it, the class name or namespace probably has a typo. ` This error occurs when navigating through the PrestaShop admin interface. It appears that the Autoloader expects to find the BulkActionInterface class in the specified file but fails to locate it, suggesting a potential issue with the class name or namespace.  [dev-2024-01-09.log](https://github.com/PrestaShop/PrestaShop/files/13877153/dev-2024-01-09.log) ### Expected behavior _No response_ ### Steps to reproduce 1. Manually update PrestaShop from version 8.1 to 8.1.3. 2. Navigate through the PrestaShop admin interface. 3. The error appears when accessing certain sections of the admin interface. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). LEXPROD SAS

Autoloader Error with BulkActionInterface After Manual Update to PrestaShop 8.1.3

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Autoloader Error with BulkActionInterface After Manual Update to PrestaShop 8.1.3 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Following a manual update of PrestaShop from version 8.1 to 8.1.3, I am encountering an Autoloader error related to the BulkActionInterface class. The error is as follows: `The autoloader expected class "PrestaShop\PrestaShop\Core\Grid\Action\Bulk\BulkActionInterface" to be defined in file "/home/kmqr1611/public_html/vendor/composer/../../src/Core/Grid/Action/Bulk/BulkActionInterface.php". The file was found but the class was not in it, the class name or namespace probably has a typo. ` This error occurs when navigating through the PrestaShop admin interface. It appears that the Autoloader expects to find the BulkActionInterface class in the specified file but fails to locate it, suggesting a potential issue with the class name or namespace.  [dev-2024-01-09.log](https://github.com/PrestaShop/PrestaShop/files/13877153/dev-2024-01-09.log) ### Expected behavior _No response_ ### Steps to reproduce 1. Manually update PrestaShop from version 8.1 to 8.1.3. 2. Navigate through the PrestaShop admin interface. 3. The error appears when accessing certain sections of the admin interface. ### PrestaShop version(s) where the bug happened 8.1.3 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). LEXPROD SAS --- 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 Field values for individual shops are overriden by default shop in product admin when saving in All shops environment. This bug has some similarity of https://github.com/PrestaShop/PrestaShop/pull/33151/files ### Expected behavior Keep shop specific values ### Steps to reproduce 1) install PS in multishop mode with total of three shops in the same group 2) Assign different currency and language to each shop 3) Switch off experimental product features 4) Choose "All shops". Create a new product, fill name, description, code and price. Save. 5) Switch the admin to the context of the first (default) shop. Save name, description for the language one. Save 6) Go to the second shop context. Switch language to language two. Fill name and description for language two only. Recalculate and set price. Save. 7) Repeat with third shop and language three. 8) Return to the all shop context, change description and save. 9) Check price for shop two and three. Check language fields for shops two and three and the coresponding languages. I was able to hot fix this for a very unhappy customer: in AdminOrdersController::processUpdate after if (Shop::isFeatureActive() && Shop::getContext() != Shop::CONTEXT_SHOP) by checking if the name is already stored in ps_product_lang for language one and conditionally unsetting some variables. But this is not a real remedy. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

Product fields ar overriden from default shop in multishop environment

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Product fields ar overriden from default shop in multishop environment 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 Field values for individual shops are overriden by default shop in product admin when saving in All shops environment. This bug has some similarity of https://github.com/PrestaShop/PrestaShop/pull/33151/files ### Expected behavior Keep shop specific values ### Steps to reproduce 1) install PS in multishop mode with total of three shops in the same group 2) Assign different currency and language to each shop 3) Switch off experimental product features 4) Choose "All shops". Create a new product, fill name, description, code and price. Save. 5) Switch the admin to the context of the first (default) shop. Save name, description for the language one. Save 6) Go to the second shop context. Switch language to language two. Fill name and description for language two only. Recalculate and set price. Save. 7) Repeat with third shop and language three. 8) Return to the all shop context, change description and save. 9) Check price for shop two and three. Check language fields for shops two and three and the coresponding languages. I was able to hot fix this for a very unhappy customer: in AdminOrdersController::processUpdate after if (Shop::isFeatureActive() && Shop::getContext() != Shop::CONTEXT_SHOP) by checking if the name is already stored in ps_product_lang for language one and conditionally unsetting some variables. But this is not a real remedy. ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_ --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When I want to Import a store contact, I have red notification that they can do it as you can see : [recording(46).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/a2a72059-3dd5-4a3b-b200-7aa2ca367ccb) FYI I use the store contact files template Issue find thank to https://github.com/PrestaShop/PrestaShop/issues/34974 ### Expected behavior I wish I could import some store contact ### Steps to reproduce 1. Go to BO 2. Go to Advenced Parameters > Import 3. Download the "Sample Store Contacts files" (the template for the store Contact import) 4. On "What do you want to Import?" set "Store Contact 5. Select the file that you just download in the "Select a file to import" 6. Click on Next step 7. Clic on Import 8. :tada: Red Alert :tada: ### 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). PS

BO - Import/Export - Can't import Store contact

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : BO - Import/Export - Can't import Store contact 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 Import a store contact, I have red notification that they can do it as you can see : [recording(46).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/a2a72059-3dd5-4a3b-b200-7aa2ca367ccb) FYI I use the store contact files template Issue find thank to https://github.com/PrestaShop/PrestaShop/issues/34974 ### Expected behavior I wish I could import some store contact ### Steps to reproduce 1. Go to BO 2. Go to Advenced Parameters > Import 3. Download the "Sample Store Contacts files" (the template for the store Contact import) 4. On "What do you want to Import?" set "Store Contact 5. Select the file that you just download in the "Select a file to import" 6. Click on Next step 7. Clic on Import 8. :tada: Red Alert :tada: ### 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). PS --- end body --- comments : --- start comments --- --- end comments ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments When deleted images in "/img/tmp/cms" FileManager should recreate them on the go, but in some case, it doesnt. ### Expected behavior _No response_ ### Steps to reproduce if you configure php to specify "memory_limit" with another suffix than "M", FileManager doesnt calculate properly memory usage. [In the file ](https://github.com/PrestaShop/PrestaShop/blob/develop/admin-dev/filemanager/include/utils.php#L303) Some admins may configure this value in php settings with a "G" or "k" or nothing, thumbnail regeneration will fail ### PrestaShop version(s) where the bug happened 1.7.7+ (at least) ### 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). Graal Network

FileManager not working properly to regen thumbnails

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : FileManager not working properly to regen thumbnails 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 deleted images in "/img/tmp/cms" FileManager should recreate them on the go, but in some case, it doesnt. ### Expected behavior _No response_ ### Steps to reproduce if you configure php to specify "memory_limit" with another suffix than "M", FileManager doesnt calculate properly memory usage. [In the file ](https://github.com/PrestaShop/PrestaShop/blob/develop/admin-dev/filemanager/include/utils.php#L303) Some admins may configure this value in php settings with a "G" or "k" or nothing, thumbnail regeneration will fail ### PrestaShop version(s) where the bug happened 1.7.7+ (at least) ### 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). Graal Network --- 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 need to click twice to order to enable the option : https://github.com/PrestaShop/PrestaShop/assets/16019289/a1fd8a87-1c24-41f0-93ab-16ab9041fbe1 This problem occurs only when I configure the module on the second try. ### Expected behavior I should be able to click the switch button just once to enable the option. ### Steps to reproduce 1. Go to BO > Modules > Email subscription > Configure 2. Enable option 1 or 2 3. See that the switch does not switch in the first try ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_emailsubscription v2.7.1 ### Your company or customer's name goes here (if applicable). _No response_

ps_emailsubscription - Switch buttons need to be clicked twice in order to enable option

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : ps_emailsubscription - Switch buttons need to be clicked twice in order to enable option 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 need to click twice to order to enable the option : https://github.com/PrestaShop/PrestaShop/assets/16019289/a1fd8a87-1c24-41f0-93ab-16ab9041fbe1 This problem occurs only when I configure the module on the second try. ### Expected behavior I should be able to click the switch button just once to enable the option. ### Steps to reproduce 1. Go to BO > Modules > Email subscription > Configure 2. Enable option 1 or 2 3. See that the switch does not switch in the first try ### PrestaShop version(s) where the bug happened 8.1 ### PHP version(s) where the bug happened 8.1 ### If your bug is related to a module, specify its name and its version ps_emailsubscription v2.7.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 Since Prestashop 8.1.1 loading an ObjectModel with a boolean field that is translatable triggers an 'Array to string conversion' error. ### Expected behavior ObjectModel with translatable boolean must load properly. If to be deprecated in a near future it should not break in a minor version. PR #34873 solves the issue ### Steps to reproduce 1. Install the provided module 2. Try to configure the module [castcrash.zip](https://github.com/PrestaShop/PrestaShop/files/13871512/castcrash.zip) ### PrestaShop version(s) where the bug happened 8.1.1+ ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Novius

PS 8.1.1 break BC with ObjectModel having translatable bool fields

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : PS 8.1.1 break BC with ObjectModel having translatable bool fields Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments Since Prestashop 8.1.1 loading an ObjectModel with a boolean field that is translatable triggers an 'Array to string conversion' error. ### Expected behavior ObjectModel with translatable boolean must load properly. If to be deprecated in a near future it should not break in a minor version. PR #34873 solves the issue ### Steps to reproduce 1. Install the provided module 2. Try to configure the module [castcrash.zip](https://github.com/PrestaShop/PrestaShop/files/13871512/castcrash.zip) ### PrestaShop version(s) where the bug happened 8.1.1+ ### PHP version(s) where the bug happened _No response_ ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). Novius --- 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 An error occurs when updating the store version to 8.1 [INTERNAL] /prestashop/override/classes/Hook.php line 249 - Error: Access to undeclared static property: Hook::$_hook_modules_cache_exec #0 /prestashop/override/classes/Hook.php(13): Hook::getAllHookRegistrationsLG() #1 /prestashop/src/Adapter/LegacyHookSubscriber.php(76): Hook::getHookModuleExecList() #2 /prestashop/vendor/symfony/symfony/src/Symfony/Component/Config/Resource/ReflectionClassResource.php(250):  ### Expected behavior _No response_ ### Steps to reproduce I cleared and disabled the cache ### 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 Upgrade 1.7 to 8.X - Error: Access to undeclared static property: Hook::$_hook_modules_cache_exec

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop Upgrade 1.7 to 8.X - Error: Access to undeclared static property: Hook::$_hook_modules_cache_exec 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 An error occurs when updating the store version to 8.1 [INTERNAL] /prestashop/override/classes/Hook.php line 249 - Error: Access to undeclared static property: Hook::$_hook_modules_cache_exec #0 /prestashop/override/classes/Hook.php(13): Hook::getAllHookRegistrationsLG() #1 /prestashop/src/Adapter/LegacyHookSubscriber.php(76): Hook::getHookModuleExecList() #2 /prestashop/vendor/symfony/symfony/src/Symfony/Component/Config/Resource/ReflectionClassResource.php(250):  ### Expected behavior _No response_ ### Steps to reproduce I cleared and disabled the cache ### 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 ---

### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://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 Prestashop from 1.7 to 8.x, an error occurs. I noticed that this is a global problem, does anyone already have a solution? When updating Prestashop to version 8.x, the following errors were displayed -> [INTERNAL] /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php line 54 - Symfony\Component\DependencyInjection\Exception\RuntimeException: You have requested a non-existent parameter "api_private_key". #0 /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(83): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue() #1 /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php(32): ### Expected behavior Hassle-free, automatic prestashop version update ### Steps to reproduce I see discussions no. #33041, no solution to the problem. There is no solution in Google. ### PrestaShop version(s) where the bug happened 1.7.8.7 ### PHP version(s) where the bug happened v7.4.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_

Prestashop Upgrade 1.7 to 8.X - api_private_key

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : Prestashop Upgrade 1.7 to 8.X - api_private_key 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 Prestashop from 1.7 to 8.x, an error occurs. I noticed that this is a global problem, does anyone already have a solution? When updating Prestashop to version 8.x, the following errors were displayed -> [INTERNAL] /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php line 54 - Symfony\Component\DependencyInjection\Exception\RuntimeException: You have requested a non-existent parameter "api_private_key". #0 /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(83): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue() #1 /var/www/prestashop/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php(32): ### Expected behavior Hassle-free, automatic prestashop version update ### Steps to reproduce I see discussions no. #33041, no solution to the problem. There is no solution in Google. ### PrestaShop version(s) where the bug happened 1.7.8.7 ### PHP version(s) where the bug happened v7.4.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 After upgrading from version 1.7.2.4 to 1.7.8.11 (files and database) my admin panel works fine, but the front end returns error 500, when I turn on debug mode I see this error. Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\RuntimeException: You have requested a non-existent parameter "database_prefix". in /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php:37 Stack trace: #0 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(60): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue(Object(Symfony\Component\DependencyInjection\Definition), true) #1 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php(30): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue(Array, true) #2 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/s in /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php on line 37  ### Expected behavior The front of the site is supposed to work ### Steps to reproduce I just manually updated Prestashop from 1.7.2.4 to 1.7.8.11 ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _No response_ ### Your company or customer's name goes here (if applicable). _No response_

You have requested a non-existent parameter "database_prefix" after update from 1.7.2.4 to 1.7.8.11

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : You have requested a non-existent parameter "database_prefix" after update from 1.7.2.4 to 1.7.8.11 Issue date: --- start body --- ### Prerequisites - [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md). - [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug. ### Describe the bug and add attachments After upgrading from version 1.7.2.4 to 1.7.8.11 (files and database) my admin panel works fine, but the front end returns error 500, when I turn on debug mode I see this error. Fatal error: Uncaught Symfony\Component\DependencyInjection\Exception\RuntimeException: You have requested a non-existent parameter "database_prefix". in /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php:37 Stack trace: #0 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/AbstractRecursivePass.php(60): Symfony\Component\DependencyInjection\Compiler\DefinitionErrorExceptionPass->processValue(Object(Symfony\Component\DependencyInjection\Definition), true) #1 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php(30): Symfony\Component\DependencyInjection\Compiler\AbstractRecursivePass->processValue(Array, true) #2 /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/s in /home/sdf/domains/algichamot.strondlafirm.hekko24.pl/public_html/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/DefinitionErrorExceptionPass.php on line 37  ### Expected behavior The front of the site is supposed to work ### Steps to reproduce I just manually updated Prestashop from 1.7.2.4 to 1.7.8.11 ### PrestaShop version(s) where the bug happened 1.7.8.11 ### PHP version(s) where the bug happened 7.4 ### If your bug is related to a module, specify its name and its version _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 the admin background login is successful, and has entered the AdminDashboard page, re-refreshing will exit directly to the login page, request prompt 403    ### Expected behavior After logging in to the administrator, I should not refresh again and exit. I hope I can use the system normally ### Steps to reproduce 1. Install nginx 1.24 2, Install php 7.4 (php8.0) 3. Install mysql 8 4. Install prestashop 8.1.3 5. Log in to prestashop admin and go to AdminDashboard 6. Exit to the login page after refreshing ### 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_

token expiration too fast

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

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

This is a GitHub Issue repo:PrestaShop owner:PrestaShop Title : token expiration too fast 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 the admin background login is successful, and has entered the AdminDashboard page, re-refreshing will exit directly to the login page, request prompt 403    ### Expected behavior After logging in to the administrator, I should not refresh again and exit. I hope I can use the system normally ### Steps to reproduce 1. Install nginx 1.24 2, Install php 7.4 (php8.0) 3. Install mysql 8 4. Install prestashop 8.1.3 5. Log in to prestashop admin and go to AdminDashboard 6. Exit to the login page after refreshing ### 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 ---