Database Schema
SiteNivo stores builder configuration in dedicated tables; field values use standard WordPress meta and options. Table names use your $wpdb->prefix (shown below as wp_).
Configuration vs values
- Configuration — CPTs, taxonomies, field groups, field definitions, options page registry, columns, redirects, visitor hits live in SiteNivo custom tables.
- Values — saved in
post_meta,user_meta,term_meta, and options (options pages), so themes and migrations stay familiar.
Custom tables
| Table | Stores |
|---|---|
wp_sitenivo_post_types | Custom post type definitions |
wp_sitenivo_taxonomies | Taxonomy definitions |
wp_sitenivo_field_groups | Field groups + location rules |
wp_sitenivo_fields | Field definitions inside groups |
wp_sitenivo_options_pages | Options page registry |
wp_sitenivo_post_columns | Admin list-table columns |
wp_sitenivo_redirects | Redirection rules |
wp_sitenivo_redirect_404 | 404 log entries |
wp_sitenivo_visitor_hits | Visitor Tracking pageviews |
Options
Module settings and toggles generally live in the wp_options table with names prefixed sitenivo_ (for example SMTP, Security, Social Buttons, and Settings flags).
Practical advice
- Do not edit SiteNivo tables by hand unless you know the schema
- Use Import / Export for configuration moves
- Uninstall “delete data” removes SiteNivo tables/options — not every meta value already written. See Uninstall & Data.