Problem/Motivation
Before #2987444: Ajax errors are not communicated through the UI there was no way to know via the UI that an Ajax error occurred. The only evidence of it happening was in the JS console.
In #2987444: Ajax errors are not communicated through the UI, functionality was added so if there is an Ajax error, this is made evident in the UI with the following message generated by the messages API.
Oops, something went wrong. Check your browser's developer console for more details.
While the specifics of the error still require opening the JS console, the fact that an error took place is actually apparent, which is a big improvement.
Because it's difficult to find the ideal wording for pretty much anything this issue was opened to facilitate potential improvements to the content of that message. If a largely-agreed-upon better option emerges here, we can update core to use that phrasing instead. There were clear benefits to getting that functionality into core as soon as possible with acceptable messaging, and deferring the composition of ideal messaging to a followup.
Proposed resolution
- Add a new (required) text entry box at /admin/config/development/logging for configuring the contents of the error message to show on AJAX exceptions.
- Optionally agree on a better default message.
Remaining tasks
Review MR.
User interface changes
New form element on the form at /admin/config/development/logging
API changes
None
Data model changes
New 'ajax_error_message' property added to system.logging config object.