sebastianklaus

<p>WordPress stores custom post types in the default posts table (typically <code>wp_posts</code>), which is fine for most setups. In the majority of use cases, WordPress sites are not used to store in excess of thousands of posts, and so this sort of setup doesn’t place much additional load on servers.</p>
<p>In cases where the site generates a significant amount of posts across multiple post types though, queries can become very expensive – especially where meta generating plugins such as Advanced Custom Fields are involved. Where a WordPress site is expected to generate thousands of posts (and subsequently, many thousands of rows of post meta) queries can be sped up significantly by splitting out data into separate tables. This plugin splits out data by post type, creating additional tables for each custom post type used. A ‘product’ custom post type for example will have its posts stored in <code>product</code> and its meta in <code>product_meta</code>.</p>
<p>If you are using WordPress a little bit longer, you already know that it is an incredibly versatile platform. With its numerous features and extensions, however, it can sometimes be difficult to keep track of and find the right method for managing your content. This is where the use of WordPress custom post types in separate tables comes in!</p>
<p>By outsourcing your custom post types to separate tables, you can better organize and manage your content. It also allows you to have better control over your database and process queries more quickly and efficiently, which can positively impact the performance of your website.</p>
<p>Moreover, outsourcing custom post types to separate tables can also help improve the security of your website. By separating your content into separate tables, you can prevent malware or hackers from accessing your entire database.</p>
<p>Overall, outsourcing WordPress custom post types to separate tables offers a range of benefits for your website. It can improve the organization and management of your content, optimize the performance of your website, and increase your security. If you want to take your website to the next level, you should consider outsourcing your custom post types to separate tables!</p>
<h4>Works with</h4>
<ul>
<li>Multisite Installations</li>
<li>Woocommerce</li>
<li>YOAST etc.</li>
<li>Advanced Custom Fields</li>
<li>… and all other registered active custom post types</li>
</ul>
<h4>Settings</h4>
<p>As soon as you select a Custom Post Type, a new table is created in the database. This table will be used for all entries of this custom post type.</p>
<p>When you migrate the existing entries, the data from the old table is copied to the new table. This process is not reversible.</p>
<p>Backup your database before migrating in case something doesn’t work as you expect.</p>
<h4>Implementation</h4>
<p>Each new post and meta table is created to the same structure as the WordPress default post and meta tables. This streamlines the storage process and means that WordPress is capable of interpreting the data wherever it would normally use a <code>wp_posts</code> row, e.g. on the admin edit post pages, admin post listing pages, and in the <code>wp-posts</code> functions (e.g. <code>get_post()</code>).</p>
<p>When new posts are created, a row is inserted into the <code>wp_posts</code> table (as normal) and an automatic MySQL trigger is used to copy this data into the new custom table. Queries to the wp_posts and wp_postmeta table are then rewritten to use the custom table, so that all future lookups and updates made by WordPress and its plugins are made to the new tables. The original <code>wp_posts</code> row is retained for lookup purposes, so that we can determine the post type (and therefore custom table) when there is only a post ID available to work with. Since these lookups are (usually) only necessary in the WordPress admin and exclusively use the primary key, they do not significantly increase the load of the request. Additionally, each ID lookup is made a maximum of once per request and the result is cached on a per-request basis.</p>
<p>To minimise unecessary lookups when writing your own queries, specify the post type you are looking for whenever possible. This will allow the plugin to simply parse the table from the query without having to lookup the post type in the <code>wp_posts</code> table.</p>
<h4>Filter Hooks</h4>
<p><strong>cpt_tables:settings_capability:</strong></p>
<p>Customise what capability the settings page should be limited to. Default is ‘manage_options’.</p>
<h3>Contribute</h3>
<p>Developed with ♥ by <a href="https://lightapps.de" rel="nofollow ugc">Sebastian</a>.</p>
<p>This plugin was initially created for own usage to get a big database cleaner.</p>
<p>Check out the <a href="https://github.com/caspahouzer/wp-cpt-tables" rel="nofollow ugc">GitHub repository</a> and submit pull requests or open issues</p>
<h3>1.2.6</h3>
<ul>
<li>Find orphaned meta values and copy to new custom table</li>
<li>Trigger optimization</li>
</ul>
<h3>1.2.5.2</h3>
<ul>
<li>Hotfix: Altered correct auto_increment field for meta table</li>
</ul>
<h3>1.2.5</h3>
<ul>
<li>Removed autoincrement from copied table as it is controles by the posts_table (Revert CPT Tables and migrate them again to get the changes working)</li>
</ul>
<h3>1.2.4</h3>
<ul>
<li>Bugfix in cleanup-cronjob</li>
</ul>
<h3>1.2.3</h3>
<ul>
<li>Revert tables on plugin deactivation</li>
</ul>
<h3>1.2.2</h3>
<ul>
<li>German translation</li>
<li>Add missing migrated post_types, when the custom table exists</li>
<li>Fixed bug on deactivate the plugin</li>
</ul>
<h3>1.2.1</h3>
<ul>
<li>Load plugin the right time when all post types are registered</li>
<li>Refactoring and bugfixing</li>
<li>Added language pot template</li>
</ul>
<h3>1.1.0</h3>
<ul>
<li>Clear orphaned post_types from activated entries</li>
<li>You can activate a cronjob for table optimization in the settings</li>
</ul>
<h3>1.0.9</h3>
<ul>
<li>Automatically remove orphaned entries in the main post table under certain conditions</li>
</ul>
<h3>1.0.8</h3>
<ul>
<li>Re-create triggers if they don’t exist</li>
</ul>
<h3>1.0.7</h3>
<ul>
<li>tested with WordPress 6.2</li>
</ul>
<h3>1.0.6</h3>
<ul>
<li>Fixed debugger warnings</li>
<li>Clean up code</li>
<li>Escape vars</li>
<li>Sanitize vars</li>
<li>Refactoring</li>
</ul>
<h3>1.0.1</h3>
<ul>
<li>Added _ to accepted chars of post type</li>
</ul>


