Join GitHub today
fix(db-upgrade): research DB upgrade issues #3383
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:
Matt will provide better wording for the existing error message, which will link to documentation that @Benunc is currently writing.
Ref #3267 (comment)
The document is published here now: https://givewp.com/documentation/core/frequent-troubleshooting-issues/handling-database-update-issues/ and the short URL is http://docs.givewp.com/troubleshooting-db-updates
We found that reason of most of DB update issue was that Ajax was inaccessible. In that case, background update is not possible. Since we can fire local ajax (on the page), so we can run completely update with local Ajax.
check this link for more information: https://github.com/wordimpress/give/issues/3420