neos/neos-development-collection

BUG: TimeableNodeVisibilityService failing if not all content dimensions are initialized

Aperta

#5774 aperta il 9 apr 2026

 (3 commenti) (0 reazioni) (0 assegnatari)PHP (248 fork)auto 404
BugGood first issue

Metriche repository

Star
 (267 stelle)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

  1. Create multiple dimensions with at least one mapping having not been initialized correctly
  2. Run ./flow timeablenodevisibility:execute
  3. Throws

Expected Behavior

Does not throw and actually handles the visibility changes for the working dimensions correctly.

Steps To Reproduce

  1. Create multiple dimensions with at least one mapping having not been initialized correctly
  2. Run ./flow timeablenodevisibility:execute
  3. Throws

Environment

- Flow: 9.1.0
- Neos: 9.1.3
- PHP: 8.3

Anything else?

Is this intended? In my opinion it could be beneficial to just log and continue so that the service works for the initialized dimensions.

Suggestion for reference: https://github.com/VolkerLieber/neos-development-collection/commit/5ff9751d2e76c45286dda7cb10dc7a689f0545f9

Guida contributor