neos/content throws 500 if no site exists and menu drawer is not accessible
#3721
Labels
Comments
6 tasks
mhsdesign
added a commit
to mhsdesign/neos-development-collection
that referenced
this issue
Feb 16, 2024
After the previous adjustments the `SiteDetectionFailedException` will only be thrown in fewer cases, the only real reproducible the `/neos/content` route. The rendering group is a bit overkill only for this thing and also might swallow 500 errors that should be presented as is and not wrapped by a vibrant welcome page. The ui should be adjusted instead. neos/neos-ui#3721
neos-bot
pushed a commit
to neos/neos
that referenced
this issue
Feb 16, 2024
After the previous adjustments the `SiteDetectionFailedException` will only be thrown in fewer cases, the only real reproducible the `/neos/content` route. The rendering group is a bit overkill only for this thing and also might swallow 500 errors that should be presented as is and not wrapped by a vibrant welcome page. The ui should be adjusted instead. neos/neos-ui#3721
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There will be a sitedetection failed exception in the
neos/contentroute when the backend controller cannot find a site.In 8.3 we dont have a graceful error as well only something like
Site doest not exist for current user: #3182We should probably redirect to some other available module, or at least keep the backend frame around and not destroy everything.
Originally posted by @mhsdesign in neos/neos-development-collection#4717 (comment)
The text was updated successfully, but these errors were encountered: