Skip to content

feat: Update for Neos 9#23

Draft
paxuclus wants to merge 6 commits into
mainfrom
feat/neos9
Draft

feat: Update for Neos 9#23
paxuclus wants to merge 6 commits into
mainfrom
feat/neos9

Conversation

@paxuclus

Copy link
Copy Markdown
Member

This removes the old yaml based configuration so only node based error pages can be used from now on

This removes the old yaml based configuration so only
node based error pages can be used from now on
@paxuclus paxuclus self-assigned this Oct 31, 2024
paxuclus added 5 commits April 3, 2025 20:44
# Conflicts:
#	Classes/Configuration/ErrorHandlerConfiguration.php
#	Classes/Configuration/NodeBasedConfiguration.php
NodeBasedConfiguration::getSiteNodes() silently found no error page
configuration at all on installations with zero content dimensions
configured, which is a valid and fairly common setup (single-locale
sites). combineAllDimensionSpacePoints() only ever produced a result
by combining pairs of dimension values, so with no dimensions the
combination loop never ran and returned an empty set; the outer
lookup then never yielded a single site node, and getConfiguration()
came back completely empty with no error/warning of any kind (not
even the --verbose per-site output).

Also fixes two issues found while getting the zero-dimension case to
actually run end-to-end:
- VisibilityConstraints::frontend() doesn't exist on this
  neos/contentrepository-core version; replaced with the documented
  Neos-specific equivalent (NeosVisibilityConstraints::excludeRemoved()
  merged with ::excludeDisabled()).
- findChildNodes() against the shared "Neos.Neos:Sites" root returns
  every site's node, not just the current one being iterated in the
  outer loop, so with N sites this reprocessed (and re-fetched/re-saved
  the error page for) each site N times over. Filtered to the matching
  child node name.
…sion

NodeAggregate::getNodeByCoveredDimensionSpacePoint() doesn't exist on
this neos/contentrepository-core version, which made errorpage:generate
fail to resolve every configured error page's source URI. Per
NodeAggregate's own documented usage, look the node up by first
resolving the occupied origin for the covered dimension space point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants