-
-
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
Custom Field - List Box v.3.4.0 fail? #2516
Comments
That looks like your laravel logs, not your browser console. Can you please tell me if there are any errors in your browser console? |
https://localhost/hardware/models/3/custom_fields?_token=3nnTfmfgM1IOgB3cfuFqJwiVJyjMUfudBAPsPt6L Failed to load resource: the server responded with a status of 500 (Internal Server Error) this is the error in the console |
Please paste me the first 20 lines of C:\xampp\htdocs\snipeit\storage\framework\views\957bb22ab9d4f68dff4136ab7edfe68ba9a0d8bb.php |
|
First 20 lines please. |
Ah, I see - you didn't comment them as code, so they were invisible. |
What's actually on line 20 in that file? |
nothing.. |
this is in line 19 |
Can you show me the value in the |
where can i look for it? sorry i am not so familiar with everything |
In your database. |
the asdfgghghg thing is just some random name haha because i wanted to test it first |
If that were true, it shouldn't be erroring on the checkbox code. It would never trigger that branch in the if/else logic. |
Should be fixed on current dev |
it's working - nice one |
Expected Behavior (or desired behavior if a feature request)
When i create an asset it should show my asset modell with custom fields.
Actual Behavior
After setting up a custom field list box for my asset modell it doesn't show the custom fields in asset-create. After i deleted my custom field list box it shows the custom fields in asset-create
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.The text was updated successfully, but these errors were encountered: