-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[5.4] Error page fix: prevent modules rendering in the incomplete Application #46272
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
base: 5.4-dev
Are you sure you want to change the base?
Conversation
Co-authored-by: Brian Teeman <[email protected]>
Co-authored-by: Brian Teeman <[email protected]>
|
As far as I can tell a module assigned to error-500 is still not displayed I forced the error page with |
|
Did you placed the Exception in the place as in the test description, before doExecute method or after? |
|
Yes. I see the correct error page but not with the error-500 module |
|
Ah sorry, I read your comment incorrectly. Yes that is correct, there will be no error-500 module. The idea of the PR is do not render any module in such situations. |
Pull Request for Issue # .
Summary of Changes
Our error page contains modules, however the module renderer will crash when error happen before the Application initialization is completed. This leads to mixed error report by Symfony error handler.
Testing Instructions
Apply patch.
Add
throw new \Exception('Test error');around herejoomla-cms/libraries/src/Application/CMSApplication.php
Lines 301 to 304 in ffe1acf
But before
$this->doExecute();And then visit the site and the administration area.
Actual result BEFORE applying this Pull Request
You will get a red page of Symfony error handler.
If you have debug enabled it will show unrelated error (something about access to undefined method or kind of that) and 2 exception traces.
Expected result AFTER applying this Pull Request
You will get Joomla error page.
If you have debug enabled it also will show the error trace.
Link to documentations
Please select: