-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
"Purchase cost" input is not interpreted correctly #2383
Comments
Thank you :) |
Snipe, licenses, components, acessories and consumables has exactly the same bug. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
When editing an asset, the price will be formatted with comma (,) for thousand seperator and dot for decimals. When this is inputted, it should save it correctly in database, however it replaces the purchase cost with the leading integers. For example the price of 8,975.00 will be converted to 8.
The input works correctly when inputting the cost as integer, 8975 will result in correct behavior. Any assets thats is edited will contain the formatted number, hence be changed to a wrong value.
Please provide answers to these questions before posting your bug report:
Version v3.1-84-g139325d
CentOS 7, Apache, PHP5.6 from Remi repository, MariaDB
Manual installation with git clone
No error is shown, just wrong data
Happens on /hardware/XXX/edit - possibly during clone and creation as well (not tested)
Same thing happens on Snipe-IT Demo.
I have not touched the database manually.
Steps to reproduce problem:
The text was updated successfully, but these errors were encountered: