#110530Workspace publishing treats elements from other pages as dependencies
Description
If a link field in a flexform references an unpublished content element or page, then that referenced record is considered a workspace dependency and is published automatically together with the referencing element (… which contains the flexform-link-field). This can lead to the unexpected behavior that a seemingly unrelated element from another page (or the page itself) still in the editing stage is published in the background without proper review.
Example:
- Page A is in draft workspace and has never been published.
- user adds a content element with a flexform that contains a link field to Page B
- user references Page A in that link field
- user publishes Page B
This leads to Page A being published as well in the background, without any information to the user.
Note that in our tests, this was also reproducible on TYPO3 v13, which didn’t use the new event, but seems to have a similar behavior.
Reviews 2
- 14.3 97373[TASK] Increase test coverage of workspace dependency resolving
- main 97337[TASK] Increase test coverage of workspace dependency resolving
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[BUGFIX] Workspace publishing treats elements from other pages as dependencies Resolves: #110530 Releases: main
Related issues 3
History 6
-
Simon Praetorius changed Related to #108992 <span data-processor="relativetime" data-value="2026-08-24T15:41:48+00:00" > 08/24/26, 15:41 </span>
-
Simon Praetorius changed description <span data-processor="relativetime" data-value="2026-08-24T15:42:53+00:00" > 08/24/26, 15:42 </span>
-
Simon Praetorius commented <span data-processor="relativetime" data-value="2026-09-10T13:51:35+00:00" > 09/10/26, 13:51 </span>
-
Simon Praetorius changed Related to #111337 <span data-processor="relativetime" data-value="2026-11-04T11:08:40+00:00" > 11/04/26, 11:08 </span>
-
Simon Praetorius commented <span data-processor="relativetime" data-value="2026-11-04T17:21:17+00:00" > 11/04/26, 17:21 </span>
Step 2 is implemented in #111343. With that in place, Step 1+3 can be accomplished on a project level by using the extended event. Also, the Core can define consistent/configurable (?) behavior for v15.
In my opinion, a reasonable default would be:
- Parents require their children (soft references to be discussed, I personally would skip them)
- Children only require their parents in a few special cases (maybe inline relation)
- FlexForm and non-FlexForm fields behave the same
-
Simon Praetorius changed Related to #111343 <span data-processor="relativetime" data-value="2026-11-04T17:21:48+00:00" > 11/04/26, 17:21 </span>
Step 1: Extend workspaces dependency resolving to get unified behavior between regular fields and flexform fields (= all dependencies should be available no matter where they are referenced).
Step 2: Extend
IsReferenceConsideredForDependencyEventto have enough context information to decide which dependency should be included and which should be skipped.Step 3: Add configuration option (e. g. UserTSconfig) to be able to choose between different strategies.