- Issue created by @sakshi@17
- 🇮🇳India sakshi@17
Added the revised patch to cover the updation and deletion of the scheduled entity.
- 🇺🇦Ukraine vitaliyb98
Thanks for reporting this issue!
I tried to reproduce the problem and investigated why it might occur. It looks like there may be some additional configuration or extra steps involved that are not mentioned in the instructions.
The main point is that when you change the node status to Draft, from that moment all subsequent changes are applied to the old revision of the node including those in the Scheduled moderation state change section. If you then schedule this draft revision to transition to Published, it will not appear in the Scheduled Publish tab/view, because the scheduled moderation is linked to the draft revision rather than the currently active revision.
Could you please provide a more detailed, step-by-step instruction on how to reproduce this issue? That would help to better understand the exact conditions under which the error occurs.
- 🇺🇦Ukraine vitaliyb98
I also reviewed the patch and noticed a couple of issues:
1. There is a duplicated line of code.
$states = $entity->get($field)->getValue(); + $states = $entity->get($field)->getValue();2. There may be a problem with mixing data between the current revision and the latest revision that you are trying to load.