neos/neos-development-collection

BUG: TimeableNodeVisibilityService failing if not all content dimensions are initialized

Open

#5,774 opened on Apr 9, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)PHP (248 forks)auto 404
BugGood first issue

Repository metrics

Stars
 (267 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Contributor guide

Research direction
Examine the TimeableNodeVisibilityService class, specifically the method that iterates over content dimensions. Identify where uninitialized dimensions cause an exception and implement try catch with logging for each dimension to allow the service to continue processing others.
Tech stack
php
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PHPFlow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65