Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Missing document node leads to exception when opening /neos/content?node=... #3766

Open
grebaldi opened this issue Apr 18, 2024 · 1 comment
Labels
9.0 Bug Label to mark the change as bugfix Regression A problem introduced by a recent change to the code base

Comments

@grebaldi
Copy link
Contributor

Description

When a user opens the UI directly via /neos/content?node=... and the document node (as identified by the node query parameter in the URL) cannot be found, the user is presented with an exception.

It is hard for the user to escape this. They would need to remove the node query parameter from the URL.

Steps to reproduce:

  1. Create a new document node
  2. Discard workspace via ./flow workspace:discard [workspace-name], while leaving the UI open
  3. Reload the UI (via Browser refresh)
  4. Exception happens

Expected Behavior

In Neos 8.3, the user is automatically redirected to the site node, if the document node cannot be found. Neos 9.0 should do the same thing.

Affected Versions

Neos: 9.0
UI: 9.0

@grebaldi grebaldi added Bug Label to mark the change as bugfix 9.0 Regression A problem introduced by a recent change to the code base labels Apr 18, 2024
@mhsdesign
Copy link
Member

Strongly related to neos/neos-development-collection#4345

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9.0 Bug Label to mark the change as bugfix Regression A problem introduced by a recent change to the code base
Projects
None yet
Development

No branches or pull requests

2 participants