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
Handle DB errors in users latest module #6666
Conversation
@test This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6666. |
Not sure if this should get merged with regards to discussion on #6710 |
@test OK, no frontend SQL error showing internal information (though it would be nice to show a generic error... instead of eating the excepton) This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6666. |
@alikon can you add the generic message also here? Like: https://github.com/joomla/joomla-cms/pull/6700/files |
added the generic message as requested
@anibalsanchez , @zero-24 thx for reporting |
RTC Thanks 😄 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6666. |
…la#6632. Closes joomla#6691. Closes joomla#6699. Closes joomla#6700. Closes joomla#6707. Closes joomla#6708. Closes joomla#6665. Closes joomla#6666. Closes joomla#6675. Closes joomla#6676.
updated to handle DB errors like #6612 ,#6632, #6665 and for #6591
Testing info
set the db offline
or
simulate a db error
change line 37 from
to
before patch you get
after you get
the module is not displayed