draft and entry not propagated correctly in certain conditions

[vnali]

yesterday some issues mentioned on discord.
there are some paths to reproduce those:

Entry not found error

1. create a section with propagate to all sites method for site 1
2. click +new entry, add title, leave editing entry or even click save draft
3. add another enabled site -site2- for that section
4. click to edit that entry and go to site 2.
   it throws entry not found error

entry -current state- not propagated

1. create a section with propagate to all sites method for site 1
2. click +new entry, add title, create entry
3. edit that entry, change the title, then leave the entry
4. add another enabled site -site2- for that section
5. click to edit that entry for site1, you can't see enabled status for site2 on site status on right side
6. click to edit that entry for site2, you can see enabled status for both site

only draft for an entry not propagated

1. create a section with propagate to all sites method for site 1
2. click +new entry, add title, create entry
3. edit that entry, change the title, click create draft
4. add another enabled site -site2- for that section
5. you can see current status is propagated correctly
6. you can see that draft is not propagated for site2

also with changing path to create entry (applying draft/creating draft/leaving without saving and ...), we can see similar behaviors for drafts, revisions and ...

Additional info

• Craft version: 3.7.33

[timkelty]

@vnali Thanks for reporting!
Fixed for the next release: 681b342

[vnali]

@timkelty thanks. i applied and tested this fix -actually deleted redundant lines deleted by Brandon- on local and it works for all 3 mentioned scenarios but if i go further i can't see revisions propagated too:

1. create a section with propagate to all sites method for site 1
2. click +new entry, add title, create entry
3. edit that entry, change the title, click create draft and apply draft, then change title -with or without clicking create draft-
4. add another enabled site -site2- for that section
5. you can see current status and drafts are propagated correctly
6. you can see the revisions are not propagated for site2

[timkelty]

@vnali Revision are addressed in Craft 4, but is a breaking change.

For the next Craft 3 release, we've added a --revisions flag to the resave/entries cli command, so following your section changes, you can run:

craft resave/entries --section=my-section --revisions

[vnali]

@timkelty after applying new changes to resave controller, it throws 'Skipped resaving .... because it's a revision' which it is related to third argument here explicitly set to true.

[timkelty]

@vnali d'oh…try now :)

[vnali]

It works. thanks!

[timkelty]

@vnali thanks for the thorough report!