#60457: Plugin Dependencies: Running update_option within wp-settings can be
catastrophic for a high traffic site
-------------------------------------------------+-------------------------
Reporter: dd32 | Owner: costdev
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 6.5
Component: Plugins | Version: trunk
Severity: normal | Resolution: fixed
Keywords: has-patch has-unit-tests has- | Focuses:
testing-info commit | performance
-------------------------------------------------+-------------------------
Changes (by costdev):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"57658" 57658]:
{{{
#!CommitTicketReference repository="" revision="57658"
Plugin Dependencies: Remove auto-deactivation and bootstrapping logic.
Automatic deactivation of dependents with unmet dependencies requires a
write operation to the database. This was performed during Core's
bootstrap, which risked the database and cache becoming out-of-sync on
sites with heavy traffic.
No longer loading plugins that have unmet requirements has not had a final
approach decided core-wide, and is still in discussion in #60491 to be
handled in a future release.
The `plugin_data` option, used to persistently store plugin data for
detecting unmet dependencies during Core's bootstrap, is no longer needed.
Follow-up to [57545], [57592], [57606], [57617].
Props dd32, azaozz, swissspidy, desrosj, afragen, pbiron, zunaid321,
costdev.
Fixes #60457. See #60491, #60510, #60518.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60457#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform