wp_setting
StaticStores setting data created by this plugin.
Column Definitions
| Column | Type | Nullable |
|---|---|---|
| format | text | NO |
| maintenance | datetime | YES |
| log_mode | int | YES |
| timezone | text | NO |
| log_backup | date | NO |
| bot_key | text | NO |
| loginblock | int | YES |
| block_user | text | NO |
| autoblock | int | YES |
| autoblocklist | text | NO |
| botblocklist | text | NO |
| botwhitelist | text | NO |
| sitekey | text | NO |
| zerodayblock | int | YES |
| trustedfile | text | NO |
| siteurlprotect | int | YES |
| protectlist | text | NO |
| notice | text | NO |
CREATE TABLE Statement
CREATE TABLE setting ( format text DEFAULT '0' NOT NULL, maintenance datetime, log_mode int DEFAULT 0 NULL, timezone text DEFAULT 'utc' NOT NULL, log_backup date DEFAULT '0000-00-00' NOT NULL, bot_key text DEFAULT '' NOT NULL, loginblock int DEFAULT 0 NULL, block_user text DEFAULT '' NOT NULL, autoblock int DEFAULT 0 NULL, autoblocklist text DEFAULT '' NOT NULL, botblocklist text DEFAULT '' NOT NULL, botwhitelist text DEFAULT '' NOT NULL, sitekey text DEFAULT '' NOT NULL, zerodayblock int DEFAULT 0 NULL, trustedfile text DEFAULT '' NOT NULL, siteurlprotect int DEFAULT 0 NULL, protectlist text DEFAULT '' NOT NULL, notice text DEFAULT '' NOT NULL );
Safe to delete?
If you have uninstalled Yasakani Cache, this table is generally safe to remove. However, always back up your database first.
Note: Some plugins share tables or are dependencies of other plugins. Verify nothing else depends on this table before dropping it.
How to remove this table
DROP TABLE IF EXISTS `wp_setting`;
Run this query using phpMyAdmin, Adminer, or your MySQL client. Back up first.
Other tables from Yasakani Cache