Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: allow list mass action update price when price mode is multiprice price #32724

Open
wants to merge 3 commits into
base: 19.0
Choose a base branch
from

Conversation

FHenry
Copy link
Member

@FHenry FHenry commented Jan 20, 2025

On the contrary of #32564 a better solution is to update all multiprice (and display inforamtion message).

As this feature was present, the old fix to avoid it was not ideal. Thie PR allow the feature again in this case and do the correct update.

@FHenry FHenry changed the base branch from develop to 19.0 January 20, 2025 16:34
@eldy eldy added the PR to fix - Conflict or CI error to solve The PHP unit tests return something wrong. Check details to know what to fix or solve the conflicts. label Jan 20, 2025
@FHenry FHenry removed the PR to fix - Conflict or CI error to solve The PHP unit tests return something wrong. Check details to know what to fix or solve the conflicts. label Jan 22, 2025
@@ -829,9 +829,8 @@
//'presend'=>img_picto('', 'email', 'class="pictofixedwidth"').$langs->trans("SendByMail"),
);
if ($user->hasRight($rightskey, 'creer')) {
if (getDolGlobalString('PRODUCT_PRICE_UNIQ') || getDolGlobalString('PRODUIT_CUSTOMER_PRICES')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems there is other cases.
When in dev mode, we see 6 different values in combo for parameter to set the for rules to define price.
The update price was implemented for 2, to if you remove this test, it means you implement it for the 6 cases now, so 4 more cases.
However in htdocs/core/actions_massactions.inc.php, i see you add only one if for case PRODUIT_MULTIPRICES
The initial fix was a protection to avoid bad effect on not yet implement cases, removing it to support more case would be better in develop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants