[wp-hackers] Plugin best practices: wp_options and storing custom
viper at viper007bond.com
Wed Apr 2 21:40:20 GMT 2008
Which is best for 99% of cases I think. For the plugin authors that know
they are storing large amounts of data in the options table, they can
manually turn it off.
On Wed, Apr 2, 2008 at 2:38 PM, Austin Matzko <if.website at gmail.com> wrote:
> On Wed, Apr 2, 2008 at 5:28 PM, Otto <otto at ottodestruct.com> wrote:
> > That only gets the options with the autoload column set to "yes".
> > Other options are only pulled into the cache on an as needed basis.
> But autoload is "yes" by default. So, plugin authors using the
> options table for mass data would need to specify that it be off.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
More information about the wp-hackers