Pratik Shrestha

Catch Plugins

Sakin Shrestha

dreamsapana

Catch Themes

Mahesh Maharjan

Essential Content Types allows you to feature the impressive content through different content/post types on your website just the way you want it. These content/post types are missed by the themes in WordPress Theme Directory as the feature falls more towards the plugins’ territory.
Content is at the forefront of any website. Changing the layout of your important content changes the way your website looks, which may not be a plus point if your current website layout is loved by your users.
Additionally, switching themes changes your website layout completely. Therefore, to keep things looking spic-and- span in your website, we bring you Essential Content.
Essential Content allows you to add up to three content/post types: 
* Portfolio – Create and display your portfolio on your website 
* Testimonials – Add customer testimonials to your website 
* Featured Content – Display the content you want as featured content on your website to attract visitors’ attention 
* Services – Add your services on your website
Features of Essential Content: 
* Enable/Disable any content/post type as needed 
* Light-weight 
* Supports all themes on WordPress
Essential Content is inspired by Jetpack’s Custom Content Types feature.
However, not everyone wants to have a plugin that “does-it- all”. Some may want plugins to be niche focused and concentrate on smaller areas.
That is precisely what we have done with Essential Content. Essential content, true to its name, has only the essential elements. We have added the features that WordPressers use most. We have ruled out all other elements to make it non-bloated and clean. It takes up lesser space and does the job well.
If you think we have missed any essential content/post types, please let us know. We’ll review the frequency of usage and add your suggestions.
Portfolio Shortcode
You can use shortcodes to embed portfolio projects on posts and pages.
Embedding Portfolio Projects
To embed portfolio projects on posts and pages, first activate the Portfolio custom content type on your site and add some projects to your portfolio.
Next, add the <code>[portfolio]</code> shortcode to a post or page. The shortcode will display projects in different ways, depending on how you use the optional attributes to customize the portfolio layout.
Attributes 
* display_types: display Project Types. (true/false) 
* display_tags: display Project Tags. (true/false) 
* display_content: display project content. (true/false) 
* include_type: display specific Project Types. Defaults to all. (comma-separated list of Project Type slugs) 
* include_tag: display specific Project Tags. Defaults to all. (comma-separated list of Project Tag slugs) 
* columns: number of columns in shortcode. Defaults to 2. (number, 1-6) 
* showposts: number of projects to display. Defaults to all. (number) 
* order: display projects in ascending or descending order. Defaults to ASC for sorting in ascending order, but you can reverse the order by using DESC to display projects in descending order instead. (ASC/DESC) 
* orderby: sort projects by different criteria, including author name, project title, and even rand to display in a random order. Defaults to sorting by date. (author, date, title, rand)
Example
<pre><code>[portfolio display_types="true" display_tags="false" include_type="grooming-tips,best-kitties" columns="2" showposts="10" orderby="title"]
</code></pre>
The example will display up to ten portfolio projects in two columns, in ascending alphabetical order by project title. It will display Project Types, hide Project Tags, and only display projects that are assigned the “Grooming Tips” or “Best Kitties” Project Types.
Featured Content Shortcode
You can use shortcodes to embed featured content on posts and pages.
Embedding Featured Content Projects
To embed featured content on posts and pages, first activate the Featured Content content type on your site and add some projects to your featured content.
Next, add the <code>[featured_content]</code> shortcode to a post or page. The shortcode will display projects in different ways, depending on how you use the optional attributes to customize the featured content layout.
Attributes 
* display_types: display Content Types. (true/false) 
* display_tags: display Content Tags. (true/false) 
* display_content: display project content. (true/false) 
* include_type: display specific Content Types. Defaults to all. (comma-separated list of Content Type slugs) 
* include_tag: display specific Content Tags. Defaults to all. (comma-separated list of Content Tag slugs) 
* columns: number of columns in shortcode. Defaults to 2. (number, 1-6) 
* showposts: number of projects to display. Defaults to all. (number) 
* order: display projects in ascending or descending order. Defaults to ASC for sorting in ascending order, but you can reverse the order by using DESC to display projects in descending order instead. (ASC/DESC) 
* orderby: sort projects by different criteria, including author name, project title, and even rand to display in a random order. Defaults to sorting by date. (author, date, title, rand)
Example
<pre><code>[featured_content display_types="true" display_tags="false" include_type="grooming-tips,best-kitties" columns="2" showposts="10" orderby="title"]
</code></pre>
The example will display up to ten featured content in two columns, in ascending alphabetical order by project title. It will display Content Types, hide Content Tags, and only display projects that are assigned the “Grooming Tips” or “Best Kitties” Content Types.
Testimonials Shortcode
You can use shortcodes to embed testimonials on posts and pages. 
Embedding Testimonials
To embed testimonials on posts and pages, first activate the Testimonial custom content type on your site and add some testimonials.
Next, add the <code>[testimonials]</code> shortcode to a post or page. The shortcode will display testimonials in different ways, depending on how you use the optional attributes to customize the testimonials layout.
Attributes 
* display_content: display testimonial content. (full/true/false) 
* image: display the featured image. (true/false) Defaults to true. 
* columns: number of columns in shortcode. Defaults to 1. (number, 1-6) 
* showposts: number of testimonials to display. Defaults to all. (number) 
* order: display testimonials in ascending or descending chronological order. Defaults to ASC for sorting in ascending order, but you can reverse the order by using DESC to display testimonials in descending order instead. (ASC/DESC) 
* orderby: sort testimonials by different criteria, including author name, testimonial title, and even rand to display in a random order. Defaults to sorting by date. (author, date, title, rand)
Example
<pre><code>[testimonials columns="2" showposts="10" orderby="title"]
</code></pre>
The example will display up to ten testimonials in two columns, in ascending alphabetical order by testimonial title.
Service Shortcode
You can use shortcodes to embed service on posts and pages.
Embedding Service Projects
To embed service on posts and pages, first activate the Service content type on your site and add some projects to your Service.
Next, add the <code>[services]</code> shortcode to a post or page. The shortcode will display projects in different ways, depending on how you use the optional attributes to customize the featured content layout.
Attributes 
* display_types: display Content Types. (true/false) 
* display_tags: display Content Tags. (true/false) 
* display_content: display project content. (true/false) 
* include_type: display specific Content Types. Defaults to all. (comma-separated list of Content Type slugs) 
* include_tag: display specific Content Tags. Defaults to all. (comma-separated list of Content Tag slugs) 
* columns: number of columns in shortcode. Defaults to 2. (number, 1-6) 
* showposts: number of projects to display. Defaults to all. (number) 
* order: display projects in ascending or descending order. Defaults to ASC for sorting in ascending order, but you can reverse the order by using DESC to display projects in descending order instead. (ASC/DESC) 
* orderby: sort projects by different criteria, including author name, project title, and even rand to display in a random order. Defaults to sorting by date. (author, date, title, rand)
Example
<pre><code>[services display_types="true" display_tags="false" include_type="grooming-tips,best-kitties" columns="2" showposts="10" orderby="title"]
</code></pre>
The example will display up to ten featured content in two columns, in ascending alphabetical order by project title. It will display Content Types, hide Content Tags, and only display projects that are assigned the “Grooming Tips” or “Best Kitties” Content Types.
Food Menu Shortcode
You can use shortcodes to embed Food Menu on posts and pages. 
Embedding Food Menu
Embedding Food Menu
To embed food menus on posts and pages, first activate the Food Menu custom content type on your site and add some food menus.
Next, add the <code>[food_menu]</code> shortcode to a post or page. The shortcode will display food menu in the selected post or page.
Attributes 
* showposts: number of menu items to display. Defaults to all. (number) 
* include_type: display specific Content Types. Defaults to all. (comma-separated list of Content Type slugs) 
* include_tag: display specific Content Tags. Defaults to all. (comma-separated list of Content Tag slugs)
Example
<pre><code>[food_menu showposts="10" include_type="pizza,burger,breakfast"]
</code></pre>
The example will display up to ten menu items. It will only display menu items in “Pizza”, “Burger” or “Breakfast” sections.
<h3>Translations</h3>
To translate the plugin, use translate.wordpress.org (GlotPress). You only need your WordPress.org account to join the collaborative translation project.
You can translate Essential Widgets on <a href="https://translate.wordpress.org/projects/wp-plugins/essential-content-types/" rel="nofollow ugc">translate.wordpress.org</a>.

Essential Content Types

Essential Content Types allows you to feature the impressive content through different content/post types on your website just the way you want it.

sebastianklaus

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.
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>.
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!
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.
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.
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!
<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>
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.
When you migrate the existing entries, the data from the old table is copied to the new table. This process is not reversible.
Backup your database before migrating in case something doesn’t work as you expect.
<h4>Implementation</h4>
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>).
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.
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.
<h4>Filter Hooks</h4>
cpt_tables:settings_capability:
Customise what capability the settings page should be limited to. Default is ‘manage_options’.
<h3>Contribute</h3>
Developed with ♥ by <a href="https://lightapps.de" rel="nofollow ugc">Sebastian</a>.
This plugin was initially created for own usage to get a big database cleaner.
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
<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

Essential Content Types vs Custom Post Type Tables