You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a resource creation or update page, when you add media (using the CuratorPicker) to a related model that is in a repeater there is an SQL error when saving. The changes to the related model do save but after that it returns a server error, and other details of the main resource do not save.
While trying to recreate this error on a minimalized setup I realized that it doesn't happen while using SQLite, but started happening when switching to Postgres (version 16). No idea about MySQL.
On SQLite there was a different bug (with no error): on the update page, after saving changes, the attached media entries on the related model(s) disappear from the curator picker. If you refresh the page they load back, however if you save again instead, they get detached from the related model(s). This might or might not be related, I have not investigated this further since I do not use SQLite usually.
Expected behavior
To save changes without an error.
Steps to reproduce
Using the reproduction repository:
Setup repo as you would an existing filament project, then migrate the database. (Use postgresql database)
1a. You can find a test user and tenant in the DatabaseSeeder.php, so you can use db:seed if you want.
Upload some media files.
Open the people resource, create a new person. Switch to the timeline tab, add a timeline entry, add some media to it, and then save the resource.
Filament Version
3.2.127
Plugin Version
3.6.14
PHP Version
PHP 8.3
Problem description
On a resource creation or update page, when you add media (using the CuratorPicker) to a related model that is in a repeater there is an SQL error when saving. The changes to the related model do save but after that it returns a server error, and other details of the main resource do not save.
While trying to recreate this error on a minimalized setup I realized that it doesn't happen while using SQLite, but started happening when switching to Postgres (version 16). No idea about MySQL.
On SQLite there was a different bug (with no error): on the update page, after saving changes, the attached media entries on the related model(s) disappear from the curator picker. If you refresh the page they load back, however if you save again instead, they get detached from the related model(s). This might or might not be related, I have not investigated this further since I do not use SQLite usually.
Expected behavior
To save changes without an error.
Steps to reproduce
Using the reproduction repository:
1a. You can find a test user and tenant in the DatabaseSeeder.php, so you can use db:seed if you want.
Reproduction repository
https://github.com/nyerslaszlo/curator-bugs
Relevant log output
The text was updated successfully, but these errors were encountered: