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
fix(db-updates): provide users with actionable steps to resolve db-updates issues #3267
Comments
@Benunc @mathetos Please correspond with @ravinderk and/or @raftaar1191 to decide the communication for DB errors. |
I'll meet with @ravinderk on this soon and we'll report back here with a call summary. |
Call Summary Consensus is that the current error message is the only place in which we can ensure that there is an actual problem. It is a vague error simply because we don't yet have enough information to know with certainty exactly why the DB update fails; it could be a lot of different things. In order to add better logic we need more information. We can't yet perfectly replicate DB update problems with Memcache for example. We can't yet perfectly replicate DB update problems with admin-ajax exactly as it happens in some of these environments. We don't know what types of server security prevents the database tables from being created. Without this information we can't have logic in the plugin that checks for these problems and gives better error messages. To that end:
That's our plan moving forward. For this issue, let's keep it focused on a better error message that points to existing docs (that are not yet finished). Docs issue here: |
Per dev team discussion, for 2.1.5 we will add @Benunc documentation link to any error that appears during DB update. We will look into further improvements in future releases. |
This is the shortlink for that new Doc as a reference: |
@mathetos Link added to notices |
User Story
As a
give administrator
, I wantclear error messages with actionable steps to take in the event of database update stalling out
so thatI can resolve it myself, or if I need to escalate it to support, I can give the support technicians a head start
.As a
support technician
I wantto limit the number of tickets that are database update-related
andhelp only the customers whose servers/web hosts are really not letting them run db updates.
Current Behavior
I (the user) currently am greeted with "please contact support" or database updates that simply do not complete.
Expected Behavior
I expect for database updates to fail gracefully, and provide me with several options to resolve the issue myself before contacting support.
Possible Solution
Acceptance criteria
Related:
https://secure.helpscout.net/conversation/587252948/19027/
The text was updated successfully, but these errors were encountered: