-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Error when creating asset - 'Purchase cost' cannot be null #2515
Comments
Can you reproduce this on the demo? I can't seem to, nor can I reproduce it locally. |
No I can't... not sure where this is coming from all the sudden. It isn't a huge deal, we can use the workaround of entering $0.00 for assets where the purchase cost is unknown. |
Still very weird that you'd be seeing one thing and the demo would be doing something else. Also I didn't see a stack trace attached - can you paste it in here? |
Or was that the purchase cost.txt? |
Are you running in strict mode? |
Should be in the purchasecost.txt |
Try running:
|
How do I check if strict-mode is enabled? |
Please see the edited SQL above |
The |
As above: |
As usual, you're a genius! I apologize for being a little slow this morning. Our fall semester just started and my brain is slightly fried. I was able to create and asset without a purchase cost successfully! Thank you! |
Expected Behavior (or desired behavior if a feature request)
When creating a new asset, the purchase cost should be marked as either required, or not required. Attempting to save the asset should produce a warning message if required fields are not filled out.
Actual Behavior
Not sure if this is intended, but somewhere in the last week or two, whenever creating an asset without a purchase cost, the page will refresh to a blank Create Asset page without generating any error message in the browser. If I put a purchase cost of 0.00 in, or whatever, the asset will create successfully. Previously, the purchase cost field could be left blank. I have included the logs below:
purchasecost.txt
Please confirm you have done the following before posting your bug report:
Please provide answers to these questions before posting your bug report:
app/storage/logs
and your webserver's logs. AttachedThe text was updated successfully, but these errors were encountered: