-
Notifications
You must be signed in to change notification settings - Fork 874
Performance: convert jetpack_blocks_disabled option to a module #39441
Copy link
Copy link
Closed
Labels
EnhancementChanges to an existing feature — removing, adding, or changing parts of itChanges to an existing feature — removing, adding, or changing parts of it[Focus] BlocksIssues related to the block editor, aka Gutenberg, and its extensions developed in JetpackIssues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack[Focus] Performance[Plugin] JetpackIssues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/
Milestone
Metadata
Metadata
Assignees
Labels
EnhancementChanges to an existing feature — removing, adding, or changing parts of itChanges to an existing feature — removing, adding, or changing parts of it[Focus] BlocksIssues related to the block editor, aka Gutenberg, and its extensions developed in JetpackIssues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack[Focus] Performance[Plugin] JetpackIssues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/
Impacted plugin
Jetpack
What
Transform jetpack_blocks_disabled to a module
How
The
jetpack_blocks_disabledoption exists to provide a way for a site admin to enable/disable Jetpack blocks via the UI, which is basically the same concept as Jetpack modules.jetpack_blocks_disabledis only set when the toggle has been used, which means it is not cached and a source of regular db calls. Transforming it into a proper module would allow it to piggyback with the modules option call/cache.Follow-up of #39422