Skip to content
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

[5.2] Error on saving nested Subform #44168

Open
coolcat-creations opened this issue Sep 30, 2024 · 11 comments
Open

[5.2] Error on saving nested Subform #44168

coolcat-creations opened this issue Sep 30, 2024 · 11 comments

Comments

@coolcat-creations
Copy link
Contributor

Steps to reproduce the issue

When I try to save this nested subform, the entries are saved but still I get the error:

Save failed with the following error: Field 'value' doesn't have a default value
grafik

grafik

If I disable the nested subform no error appears.

Expected result

no error

System information (as much as possible)

The currently installed Joomla! version is "‎5.2.0-rc1-dev" ‎5.2.0-rc1-dev

@brianteeman
Copy link
Contributor

From the information provided I could not replicate the error

@coolcat-creations
Copy link
Contributor Author

Maybe because I updated the site with an update package ? No clean installation...
Not sure how to debug.

@coolcat-creations
Copy link
Contributor Author

I tested it on another site I upgraded from 5.1.4 to 5.2 nightly build and same:
The error appears when data is added into the nested subform (in my case the grid items)

grafik

@brianteeman
Copy link
Contributor

are you sure the problem isnt from the first field where you have not selected an item?

@coolcat-creations
Copy link
Contributor Author

Yes because if I leave the "grid" fields empty the error does not appear and because in my first testing site no other fields exist.

@hayyi
Copy link

hayyi commented Sep 30, 2024

I encountered the same error, but resolved it by changing my database column from non-nullable to nullable, which made the error disappear. I'm not sure if this is related to your issue, but it might be worth checking your database for the stored value

@coolcat-creations
Copy link
Contributor Author

Ok but thats a fresh install of 5.1.4 + Update to RC1, not sure sending the users to the database is a good user experience. Maybe this set to Nullable could be implemented in the update?

@brianteeman
Copy link
Contributor

It should be NULL by default

@coolcat-creations
Copy link
Contributor Author

I confirm it was NULL

@brianteeman
Copy link
Contributor

So it is nothing to do with that then

@coolcat-creations
Copy link
Contributor Author

Agree, but the error is there anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants