You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Concerns with this are that if a user has enabled auto update of plugins new features may not be functional (or worse the plugin may fail) until the admin has visited the backend. To mitigate this conditional code needs to be added to ensure no new features that require the update code to run are used until after it has run.
Running the upgrade process on every page load avoids this concern but does potentially has other side effects for the page load that it runs on (if there is a long upgrade process required the user of that page load may see a delay in loading or a complete failure or error message).
Both have pros and cons and running only during admin page loads received the most votes during the meeting.
The current database update code is contained in the plugin activation hook, however this hook is not fired when a plugin upgrade occurs.
This code should be moved outside of the activation function.
The text was updated successfully, but these errors were encountered: