It seems that the "root" cause may come from any module which "wrongly" affect translation data on save.
I've added #3412626: Difference between the 'Paragraphs (stable)' widget and the 'Paragraphs Legacy Asymmetric' widget → as related, since after switching my paragraphs fields to the Paragraphs Legacy Asymmetric widget, I can't reproduce the issue on new page/content.
It seems to be related to 🐛 Content moderation workflow changes against one language affect translations too Needs work
So after switching my fields to the Paragraphs Legacy Asymmetric widget, it fixed the related issue. Ssaving a draft in a translation created a new revision in the original language, based on the last published version (ignoring more recent drafts in that language).
@peterwcm thanks a lot for the workaround. I didn't test the patch yet, but the "workaround" gave me back a more stable paragraphs : )
A client reported this issue on a production website. It was certainly working "before", but i don't know which update triggered this.
One thing, it happens for me even as admin, so at least for my case it's not related to the user without "bypass node access" related issue.
Got this issue today. It breaks webform submission download. If a user uploaded a file it's impossible to access it from the backend, even when connected as administrator.
The patch in #15 fixed the issue (and the file is still protected from anonymous user view : )
I was testing mercury and and was sad to see it didn't work with sdc. So thanks a lot sethhill for this patch, it's working fine now
I also confirm this merge request fixed the issue.
Thanks @nuuou, the merge request worked perfectly for my use case. I was trying to index keywords, and this patch made it work nicely : )
I've got the same issue. I've defined a global "search" exposed form in block, which is added to the header of the website. Then on all 404 pages it shows the same error.
I've tried the patch in #12 and it went nicely, even if I'm still using the 6.x version. The patch fixed the issue, at least there is now no more errors.
I tried to reroll the merge request for drupal 10.2 but I'm not sure of the correct workflow, especially since the current merge request is based on the 10.1 branch.
Here is the commit I made: https://git.drupalcode.org/issue/drupal-2325899/-/commit/d665b876f6c1ab2...
And I'm attaching a patch which should hopefully work on 10.2.6
Here is a patch file with the change from the merge request.
I don't know why patch in #7 didn't apply in my setup so here is a simple reroll of it
I wasn't able to apply patch in #24 to the current 6.0.0 so here is a reroll.
I confirm the patch in #2 fixed the same issue as described in op. Thanks @thatguy !
Hi cilefen, thanks I confirm this was a duplicate, the patch in the related issue fixed the export.
idflood → created an issue.