Custom Post Type Tables


Hello Sebastian, 



Thank you for this amazing plugin. 



I'm encountering an error after migrating WooCommerce products. Additionally, I would like to ask if this is compatible with Gutenberg templates?



Fatal error: Uncaught Exception: Trigger already exists in /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/lib/Db.php:62 Stack trace: #0 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/lib/Triggers.php(210): WPCPT_Tables_Db->query('CREATE TRIGGER ...') #1 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/lib/Triggers.php(62): WPCPT_Tables_Triggers->insertMetaTrigger(Array) #2 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/core.php(179): WPCPT_Tables_Triggers->create(Array) #3 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/core.php(92): WPCPT_Tables_Core->checkExistingTriggers() #4 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-includes/class-wp-hook.php(308): WPCPT_Tables_Core->load('') #5 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #6 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-settings.php(486): do_action('plugins_loaded') #8 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-config.php(93): require_once('/Users/admin/Lo...') #9 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-load.php(50): require_once('/Users/admin/Lo...') #10 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-admin/admin.php(34): require_once('/Users/admin/Lo...') #11 /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-admin/plugins.php(10): require_once('/Users/admin/Lo...') #12 {main} thrown in /Users/admin/Local Sites/woocommerce-invoice-manager/app/public/wp-content/plugins/cpt-tables/lib/Db.php on line 62






Great!

Allow storing custom post types in their own tables in order to make querying large datasets more efficient

kdmurthy

<p>WpPDE is a development environment for WordPress. You can create your own plugins and maintain them using WpPDE.</p>
<p>WpPDE allows you to create plugins that contain:</p>
<ul>
<li>Widgets</li>
<li>Actions</li>
<li>Hooks</li>
</ul>
<p>WpPDE integrates with <a href="http://ace.ajax.org" rel="nofollow ugc">Ace editor</a> to provide a productive development environment.</p>
<p>WpPDE also facilitate easy creation of readme files for your plugins.</p>
<h4>Documentation</h4>
<ul>
<li><a href="http://wp-pde.jaliansystems.com/" rel="nofollow ugc">WpPDE – Plugin Development Environment</a> – Official home page</li>
<li><a href="http://wp-pde.jaliansystems.com/documentation/" rel="nofollow ugc">WpPDE – User Guide</a> – Documentation for WpPDE plugin</li>
<li><a href="http://wp-pde.jaliansystems.com/tutorials/" rel="nofollow ugc">WpPDE – Tutorials</a> – Selected screencasts demonstrating the functionality.</li>
</ul>
<h4>Plugin Elements</h4>
<p>Use the <strong>Plugin Elements</strong> box to add different type of items to your plugin. You can add:</p>
<ul>
<li>Actions</li>
<li>Filters</li>
<li>Widgets (More on this in the next section)</li>
</ul>
<h4>Widgets</h4>
<p>Once a widget element is added to the plugin, you can configure it in the GUI. You can also add form elements to the widget. WpPDE automatically creates the widget form for you including saving of the widget data. You just need to provide the display code (corresponding to <code>widget()</code> method).</p>
<h4>Form Elements</h4>
<p>You can various kinds of form elements to the widget. These include:</p>
<ul>
<li>Labels (with various styles)</li>
<li>Checkbox</li>
<li>Text</li>
<li>Text Area</li>
<li>Radio</li>
<li>Dropdown lists</li>
</ul>
<p>You can also hide/unhide dependent elements using the value of the selected item for checkbox, radio and dropdown items.</p>
<h4>External Files</h4>
<p>You can add external files (javascript, css, PHP etc.) to your plugin using the <code>External Files</code> box. WpPDE even lets you enqueue(or require) the files automatically.</p>
<h4>Readme Generation</h4>
<p>WpPDE can generate readme files (in standard wordpress readme format or markdown format for github). Provide the information in <code>About the Plugin</code> box and let WpPDE generate the files for you.</p>
<h4>Editor Options</h4>
<p>You can change the editor options using the <code>Editor Options</code> box.</p>


WpPDE

A development environment for creating plugins with support for widgets, actions and hooks.

Custom Post Type Tables vs WpPDE