In the 8.6.2/8.5.8 security release, core intentionally introduced a backwards compatibility break. A new method was added to StateTransitionValidationInterface and workflow participants has an implementation of this interface, but with no implementation.
As it stands in those releases, we don't have enough information to properly implement the new method, so the ability to fix this is contingent upon #3007716: Security update introduces breaking changes to content moderation landing in core.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | interdiff-3007906-3-6.txt | 1.25 KB | kevin.dutra |
| #6 | security-bc-break-3007906-6.patch | 1.71 KB | kevin.dutra |
| #3 | security-bc-break-3007906-3.patch | 1.33 KB | kevin.dutra |
Comments
Comment #2
kevin.dutra commentedComment #3
kevin.dutra commentedBased on where the core patch is headed, here is a simple implementation.
Comment #4
kevin.dutra commentedComment #5
kevin.dutra commentedHmm, this doesn't quite work.
getValidTransitions()doesn't always correctly identify the current state of the post when validating and so it doesn't generate the correct list.Comment #6
kevin.dutra commentedHere we go, now the initial state of the entity is ensured.
Comment #9
jhedstromSince this resolves a fatal error I'm committing it. The tests that are failing appear to be new issues with core deprecations. These will be addressed in #3047489: Fix deprecations.