-
-
Notifications
You must be signed in to change notification settings - Fork 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
3.6.5 -> 4.0.4 post update - Company cannot be NULL (not selected) #4044
Comments
update: I can't seem to update any asset - page flashes and reloads original content.
|
I can't pretty much do anything. I believe the issue comes from company ID (I don't have multiple companies) seems like code is trying to use non-existent field in database. My migrations (from 3.6.5) were successful. If I run migrate script again I get 'nothing to migrate' update: I created a (single) company. If I edit asset/user and select this company, it works (saves and assigns the asset/user to that company. But if company is not selected, error occurs. |
What mysql version are you using? |
5.5.44-MariaDB |
I could have sworn we pulled out all of the foreign key constraints ages and ages ago. :-/ |
Try running:
from a mysql prompt. |
Thanks @snipe - that solved the problem with users. I guess now repeat for assets table? Any other tables i need to drop the foreign keys? |
The latest from master has a migration that should fix this issue for everything. |
I hate to bring this one up back to life, but I've got another one of these. When I try to create an asset type:
|
Expected Behavior (or desired behavior if a feature request)
user updated and return to previous page
Actual Behavior
500 error message displayed
Please confirm you have done the following before posting your bug report:
Please provide answers to these questions before posting your bug report:
4.0.4
CentOS 7
manual install
N/A - demo does not allow saving updated user information - but does not crash
app/storage/logs
and your webserver's logs.The text was updated successfully, but these errors were encountered: