- Issue created by @aaron.ferris
- 🇬🇧United Kingdom aaron.ferris
From what I can gather, this is related to revision_translation_affected not being set for the various VIDs.
From what I can tell, searching and replacing on a paragraph doesn't create a new parent/grandparent (node) revision.
1. Fresh install of D10
2. Paragraphs - 8.x-1.16
3. ERR - 8.x-1.11
5. Create a new paragraph type
6. Keep it basic, single plain text field
7. Have a content type with an ERR field that can reference the new paragraph, set this content type to create a new revision by default
8. Add a node of this type, with a paragraph, use dummy text for the single field value
9. Create a few revisions just for reference
10. Configure Scanner for this content type and paragraph
11. Search for the string added in step 8
12. Replace with something new
Expected
A new revision should have been created with the replaced values
Actual
Scratch that, a new revision IS created, as can be seen by going to the revisions tab, finding the latest and then iterating +1 - so its more like the revision isn't displayed in the revisions table rather than it not being created.
Compare the above behaviour to a content type with a single text field, every scan and replace in this scenario has the last updated time, revision log, revision etc all nicely in the revisions table.
Not sure if this is config, but I've tried it in a project and a fresh D10 spinup and im seeing the same behaviour.
Active
Code
From what I can gather, this is related to revision_translation_affected not being set for the various VIDs.