-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Frontend: Changing JError to enqueueMessage when access is not permitted (Solves partly https://github.com/joomla/joomla-cms/issues/7812 #7824
Conversation
There's a small concern here I didn't think about before (not trying to block this in case someone gets that impression). In our bootstrap, we define the error handler for JError::raiseError() to ultimately call JError::customErrorPage() which renders the page as a |
@mbabker What do you think? |
|
That's over my head I am afraid. Better close this and let it to someone more qualified. Could you look also at #7825 where the matter is slightly different? |
Added setHeader as suggested by @mbabker |
Looks fine from review. |
Applied patch and looks fine to me as well. Thanks JM |
2 testers OK. RTC This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7824. |
Thank you @infograf768! |
Frontend: Changing JError to enqueueMessage when access is not permitted (Solves partly #7812
See test instructions in #7812
When access is not permitted, in the cases taken care off in this PR, we will get an Error message instead of loading the error.php page.