-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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 Fatal Error PHP 8 : division by 0 #25384
Merged
eldy
merged 2 commits into
Dolibarr:17.0
from
atm-lena:17.0_FIX_PHP8_FatalErrorDivisionByZero
Jul 28, 2023
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't you think we should, instead of just doing
line_cost = $obj->min_price
replace each qy with 1 if not defined. So we would get
$line_cost = $obj->min_price / (empty($obj->qty) ? 1 : $obj->qty) * (empty($sub_bom_line->qty) ? 1 : $sub_bom_line->qty) * (empty($line->qty) ? 1 : $line->qty)
;Because a not defined qty means 1 i think ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if a qty is defined as 0 (not quite sure if it's possible in this case) ?
But with the check on empty you will assume that his value is 1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On BOM, having a qty of 0 of a product should be same than not having the line at all. So this should not happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's important to allow to have a quantity of 0 for example for product for which we don't know the exact quantity we are going to use. We need to have it in the BOM but we don't know the qty so we can put 0 just to have the information that we need this product. Also it can be usefull for products (like consumables) we need only if something happens during the production, it's good to have it in the BOM so the operator can consume this product if needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Note that currently on v18, using a 0 qty is not possible. For your use case, we need to enter 1
Not also that you can add product on the fly during the production even if not present into the BOM.