-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Cloned fields do not save data when used in an Entry #57
Comments
I'm also getting this error on 3.1.8. It seems like there is an issue where a cloned matrix field is taking the subfields from the original, not cloning them. Looking at the database directly, it did not duplicate the subfields. It also seems like depending on how you interact with the back end, they can switch back and forth from belonging to the original matrix field and the cloned one. |
FYI, Field Manager isn't fully tested in 3.1.x, but will be sorted very soon (ASAP) and in the next release. The underlying field API has changed a bit in 3.1.x |
Same thing happened here. Now the field I initially cloned is somewhat corrupted and won't let the entry page save... Can't seem to be able to delete the corrupted field either... |
Should be fixed in https://github.com/verbb/field-manager/releases/tag/2.0.5 |
Description
A Cloned field is unable to save data into it. I had a short back and forth with Pixel and Tonic who were able to give this information, when a field I'd previously Cloned was not saving content in an Entry...
I hadn't created the new Matrix field manually, I'd used Field Manager's Clone feature.
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: