issue_owner_repo
sequencelengths 2
2
| issue_body
stringlengths 0
261k
⌀ | issue_title
stringlengths 1
953
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
726
| issue_created_at
unknown | issue_updated_at
unknown | issue_html_url
stringlengths 37
62
| issue_github_id
int64 285M
2.37B
| issue_number
int64 1
168k
| msg
stringlengths 159
261k
| n_tokens
int64 159
261k
| __index_level_0__
int64 38
208k
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 using product customizations with an additional cost, two issues arise. The additional cost for basic customizations in Prestashop cannot be managed directly, but they can be handled through a custom module by utilizing the id_module and price fields in the customized_data table, which Prestashop automatically uses to calculate the product cost.
Issue 1:
When purchasing a customized item with an extra charge, the "Total products" column on the order confirmation page is incorrect.
Attached are screenshot **01 - Order create.png** and video **01 - Order create.webm**.
Issue 2:
When purchasing the same customized item with two different customizations and two different costs, if I modify the cost of one of the two items in the order, the system updates the cost of both products.
Attached are screenshots **02 - Order edit - 01.png** and **02 - Order edit - 02.png** and video **02 - Order edit.webm**.
Attached is a module that adds 2 customizations to any item added to the cart. Adding the same item twice (with two separate cart additions), the system adds 2 different customizations with 2 different costs.
The module is just an example and with quickly developed code.
**01 - Order create.png**
![01 - Order create](https://github.com/PrestaShop/PrestaShop/assets/2463965/cf4007d1-da5c-4594-a5bb-17e7406dd086)
**01 - Order create.webm**
[01 - Order create.webm](https://github.com/PrestaShop/PrestaShop/assets/2463965/a44ac956-c171-429b-b49e-afdbd7dfd6e1)
**02 - Order edit - 01.png**
![02 - Order edit - 01](https://github.com/PrestaShop/PrestaShop/assets/2463965/bed55618-5d58-4396-9771-8c962759bf97)
**02 - Order edit - 02.png**
![02 - Order edit - 02](https://github.com/PrestaShop/PrestaShop/assets/2463965/065994ab-2d9f-4db7-805f-15f90c3b1091)
**02 - Order edit.webm**
[02 - Order edit.webm](https://github.com/PrestaShop/PrestaShop/assets/2463965/55280fda-5fa3-49d9-8e7e-9f9e008975ef)
**Module**
[cnc_prova_configurazionearticolo.zip](https://github.com/user-attachments/files/15520943/cnc_prova_configurazionearticolo.zip)
### Expected behavior
_No response_
### Steps to reproduce
Issue 1:
1. Access the site and add a product to the cart.
2. Add a customization with an additional cost to the product.
3. Proceed to checkout and complete the order.
4. Observe the "Total products" column on the order confirmation page.
Issue 2:
1. Access the site and add the same product to the cart with two different customizations and different costs.
2. Complete the order.
3. Modify the cost of one of the customizations in the order.
4. Observe that the system updates the cost of both customizations.
### PrestaShop version(s) where the bug happened
8.1.x
### PHP version(s) where the bug happened
all
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Codencode | Problems with Product Customizations | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36286/comments | 2 | "2024-06-01T06:23:06" | "2024-06-11T09:17:38" | https://github.com/PrestaShop/PrestaShop/issues/36286 | 2,328,950,769 | 36,286 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Problems with Product Customizations
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 using product customizations with an additional cost, two issues arise. The additional cost for basic customizations in Prestashop cannot be managed directly, but they can be handled through a custom module by utilizing the id_module and price fields in the customized_data table, which Prestashop automatically uses to calculate the product cost.
Issue 1:
When purchasing a customized item with an extra charge, the "Total products" column on the order confirmation page is incorrect.
Attached are screenshot **01 - Order create.png** and video **01 - Order create.webm**.
Issue 2:
When purchasing the same customized item with two different customizations and two different costs, if I modify the cost of one of the two items in the order, the system updates the cost of both products.
Attached are screenshots **02 - Order edit - 01.png** and **02 - Order edit - 02.png** and video **02 - Order edit.webm**.
Attached is a module that adds 2 customizations to any item added to the cart. Adding the same item twice (with two separate cart additions), the system adds 2 different customizations with 2 different costs.
The module is just an example and with quickly developed code.
**01 - Order create.png**
![01 - Order create](https://github.com/PrestaShop/PrestaShop/assets/2463965/cf4007d1-da5c-4594-a5bb-17e7406dd086)
**01 - Order create.webm**
[01 - Order create.webm](https://github.com/PrestaShop/PrestaShop/assets/2463965/a44ac956-c171-429b-b49e-afdbd7dfd6e1)
**02 - Order edit - 01.png**
![02 - Order edit - 01](https://github.com/PrestaShop/PrestaShop/assets/2463965/bed55618-5d58-4396-9771-8c962759bf97)
**02 - Order edit - 02.png**
![02 - Order edit - 02](https://github.com/PrestaShop/PrestaShop/assets/2463965/065994ab-2d9f-4db7-805f-15f90c3b1091)
**02 - Order edit.webm**
[02 - Order edit.webm](https://github.com/PrestaShop/PrestaShop/assets/2463965/55280fda-5fa3-49d9-8e7e-9f9e008975ef)
**Module**
[cnc_prova_configurazionearticolo.zip](https://github.com/user-attachments/files/15520943/cnc_prova_configurazionearticolo.zip)
### Expected behavior
_No response_
### Steps to reproduce
Issue 1:
1. Access the site and add a product to the cart.
2. Add a customization with an additional cost to the product.
3. Proceed to checkout and complete the order.
4. Observe the "Total products" column on the order confirmation page.
Issue 2:
1. Access the site and add the same product to the cart with two different customizations and different costs.
2. Complete the order.
3. Modify the cost of one of the customizations in the order.
4. Observe that the system updates the cost of both customizations.
### PrestaShop version(s) where the bug happened
8.1.x
### PHP version(s) where the bug happened
all
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Codencode
--- end body ---
comments :
--- start comments ---
--- end comments --- | 3,555 | 38 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 randomly get errors when deleting cache.
It's a bit strange when the code checks for file existence just before deleting it. Maybe it can be resolved by `@unlink`?
![Snímek obrazovky 2024-05-31 173150](https://github.com/PrestaShop/PrestaShop/assets/6097524/01a0bd79-9c8c-4a11-b3c0-5bc4276c6950)
Ping @PrestaShop/tech-council
### Expected behavior
Cache should be deleted reliably.
### Steps to reproduce
-
### PrestaShop version(s) where the bug happened
develop
### 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_ | Warning when clearing cache on windows | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36282/comments | 0 | "2024-05-31T15:35:09" | "2024-06-10T07:59:15" | https://github.com/PrestaShop/PrestaShop/issues/36282 | 2,328,105,857 | 36,282 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Warning when clearing cache 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
I randomly get errors when deleting cache.
It's a bit strange when the code checks for file existence just before deleting it. Maybe it can be resolved by `@unlink`?
![Snímek obrazovky 2024-05-31 173150](https://github.com/PrestaShop/PrestaShop/assets/6097524/01a0bd79-9c8c-4a11-b3c0-5bc4276c6950)
Ping @PrestaShop/tech-council
### Expected behavior
Cache should be deleted reliably.
### Steps to reproduce
-
### PrestaShop version(s) where the bug happened
develop
### 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 --- | 1,271 | 39 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 suggesting to change the current regex at this line: https://github.com/PrestaShop/PrestaShop/blob/52f6c739ce92b3c17670b7f5d1f638020796cbbd/classes/AddressFormat.php#L500
from this:
`#id|id_\w#`
to this:
`#^id$|^id_.*$|^.*_id$#`
### Expected behavior
Explanation and context:
this method is currently used only in AdminContriesController.php: https://github.com/PrestaShop/PrestaShop/blob/52f6c739ce92b3c17670b7f5d1f638020796cbbd/controllers/admin/AdminCountriesController.php#L518
and its purpose, is to get all of the public properties of the Address class, and to filter out all of the properties which are not directly linked to the Address class
So by leveraging the method in AdminCountriesController.php, we have this section of the Backoffice where we can setup the Address format with the fields we want to show, great!
![image](https://github.com/PrestaShop/PrestaShop/assets/79152536/1aef2a76-051d-4230-9dc2-5e4a705bc60b)
Now the trouble comes whenever a module overrides the Address class and adds some additional public properties: in this case, you'll see the new properties will be added into the address format setup in Backoffice, however, whenever a new property starts with 'id', the method filters out the property even if it's a direct field which needs to be shown.
In my case, my module was adding a new property called "identification_code", which indeed needs to be included in the list and not filtered out.
By changing the regex, the problem would be solved.
### Steps to reproduce
1. Create a module which overrides the standard Address class
2. add some custom public properties which need to be showed into the Country settings Backoffice page ( Zones > Country > edit a country and setup the address format, see tab "Address" ).
3. see the custom public properties which starts with "id" are filtered out by prestashop, and thus cannot be setup anyhow in this section.
### PrestaShop version(s) where the bug happened
8.1.6
### 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 | Improve AddressFormat's getValidateFields method used to filter out id fields | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36281/comments | 1 | "2024-05-31T15:23:55" | "2024-06-10T07:57:24" | https://github.com/PrestaShop/PrestaShop/issues/36281 | 2,328,086,408 | 36,281 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Improve AddressFormat's getValidateFields method used to filter out id 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
I'm suggesting to change the current regex at this line: https://github.com/PrestaShop/PrestaShop/blob/52f6c739ce92b3c17670b7f5d1f638020796cbbd/classes/AddressFormat.php#L500
from this:
`#id|id_\w#`
to this:
`#^id$|^id_.*$|^.*_id$#`
### Expected behavior
Explanation and context:
this method is currently used only in AdminContriesController.php: https://github.com/PrestaShop/PrestaShop/blob/52f6c739ce92b3c17670b7f5d1f638020796cbbd/controllers/admin/AdminCountriesController.php#L518
and its purpose, is to get all of the public properties of the Address class, and to filter out all of the properties which are not directly linked to the Address class
So by leveraging the method in AdminCountriesController.php, we have this section of the Backoffice where we can setup the Address format with the fields we want to show, great!
![image](https://github.com/PrestaShop/PrestaShop/assets/79152536/1aef2a76-051d-4230-9dc2-5e4a705bc60b)
Now the trouble comes whenever a module overrides the Address class and adds some additional public properties: in this case, you'll see the new properties will be added into the address format setup in Backoffice, however, whenever a new property starts with 'id', the method filters out the property even if it's a direct field which needs to be shown.
In my case, my module was adding a new property called "identification_code", which indeed needs to be included in the list and not filtered out.
By changing the regex, the problem would be solved.
### Steps to reproduce
1. Create a module which overrides the standard Address class
2. add some custom public properties which need to be showed into the Country settings Backoffice page ( Zones > Country > edit a country and setup the address format, see tab "Address" ).
3. see the custom public properties which starts with "id" are filtered out by prestashop, and thus cannot be setup anyhow in this section.
### PrestaShop version(s) where the bug happened
8.1.6
### 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 --- | 2,843 | 40 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
While performing an update via 1-Click Upgrade, I'm getting an error at the end related to ps_psgdpr
----------------------------------------------------------------------------------------------------
Updating database schema...
Executing: ALTER TABLE ps_translation CHANGE `key` `key` TEXT NOT NULL COLLATE `utf8_bin`
Executing: ALTER TABLE ps_authorized_application CHANGE name name VARCHAR(50) NOT NULL
Executing: ALTER TABLE ps_feature_flag CHANGE state state TINYINT(1) DEFAULT '0', CHANGE description_wording description_wording VARCHAR(512) DEFAULT '' NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent_lang MODIFY id_gdpr_consent INT UNSIGNED NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent_lang DROP PRIMARY KEY
Executing: ALTER TABLE ps_psgdpr_consent_lang CHANGE id_gdpr_consent id_gdpr_consent INT NOT NULL, CHANGE id_lang id_lang INT NOT NULL, CHANGE id_shop id_shop INT NOT NULL, CHANGE message message VARCHAR(255) NOT NULL
Executing: CREATE INDEX IDX_9C2246C9BEB78BEF ON ps_psgdpr_consent_lang (id_gdpr_consent)
Executing: CREATE INDEX IDX_9C2246C9BA299860 ON ps_psgdpr_consent_lang (id_lang)
Executing: ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang)
Executing: DROP INDEX id_customer ON ps_psgdpr_log
Executing: DROP INDEX idx_id_customer ON ps_psgdpr_log
Executing: ALTER TABLE ps_psgdpr_log CHANGE id_gdpr_log id_gdpr_log INT AUTO_INCREMENT NOT NULL, CHANGE id_customer id_customer INT NOT NULL, CHANGE id_guest id_guest INT NOT NULL, CHANGE client_name client_name VARCHAR(255) NOT NULL, CHANGE id_module id_module INT NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent MODIFY id_gdpr_consent INT UNSIGNED NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent DROP PRIMARY KEY
Executing: ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL
15:01:56 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL':
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL':\n \n SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key """]
In AbstractMySQLDriver.php line 128:
An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE
id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_mod
ule id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANG
E error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCH
AR(255) NOT NULL':
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
In Exception.php line 18:
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
In PDOConnection.php line 141:
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--]
### Expected behavior
To successfully upgrade the ps from 8.1.0 to 8.1.6
### Steps to reproduce
Install 8.1.0 version
Make sure you have the ps_psgdpr module activated.
Perform an update through 1-Click Upgrade from 8.1.0 to 8.1.6
### PrestaShop version(s) where the bug happened
8.1.0
### PHP version(s) where the bug happened
7.4
### If your bug is related to a module, specify its name and its version
ps_psgdpr
### Your company or customer's name goes here (if applicable).
_No response_ | Upgrade from 8.1.0 to 8.1.6 causing error via 1-Click Upgrade | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36280/comments | 9 | "2024-05-31T12:04:42" | "2024-06-12T15:46:48" | https://github.com/PrestaShop/PrestaShop/issues/36280 | 2,327,690,242 | 36,280 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Upgrade from 8.1.0 to 8.1.6 causing error via 1-Click Upgrade
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
While performing an update via 1-Click Upgrade, I'm getting an error at the end related to ps_psgdpr
----------------------------------------------------------------------------------------------------
Updating database schema...
Executing: ALTER TABLE ps_translation CHANGE `key` `key` TEXT NOT NULL COLLATE `utf8_bin`
Executing: ALTER TABLE ps_authorized_application CHANGE name name VARCHAR(50) NOT NULL
Executing: ALTER TABLE ps_feature_flag CHANGE state state TINYINT(1) DEFAULT '0', CHANGE description_wording description_wording VARCHAR(512) DEFAULT '' NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent_lang MODIFY id_gdpr_consent INT UNSIGNED NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent_lang DROP PRIMARY KEY
Executing: ALTER TABLE ps_psgdpr_consent_lang CHANGE id_gdpr_consent id_gdpr_consent INT NOT NULL, CHANGE id_lang id_lang INT NOT NULL, CHANGE id_shop id_shop INT NOT NULL, CHANGE message message VARCHAR(255) NOT NULL
Executing: CREATE INDEX IDX_9C2246C9BEB78BEF ON ps_psgdpr_consent_lang (id_gdpr_consent)
Executing: CREATE INDEX IDX_9C2246C9BA299860 ON ps_psgdpr_consent_lang (id_lang)
Executing: ALTER TABLE ps_psgdpr_consent_lang ADD PRIMARY KEY (id_gdpr_consent, id_lang)
Executing: DROP INDEX id_customer ON ps_psgdpr_log
Executing: DROP INDEX idx_id_customer ON ps_psgdpr_log
Executing: ALTER TABLE ps_psgdpr_log CHANGE id_gdpr_log id_gdpr_log INT AUTO_INCREMENT NOT NULL, CHANGE id_customer id_customer INT NOT NULL, CHANGE id_guest id_guest INT NOT NULL, CHANGE client_name client_name VARCHAR(255) NOT NULL, CHANGE id_module id_module INT NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent MODIFY id_gdpr_consent INT UNSIGNED NOT NULL
Executing: ALTER TABLE ps_psgdpr_consent DROP PRIMARY KEY
Executing: ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL
15:01:56 CRITICAL [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL':
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_module id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANGE error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCHAR(255) NOT NULL':\n \n SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key """]
In AbstractMySQLDriver.php line 128:
An exception occurred while executing 'ALTER TABLE ps_psgdpr_consent CHANGE
id_gdpr_consent id_gdpr_consent INT AUTO_INCREMENT NOT NULL, CHANGE id_mod
ule id_module INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL, CHANG
E error error TINYINT(1) NOT NULL, CHANGE error_message error_message VARCH
AR(255) NOT NULL':
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
In Exception.php line 18:
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
In PDOConnection.php line 141:
SQLSTATE[42000]: Syntax error or access violation: 1075 Incorrect table def
inition; there can be only one auto column and it must be defined as a key
prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--]
### Expected behavior
To successfully upgrade the ps from 8.1.0 to 8.1.6
### Steps to reproduce
Install 8.1.0 version
Make sure you have the ps_psgdpr module activated.
Perform an update through 1-Click Upgrade from 8.1.0 to 8.1.6
### PrestaShop version(s) where the bug happened
8.1.0
### PHP version(s) where the bug happened
7.4
### If your bug is related to a module, specify its name and its version
ps_psgdpr
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 5,481 | 41 |
[
"PrestaShop",
"PrestaShop"
] | null | Kanbot deployment ! Feature wording | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36278/comments | 0 | "2024-05-31T07:47:50" | "2024-05-31T07:48:05" | https://github.com/PrestaShop/PrestaShop/issues/36278 | 2,327,177,710 | 36,278 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Kanbot deployment ! Feature wording
Issue date:
--- start body ---
None
--- end body ---
comments :
--- start comments ---
--- end comments --- | 210 | 42 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
If you are in maintenance mode, but you have access to the backoffice, you can place an order (with external validation) and you will be charged, but PrestaShop will not register it.
This is because (at least with Redsys in Spain) the POS itself calls a URL (to validate the cart) `https://bmw-motorrad.burgocar.es/index.php?fc=module&module=redsyspur&controller=validation` that does not execute the `postProcess()` method of the `validation.php` file, which extends `ModuleFrontController`. Redsys takes it for good, they charge you, but PrestaShop has not been able to make its checks, and, therefore, the order does not exist or anything.
The order of execution is like this:
1. The previous URL is called.
2. It ends up getting to Controller.php, method run()
3. That method calls `init()`, but as the `RedsyspurValidationModuleFrontController` class extends `ModuleFrontController` which in turn extends `FrontController`, first the `init()` of `FrontController` is executed, which on line 474 checks that I am in maintenance. As I am, it shows me the maintenance page, the `init()` call of `Controller.php`, is not executed and, therefore, the rest of the `run()` code is not executed either (which is who calls `postProcess()` of `RedsyspurValidationModuleFrontController`).
Therefore, I have not been able to validate the POS result and I do not create the order or anything else, but the money in the bank account has disappeared.
### Expected behavior
_No response_
### Steps to reproduce
1. Put in maintenance mode.
2. buy something with a method which does external validation.
3. no validation is executed, so the order is not created.
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.1.23
### If your bug is 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 module charges you, but the order is not created. | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36277/comments | 1 | "2024-05-31T07:16:14" | "2024-06-10T08:12:49" | https://github.com/PrestaShop/PrestaShop/issues/36277 | 2,327,126,940 | 36,277 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Payment module charges you, but the order is not 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
If you are in maintenance mode, but you have access to the backoffice, you can place an order (with external validation) and you will be charged, but PrestaShop will not register it.
This is because (at least with Redsys in Spain) the POS itself calls a URL (to validate the cart) `https://bmw-motorrad.burgocar.es/index.php?fc=module&module=redsyspur&controller=validation` that does not execute the `postProcess()` method of the `validation.php` file, which extends `ModuleFrontController`. Redsys takes it for good, they charge you, but PrestaShop has not been able to make its checks, and, therefore, the order does not exist or anything.
The order of execution is like this:
1. The previous URL is called.
2. It ends up getting to Controller.php, method run()
3. That method calls `init()`, but as the `RedsyspurValidationModuleFrontController` class extends `ModuleFrontController` which in turn extends `FrontController`, first the `init()` of `FrontController` is executed, which on line 474 checks that I am in maintenance. As I am, it shows me the maintenance page, the `init()` call of `Controller.php`, is not executed and, therefore, the rest of the `run()` code is not executed either (which is who calls `postProcess()` of `RedsyspurValidationModuleFrontController`).
Therefore, I have not been able to validate the POS result and I do not create the order or anything else, but the money in the bank account has disappeared.
### Expected behavior
_No response_
### Steps to reproduce
1. Put in maintenance mode.
2. buy something with a method which does external validation.
3. no validation is executed, so the order is not created.
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.1.23
### If your bug is 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 --- | 2,568 | 43 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Unknown error alla linea 114 nel file /home/customer/www/***********
<img width="524" alt="Screenshot 2024-05-29 alle 22 22 01" src="https://github.com/PrestaShop/PrestaShop/assets/160724004/73ecb116-fcb0-4403-a249-0474f5a5dfd8">
.it/public_html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_compile_private_modifier.php
[16384] Using php-function "array_merge" as a modifier is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier.
### Expected behavior
_No response_
### Steps to reproduce
No particular action
Unfortunately, after installing version 8.1.5, many errors continue to follow one another
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.0.30
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Unknown error alla linea 114 nel file /home/customer/www........ | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36273/comments | 7 | "2024-05-29T20:41:11" | "2024-06-22T19:37:32" | https://github.com/PrestaShop/PrestaShop/issues/36273 | 2,324,212,718 | 36,273 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Unknown error alla linea 114 nel file /home/customer/www........
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Unknown error alla linea 114 nel file /home/customer/www/***********
<img width="524" alt="Screenshot 2024-05-29 alle 22 22 01" src="https://github.com/PrestaShop/PrestaShop/assets/160724004/73ecb116-fcb0-4403-a249-0474f5a5dfd8">
.it/public_html/vendor/smarty/smarty/libs/sysplugins/smarty_internal_compile_private_modifier.php
[16384] Using php-function "array_merge" as a modifier is deprecated and will be removed in a future release. Use Smarty::registerPlugin to explicitly register a custom modifier.
### Expected behavior
_No response_
### Steps to reproduce
No particular action
Unfortunately, after installing version 8.1.5, many errors continue to follow one another
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.0.30
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,561 | 44 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 using the Faceted Search module in PrestaShop, I encountered unexpected behavior when selecting filters. Specifically, when selecting both the "Screen Size: 16 inch" and "Screen Size: 17 inch" filters, followed by selecting the "Graphics Card: RTX4050", which is only available in 17-inch (17.3) laptops, the "Screen Size: 16 inch" filter is automatically cleared. This behavior is not desired as I expect both screen size filters to remain active even after selecting the graphics card filter.
url: https://mkshop.nl/12-laptops
### Expected behavior
After selecting the 'Graphics Card: RTX4050' filter, I expect both the 'Screen Size: 16 inch' and 'Screen Size: 17 inch' filters to remain active, displaying all products with 16-inch and 17-inch screens, in addition to the selected product with the graphics card.
### Steps to reproduce
1. Navigate to the product page with laptops in the "Laptops" category.
2. Select the "Screen Size: 16 inch" filter and "Screen Size: 17 inch" filter.
3. Then, select the "Graphics Card: RTX4050".
4. Observe that the "Screen Size: 16 inch" filter is automatically cleared.
### PrestaShop version(s) where the bug happened
8.1.1
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
faceted search v3.15.1
### Your company or customer's name goes here (if applicable).
_No response_ | Filter cleared unexpectedly when adding incompatible criteria | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36267/comments | 3 | "2024-05-29T09:20:15" | "2024-06-14T14:38:19" | https://github.com/PrestaShop/PrestaShop/issues/36267 | 2,322,811,080 | 36,267 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Filter cleared unexpectedly when adding incompatible criteria
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
When using the Faceted Search module in PrestaShop, I encountered unexpected behavior when selecting filters. Specifically, when selecting both the "Screen Size: 16 inch" and "Screen Size: 17 inch" filters, followed by selecting the "Graphics Card: RTX4050", which is only available in 17-inch (17.3) laptops, the "Screen Size: 16 inch" filter is automatically cleared. This behavior is not desired as I expect both screen size filters to remain active even after selecting the graphics card filter.
url: https://mkshop.nl/12-laptops
### Expected behavior
After selecting the 'Graphics Card: RTX4050' filter, I expect both the 'Screen Size: 16 inch' and 'Screen Size: 17 inch' filters to remain active, displaying all products with 16-inch and 17-inch screens, in addition to the selected product with the graphics card.
### Steps to reproduce
1. Navigate to the product page with laptops in the "Laptops" category.
2. Select the "Screen Size: 16 inch" filter and "Screen Size: 17 inch" filter.
3. Then, select the "Graphics Card: RTX4050".
4. Observe that the "Screen Size: 16 inch" filter is automatically cleared.
### PrestaShop version(s) where the bug happened
8.1.1
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
faceted search v3.15.1
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 2,012 | 45 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 user clicks on the "Forgot your password?" link. is redirected to a page where the email address linked to the account is requested in order to receive the link to change the password.
However, the link they receive, if clicked, takes you back to the page where you are asked to enter your email, instead of opening the page for changing your password.
If the link displayed in the email is instead copied and pasted, it correctly takes you back to the password change page.
With the inspect tool I saw that the text of the generated link does not correspond to the actual link indicated in the href.
![1](https://github.com/PrestaShop/PrestaShop/assets/20090246/cb204eb9-0e6f-4064-9c11-32154d8c29e4)
![2](https://github.com/PrestaShop/PrestaShop/assets/20090246/787ab712-d40d-4962-82a7-f3fc409b5eac)
![3](https://github.com/PrestaShop/PrestaShop/assets/20090246/2a2e3ead-6129-44b2-9453-39b39bca68b6)
![4](https://github.com/PrestaShop/PrestaShop/assets/20090246/6d83e954-4cdb-4115-b4b9-c23501cd4d02)
![5-a](https://github.com/PrestaShop/PrestaShop/assets/20090246/ac84d02a-e541-4d98-8e54-31332da12569)
![5-b](https://github.com/PrestaShop/PrestaShop/assets/20090246/2eb8dd2f-b60f-433b-90cd-d6383a90bee7)
![6](https://github.com/PrestaShop/PrestaShop/assets/20090246/e0543e0d-2b31-4c7a-be0d-973d0ce3b253)
### Expected behavior
I plan to access the password change page by clicking on the link received
### Steps to reproduce
1. Click "Forgot your password?" on login page
2. Enter your registered email and click the button to receive the password reset link
3. Click on the link you received via email
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
7.3
### If your bug is related to a module, specify its name and its version
E-mail module and/or Customer "Sign in" module
### Your company or customer's name goes here (if applicable).
_No response_ | Password Reset Link Redirects to Email Request Page Instead of Password Change Page When Clicked | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36265/comments | 3 | "2024-05-29T09:03:24" | "2024-06-14T09:29:04" | https://github.com/PrestaShop/PrestaShop/issues/36265 | 2,322,777,034 | 36,265 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Password Reset Link Redirects to Email Request Page Instead of Password Change Page When Clicked
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 user clicks on the "Forgot your password?" link. is redirected to a page where the email address linked to the account is requested in order to receive the link to change the password.
However, the link they receive, if clicked, takes you back to the page where you are asked to enter your email, instead of opening the page for changing your password.
If the link displayed in the email is instead copied and pasted, it correctly takes you back to the password change page.
With the inspect tool I saw that the text of the generated link does not correspond to the actual link indicated in the href.
![1](https://github.com/PrestaShop/PrestaShop/assets/20090246/cb204eb9-0e6f-4064-9c11-32154d8c29e4)
![2](https://github.com/PrestaShop/PrestaShop/assets/20090246/787ab712-d40d-4962-82a7-f3fc409b5eac)
![3](https://github.com/PrestaShop/PrestaShop/assets/20090246/2a2e3ead-6129-44b2-9453-39b39bca68b6)
![4](https://github.com/PrestaShop/PrestaShop/assets/20090246/6d83e954-4cdb-4115-b4b9-c23501cd4d02)
![5-a](https://github.com/PrestaShop/PrestaShop/assets/20090246/ac84d02a-e541-4d98-8e54-31332da12569)
![5-b](https://github.com/PrestaShop/PrestaShop/assets/20090246/2eb8dd2f-b60f-433b-90cd-d6383a90bee7)
![6](https://github.com/PrestaShop/PrestaShop/assets/20090246/e0543e0d-2b31-4c7a-be0d-973d0ce3b253)
### Expected behavior
I plan to access the password change page by clicking on the link received
### Steps to reproduce
1. Click "Forgot your password?" on login page
2. Enter your registered email and click the button to receive the password reset link
3. Click on the link you received via email
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
7.3
### If your bug is related to a module, specify its name and its version
E-mail module and/or Customer "Sign in" module
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 2,607 | 46 |
[
"PrestaShop",
"PrestaShop"
] | **US**
Optimize the carrier update, avoid generating a new instance on each save, handle duplication ONLY when the carrier is already assigned to an order
Impact on module ??
| Optimize the carrier update, avoid generating a new instance on each save, handle duplication ONLY when the carrier is already assigned to an order | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36263/comments | 1 | "2024-05-28T13:42:43" | "2024-06-20T07:07:34" | https://github.com/PrestaShop/PrestaShop/issues/36263 | 2,321,106,724 | 36,263 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Optimize the carrier update, avoid generating a new instance on each save, handle duplication ONLY when the carrier is already assigned to an order
Issue date:
--- start body ---
**US**
Optimize the carrier update, avoid generating a new instance on each save, handle duplication ONLY when the carrier is already assigned to an order
Impact on module ??
--- end body ---
comments :
--- start comments ---
--- end comments --- | 498 | 47 |
[
"PrestaShop",
"PrestaShop"
] | **US**
As a merchant, I want to config my zones and the shipping costs.
**Specs**
1. Shipping locations
- Add button zones.
The button opens the modal, displays all the zones.
The zones selected are displayed as tag with the zone label.
If user selects all the zones than the tag 'All zones' is displayed
2. Shipping costs
- Free shipping toggle switch behavior
This is toggle switch ([Forms switch story UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--switch-story)) that allows choosing if the carrier is free or not.
- Add handling costs toggle switch behavior
This is toggle switch ([Forms switch story UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--switch-story)) that allows choosing if the handling costs are added to the final price or not.
- Billing radio buttons behavior
There are 2 radio buttons ([Forms radio buttons](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--radio-buttons)) are displayed: "According to total price." and "According to total weight.". When "According to total price" is selected, the ranges are defined by currency. The currency displayed is the default one configured in International > Localization. When "According to total weight" is selected, the ranges are defined by weight. The weight displayed is the one defined in International > Localization.
- Tax dropdown behavior
This is dropdown menu ([Dropdowns basics UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/dropdowns--basics)) that displays all the enabled tax rules existing in International > Taxes > Taxes rules.
- Out-of-range behavior dropdown behavior
This is dropdown menu ([Dropdowns basics UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/dropdowns--basics)) that allows to select one of the 2 options: "Apply the cost of the highest defined range" or "Disable carrier".
If the total weight or total price of the cart is not in one of the defined ranges and if the chosen option is "Disable carrier", then the carrier will be disabled. If the total weight or total price of the cart is not in one of the defined ranges and if the chosen option is "Apply the cost of the highest defined range", then the carrier price will be the one corresponding to the highest range.
When the free shipping is enabled, all the input and button are disabled and greyed.
**Design**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/9270caaa-d2dd-4f15-8788-6c749e139f7d)
| [UI] Shipping costs and location configuration | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36262/comments | 0 | "2024-05-28T13:17:30" | "2024-06-20T07:43:21" | https://github.com/PrestaShop/PrestaShop/issues/36262 | 2,321,047,666 | 36,262 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : [UI] Shipping costs and location configuration
Issue date:
--- start body ---
**US**
As a merchant, I want to config my zones and the shipping costs.
**Specs**
1. Shipping locations
- Add button zones.
The button opens the modal, displays all the zones.
The zones selected are displayed as tag with the zone label.
If user selects all the zones than the tag 'All zones' is displayed
2. Shipping costs
- Free shipping toggle switch behavior
This is toggle switch ([Forms switch story UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--switch-story)) that allows choosing if the carrier is free or not.
- Add handling costs toggle switch behavior
This is toggle switch ([Forms switch story UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--switch-story)) that allows choosing if the handling costs are added to the final price or not.
- Billing radio buttons behavior
There are 2 radio buttons ([Forms radio buttons](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/forms--radio-buttons)) are displayed: "According to total price." and "According to total weight.". When "According to total price" is selected, the ranges are defined by currency. The currency displayed is the default one configured in International > Localization. When "According to total weight" is selected, the ranges are defined by weight. The weight displayed is the one defined in International > Localization.
- Tax dropdown behavior
This is dropdown menu ([Dropdowns basics UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/dropdowns--basics)) that displays all the enabled tax rules existing in International > Taxes > Taxes rules.
- Out-of-range behavior dropdown behavior
This is dropdown menu ([Dropdowns basics UI kit](https://build.prestashop-project.org/prestashop-ui-kit/?path=/story/dropdowns--basics)) that allows to select one of the 2 options: "Apply the cost of the highest defined range" or "Disable carrier".
If the total weight or total price of the cart is not in one of the defined ranges and if the chosen option is "Disable carrier", then the carrier will be disabled. If the total weight or total price of the cart is not in one of the defined ranges and if the chosen option is "Apply the cost of the highest defined range", then the carrier price will be the one corresponding to the highest range.
When the free shipping is enabled, all the input and button are disabled and greyed.
**Design**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/9270caaa-d2dd-4f15-8788-6c749e139f7d)
--- end body ---
comments :
--- start comments ---
--- end comments --- | 2,763 | 48 |
[
"PrestaShop",
"PrestaShop"
] | **US**
I want to set the price depending on the range and the zone.
**Specs**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/a964961b-6774-4e5e-975b-e884e7001d99)
Once the ranges are saved, a list of zones is displayed containing all the ranges with an empty input. Depending on the configuration, either price or weight metrics are displayed, along with the currency or weight metrics.
If the ranges or zones are updated, then the list of range/zone is also updated. The value is kept if the range min and max stay the same even if the range position changed.
Max 4 ranges per row displayed.
Once the form saved the value are persisted.
**Responsive**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/b93f6925-319f-47d2-af5f-bba734f42d4f)
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0 | [UI] Price management from the range and zone Part 2 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36260/comments | 1 | "2024-05-28T13:16:12" | "2024-05-29T13:49:21" | https://github.com/PrestaShop/PrestaShop/issues/36260 | 2,321,044,918 | 36,260 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : [UI] Price management from the range and zone Part 2
Issue date:
--- start body ---
**US**
I want to set the price depending on the range and the zone.
**Specs**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/a964961b-6774-4e5e-975b-e884e7001d99)
Once the ranges are saved, a list of zones is displayed containing all the ranges with an empty input. Depending on the configuration, either price or weight metrics are displayed, along with the currency or weight metrics.
If the ranges or zones are updated, then the list of range/zone is also updated. The value is kept if the range min and max stay the same even if the range position changed.
Max 4 ranges per row displayed.
Once the form saved the value are persisted.
**Responsive**
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/b93f6925-319f-47d2-af5f-bba734f42d4f)
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,124 | 49 |
[
"PrestaShop",
"PrestaShop"
] | **US**
As a merchant, I want to be able to configure my shipping range.
**Specs**
When I select a range, a modal window opens to choose the specific ranges I wish to set.
The modal features:
- A table with 3 columns (Minimum, Maximum, Action (delete), Plus button (revealed upon hovering)
- An option to add a range
Upon selecting "add range" either from the designated button or the plus button within a row, a new row is appended at the bottom of the table. The minimum value for the new row is automatically set to match the maximum value of the preceding row.
Once the users input the maximum value, the minimum value for the next row is automatically populated.
Once users press the delete button, the range is removed.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/5cac2c8f-68f9-42b3-9ded-2b27a78aad6f)
When a minimum is higher than the max, the input is displayed in red.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/48eabd94-b0df-4d32-b02f-b1583daf9328)
If the users save while the inputs are reds then a error message is displayed.
error message: Make sure there are no overlapping ranges. Remember, the minimum is part of the range, but the maximum isn't. So, the upper limit of a range is the lower limit of the next range.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/41308d69-a972-4194-b73b-aa7878018e64)
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0
## Todo
- [ ] POC modal only range creation
- [ ] Add the business rules | [UI] Shipping costs Range part 1 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36259/comments | 0 | "2024-05-28T13:15:09" | "2024-05-29T13:49:04" | https://github.com/PrestaShop/PrestaShop/issues/36259 | 2,321,042,447 | 36,259 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : [UI] Shipping costs Range part 1
Issue date:
--- start body ---
**US**
As a merchant, I want to be able to configure my shipping range.
**Specs**
When I select a range, a modal window opens to choose the specific ranges I wish to set.
The modal features:
- A table with 3 columns (Minimum, Maximum, Action (delete), Plus button (revealed upon hovering)
- An option to add a range
Upon selecting "add range" either from the designated button or the plus button within a row, a new row is appended at the bottom of the table. The minimum value for the new row is automatically set to match the maximum value of the preceding row.
Once the users input the maximum value, the minimum value for the next row is automatically populated.
Once users press the delete button, the range is removed.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/5cac2c8f-68f9-42b3-9ded-2b27a78aad6f)
When a minimum is higher than the max, the input is displayed in red.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/48eabd94-b0df-4d32-b02f-b1583daf9328)
If the users save while the inputs are reds then a error message is displayed.
error message: Make sure there are no overlapping ranges. Remember, the minimum is part of the range, but the maximum isn't. So, the upper limit of a range is the lower limit of the next range.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/41308d69-a972-4194-b73b-aa7878018e64)
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0
## Todo
- [ ] POC modal only range creation
- [ ] Add the business rules
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,786 | 50 |
[
"PrestaShop",
"PrestaShop"
] | **US**
I want to set a max width, height, weight and deph of an order
**Specs**
- Maximum order width (Dimension unit) input behavior
This is input field to enter package width. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order height (Dimension unit) input
This is input field to enter package height. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order depth (Dimension unit) input behavior
This is input field to enter package depth. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order weight (Dimension unit) input behavior
This is input field to enter package weight. The weight dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
**Notes**
Package is renamed Order. and the image will not be replaced.
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0 | [UI] Create & Update command Size, weight, and group access | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36258/comments | 1 | "2024-05-28T13:09:18" | "2024-06-19T12:04:09" | https://github.com/PrestaShop/PrestaShop/issues/36258 | 2,321,029,875 | 36,258 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : [UI] Create & Update command Size, weight, and group access
Issue date:
--- start body ---
**US**
I want to set a max width, height, weight and deph of an order
**Specs**
- Maximum order width (Dimension unit) input behavior
This is input field to enter package width. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order height (Dimension unit) input
This is input field to enter package height. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order depth (Dimension unit) input behavior
This is input field to enter package depth. The dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
- Maximum order weight (Dimension unit) input behavior
This is input field to enter package weight. The weight dimension unit mentioned in parenthesis is the one defined in International > Localization > Localization.
**Notes**
Package is renamed Order. and the image will not be replaced.
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,337 | 51 |
[
"PrestaShop",
"PrestaShop"
] | **US**
As a merchant, I want to be able edit the general setting of my carrier.
**Specs**
- Carrier name input behavior
This is input (Forms normal UI kit) to enter carrier name.
- Transit time input behavior
This is input (Forms normal UI kit) to enter transit time. This input has language dropdown to enter information for customers in different languages.
- Speed grade input behavior
This is input (Forms normal UI kit) to enter speed grade.
- Logo input behavior
This is input (Forms files UI kit) to choose file that will be shown as carrier logo. This input has a file icon on the left input side. On the right input side there is CTA button with a catalog icon with title Choose a file. Once clicked on input or button opens modal with this PC files. When file uploaded it is shown in Logo block in each carrier creation step.
- Tracking URL input
This is input (Forms normal UI kit) to enter tracking URL.
- Group and Shop association checkboxes behavior
The user associate the Group and Shop through the modal. The modal lists all the Groups and Shops
The ID and the name of all existing customers' groups are displayed. A checkbox (Forms checkboxes UI kit) is displayed before each group to select or unselect them.
A global checkbox allows selecting/unselecting all customers' groups in one click. It displays on the form the label 'All'
Once an element is selected and the modal closes, the selected elements are displayed in a tag. A tag can be deleted by pressing the cross next to the tag label.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/29a1a58a-a4a3-4bea-9b6b-51443bc0475a)
By default, the All the shop and All the customer are selected
**Remarks**
- Ideally, the shops should filter the groups and location. If yes then, put the shop association first.
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0 | [UI] Create & Update General Setting | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36257/comments | 2 | "2024-05-28T13:00:52" | "2024-06-04T09:04:34" | https://github.com/PrestaShop/PrestaShop/issues/36257 | 2,321,011,283 | 36,257 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : [UI] Create & Update General Setting
Issue date:
--- start body ---
**US**
As a merchant, I want to be able edit the general setting of my carrier.
**Specs**
- Carrier name input behavior
This is input (Forms normal UI kit) to enter carrier name.
- Transit time input behavior
This is input (Forms normal UI kit) to enter transit time. This input has language dropdown to enter information for customers in different languages.
- Speed grade input behavior
This is input (Forms normal UI kit) to enter speed grade.
- Logo input behavior
This is input (Forms files UI kit) to choose file that will be shown as carrier logo. This input has a file icon on the left input side. On the right input side there is CTA button with a catalog icon with title Choose a file. Once clicked on input or button opens modal with this PC files. When file uploaded it is shown in Logo block in each carrier creation step.
- Tracking URL input
This is input (Forms normal UI kit) to enter tracking URL.
- Group and Shop association checkboxes behavior
The user associate the Group and Shop through the modal. The modal lists all the Groups and Shops
The ID and the name of all existing customers' groups are displayed. A checkbox (Forms checkboxes UI kit) is displayed before each group to select or unselect them.
A global checkbox allows selecting/unselecting all customers' groups in one click. It displays on the form the label 'All'
Once an element is selected and the modal closes, the selected elements are displayed in a tag. A tag can be deleted by pressing the cross next to the tag label.
![Image](https://github.com/PrestaShop/PrestaShop/assets/43613217/29a1a58a-a4a3-4bea-9b6b-51443bc0475a)
By default, the All the shop and All the customer are selected
**Remarks**
- Ideally, the shops should filter the groups and location. If yes then, put the shop association first.
**Design**
https://www.figma.com/design/QlgjdPJHkpTZ8NSgLa4qzr/Carrier-page?node-id=1-1913&t=dxi5Fx4de7sqiuT1-0
--- end body ---
comments :
--- start comments ---
--- end comments --- | 2,127 | 52 |
[
"PrestaShop",
"PrestaShop"
] | When dependabot has no module to update in prestashop, it fails on this error:
`cron_php_update_modules.txt: No such file or directory`
seems like this file is created only when there are modules to update, so it fails when trying to read it while there's no module to update
https://github.com/PrestaShop/PrestaShop/actions/runs/6843635964/job/18606450426 | Dependabot (module) fails when there is nothing to be done | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36254/comments | 0 | "2024-05-28T08:54:26" | "2024-05-28T08:54:52" | https://github.com/PrestaShop/PrestaShop/issues/36254 | 2,320,503,392 | 36,254 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Dependabot (module) fails when there is nothing to be done
Issue date:
--- start body ---
When dependabot has no module to update in prestashop, it fails on this error:
`cron_php_update_modules.txt: No such file or directory`
seems like this file is created only when there are modules to update, so it fails when trying to read it while there's no module to update
https://github.com/PrestaShop/PrestaShop/actions/runs/6843635964/job/18606450426
--- end body ---
comments :
--- start comments ---
--- end comments --- | 588 | 53 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
It doesn't save when I select all the categories.
When I enter the template and select all the categories and then click save it does not save the categories
https://somup.com/cZhujD5mwR
### Expected behavior
It should save all the selected categories
### Steps to reproduce
1. I enter the squad
2. I select all the categories with the available tool
3 save
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
7.4, 8
### If your bug is related to a module, specify its name and its version
facetedsearch v3.15.1
### Your company or customer's name goes here (if applicable).
_No response_ | It doesn't save when I select all categories | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36253/comments | 2 | "2024-05-28T08:18:51" | "2024-05-28T10:22:12" | https://github.com/PrestaShop/PrestaShop/issues/36253 | 2,320,431,382 | 36,253 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : It doesn't save when I select all categories
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
It doesn't save when I select all the categories.
When I enter the template and select all the categories and then click save it does not save the categories
https://somup.com/cZhujD5mwR
### Expected behavior
It should save all the selected categories
### Steps to reproduce
1. I enter the squad
2. I select all the categories with the available tool
3 save
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
7.4, 8
### If your bug is related to a module, specify its name and its version
facetedsearch v3.15.1
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,231 | 54 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Create a file csv, with image urls (my file the location of image is not local, is stored in another domain/server)
Upload file, and run.
The folders have a chmod 775 and if i change all folders to 777 the upload goes
The server log
<img width="476" alt="Captura de ecrã 2024-05-27 222207" src="https://github.com/PrestaShop/PrestaShop/assets/54105234/6651ea16-428b-4d37-a147-3740c49c2540">
### Expected behavior
Import sucess, with images located in server, with file/folder correct location
### Steps to reproduce
1 - Upload csv
2 - Id and URL (outside server location, didn´t test it with local images)
3 - See product list results (image alternate text instead)
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Import via csv - image download in another location - folder permissions issue | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36251/comments | 1 | "2024-05-27T21:27:06" | "2024-05-30T14:49:48" | https://github.com/PrestaShop/PrestaShop/issues/36251 | 2,319,797,227 | 36,251 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Import via csv - image download in another location - folder permissions 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
Create a file csv, with image urls (my file the location of image is not local, is stored in another domain/server)
Upload file, and run.
The folders have a chmod 775 and if i change all folders to 777 the upload goes
The server log
<img width="476" alt="Captura de ecrã 2024-05-27 222207" src="https://github.com/PrestaShop/PrestaShop/assets/54105234/6651ea16-428b-4d37-a147-3740c49c2540">
### Expected behavior
Import sucess, with images located in server, with file/folder correct location
### Steps to reproduce
1 - Upload csv
2 - Id and URL (outside server location, didn´t test it with local images)
3 - See product list results (image alternate text instead)
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,572 | 55 |
[
"PrestaShop",
"PrestaShop"
] | On login page click on `I forgot my password`
Then click on `Cancel` button, nothing happens
This used to work but the IDs must have changed because of some refacto, updating the selector should be good Basing it on a dedicated class should make it more stable as well https://github.com/PrestaShop/PrestaShop/blob/77e912bfde5011c34ffa64475f7ae78980e9cc8d/admin-dev/themes/new-theme/js/pages/login/login-map.ts#L33 | Reset password -> back button not working. | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36249/comments | 1 | "2024-05-27T14:15:20" | "2024-06-04T16:20:18" | https://github.com/PrestaShop/PrestaShop/issues/36249 | 2,319,269,451 | 36,249 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Reset password -> back button not working.
Issue date:
--- start body ---
On login page click on `I forgot my password`
Then click on `Cancel` button, nothing happens
This used to work but the IDs must have changed because of some refacto, updating the selector should be good Basing it on a dedicated class should make it more stable as well https://github.com/PrestaShop/PrestaShop/blob/77e912bfde5011c34ffa64475f7ae78980e9cc8d/admin-dev/themes/new-theme/js/pages/login/login-map.ts#L33
--- end body ---
comments :
--- start comments ---
--- end comments --- | 631 | 56 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Exceptions of type CoreException thrown in this block are not caught.
Dispatcher line 502
```
try {
$controller = Controller::getController($controller_class);
// Execute hook dispatcher
Hook::exec('actionDispatcher', $params_hook_action_dispatcher);
// Running controller
$controller->run();
// Execute hook dispatcher after
Hook::exec('actionDispatcherAfter', $params_hook_action_dispatcher);
} catch (PrestaShopException $e) {
$e->displayMessage();
}
```
For example, the function Hook::coreRenderWidget($module, $hook_name, $params) converts all exceptions to CoreException and they will never be caught.
```
public static function coreRenderWidget($module, $hook_name, $params)
{
$context = Context::getContext();
if (!Module::isEnabled($module->name) || $context->isMobile() && !Module::isEnabledForMobileDevices($module->name)) {
return null;
}
try {
return $module->renderWidget($hook_name, $params);
} catch (Exception $e) {
$environment = ServiceLocator::get('\\PrestaShop\\PrestaShop\\Adapter\\Environment');
if ($environment->isDebug()) {
throw new CoreException($e->getMessage(), $e->getCode(), $e);
}
}
return '';
}
```
@kpodemski
### Expected behavior
Catch exceptions and display the error message
### Steps to reproduce
1. - Throw any exception in a widget
### PrestaShop version(s) where the bug happened
8.1.6
### 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_ | CoreExceptions are not being caught in the dispatcher | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36248/comments | 2 | "2024-05-27T13:57:35" | "2024-05-30T13:51:18" | https://github.com/PrestaShop/PrestaShop/issues/36248 | 2,319,229,405 | 36,248 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : CoreExceptions are not being caught in the dispatcher
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Exceptions of type CoreException thrown in this block are not caught.
Dispatcher line 502
```
try {
$controller = Controller::getController($controller_class);
// Execute hook dispatcher
Hook::exec('actionDispatcher', $params_hook_action_dispatcher);
// Running controller
$controller->run();
// Execute hook dispatcher after
Hook::exec('actionDispatcherAfter', $params_hook_action_dispatcher);
} catch (PrestaShopException $e) {
$e->displayMessage();
}
```
For example, the function Hook::coreRenderWidget($module, $hook_name, $params) converts all exceptions to CoreException and they will never be caught.
```
public static function coreRenderWidget($module, $hook_name, $params)
{
$context = Context::getContext();
if (!Module::isEnabled($module->name) || $context->isMobile() && !Module::isEnabledForMobileDevices($module->name)) {
return null;
}
try {
return $module->renderWidget($hook_name, $params);
} catch (Exception $e) {
$environment = ServiceLocator::get('\\PrestaShop\\PrestaShop\\Adapter\\Environment');
if ($environment->isDebug()) {
throw new CoreException($e->getMessage(), $e->getCode(), $e);
}
}
return '';
}
```
@kpodemski
### Expected behavior
Catch exceptions and display the error message
### Steps to reproduce
1. - Throw any exception in a widget
### PrestaShop version(s) where the bug happened
8.1.6
### 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 --- | 2,458 | 57 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
On backend, in product combination entered minimal quanity for sale: 50. Then, on frontend product page, tried to enter quantity by keyboard: 100 (or any value from 100 to 499), the quantity jumps back to 50.
### Expected behavior
The minimum quantity must not allow to enter quantity that is less than the minimum. In this example, must not allow to enter 0 - 49.
The problem is that it also does not allow to enter values from 100 to 499 BY KEYBOARD. It reverts to 50
### Steps to reproduce
1. Go to back office, create a product with combinations
2. Open combination, set minimal quanity for sale: 50.
3. Go to frontend product page.
4. In the quantity field, enter quantity 100 by keyboard (or any value from 100 to 499).
5. The quantity in the field goes back to 50.
### PrestaShop version(s) where the bug happened
1.7.8.11
### 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_ | When minimal quantity for sale set, then on product page not possible to enter quantity by keyboard | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36245/comments | 3 | "2024-05-27T12:04:49" | "2024-05-30T13:50:04" | https://github.com/PrestaShop/PrestaShop/issues/36245 | 2,318,998,169 | 36,245 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : When minimal quantity for sale set, then on product page not possible to enter quantity by keyboard
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
On backend, in product combination entered minimal quanity for sale: 50. Then, on frontend product page, tried to enter quantity by keyboard: 100 (or any value from 100 to 499), the quantity jumps back to 50.
### Expected behavior
The minimum quantity must not allow to enter quantity that is less than the minimum. In this example, must not allow to enter 0 - 49.
The problem is that it also does not allow to enter values from 100 to 499 BY KEYBOARD. It reverts to 50
### Steps to reproduce
1. Go to back office, create a product with combinations
2. Open combination, set minimal quanity for sale: 50.
3. Go to frontend product page.
4. In the quantity field, enter quantity 100 by keyboard (or any value from 100 to 499).
5. The quantity in the field goes back to 50.
### PrestaShop version(s) where the bug happened
1.7.8.11
### 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 --- | 1,694 | 58 |
[
"PrestaShop",
"PrestaShop"
] | Reimplement PS_COOKIE_CHECKIP functionality removed in https://github.com/PrestaShop/PrestaShop/pull/35983. This feature allows to enable/disable checking IP address of the session. Helps prevent cookie theft. Some people running proxies disabled it, because the IP behind the proxy fluctuated and they were logged out every few minutes. Good would be to check both client IP address and X-Forwarded-For header. | Check IP when connected on BO | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36243/comments | 0 | "2024-05-27T07:51:48" | "2024-06-04T16:19:48" | https://github.com/PrestaShop/PrestaShop/issues/36243 | 2,318,489,921 | 36,243 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Check IP when connected on BO
Issue date:
--- start body ---
Reimplement PS_COOKIE_CHECKIP functionality removed in https://github.com/PrestaShop/PrestaShop/pull/35983. This feature allows to enable/disable checking IP address of the session. Helps prevent cookie theft. Some people running proxies disabled it, because the IP behind the proxy fluctuated and they were logged out every few minutes. Good would be to check both client IP address and X-Forwarded-For header.
--- end body ---
comments :
--- start comments ---
--- end comments --- | 611 | 59 |
[
"PrestaShop",
"PrestaShop"
] | null | Integrate proper icons for facebook, twitter and github in the login page | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36242/comments | 6 | "2024-05-27T07:48:05" | "2024-06-05T15:16:00" | https://github.com/PrestaShop/PrestaShop/issues/36242 | 2,318,481,780 | 36,242 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Integrate proper icons for facebook, twitter and github in the login page
Issue date:
--- start body ---
None
--- end body ---
comments :
--- start comments ---
--- end comments --- | 248 | 60 |
[
"PrestaShop",
"PrestaShop"
] | null | Login page is not responsive. | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36241/comments | 1 | "2024-05-27T07:47:57" | "2024-06-04T15:03:21" | https://github.com/PrestaShop/PrestaShop/issues/36241 | 2,318,481,434 | 36,241 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Login page is not responsive.
Issue date:
--- start body ---
None
--- end body ---
comments :
--- start comments ---
--- end comments --- | 204 | 61 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
1. enable maintenance mode
2. enable debug mode
3. click on oneclick upgrade
4. I wait 50 seconds or more
5. here are the errors I get when upgrading from 8.1.5 to 8.1.6
6. `in [/home/udlah5r1/domains/100asa.it/public_html/classes/db/DbPDO.php ](https://www.100asa.it/Back100asa/index.php?controller=AdminSelfUpgrade&token=82f83b6322f9c89b5db8c3746c92922f)(line 151)
protected function _query($sql) { try { return $this->link->query($sql); } catch (\PDOException $exception) { throw new PrestaShopException($exception->getMessage(), (int) $exception->getCode(), $exception); } } /** * Returns the next row from the result s`
![screenshot-www 100asa it-2024 05 25-09_15_21](https://github.com/PrestaShop/PrestaShop/assets/5500935/69c68e71-e708-4956-8e00-e5244cca0547)
### Expected behavior
_No response_
### Steps to reproduce
1. enable maintenance mode
2. enable debug mode
3. click on oneclick upgrade
4. I wait 50 seconds or more
5. here are the errors I get when upgrading from 8.1.5 to 8.1.6
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.0 , 8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | upgrade from 8.1.5 to 8.1.6 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36235/comments | 4 | "2024-05-25T07:17:35" | "2024-06-14T09:29:12" | https://github.com/PrestaShop/PrestaShop/issues/36235 | 2,316,790,152 | 36,235 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : upgrade from 8.1.5 to 8.1.6
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
1. enable maintenance mode
2. enable debug mode
3. click on oneclick upgrade
4. I wait 50 seconds or more
5. here are the errors I get when upgrading from 8.1.5 to 8.1.6
6. `in [/home/udlah5r1/domains/100asa.it/public_html/classes/db/DbPDO.php ](https://www.100asa.it/Back100asa/index.php?controller=AdminSelfUpgrade&token=82f83b6322f9c89b5db8c3746c92922f)(line 151)
protected function _query($sql) { try { return $this->link->query($sql); } catch (\PDOException $exception) { throw new PrestaShopException($exception->getMessage(), (int) $exception->getCode(), $exception); } } /** * Returns the next row from the result s`
![screenshot-www 100asa it-2024 05 25-09_15_21](https://github.com/PrestaShop/PrestaShop/assets/5500935/69c68e71-e708-4956-8e00-e5244cca0547)
### Expected behavior
_No response_
### Steps to reproduce
1. enable maintenance mode
2. enable debug mode
3. click on oneclick upgrade
4. I wait 50 seconds or more
5. here are the errors I get when upgrading from 8.1.5 to 8.1.6
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.0 , 8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,915 | 62 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 many prestashop from 8.1.5 to 8.1.6 ; same problem
![Capture d’écran 2024-05-25 à 3 03 24 AM](https://github.com/PrestaShop/PrestaShop/assets/30599677/ebd0a42a-5aa9-4352-b2ef-7b5f552db2c8)
### Expected behavior
_No response_
### Steps to reproduce
just upgrade with the module autoupgrad version 5.0.2
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2
### If your bug is related to a module, specify its name and its version
autoupgrade
### Your company or customer's name goes here (if applicable).
_No response_ | Warning message after upgrade presatshop 8.1.6 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36234/comments | 6 | "2024-05-25T02:04:34" | "2024-05-28T09:55:22" | https://github.com/PrestaShop/PrestaShop/issues/36234 | 2,316,577,898 | 36,234 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Warning message after upgrade presatshop 8.1.6
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 many prestashop from 8.1.5 to 8.1.6 ; same problem
![Capture d’écran 2024-05-25 à 3 03 24 AM](https://github.com/PrestaShop/PrestaShop/assets/30599677/ebd0a42a-5aa9-4352-b2ef-7b5f552db2c8)
### Expected behavior
_No response_
### Steps to reproduce
just upgrade with the module autoupgrad version 5.0.2
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2
### If your bug is related to a module, specify its name and its version
autoupgrade
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,181 | 63 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Error in GSC : Type de valeur incorrect
### Expected behavior
No error in structured datas
the last item of the products on the category page must not have a comma
### Steps to reproduce
Test category page with : https://validator.schema.org/
![Capture d'écran 2024-05-24 130117](https://github.com/PrestaShop/PrestaShop/assets/61431435/002eb966-8e83-41b4-9961-4f74464df17a)
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Error schema.org in category pages | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36230/comments | 4 | "2024-05-24T11:02:28" | "2024-05-31T17:21:11" | https://github.com/PrestaShop/PrestaShop/issues/36230 | 2,315,116,367 | 36,230 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Error schema.org in category pages
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Error in GSC : Type de valeur incorrect
### Expected behavior
No error in structured datas
the last item of the products on the category page must not have a comma
### Steps to reproduce
Test category page with : https://validator.schema.org/
![Capture d'écran 2024-05-24 130117](https://github.com/PrestaShop/PrestaShop/assets/61431435/002eb966-8e83-41b4-9961-4f74464df17a)
### PrestaShop version(s) where the bug happened
8.1.6
### 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 --- | 1,228 | 64 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 setting up a discount, there is an option to define a discount based on "selected product(s)".
However, the in-line documentation (i.e. hover over this option) and the "help" button/screen on the right side of the page do not define this behavior.
Perhaps this discount applies to the "Condition > production selection" items. If so, it should specifically say that.
---
# Applicable best practice / mantra
Any error when pricing products can be very bad for a merchant. Therefore software for setting up pricing should be reliable and unambiguous.
### Expected behavior
An in-line popup clearly and unambiguously explains how the pricing discount will be applied.
### Steps to reproduce
Go here and click this:
![Screenshot 2024-05-23 at 16 08 25](https://github.com/PrestaShop/PrestaShop/assets/382183/417ac33f-5f95-4f0c-bdcb-904b271a9e66)
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Discounts > Cart rules > Actions > Apply discount to > Selected product(s) is undefined behavior | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36225/comments | 2 | "2024-05-23T20:14:46" | "2024-06-11T08:51:16" | https://github.com/PrestaShop/PrestaShop/issues/36225 | 2,313,752,949 | 36,225 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Discounts > Cart rules > Actions > Apply discount to > Selected product(s) is undefined behavior
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 setting up a discount, there is an option to define a discount based on "selected product(s)".
However, the in-line documentation (i.e. hover over this option) and the "help" button/screen on the right side of the page do not define this behavior.
Perhaps this discount applies to the "Condition > production selection" items. If so, it should specifically say that.
---
# Applicable best practice / mantra
Any error when pricing products can be very bad for a merchant. Therefore software for setting up pricing should be reliable and unambiguous.
### Expected behavior
An in-line popup clearly and unambiguously explains how the pricing discount will be applied.
### Steps to reproduce
Go here and click this:
![Screenshot 2024-05-23 at 16 08 25](https://github.com/PrestaShop/PrestaShop/assets/382183/417ac33f-5f95-4f0c-bdcb-904b271a9e66)
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,782 | 65 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
This error message is incorrect, based on a plain reading of the text:
> This product is below the low stock level you have defined. Low stock level: 0
Mathematically this is because:
> 0 < 0
is false.
---
Shown here
![Screenshot 2024-05-23 at 14 57 11](https://github.com/PrestaShop/PrestaShop/assets/382183/abccb1d8-66cc-4870-9d55-c55a450876a7)
### Expected behavior
Either the error message should be changed to:
> This product is <mark>equal to or</mark> below the low stock level you have defined.
or the message should be kept but there should be a way to disable the low stock warning. This would be similar to setting the low stock amount to "-1". But a stock quantity of "-1" is an abstraction that does not relate to anything that humans physically encounter, so this should be managed by a separate checkbox in the GUI.
### Steps to reproduce
Set quantity to zero
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Inaccurate "This product is below the low stock level you have defined." | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36224/comments | 2 | "2024-05-23T19:04:18" | "2024-05-29T12:26:42" | https://github.com/PrestaShop/PrestaShop/issues/36224 | 2,313,638,813 | 36,224 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Inaccurate "This product is below the low stock level you have defined."
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
This error message is incorrect, based on a plain reading of the text:
> This product is below the low stock level you have defined. Low stock level: 0
Mathematically this is because:
> 0 < 0
is false.
---
Shown here
![Screenshot 2024-05-23 at 14 57 11](https://github.com/PrestaShop/PrestaShop/assets/382183/abccb1d8-66cc-4870-9d55-c55a450876a7)
### Expected behavior
Either the error message should be changed to:
> This product is <mark>equal to or</mark> below the low stock level you have defined.
or the message should be kept but there should be a way to disable the low stock warning. This would be similar to setting the low stock amount to "-1". But a stock quantity of "-1" is an abstraction that does not relate to anything that humans physically encounter, so this should be managed by a separate checkbox in the GUI.
### Steps to reproduce
Set quantity to zero
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,798 | 66 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Tooltip is missing here
![Screenshot 2024-05-23 at 11 57 07](https://github.com/PrestaShop/PrestaShop/assets/382183/e58d91a5-6ab9-46b8-90be-3b2b208c3234)
### Expected behavior
Similar tooltip like this:
![Screenshot 2024-05-23 at 11 57 09](https://github.com/PrestaShop/PrestaShop/assets/382183/50c123a5-d48e-4cae-9fcd-26a0dd61649a)
### Steps to reproduce
Visit admin####/index.php?controller=AdminCartRules&addcart_rule&token=####
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Tooltip missing for Cart Rule / Status | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36222/comments | 1 | "2024-05-23T15:58:52" | "2024-05-28T10:04:51" | https://github.com/PrestaShop/PrestaShop/issues/36222 | 2,313,290,301 | 36,222 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Tooltip missing for Cart Rule / Status
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Tooltip is missing here
![Screenshot 2024-05-23 at 11 57 07](https://github.com/PrestaShop/PrestaShop/assets/382183/e58d91a5-6ab9-46b8-90be-3b2b208c3234)
### Expected behavior
Similar tooltip like this:
![Screenshot 2024-05-23 at 11 57 09](https://github.com/PrestaShop/PrestaShop/assets/382183/50c123a5-d48e-4cae-9fcd-26a0dd61649a)
### Steps to reproduce
Visit admin####/index.php?controller=AdminCartRules&addcart_rule&token=####
### PrestaShop version(s) where the bug happened
8
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,299 | 67 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 `TaxManagerModuleCore` class, the `install` method registers the module to the `taxManager` hook. However, this is insufficient for proper functionality. The module should also be registered to the `actionTagManager` hook to ensure complete integration with the tax management system.
### Expected behavior
The module should seamlessly integrate with the tax management system, handling tax calculations and related tasks effectively.
### Steps to reproduce
1. Develop a custom module that extends the `TaxManagerModuleCore` class. This module will serve as a test case to demonstrate the incomplete hook registration issue.
2. Utilize the `Hook::getModulesFromHook(Hook::getIdByName('taxManager'));` method within the custom module. This will retrieve a list of modules registered to the `taxManager` hook.
3. Verify that the custom module is not included in the retrieved list of modules. This confirms that the `TaxManagerModuleCore` class is not properly registered to the `actionTagManager` hook.
### PrestaShop version(s) where the bug happened
develop
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Incomplete Hook Registration in TaxManagerModuleCore Class | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36219/comments | 2 | "2024-05-22T22:45:48" | "2024-06-14T09:11:02" | https://github.com/PrestaShop/PrestaShop/issues/36219 | 2,311,620,271 | 36,219 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Incomplete Hook Registration in TaxManagerModuleCore Class
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 `TaxManagerModuleCore` class, the `install` method registers the module to the `taxManager` hook. However, this is insufficient for proper functionality. The module should also be registered to the `actionTagManager` hook to ensure complete integration with the tax management system.
### Expected behavior
The module should seamlessly integrate with the tax management system, handling tax calculations and related tasks effectively.
### Steps to reproduce
1. Develop a custom module that extends the `TaxManagerModuleCore` class. This module will serve as a test case to demonstrate the incomplete hook registration issue.
2. Utilize the `Hook::getModulesFromHook(Hook::getIdByName('taxManager'));` method within the custom module. This will retrieve a list of modules registered to the `taxManager` hook.
3. Verify that the custom module is not included in the retrieved list of modules. This confirms that the `TaxManagerModuleCore` class is not properly registered to the `actionTagManager` hook.
### PrestaShop version(s) where the bug happened
develop
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,898 | 68 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 evening,
After trying to load the 'Paccofacile' form from the BO, the error below emerged after doing these actions:
The ZIP file of the module was not loaded, I thought it was a problem of the Prestashop marketplace and I was deactivating the module then but it was a bad idea because the error came back. I went into debug mode without understanding the problem and restored the last backup. I cleaned the cache but nothing ....
Compile Error: Declaration of WebserviceSpecificManagementPaccofaciletracking::setObjectOutput(WebserviceOutputBuilderCore $obj) must be compatible with WebserviceSpecificManagementInterface::setObjectOutput(WebserviceOutputBuilder $obj)
[Symfony\Component\ErrorHandler\Error\FatalError 0]
Thank you for your help.
Laura
### Expected behavior
_No response_
### Steps to reproduce
1)The ZIP file of the module was not loaded, I thought it was a problem of the Prestashop marketplace and I was deactivating the module then but it was a bad idea because the error came back.
2)I went into debug mode without understanding the problem and restored the last backup.
3) I cleaned the cache but nothing ....
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
7.4.33
### If your bug is related to a module, specify its name and its version
Paccofacile v.1.0.19
### Your company or customer's name goes here (if applicable).
_No response_ | Error loading "Paccofacile" module | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36218/comments | 3 | "2024-05-22T21:42:38" | "2024-05-29T12:17:34" | https://github.com/PrestaShop/PrestaShop/issues/36218 | 2,311,541,266 | 36,218 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Error loading "Paccofacile" module
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Good evening,
After trying to load the 'Paccofacile' form from the BO, the error below emerged after doing these actions:
The ZIP file of the module was not loaded, I thought it was a problem of the Prestashop marketplace and I was deactivating the module then but it was a bad idea because the error came back. I went into debug mode without understanding the problem and restored the last backup. I cleaned the cache but nothing ....
Compile Error: Declaration of WebserviceSpecificManagementPaccofaciletracking::setObjectOutput(WebserviceOutputBuilderCore $obj) must be compatible with WebserviceSpecificManagementInterface::setObjectOutput(WebserviceOutputBuilder $obj)
[Symfony\Component\ErrorHandler\Error\FatalError 0]
Thank you for your help.
Laura
### Expected behavior
_No response_
### Steps to reproduce
1)The ZIP file of the module was not loaded, I thought it was a problem of the Prestashop marketplace and I was deactivating the module then but it was a bad idea because the error came back.
2)I went into debug mode without understanding the problem and restored the last backup.
3) I cleaned the cache but nothing ....
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
7.4.33
### If your bug is related to a module, specify its name and its version
Paccofacile v.1.0.19
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 2,018 | 69 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 abstract class `TaxManagerModuleCore`, the `hookTaxManager` method returns a new instance of the current class (`new $class()`). However, the returned class should be initialized with two mandatory arguments: `address` and `type`. This initialization error can lead to malfunctions and unexpected behavior of the module.
### Expected behavior
The `hookTaxManager` method should return a new instance of the current class correctly initialized with the `address` and `type` arguments.
### Steps to reproduce
1. Create a custom module that extends the `TaxManagerModuleCore` class.
2. Implement the `hookTaxManager` method in the custom module.
3. Run the module in Prestashop.
### PrestaShop version(s) where the bug happened
1.7.x, 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_ | Initialization Error in TaxManagerModuleCore Class | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36217/comments | 2 | "2024-05-22T14:30:15" | "2024-06-14T09:10:33" | https://github.com/PrestaShop/PrestaShop/issues/36217 | 2,310,708,425 | 36,217 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Initialization Error in TaxManagerModuleCore Class
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 abstract class `TaxManagerModuleCore`, the `hookTaxManager` method returns a new instance of the current class (`new $class()`). However, the returned class should be initialized with two mandatory arguments: `address` and `type`. This initialization error can lead to malfunctions and unexpected behavior of the module.
### Expected behavior
The `hookTaxManager` method should return a new instance of the current class correctly initialized with the `address` and `type` arguments.
### Steps to reproduce
1. Create a custom module that extends the `TaxManagerModuleCore` class.
2. Implement the `hookTaxManager` method in the custom module.
3. Run the module in Prestashop.
### PrestaShop version(s) where the bug happened
1.7.x, 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 --- | 1,563 | 70 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 currently building an new PrestaShop 8.1.6 shop and had no issues until I tried to add a new user. I discovered that the file OptionsChecker.php was not uploaded to the server with FileZilla, so I uploaded it again. From that moment I have "deprecated" errors on practically everypage I edit in the back-end. Could this be PHP version related?
### Expected behavior
_No response_
### Steps to reproduce
![error na aanmaken nieuwe gebruiker 01](https://github.com/PrestaShop/PrestaShop/assets/45594881/896abae3-79e1-426e-898e-32fbbf919398)
![error na adresgegevens invoer 05](https://github.com/PrestaShop/PrestaShop/assets/45594881/f7a01418-5f80-423b-aff8-a1bc6cd45e4f)
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2.16
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Caer boardsports | Deprecated error on many pages. Prestashop 8.1.6 with PHP 8.2.16 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36214/comments | 3 | "2024-05-22T11:54:47" | "2024-05-29T13:48:15" | https://github.com/PrestaShop/PrestaShop/issues/36214 | 2,310,340,670 | 36,214 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Deprecated error on many pages. Prestashop 8.1.6 with PHP 8.2.16
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 currently building an new PrestaShop 8.1.6 shop and had no issues until I tried to add a new user. I discovered that the file OptionsChecker.php was not uploaded to the server with FileZilla, so I uploaded it again. From that moment I have "deprecated" errors on practically everypage I edit in the back-end. Could this be PHP version related?
### Expected behavior
_No response_
### Steps to reproduce
![error na aanmaken nieuwe gebruiker 01](https://github.com/PrestaShop/PrestaShop/assets/45594881/896abae3-79e1-426e-898e-32fbbf919398)
![error na adresgegevens invoer 05](https://github.com/PrestaShop/PrestaShop/assets/45594881/f7a01418-5f80-423b-aff8-a1bc6cd45e4f)
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2.16
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Caer boardsports
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,560 | 71 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 configure some module the error is present. Modules where I could see the error:
- marketingWithGoogle
- ps_faviconnotificationbo
- autoupgrade
![image](https://github.com/PrestaShop/PrestaShop/assets/36233446/80c294ec-2cbb-494d-a08a-f86238448359)
### Expected behavior
Access to the module configuration page works correctly
### Steps to reproduce
1 Install v9
2 go to module manager
3 Configure "Order Notifications on the Favicon" module
4 see error
### PrestaShop version(s) where the bug happened
9.0.0
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Employee is not granted read on controller ... | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36212/comments | 1 | "2024-05-21T15:49:10" | "2024-05-29T13:50:30" | https://github.com/PrestaShop/PrestaShop/issues/36212 | 2,308,607,136 | 36,212 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Employee is not granted read on controller ...
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 configure some module the error is present. Modules where I could see the error:
- marketingWithGoogle
- ps_faviconnotificationbo
- autoupgrade
![image](https://github.com/PrestaShop/PrestaShop/assets/36233446/80c294ec-2cbb-494d-a08a-f86238448359)
### Expected behavior
Access to the module configuration page works correctly
### Steps to reproduce
1 Install v9
2 go to module manager
3 Configure "Order Notifications on the Favicon" module
4 see error
### PrestaShop version(s) where the bug happened
9.0.0
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,330 | 72 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 credit slip is generated, but concerns only delivery fees, the PDF generation of this credit slip generates an issue :
> PrestaShop\PrestaShop\Core\Util\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in classes/pdf/HTMLTemplateOrderSlip.php on line 169
[TypeError 0]
I modified the HTMLTemplateOrderSlip.php on line 169 like this :
```
$order_details = [];
$order_details = $this->order->products;
if (!empty($order_details)) {
// Sort products by Reference ID (and if equals (like combination) by Supplier Reference)
$sorter = new Sorter();
$order_details = $sorter->natural($order_details, Sorter::ORDER_DESC, 'product_reference', 'product_supplier_reference');
}
```
### Expected behavior
_No response_
### Steps to reproduce
1. Generate an credit slip with only delivery fees
2. generate associated PDF
### 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).
Romaric PIBOLLEAU - RP2I | PDF generation of OrderSlip generates an error if no product inside (orderslip concerns only delivrey fees) | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36209/comments | 3 | "2024-05-21T13:31:43" | "2024-05-21T13:51:01" | https://github.com/PrestaShop/PrestaShop/issues/36209 | 2,308,323,856 | 36,209 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : PDF generation of OrderSlip generates an error if no product inside (orderslip concerns only delivrey fees)
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 credit slip is generated, but concerns only delivery fees, the PDF generation of this credit slip generates an issue :
> PrestaShop\PrestaShop\Core\Util\Sorter::natural(): Argument #1 ($array) must be of type array, null given, called in classes/pdf/HTMLTemplateOrderSlip.php on line 169
[TypeError 0]
I modified the HTMLTemplateOrderSlip.php on line 169 like this :
```
$order_details = [];
$order_details = $this->order->products;
if (!empty($order_details)) {
// Sort products by Reference ID (and if equals (like combination) by Supplier Reference)
$sorter = new Sorter();
$order_details = $sorter->natural($order_details, Sorter::ORDER_DESC, 'product_reference', 'product_supplier_reference');
}
```
### Expected behavior
_No response_
### Steps to reproduce
1. Generate an credit slip with only delivery fees
2. generate associated PDF
### 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).
Romaric PIBOLLEAU - RP2I
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,871 | 73 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 bug related to the database table ps_cusotmization_field. If an entry is present in the table with the "is_module" column set to 1, this seems to get reset to 0 whenever the product is saved after editing in the back office. This causes issues for modules which utilize the customization_field table.
This seems to affect more recent versions of Prestashop, at least from 8.1.3 onwards but not tested on earlier versions.
### Expected behavior
The existing value for "is_module" should not be overwritten
### Steps to reproduce
Create an entry in the ps_cusotmization_field table for a product, eg product ID #16
Set the "is_module" column to 1
Not in the back office edit product #16 and save the changes
Notice the "is_module" column has been set to 0
### 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_ | CustomizationField::is_module flag gets reset after a product save | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36208/comments | 3 | "2024-05-21T09:14:26" | "2024-06-14T07:45:25" | https://github.com/PrestaShop/PrestaShop/issues/36208 | 2,307,791,411 | 36,208 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : CustomizationField::is_module flag gets reset after a product save
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 bug related to the database table ps_cusotmization_field. If an entry is present in the table with the "is_module" column set to 1, this seems to get reset to 0 whenever the product is saved after editing in the back office. This causes issues for modules which utilize the customization_field table.
This seems to affect more recent versions of Prestashop, at least from 8.1.3 onwards but not tested on earlier versions.
### Expected behavior
The existing value for "is_module" should not be overwritten
### Steps to reproduce
Create an entry in the ps_cusotmization_field table for a product, eg product ID #16
Set the "is_module" column to 1
Not in the back office edit product #16 and save the changes
Notice the "is_module" column has been set to 0
### 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 --- | 1,655 | 74 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
I am taking the liberty of contacting you, because despite my research I am unfortunately bredouille.
The problem is that my Link List is disconnected for no apparent reason.
It worked for more than 3 months and then the drama. ^^
![Footer bug](https://github.com/PrestaShop/PrestaShop/assets/170365377/45e309cb-eb49-4fa3-a1b8-70436ff30e85)
I'd like to ask you a quick question: do you know why a menu is displayed like this?
And more importantly, how do you get it to display correctly ?
### Expected behavior
_No response_
### Steps to reproduce
No special manipulations, it simply appears like this.
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
Link List v6.0.7
### Your company or customer's name goes here (if applicable).
_No response_ | Display bug footer link - EMERGENCY | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36206/comments | 1 | "2024-05-20T19:48:04" | "2024-05-21T10:49:03" | https://github.com/PrestaShop/PrestaShop/issues/36206 | 2,306,666,533 | 36,206 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Display bug footer link - EMERGENCY
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
I am taking the liberty of contacting you, because despite my research I am unfortunately bredouille.
The problem is that my Link List is disconnected for no apparent reason.
It worked for more than 3 months and then the drama. ^^
![Footer bug](https://github.com/PrestaShop/PrestaShop/assets/170365377/45e309cb-eb49-4fa3-a1b8-70436ff30e85)
I'd like to ask you a quick question: do you know why a menu is displayed like this?
And more importantly, how do you get it to display correctly ?
### Expected behavior
_No response_
### Steps to reproduce
No special manipulations, it simply appears like this.
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
Link List v6.0.7
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,470 | 75 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
https://github.com/PrestaShop/PrestaShop/assets/6115458/b1911da0-6af5-45b5-9eba-b1b45ab676a8
### Expected behavior
Categories to be searchable and editable
### Steps to reproduce
1. Go to the Experimental feature section and enable the new product page
2. Go to a product and try to edit the category
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.1.28
### Additional information
The old product page works fine
![image](https://github.com/PrestaShop/PrestaShop/assets/6115458/961da956-3d20-4640-9bdd-f60e8f0cea47)
No requests are happening when searching, I don't know if it's supposed to though as the old one doesn't seem to make any request either
No js errors either
A request is happening when opening the category modal like so `/admin.../index.php/sell/catalog/categories/tree?_token=xxx` but returns `[]` | New product page: category of a product cannot be modified/searched | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36205/comments | 5 | "2024-05-20T17:46:48" | "2024-05-21T13:34:56" | https://github.com/PrestaShop/PrestaShop/issues/36205 | 2,306,465,325 | 36,205 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : New product page: category of a product cannot be modified/searched
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
https://github.com/PrestaShop/PrestaShop/assets/6115458/b1911da0-6af5-45b5-9eba-b1b45ab676a8
### Expected behavior
Categories to be searchable and editable
### Steps to reproduce
1. Go to the Experimental feature section and enable the new product page
2. Go to a product and try to edit the category
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
8.1.28
### Additional information
The old product page works fine
![image](https://github.com/PrestaShop/PrestaShop/assets/6115458/961da956-3d20-4640-9bdd-f60e8f0cea47)
No requests are happening when searching, I don't know if it's supposed to though as the old one doesn't seem to make any request either
No js errors either
A request is happening when opening the category modal like so `/admin.../index.php/sell/catalog/categories/tree?_token=xxx` but returns `[]`
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,519 | 76 |
[
"PrestaShop",
"PrestaShop"
] | null | Make TokenizedUrlsListener dynamic so that it automatically gets the public routes based on configured access controls | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36204/comments | 0 | "2024-05-20T16:29:36" | "2024-05-22T13:07:36" | https://github.com/PrestaShop/PrestaShop/issues/36204 | 2,306,346,579 | 36,204 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Make TokenizedUrlsListener dynamic so that it automatically gets the public routes based on configured access controls
Issue date:
--- start body ---
None
--- end body ---
comments :
--- start comments ---
--- end comments --- | 293 | 77 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Hello, When I do an upgrade from version 8.x.x to 9.0.0, I'll have an exception when I want to go on 1 click Upgrade (to rollback for example) as you can see :
[recording(208).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/07ee16df-0ae2-451e-81cf-114fe1afa97b)
### Expected behavior
I wish I could use the module after the upgrade
### Steps to reproduce
1. Install a fresh Prestashop 8.1.6
2. Install a autoupgrade in dev version (for example https://github.com/PrestaShop/autoupgrade/pull/699)
3. Do a manual upgrade to 9.0.0
4. Go on the BO of 9.0.0
5. Clic on the 1-Click Upgrade shortcut
6. You'll have the exception
### PrestaShop version(s) where the bug happened
8.x.x
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
autoupgrade v5.0.1 from dev branch
### Your company or customer's name goes here (if applicable).
PS | Autoupgrade - Upgrade to 9.0.0 - When you want to go on 1 Click Upgrade, you don't have the right | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36202/comments | 1 | "2024-05-20T15:54:35" | "2024-06-13T08:20:12" | https://github.com/PrestaShop/PrestaShop/issues/36202 | 2,306,287,335 | 36,202 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Autoupgrade - Upgrade to 9.0.0 - When you want to go on 1 Click Upgrade, you don't have the right
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Hello, When I do an upgrade from version 8.x.x to 9.0.0, I'll have an exception when I want to go on 1 click Upgrade (to rollback for example) as you can see :
[recording(208).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/07ee16df-0ae2-451e-81cf-114fe1afa97b)
### Expected behavior
I wish I could use the module after the upgrade
### Steps to reproduce
1. Install a fresh Prestashop 8.1.6
2. Install a autoupgrade in dev version (for example https://github.com/PrestaShop/autoupgrade/pull/699)
3. Do a manual upgrade to 9.0.0
4. Go on the BO of 9.0.0
5. Clic on the 1-Click Upgrade shortcut
6. You'll have the exception
### PrestaShop version(s) where the bug happened
8.x.x
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
autoupgrade v5.0.1 from dev branch
### Your company or customer's name goes here (if applicable).
PS
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,578 | 78 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 created website in win10 local wsl2 using prestashop open source program, which currently works fine on win10.
I uploaded the source code from the root directory of the website /var/www/ucoredata to the /var/www/ucoredata.tech directory on the remote server via scp.
At the same time, I also created a mysql database prestashop on the remote server and imported the local sql database into prestashop.
I used the virtual domain ucoredata.com locally for testing and development.
I have used the real domain ucoredata.tech on the remote server
I have changed the virtual domain ucoredata.com to www.ucoredata.tech in the remote database.
Currently when I visit www.ucoredata.tech through my browser, it prompts:
This page is not functioning properly www.ucoredata.tech cannot process this request at this time.
HTTP ERROR 500
Looking forward to your help and answers, thanks in advance! Thanks in advance!
Visit the frontend
![01](https://github.com/PrestaShop/PrestaShop/assets/136626456/1133b19c-24fa-4119-a8ef-b8501d94f868)
Visit Backend
![02](https://github.com/PrestaShop/PrestaShop/assets/136626456/34313e11-169c-4647-9198-9a28aa16cb60)
### Expected behavior
The site can be accessed normally
### Steps to reproduce
Environment test: Upload environment test file
scp phppsinfo.php stuffren@192.3.112.214:/var/www/ucoredata.tech/
![03-phppsinfo](https://github.com/PrestaShop/PrestaShop/assets/136626456/185eec15-bc8f-48e5-9b9d-4cc200d61db4)
As you can see based on the screenshot, my configuration almost always matches the environment configuration officially required by prestashop.
Step 1. Package the source code in win10 local wsl2
Step 2: Upload the packaged file to the server using the scp command
Step 3: Unzip the file
Step 4: Create a new database
Name, login and password of the mysql database in the remote server.
Keep the same name, login name and password of the database in the remote server as the mysql database in the local wsl2.
### PrestaShop version(s) where the bug happened
8.1.5;I didn't do the upgrade, it has nothing to do with the upgrade
### PHP version(s) where the bug happened
PHP 8.1.2-1ubuntu2.17 (cli) (built: May 1 2024 10:10:07) (NTS)
### If your bug is related to a module, specify its name and its version
no
### Your company or customer's name goes here (if applicable).
no | Uploading win10 local source code to a remote server prompts HTTP ERROR 500 【请求帮助!!!谢谢!】 | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36201/comments | 9 | "2024-05-20T15:40:59" | "2024-05-24T08:49:09" | https://github.com/PrestaShop/PrestaShop/issues/36201 | 2,306,264,095 | 36,201 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Uploading win10 local source code to a remote server prompts HTTP ERROR 500 【请求帮助!!!谢谢!】
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
I have created website in win10 local wsl2 using prestashop open source program, which currently works fine on win10.
I uploaded the source code from the root directory of the website /var/www/ucoredata to the /var/www/ucoredata.tech directory on the remote server via scp.
At the same time, I also created a mysql database prestashop on the remote server and imported the local sql database into prestashop.
I used the virtual domain ucoredata.com locally for testing and development.
I have used the real domain ucoredata.tech on the remote server
I have changed the virtual domain ucoredata.com to www.ucoredata.tech in the remote database.
Currently when I visit www.ucoredata.tech through my browser, it prompts:
This page is not functioning properly www.ucoredata.tech cannot process this request at this time.
HTTP ERROR 500
Looking forward to your help and answers, thanks in advance! Thanks in advance!
Visit the frontend
![01](https://github.com/PrestaShop/PrestaShop/assets/136626456/1133b19c-24fa-4119-a8ef-b8501d94f868)
Visit Backend
![02](https://github.com/PrestaShop/PrestaShop/assets/136626456/34313e11-169c-4647-9198-9a28aa16cb60)
### Expected behavior
The site can be accessed normally
### Steps to reproduce
Environment test: Upload environment test file
scp phppsinfo.php stuffren@192.3.112.214:/var/www/ucoredata.tech/
![03-phppsinfo](https://github.com/PrestaShop/PrestaShop/assets/136626456/185eec15-bc8f-48e5-9b9d-4cc200d61db4)
As you can see based on the screenshot, my configuration almost always matches the environment configuration officially required by prestashop.
Step 1. Package the source code in win10 local wsl2
Step 2: Upload the packaged file to the server using the scp command
Step 3: Unzip the file
Step 4: Create a new database
Name, login and password of the mysql database in the remote server.
Keep the same name, login name and password of the database in the remote server as the mysql database in the local wsl2.
### PrestaShop version(s) where the bug happened
8.1.5;I didn't do the upgrade, it has nothing to do with the upgrade
### PHP version(s) where the bug happened
PHP 8.1.2-1ubuntu2.17 (cli) (built: May 1 2024 10:10:07) (NTS)
### If your bug is related to a module, specify its name and its version
no
### Your company or customer's name goes here (if applicable).
no
--- end body ---
comments :
--- start comments ---
--- end comments --- | 3,010 | 79 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
We're trying to load some custom js files from a hook action.
In our hook action :
`$this->context->controller->addJS([somepath].js); `
it seams to go throught `addJS` function but the files are not loaded
### Expected behavior
_No response_
### Steps to reproduce
1. call `addJS` function in hook action with `$this->context->controller`
2. go through `addJS` function in `PrestaShop/classes/controller/Controller.php` and try to print` $js_files`
a bunch of JS files in this list are not loaded on layout
### PrestaShop version(s) where the bug happened
9.0.0
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
ps_mbo
### Your company or customer's name goes here (if applicable).
_No response_ | $this->addJS in module not loading front js files in layout | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36200/comments | 2 | "2024-05-20T15:33:00" | "2024-05-22T11:23:26" | https://github.com/PrestaShop/PrestaShop/issues/36200 | 2,306,250,417 | 36,200 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : $this->addJS in module not loading front js files in layout
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
We're trying to load some custom js files from a hook action.
In our hook action :
`$this->context->controller->addJS([somepath].js); `
it seams to go throught `addJS` function but the files are not loaded
### Expected behavior
_No response_
### Steps to reproduce
1. call `addJS` function in hook action with `$this->context->controller`
2. go through `addJS` function in `PrestaShop/classes/controller/Controller.php` and try to print` $js_files`
a bunch of JS files in this list are not loaded on layout
### PrestaShop version(s) where the bug happened
9.0.0
### PHP version(s) where the bug happened
8.1
### If your bug is related to a module, specify its name and its version
ps_mbo
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,382 | 80 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
![image](https://github.com/PrestaShop/PrestaShop/assets/53503340/5349e12c-3700-444e-9d9d-ac3d5a481290)
During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears.
" error.
I've tested this in a number of ways, including local VM testing, VPS testing all of which have issues when it comes to this step.
### Expected behavior
_No response_
### Steps to reproduce
During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears.
" error.
I've tested this in a number of ways, including local VM testing, VPS testing all of which have issues when it comes to this step.
### PrestaShop version(s) where the bug happened
8.1.6
### 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_ | During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears. " error | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36196/comments | 2 | "2024-05-20T08:09:01" | "2024-05-21T10:48:25" | https://github.com/PrestaShop/PrestaShop/issues/36196 | 2,305,390,112 | 36,196 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears. " 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
![image](https://github.com/PrestaShop/PrestaShop/assets/53503340/5349e12c-3700-444e-9d9d-ac3d5a481290)
During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears.
" error.
I've tested this in a number of ways, including local VM testing, VPS testing all of which have issues when it comes to this step.
### Expected behavior
_No response_
### Steps to reproduce
During the installation process, at the "Install Module" step, the message "1: HTTP 500 - error -" appears.
" error.
I've tested this in a number of ways, including local VM testing, VPS testing all of which have issues when it comes to this step.
### PrestaShop version(s) where the bug happened
8.1.6
### 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 --- | 1,594 | 81 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 cannot edit layout of theme installed.
The link going on module page but not in layout configuration
Prestashop 8.1.6
PHP 8.1.28
https://github.com/PrestaShop/PrestaShop/assets/8173557/98ad82b0-fe35-4562-a6f1-58c7d1b3f2c3
https://github.com/PrestaShop/PrestaShop/assets/8173557/32898645-3238-4969-8017-9425f9f693a4
### Expected behavior
_No response_
### Steps to reproduce
Design -> customization
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Fershop.it | Edit Layout of template button link going in module page | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36192/comments | 5 | "2024-05-19T19:42:05" | "2024-05-29T13:52:13" | https://github.com/PrestaShop/PrestaShop/issues/36192 | 2,304,753,732 | 36,192 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Edit Layout of template button link going in module 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 cannot edit layout of theme installed.
The link going on module page but not in layout configuration
Prestashop 8.1.6
PHP 8.1.28
https://github.com/PrestaShop/PrestaShop/assets/8173557/98ad82b0-fe35-4562-a6f1-58c7d1b3f2c3
https://github.com/PrestaShop/PrestaShop/assets/8173557/32898645-3238-4969-8017-9425f9f693a4
### Expected behavior
_No response_
### Steps to reproduce
Design -> customization
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.1.28
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Fershop.it
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,317 | 82 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Hey,
i tried to install PrestaShop on my localhost XAMPP Server, when I try to install it this Error comes:
![image](https://github.com/PrestaShop/PrestaShop/assets/159568343/0f58a5ea-7424-4d68-aa97-c392e47a91ac)
I already enabled in the php.ini:
- extension=zip
- extension=php_zip.dll
- extension=gd
But nothing helped...
Can someone help pls.
### Expected behavior
that the installation runs corecctly
### Steps to reproduce
1. setup prestaShop like in the docs
2. Running the AutoInstallation
3. Error comes
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2.12
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
zGamerZz | PrestaShop installation requires the Zip PHP extension to be enabled. (XAMPP) | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36191/comments | 1 | "2024-05-18T18:49:43" | "2024-05-29T13:53:25" | https://github.com/PrestaShop/PrestaShop/issues/36191 | 2,304,257,715 | 36,191 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : PrestaShop installation requires the Zip PHP extension to be enabled. (XAMPP)
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Hey,
i tried to install PrestaShop on my localhost XAMPP Server, when I try to install it this Error comes:
![image](https://github.com/PrestaShop/PrestaShop/assets/159568343/0f58a5ea-7424-4d68-aa97-c392e47a91ac)
I already enabled in the php.ini:
- extension=zip
- extension=php_zip.dll
- extension=gd
But nothing helped...
Can someone help pls.
### Expected behavior
that the installation runs corecctly
### Steps to reproduce
1. setup prestaShop like in the docs
2. Running the AutoInstallation
3. Error comes
### PrestaShop version(s) where the bug happened
8.1.6
### PHP version(s) where the bug happened
8.2.12
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
zGamerZz
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,451 | 83 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Admin hooks of format "display#controller_name#Form" on legacy admin forms such as "displayAdminReturnForm" are not executed.
The hook is supposed to be called here : https://github.com/PrestaShop/PrestaShop/blob/8.1.6/admin-dev/themes/default/template/helpers/form/form.tpl#L663
Here `$name_controller` is supposed to be the name of the controller, so for exemple "AdminReturn" in the case of the "AdminReturn" controller when we try to view a single order return. The hook should be called at the end of the form
![screenshot-127 0 0 1_4502-2024 05 17-12_55_42](https://github.com/PrestaShop/PrestaShop/assets/28593328/bbb78141-796f-4585-a8e5-1a72f4dd94ce)
But actually, the value of `$name_controller` is an empty string, so the executed hook is "displayForm" and not "displayAdminReturnForm". This behaviour is caused by these two code snippets:
https://github.com/PrestaShop/PrestaShop/blob/develop/classes/controller/AdminController.php#L2621C1-L2623C10
https://github.com/PrestaShop/PrestaShop/blob/8.1.6/classes/helper/HelperForm.php#L40
On the `AdminController.php` file, we see that `$name_controller` takes the value only if it doesn't equal null. But in the `HelperForm.php` file we see that `$name_controller` is not equal to null, it's an empty string, thus the bug : `$name_controller` is equal to an empty string and never takes the `Tools::getValue('controller')` as a value
We see in this file the smarty affectation of the "name_controller" variable used in the `form.tpl` file
https://github.com/PrestaShop/PrestaShop/blob/8.1.6/classes/helper/HelperForm.php#L291
This PR introduced this bug : https://github.com/PrestaShop/PrestaShop/pull/31514
### Expected behavior
The hook "displayAdminReturnForm" should be executed at the end of a return form in backoffice (in the red rectangle on the screenshot above)
### Steps to reproduce
1. Create a module that's attached to the "displayAdminReturnForm" hook
2. On this module, create a function that returns a simple string, such as "test"
3. On the "AdminReturn" in backoffice, select a return issued by a customer
4. The text "test" should appear at the end of the form (see screenshot above), but it doesn't
### PrestaShop version(s) where the bug happened
Tested on 8.1.4, but was presumably introduced in 8.0.2
### PHP version(s) where the bug happened
N/A
### If your bug is related to a module, specify its name and its version
N/A
### Your company or customer's name goes here (if applicable).
PliciWeb | Admin hooks of format "display#controller_name#Form" on legacy admin forms are not executed | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36185/comments | 1 | "2024-05-17T12:16:11" | "2024-05-29T14:11:01" | https://github.com/PrestaShop/PrestaShop/issues/36185 | 2,302,592,046 | 36,185 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Admin hooks of format "display#controller_name#Form" on legacy admin forms are not executed
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Admin hooks of format "display#controller_name#Form" on legacy admin forms such as "displayAdminReturnForm" are not executed.
The hook is supposed to be called here : https://github.com/PrestaShop/PrestaShop/blob/8.1.6/admin-dev/themes/default/template/helpers/form/form.tpl#L663
Here `$name_controller` is supposed to be the name of the controller, so for exemple "AdminReturn" in the case of the "AdminReturn" controller when we try to view a single order return. The hook should be called at the end of the form
![screenshot-127 0 0 1_4502-2024 05 17-12_55_42](https://github.com/PrestaShop/PrestaShop/assets/28593328/bbb78141-796f-4585-a8e5-1a72f4dd94ce)
But actually, the value of `$name_controller` is an empty string, so the executed hook is "displayForm" and not "displayAdminReturnForm". This behaviour is caused by these two code snippets:
https://github.com/PrestaShop/PrestaShop/blob/develop/classes/controller/AdminController.php#L2621C1-L2623C10
https://github.com/PrestaShop/PrestaShop/blob/8.1.6/classes/helper/HelperForm.php#L40
On the `AdminController.php` file, we see that `$name_controller` takes the value only if it doesn't equal null. But in the `HelperForm.php` file we see that `$name_controller` is not equal to null, it's an empty string, thus the bug : `$name_controller` is equal to an empty string and never takes the `Tools::getValue('controller')` as a value
We see in this file the smarty affectation of the "name_controller" variable used in the `form.tpl` file
https://github.com/PrestaShop/PrestaShop/blob/8.1.6/classes/helper/HelperForm.php#L291
This PR introduced this bug : https://github.com/PrestaShop/PrestaShop/pull/31514
### Expected behavior
The hook "displayAdminReturnForm" should be executed at the end of a return form in backoffice (in the red rectangle on the screenshot above)
### Steps to reproduce
1. Create a module that's attached to the "displayAdminReturnForm" hook
2. On this module, create a function that returns a simple string, such as "test"
3. On the "AdminReturn" in backoffice, select a return issued by a customer
4. The text "test" should appear at the end of the form (see screenshot above), but it doesn't
### PrestaShop version(s) where the bug happened
Tested on 8.1.4, but was presumably introduced in 8.0.2
### PHP version(s) where the bug happened
N/A
### If your bug is related to a module, specify its name and its version
N/A
### Your company or customer's name goes here (if applicable).
PliciWeb
--- end body ---
comments :
--- start comments ---
--- end comments --- | 3,178 | 84 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 upgrade from a Prestashop version 8.0.5 to 8.1.6 by a major version, I have a blank FO as you can see :
[recording(205).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/ff2f2a68-d5ee-4d9b-abfb-267b88649336)
FYI : I didn't have this issue with 8.1.5 and 1.7.8.11
### Expected behavior
I wish I could use my FO after the upgrade
### Steps to reproduce
1. Install a fresh 8.0.5
2. Go to BO > Modules > Modules Manager
3. Install Autoupgrade (1-Click Upgrade)
4. Clic on configure
5. Select the Major version
6. Do the upgrade
7. After the upgrade, clic on view my shop :x:
### PrestaShop version(s) where the bug happened
8.0.5
### PHP version(s) where the bug happened
7.4 and 8.1
### If your bug is related to a module, specify its name and its version
autoupgrade v5.0.1
### Your company or customer's name goes here (if applicable).
PS | Autoupgrade - From 8.0.5 to 8.1.6 - FO is blank | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36184/comments | 1 | "2024-05-17T09:25:23" | "2024-05-29T13:54:17" | https://github.com/PrestaShop/PrestaShop/issues/36184 | 2,302,237,301 | 36,184 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Autoupgrade - From 8.0.5 to 8.1.6 - FO is blank
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://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 upgrade from a Prestashop version 8.0.5 to 8.1.6 by a major version, I have a blank FO as you can see :
[recording(205).webm](https://github.com/PrestaShop/PrestaShop/assets/100699445/ff2f2a68-d5ee-4d9b-abfb-267b88649336)
FYI : I didn't have this issue with 8.1.5 and 1.7.8.11
### Expected behavior
I wish I could use my FO after the upgrade
### Steps to reproduce
1. Install a fresh 8.0.5
2. Go to BO > Modules > Modules Manager
3. Install Autoupgrade (1-Click Upgrade)
4. Clic on configure
5. Select the Major version
6. Do the upgrade
7. After the upgrade, clic on view my shop :x:
### PrestaShop version(s) where the bug happened
8.0.5
### PHP version(s) where the bug happened
7.4 and 8.1
### If your bug is related to a module, specify its name and its version
autoupgrade v5.0.1
### Your company or customer's name goes here (if applicable).
PS
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,471 | 85 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Good morning,
I have a problem with assigning categories and subcategories.
Every day I manually reload a .csv file that I need to update the stocks of the over 1000 products I have on my site, the upload is set with a table that only updates the prices and stocks, all the other columns (name, category, etc) are ignored. After import, however, the categories and subcategories are reset on all products, leaving only one category, the highest among those assigned, even if it had another one set as default, and removing all subsequent subcategories.
Example:
I assign to product A the generic category 1 (Default category), the subcategory 2 and the sub-subcategory 3,
I assign generic category 1, subcategory 2 and sub-subcategory 3 (Default Category) to product B.
I assign only subcategory 2 and sub-subcategory 3 to product C (default category)
After the next import:
Products A and B remain assigned only in category 1, subcategory 2 and sub-subcategory 3 are removed, even if 3 for product B was set as Default.
Product C remains assigned to subcategory 2, and sub-subcategory 3 (set as default) is removed.
The big problem is that if I only assign the sub-subcategory 3, even if it is a daughter of 2 which in turn is a daughter of 1, the product appears only in 3 and does not appear either in category 1 or in subcategory 2.
In practice, the system does not allow me to assign more than one category to each product, or to essentially have subcategories.
website: sanmicheleparafarmacia.com
Prestashop version: 8.1.3
PHP version:7.3
Steps to reproduce the problem:
1. Import product from file.csv (without modules) from Advanced Parameters -> Import
2. Add manually category and subcategory to product from edit product page in backend
3. Update the products with a new.csv file, again going from Advanced parameters -> Import, using a data matching configuration ignoring almost all the columns except reference, stock and price, therefore also ignoring the categories column.
![Add-category-1](https://github.com/PrestaShop/PrestaShop/assets/20090246/e330d259-f888-4036-aa2f-983e560f8ba7)
![Add-category-2](https://github.com/PrestaShop/PrestaShop/assets/20090246/11754e42-5f9a-40a6-ba2a-785ab51afebd)
![1](https://github.com/PrestaShop/PrestaShop/assets/20090246/de6e8ec3-30ef-4f9c-acbb-71b82cc79eb4)
![2](https://github.com/PrestaShop/PrestaShop/assets/20090246/a54f4425-03e9-466a-9fb6-76cc38976f1e)
![3](https://github.com/PrestaShop/PrestaShop/assets/20090246/077c51db-6c29-4006-a57d-e8e16cff775d)
![4](https://github.com/PrestaShop/PrestaShop/assets/20090246/277978e6-dddb-46df-bd68-027c9c636874)
![5](https://github.com/PrestaShop/PrestaShop/assets/20090246/5fc6bf7c-383a-4f16-85ae-43a5af331282)
![Final-result-after-second-import](https://github.com/PrestaShop/PrestaShop/assets/20090246/271e034e-2acb-4137-8522-eaaf93aacda6)
### Expected behavior
I want the categories and subcategories to remain those assigned manually and not to be deleted each time a new.csv file is imported
### Steps to reproduce
1. Import products from file.csv (without modules) from Advanced Parameters -> Import
2. Add manually category and subcategory to product from edit product page in backend
3. Update the products with a new.csv file, again going from Advanced parameters -> Import, using a data matching configuration ignoring almost all the columns except reference, stock and price, therefore also ignoring the categories column.
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
7.3
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Parafarmacia San Michele s.r.l | Prestashop 8.1.3 - Each new import with file.csv deletes the categories assigned to the products | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36183/comments | 4 | "2024-05-17T08:32:49" | "2024-06-14T08:40:42" | https://github.com/PrestaShop/PrestaShop/issues/36183 | 2,302,133,060 | 36,183 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Prestashop 8.1.3 - Each new import with file.csv deletes the categories assigned to the products
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
Good morning,
I have a problem with assigning categories and subcategories.
Every day I manually reload a .csv file that I need to update the stocks of the over 1000 products I have on my site, the upload is set with a table that only updates the prices and stocks, all the other columns (name, category, etc) are ignored. After import, however, the categories and subcategories are reset on all products, leaving only one category, the highest among those assigned, even if it had another one set as default, and removing all subsequent subcategories.
Example:
I assign to product A the generic category 1 (Default category), the subcategory 2 and the sub-subcategory 3,
I assign generic category 1, subcategory 2 and sub-subcategory 3 (Default Category) to product B.
I assign only subcategory 2 and sub-subcategory 3 to product C (default category)
After the next import:
Products A and B remain assigned only in category 1, subcategory 2 and sub-subcategory 3 are removed, even if 3 for product B was set as Default.
Product C remains assigned to subcategory 2, and sub-subcategory 3 (set as default) is removed.
The big problem is that if I only assign the sub-subcategory 3, even if it is a daughter of 2 which in turn is a daughter of 1, the product appears only in 3 and does not appear either in category 1 or in subcategory 2.
In practice, the system does not allow me to assign more than one category to each product, or to essentially have subcategories.
website: sanmicheleparafarmacia.com
Prestashop version: 8.1.3
PHP version:7.3
Steps to reproduce the problem:
1. Import product from file.csv (without modules) from Advanced Parameters -> Import
2. Add manually category and subcategory to product from edit product page in backend
3. Update the products with a new.csv file, again going from Advanced parameters -> Import, using a data matching configuration ignoring almost all the columns except reference, stock and price, therefore also ignoring the categories column.
![Add-category-1](https://github.com/PrestaShop/PrestaShop/assets/20090246/e330d259-f888-4036-aa2f-983e560f8ba7)
![Add-category-2](https://github.com/PrestaShop/PrestaShop/assets/20090246/11754e42-5f9a-40a6-ba2a-785ab51afebd)
![1](https://github.com/PrestaShop/PrestaShop/assets/20090246/de6e8ec3-30ef-4f9c-acbb-71b82cc79eb4)
![2](https://github.com/PrestaShop/PrestaShop/assets/20090246/a54f4425-03e9-466a-9fb6-76cc38976f1e)
![3](https://github.com/PrestaShop/PrestaShop/assets/20090246/077c51db-6c29-4006-a57d-e8e16cff775d)
![4](https://github.com/PrestaShop/PrestaShop/assets/20090246/277978e6-dddb-46df-bd68-027c9c636874)
![5](https://github.com/PrestaShop/PrestaShop/assets/20090246/5fc6bf7c-383a-4f16-85ae-43a5af331282)
![Final-result-after-second-import](https://github.com/PrestaShop/PrestaShop/assets/20090246/271e034e-2acb-4137-8522-eaaf93aacda6)
### Expected behavior
I want the categories and subcategories to remain those assigned manually and not to be deleted each time a new.csv file is imported
### Steps to reproduce
1. Import products from file.csv (without modules) from Advanced Parameters -> Import
2. Add manually category and subcategory to product from edit product page in backend
3. Update the products with a new.csv file, again going from Advanced parameters -> Import, using a data matching configuration ignoring almost all the columns except reference, stock and price, therefore also ignoring the categories column.
### PrestaShop version(s) where the bug happened
8.1.3
### PHP version(s) where the bug happened
7.3
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
Parafarmacia San Michele s.r.l
--- end body ---
comments :
--- start comments ---
--- end comments --- | 4,407 | 86 |
[
"PrestaShop",
"PrestaShop"
] | This is the step to integrate an alpha version in the core, the theme will be accessible but not used as the default one
- [x] Release the theme with the latest changes into a 0.2.0 version (see this PR https://github.com/PrestaShop/hummingbird/pull/600 - the version needs to be bumped to 0.2.0)
- [ ] Prepare a page in devdocs that explains the technical constraints for this theme (can be empty at first but we need the URL for the following task) The page can later be enriched
- [ ] Explain that the theme is based on bootstrap5 and won't be compatible with all modules until they handle the theme
- [ ] Explain the trick about integrating the Bootstrap Compatibility Layer (we still need to decide if it should be in the core, in the theme or in the module)
- [ ] Integrate hummingbird 0.2.0 into composer, adapt UI tests that don't need to install the theme anymore, integrate a warning popup when the theme is enabled to warn about bootstrap with a link to devdoc for more details (also see this issue https://github.com/PrestaShop/hummingbird/issues/581) | Integrate an alpha release of the theme in the project | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36182/comments | 1 | "2024-05-17T08:21:15" | "2024-06-03T07:32:50" | https://github.com/PrestaShop/PrestaShop/issues/36182 | 2,302,111,971 | 36,182 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Integrate an alpha release of the theme in the project
Issue date:
--- start body ---
This is the step to integrate an alpha version in the core, the theme will be accessible but not used as the default one
- [x] Release the theme with the latest changes into a 0.2.0 version (see this PR https://github.com/PrestaShop/hummingbird/pull/600 - the version needs to be bumped to 0.2.0)
- [ ] Prepare a page in devdocs that explains the technical constraints for this theme (can be empty at first but we need the URL for the following task) The page can later be enriched
- [ ] Explain that the theme is based on bootstrap5 and won't be compatible with all modules until they handle the theme
- [ ] Explain the trick about integrating the Bootstrap Compatibility Layer (we still need to decide if it should be in the core, in the theme or in the module)
- [ ] Integrate hummingbird 0.2.0 into composer, adapt UI tests that don't need to install the theme anymore, integrate a warning popup when the theme is enabled to warn about bootstrap with a link to devdoc for more details (also see this issue https://github.com/PrestaShop/hummingbird/issues/581)
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,299 | 87 |
[
"PrestaShop",
"PrestaShop"
] | ### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
If I delete an address from a user's profile, it doesn't actually delete in the database and therefore my xml has saved addresses that my users don't have.
![Screenshot 2024-05-17 094904](https://github.com/PrestaShop/PrestaShop/assets/156414093/79db01cc-1000-4303-a554-103f9dd13638)
![Screenshot 2024-05-17 095058](https://github.com/PrestaShop/PrestaShop/assets/156414093/5c0bdaa3-21a7-4694-adc8-3ccdca8216f0)
### Expected behavior
When I delete an address from my profile it should also be deleted in the API
### Steps to reproduce
1. Create user
2. Add Address
3. Delete Address
4. Check www.site.it/api/addresses
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_ | Customer addresses persist in the XML even after deletion from FO or BO ( WEBSERVICES ) | https://api.github.com/repos/PrestaShop/PrestaShop/issues/36181/comments | 5 | "2024-05-17T08:11:39" | "2024-05-22T07:40:21" | https://github.com/PrestaShop/PrestaShop/issues/36181 | 2,302,094,736 | 36,181 | This is a GitHub Issue
repo:PrestaShop
owner:PrestaShop
Title : Customer addresses persist in the XML even after deletion from FO or BO ( WEBSERVICES )
Issue date:
--- start body ---
### Prerequisites
- [X] I understand and accept the project's [code of conduct](https://github.com/PrestaShop/PrestaShop/blob/develop/CODE_OF_CONDUCT.md).
- [X] I have already [searched in existing issues](https://github.com/PrestaShop/PrestaShop/issues?q=is%3Aissue+label%3ABug) and found no previous report of this bug.
### Describe the bug and add attachments
If I delete an address from a user's profile, it doesn't actually delete in the database and therefore my xml has saved addresses that my users don't have.
![Screenshot 2024-05-17 094904](https://github.com/PrestaShop/PrestaShop/assets/156414093/79db01cc-1000-4303-a554-103f9dd13638)
![Screenshot 2024-05-17 095058](https://github.com/PrestaShop/PrestaShop/assets/156414093/5c0bdaa3-21a7-4694-adc8-3ccdca8216f0)
### Expected behavior
When I delete an address from my profile it should also be deleted in the API
### Steps to reproduce
1. Create user
2. Add Address
3. Delete Address
4. Check www.site.it/api/addresses
### PrestaShop version(s) where the bug happened
8.1.5
### PHP version(s) where the bug happened
_No response_
### If your bug is related to a module, specify its name and its version
_No response_
### Your company or customer's name goes here (if applicable).
_No response_
--- end body ---
comments :
--- start comments ---
--- end comments --- | 1,537 | 88 |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
Use the Edit dataset card button to edit it.
- Downloads last month
- 2