Add database migration for disabling autoload for our options

[swissspidy]

Task Description

Noticed while reviewing #13700.

On my local site our options were all autoloaded for some reason. They shouldn't be; especially when we do the cache priming.

We could add a database migration that runs once to call wp_set_options_autoload() for all our options to disable autoloading.

Not sure if it's really needed though and whether it's worth it.

Also: the function is only available in WP 6.4+

[Swanand01]

Hi @swissspidy, should we get started with this since we have bumped up WP version requirement to 6.4?

[swissspidy]

Counter question: on your development site, are the Web Stories options set to autoload or not? I'm trying to understand whether this was an issue only on my site, or if it affects other sites as well.

In theory they shouldn't be, in which case we wouldn't really need this migration (except for peace of mind)

[Swanand01]

Counter question: on your development site, are the Web Stories options set to autoload or not? I'm trying to understand whether this was an issue only on my site, or if it affects other sites as well.

In theory they shouldn't be, in which case we wouldn't really need this migration (except for peace of mind)

I can see some options being autoloaded:

[swissspidy]

Interesting 👀

Let me check this on some other sites to see if there's a pattern.