-
Notifications
You must be signed in to change notification settings - Fork 12
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
Exception when not page found on netgen/admin-ui-bundle": "^2.1.4 #19
Comments
Hi @damaya, On what pages you get the exception? Admin UI 404 pages should display legacy error pages by default. |
Hi @emodric thanks so much for your answer:
We have a replica of our staging site without the NetgenAdminUI Bundle, the 404 error pages works as expected and in the same way as the site with the AdminUI, but without the flooding of error logs. Thanks in advance for your time and your help. |
You can tune what goes into your logs in Monolog configuration: https://symfony.com/doc/current/logging.html But, you're saying that in regular 404 errors, the ones not related to Netgen Admin UI, you do not get an entry in your log file, but only when using Netgen Admin UI? That sounds a bit weird. For me, when accessing a non existing page inside Netgen Admin UI, no error is written to the log, neither in What version of Legacy Bridge are you running? |
Hi there, recently we updated the error handling in our site to change redirects to an external static error site 404.mysite.com, to an internal error page (twigBundle view/exception) with response _404 which is the expected behavior.
However, we noticed an exception:
request.ERROR: Uncaught PHP Exception Netgen\Bundle\AdminUIBundle\Exception\NotFoundHttpException: "Not Found" at /home/ubuntu/mysite/vendor/netgen/admin-ui-bundle/bundle/EventListener/LegacyResponseListener.php line 62 {"exception":"[object] (Netgen\\Bundle\\AdminUIBundle\\Exception\\NotFoundHttpException(code: 0): Not Found at /home/mysite/vendor/netgen/admin-ui-bundle/bundle/EventListener/LegacyResponseListener.php:62)"} []
Could you please enlight us how to add a config or override to avoid this exception?
Thanks in advance.
The text was updated successfully, but these errors were encountered: