[wp-trac] [WordPress Trac] #50687: Consider Banning use of wp_options by Plugins
WordPress Trac
noreply at wordpress.org
Fri Jul 17 15:33:18 UTC 2020
#50687: Consider Banning use of wp_options by Plugins
--------------------------------+--------------------------
Reporter: thegulshankumar | Owner: (none)
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Options, Meta APIs | Version:
Severity: normal | Resolution: wontfix
Keywords: close | Focuses: performance
--------------------------------+--------------------------
Changes (by johnbillion):
* status: new => closed
* version: 5.4.2 =>
* resolution: => wontfix
* milestone: Awaiting Review =>
Comment:
Thanks for your interest in this issue @thegulshankumar but this isn't
anything that can be enforced by -- nor is appropriate for -- a core
change. The options table is meant for both core and custom options and
there's no reason for that not to be the case. Whoever would want a whole
new database table just to store one plugin option?
Every database table in WordPress can be abused, it's up to plugin
developers to follow best practices and choose an appropriate storage
mechanism for their data, whether that be a single row in the options
table, or a whole new database structure, or something in between.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50687#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list