Closed benjaminkohl closed 5 years ago
We tracked down the cause for this in one entry and I think we'll find similar cases throughout the site. We had a text field with a length limit on it and the entry had been previously saved with a value that was too long for that field. It is possible that the long text value came through Feed Me.
If we tried to shorten that value via the CP form and save the entry, the same error described above occurs—maybe because it is trying to save a copy of the entry in its original state? I manually fixed the value in that text field using a DB query then we were able to re-save the entry from the control panel without getting an error.
If we tried to shorten that value via the CP form and save the entry, the same error described above occurs—maybe because it is trying to save a copy of the entry in its original state?
That would make sense if versioning had recently been turned on for the section, so Craft needed to save an initial revision for the entry before saving a new one. However I just tried reproducing locally, with these steps:
When doing that, a new revision is created with the field’s original value, even though it didn’t validate by the time the revision was created. No errors or anything.
Do you happen to have a database backup that I could reproduce your error with? If so can you please send that and your composer.json
& composer.lock
files over to support@craftcms.com?
This is still an issue. I used Feed Me to import posts from another blog. This specific entry had a field value that was longer than the allowed maximum. I can't save that entry, even if the new value is shorter.
@nicbou Please ensure you are running the latest version of Craft and Feed Me. If the issue still occurs, then please post a new issue over at https://github.com/craftcms/feed-me.
Description
We updated a client site to Craft 3.3.4.1 this morning and now they are unable to change and save many of their entries. When they click save, the request errors out. We checked the log and apparently the element is being duplicated as part of the revisions logic and it is not passing validation. An exception is thrown but it isn't handled gracefully so we don't know where to start looking into what isn't passing validation. The entries in question were saving just fine prior to the update.
Here is the entire stack trace:
Steps to reproduce
Additional info
Amazon S3 1.2.5 Button Box 2.0.4 Cache Flag 1.0.3 CP Field Inspect 1.0.6 Feed Me 4.1.2 Freeform 3.4.1 Hvrcraft 3.0.0-beta.4 Imager v2.2.0 Inventory 2.0.3 Linkit 1.1.11 Link Vault 3.0.5.3 Many to Many Field Type 1.0.2.2 Maps 3.6.4.3 Position Fieldtype 1.0.14 Redactor 2.4.0 Relabel 1.3.3 Relations 1.2.1 Retour 3.1.24 SEOmatic 3.2.24 Sidebar Entry Types 1.0.3 Spoon 3.3.7 Super Table 2.3.0 Typogrify 1.1.18