Organize your Page Builder Templates in the WordPress Admin. Better overview, don't get lost. Time saver. With extended plugin & theme suppor …
Organize your Page Builder Templates in the WordPress Admin. Time saver, especially for bigger projects. Get a better and faster overview, don’t get lost. Filter templates with your categories. With extended plugin & theme support.
Out of the box the plugin includes integrations for a lot of awesome Page Builders, Themes and Plugins. If any supported integration is installed & active, the “Builder Template Categories” plugin just applies its additions. The plugin is really lightweight and simple. Just activate and you’re done – and can use the categorization.
You are building a big site with lots of different templates across various template libraries of different plugins.
Now the “Builder Template Categories” plugin helps you organize those templates better and more efficiently. For example you have a template category “Landing Pages”.
This category is now visible in Elementor’s “My Templates”, as well as in the Theme “GeneratePress” and its “Elements” Module, as well as in “PopBox for Elementor” plugin and also in “Pods” plugin’s “Templates”.
So in every one of those libraries you can now filter and list all parts of templates for this specific post type that belong to your “Landing Pages” category.
Please note: The categories are global but when filtering only those items are listed that are connected to the specific post type. See the FAQ for more info on that
Try Toolbar Extras my other plugin for Site Builders and admins: Building sites with Elementor? Your work will get easier & faster with Toolbar Extras. With extended plugin & theme support baked right in. Of course, “Builder Template Categories” is integrated as well π
toolbar extras
in the plugin installer πAdministrator
(needed capability edit_theme_options
)en_US
= default, always includedde_DE
– always includedde_DE_formal
– always includedfr_FR
– by the community, thanks to Bruno Tritsch.pot
file (builder-template-categories.pot
) for translators is always included in the plugin’s ‘languages’ folder πIf you want to translate, go to the Translation Portal at translate.wordpress.org.
You can also contribute code-wise via our Builder Template Categories GitHub Repository – and see where you can help.
Enjoy using Builder Template Categories? Please consider making a donation – every donation helps to support the project’s continued development, maintenance and support.
Thank you very much in advance for your support!
Idea Behind / Philosophy: Just a little lightweight plugin for all the Non-Coder site builders out there using plugins or themes with template libraries and wanting to categorize these templates. Just making their daily work and life just a little easier.
Special Thanks go out to my family for allowing me to do such spare time projects (aka free plugins) and supporting me in every possible way!
edit_theme_options
builder template categories
), or extract the ZIP file and drop the contents in the wp-content/plugins/
directory of your WordPress installation.Template Categories for Elementor "My Templates" - Filtering for templates: 1) Dropdown of template categories, 2) Links to template categories
List of Template Categories - plus help info about all current active integrations
Edit a template category: 1) Title is the most important item; 2) Description field ist useful for internal notes or for your team of designers/ site builders etc.
Template categories for "Astra Custom Layouts" - Astra Theme via Astra Pro plugin
Template categories for "GeneratePress Elements" - GP Premium plugin (v1.7+)
Template categories for "OceanWP My Library" - Ocean Extra plugin
Edit a template - and set the template category (Example of an Elementor template)
Post type Bulk Actions: Add a template category to selected templates in one action step
Plugins page - list of all plugins - "Builder Template Categories" with link to taxonomy listing table
Reusable Blocks support in Block Editor (Gutenberg) in WordPress 5.0+ - post type list table (overview)
Editing a Reusable Block - adding the "Builder Template Categories" taxonomy via the new Block Editor JavaScript-based meta box
Applying template categories to more than one template at once is easily possible: just use the built-in “Bulk Actions” from WordPress Core, which are available for any post type.
original video linkby plugin developer David Decker
The answer is simple: Our taxonomy is only for organizing purposes if you have to manage many, many templates. It is easy to just enter 2 or more different categories if you use more than one of the supported integrations (and therefore have our taxonomy applied to more than one post type).
It would add a lot of bloat to register a “organizing taxonomy” for every supported post type of an integration. This really makes absolutely no sense in my opinion. Of course, you are free to tweak the behavior of the plugin with the built-in filters or WordPress Core functions, filters, actions and classes. Plus, you can at any time easily register any custom taxonomy yourself.
This plugin here is a “quick and easy” solution: install, activate, organize with categories. Done.
The counter works fine, really.
The “issue” you’re seeing is most likely that: you have more than one of the supported integrations active. Therefore the categories are global and applied to each of the integrations. But the terms count for the categories remains also global.
Example:
The term counter in the taxonomy list table will always display: 15. This is the global term count.
Continuing the example: When filtering in “Elementor My Templates” for “Landing Pages” you will get 5 results. Which is fully correct. These are the 5 results that are connected to this post type. The same filter in “Astra Custom Layouts” will bring 10, of course, as only these 10 terms are connected to this Layouts Post Type. And so on…! π
This plugin only works and makes sense for Administrator users just because the post types it integrates with are mostly only accessable for administrators. The target user group of this plugin are site builders, admins, developers who want to organize their admin area better, plus their website projects.
To customize the capability to make the taxonomy appear in the Admin Dashboard you can use a filter:
add_filter( 'btc/filter/capability/submenu', 'btc_custom_capability_submenu' ); /** * Plugin: Builder Template Categories - Custom capability. * * @return string String ID of new capability. */ function btc_custom_capability_submenu() { return 'edit_posts'; } // end function
(This code snippet as a GitHub Gist)
Elementor (free) is not required. But once it is installed and active the integration gets loaded, meaning, the taxonomy for categorizing Elementor templates appears (My Templates Library). This will make organizing templates a breeze π
I totally recommend Elementor – so, with it active, this plugin here will make the perfect sense!
Absolutely not. For the Elementor integration the free version of Elementor is enough as it already adds the template library (“My Templates”).
However, I strongly recommend Elementor Pro as it is so useful for Non-Coder Designers site builders.
All the others already have template categories by default, or, on the other hand, cannot be supported with a post type taxonomy.
Update:
* Brizy Page Builder added template feature in their version 1.0.25 – we added integration with our plugin version 1.0.1
* Visual Composer Website Builder for Headers, Footers, Sidebars, Global Templates – we added integration with our plugin version 1.4.0
* Avada Fusion Builder in Avada Theme – we added integration with our plugin version 1.4.0
* Beaver Builder & Beaver Themer – we added integration with our plugin version 1.6.0
* Divi Builder (plugin version, Divi Theme, Extra Theme) – we added integration with our plugin version 1.6.0
Yes, absolutely. β Once I discover another theme (or via an add-on plugin) which adds a template library but has no categories for organizing I consider adding an integration. Of course, you can also make me aware of other themes and plugins with such libraries.
Yes, absolutely. – Once I discover another plugin which adds a template library but has no categories for organizing I consider adding an integration. Of course, you can also make me aware of other themes and plugins with such libraries.
Yes, of course! – The plugin is fully compatible with Gutenberg Block Editor which is (becoming) WordPress 5.0+. It even supports the “Reusable Blocks” feature and adds our template category for that. This means, you can now categorize your reusable blocks and edit them from a dedicated screen!
Beyond that, there is already integration with some Gutenberg-specific plugins built-in. More integrations might follow over time.
Yes, this plugin works with the Classic Editor plugin perfectly fine.
I will try my best to also have my plugin work perfectly in ClassicPress, the fork of WordPress without Gutenberg. It should already be fully compatible but I will follow all events closely to adjust compat if needed.
Absolutely not. The plugin will only do its stuff for logged-in Administrator users. It does nothing for visitors of your site. Plugin loads its stuff only when needed and if supported theme/ plugin is active. Plugin was built to be as lightweight as possible.
Yes, it works fine in Multisite, you could even activate it Network-wide. However, the taxonomy is only added on a per site basis (if the supported integrations are active). Therefore it makes the most sense to activate the plugin on a per site basis.
Technically not. However, without the integrations this plugin doesn’t make any sense. So you want to have at least one of the integrations installed and activated.
Or, you can also register your own custom integration (see snippets below) if you do not want or need the built-in integrations.
Note: One exception is the new Block Editor since WordPress 5.0+. The Block Editor has a feature called “Reusable Blocks” and this is already natively integrated with our plugin, “Builder Template Categories”. So, once you have WordPress 5.0+ active you already have one native integration active by default ;-).
Good question. If you used our plugin, Builder Template Categories, before it’s recommended to use it still to not lose your data and for consistency, of course. You absolutely can run both taxonomies side by side. This plugin here always plays nice with others! π
And, Builder Template Categories, has a big advantage over Elementor’s own taxonomy: our taxonomy is global! This means, it is used by other integrations at the same time – if those are active side by side with Elementor. This “effect” just makes our plugin way more smart and usable in the long run.
That is especially useful if you work with Elementor, PLUS one of these:
If you ask me: In such a case Builder Template Categories has way more power and makes just more sense, also if you’re working with a team.
Note: Shortly I will also provide ways to disable Elementor’s taxonomy if you want.
Yes, of course.
There are numerous filters built-in, plus the default filters for taxonomies from WordPress Core apply.
If you want to add support for your own custom library, just declare the following register statement via our filter:
add_filter( 'btc/filter/integrations/all', 'btc_register_custom_integration' ); /** * Plugin: Builder Template Categories - Register custom integration. * * @param array $integrations Holds array of all registered integrations. * @return array Tweaked array of registered integrations. */ function btc_register_custom_integration( array $integrations ) { $post_type = 'your-post-type'; $submenu_hook = 'your-custom-settings-page'; // as in: your-site.domain/wp-admin/admin.php?page=your-custom-settings-page; // or alternative: $submenu_hook = 'edit.php?post_type=' . $post_type; $template_label = 'template'; // or: library, layout, element, popup, lightbox, block, listing, post-type, field, box, bar, hook, filter, section, flow, snippet $integrations[ 'your-custom-handle-lowercase' ] = array( 'label' => __( 'My Custom Templates', 'your-textdomain' ), 'submenu_hook' => $submenu_hook, 'post_type' => $post_type, 'template_label' => $template_label, 'admin_url' => 'edit.php?post_type=' . $post_type, ); return $integrations; } // end function
(This code snippet as a GitHub Gist)
Best practice is to wrap the whole code above in a conditional to check if the theme/ plugin/ post type is active before applying anything from our “Builder Template Categories” stuff.
More Code Snippets? – More stuff is available in the plugin’s Wiki at GitHub page
/wp-content/languages/builder-template-categories/
(just create this folder) – This enables you to use fully custom translations that won’t be overridden on plugin updates. Also, complete custom English wording is possible with that as well, just use a language file like builder-template-categories-en_US.mo/.po
to achieve that (for creating one see the following tools).Easy WordPress.org plugin translation platform with GlotPress platform:Translate “Builder Template Categories”…
Note: All my plugins are internationalized/ translateable by default. This is very important for all users worldwide. So please contribute your language to the plugin to make it even more useful. For translating and validating I recommend the awesome “Poedit Editor”, which works fine on Windows, macOS and Linux.
As of version 1.7.0 of the plugin the following was achieved:
.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packswp_block
post type, plus admin enhancements – this lets you manage the “reusable blocks” feature better.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packs.pot
file plus all German translations (formal, informal) and language packscomposer.json
file in the plugin’s root folder – this is great for developers using Composer