-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 categories search plugin #7073
Conversation
Sorry can you add a full stop at the end
On 30 May 2015 at 18:00, Nicola Galgano notifications@github.com wrote:
Brian Teeman |
You have a binary patch file for some reason :P sorry! |
no, only my mistake |
Please add as the one in en-GB.ini is a fall back
|
removed Whitespace found at end of line 181
as requested #7073 (comment) the side one
as requested #7073 (comment) the admin one
@infograf768 strings added |
Do we need this string also in administrator/language/en-GB/en-GB.ini ? Or is only the frontend used as fallback? I wonder if we cna extend the error message a tiny bit. Currently there is absoluetly no value in it. You could as well show nothing because the user can probably figure out himself that there was some error. |
So don't forget the full message is going to be stored in the logs. This is a message targeted at the frontend user who wants to see content and doesn't care where the error message comes from. That's how me and Brian came up with this string |
Yeah, I'm aware it's going to be logged. I would even suggest to extend the message and include something like the existing one for JLayout (?): So I would even use something like: Don't show the actual error, but give the user (who may be the admin!) a clue what happend. |
We could even tell in the message that the actual error was logged. That would be most helpful to the admin. |
I agree having a "report the error below" might help - but then we need to have something significant the backend admin understands it but enough that the frontend user doesn't understand it... |
He is allowed to understand. That's not a problem at all as long as no sensible data is shown. |
if i understand well, @Bakual you want a little bit more informative msg |
Sorry but there is zero value telling a guest that something has been
|
There is even less value in showing "There was an error" when the guest already can see that by looking at the page. |
ok, i'll wait till a final decision will be taken, where all agree... |
Just do what @wilsonge says. He is in charge 😄 |
Just in case, it works OK This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7073. |
After having a chat with @wilsonge we settled for |
thx for take care of these |
No THANKYOU for going through the CMS and finding all these places where we weren't catching exceptions! |
It's a pleasure to work with you folks, I like costructive critic to mY dirty fixes... |
…oomla#6714. Closes joomla#6715. Closes joomla#6716. Closes joomla#6717. Closes joomla#7073.
added the generic message string "There has been an error" as suggested in #6710