The work is ongoing on the development for the GD Content Tools Pro 6.0, with the preliminary release date set to February 9, 2022. The new version is a big step forward, and preparation for even more changes coming in the future.
Before I talk more about the upcoming features and improvements, it is important to note the breaking changes and requirements.
The new plugin version will require WordPress 5.3 or newer (tested with 5.9), PHP 7.2, or newer. The Tagger Addon feature has been removed from the plugin because all third-party services used for it are gone, and the feature worked with Classic Editor only. The plugin also loses capability for having addons, and bbPress support is now reintegrated into plugin code.
The image below shows updated styling (and some extra features) for the metabox in the post editor, here inside the Block Editor. The focus of this new version is indeed on the metabox aspect, but many other things have been changed.
So, the list of changes so far, with a few more things to be included until the release date.
- Updated system requirements
- Updated custom post types and taxonomies labels
- Plugin styling done using SASS with a lot of changes
- Plugin JavaScript rewrite and optimization
- Metabox styling improved with Block editor specific changes
- Improved metabox field repeater controls
- Updates to many fields, including Image and Gallery
- Updated PHP and WordPress data sources lists
- Updated several third party JavaScript libraries
- More options for the bbPress Integration
- Removed support for addons and addons moved into core
- Removed Tagger addon
- Removed many legacy, outdated and deprecated functions
- Several bug fixes, mostly metabox related
I will try to release the Beta version next week to test some of the changes that might be causing problems depending on the use context, and if nothing unexpected happens, the plugin will be released on February 9, 2022.
Amazing news, 2 questions please :
1) could we search and filter ?
2) will it have a Multiple level select field allows wich user to select several related values. There is values constructor in field settings that allows enter values. The field could be set up so user can enter it’s own value to the list or select only one of proposed values and a List auto-complete field which allows the user to select multiple values from a suggestion dropdown list. User can enter own value ?
thank you
Hi,
1. This is planned for one of the future versions, but I don’t know when that will happen. Version 6.0 includes a lot of changes already that are important to the way the plugin works, and front-end search and filter based on metadata would take a lot of time, and I want to release the plugin soon. I still don’t know how to create a search and filter to be a good feature. Other plugins that do this are mostly doing that very badly, and I want to do this right, so it will take time.
2. I didn’t quite understand everything in your comment here, but if you are referring to connected dropdowns (select value in one, another one shows with values related to the first selection, and so on), that is currently not in the plans. I can’t even see how the interface for setting up the field would look like and work and make it usable.
Milan
Hello
Maybe a search and filter like https://metabox.io/?
But other idea you could create a plug-in for using metabox.io in bbpress. Loot at Metabox forum, it is one of the most wanted feature. Metabox can already work with bbpress but it requires specific template.
I have no plans to support third-party system in this way. Search/Filter is coming to the plugin, but it will take time.
As for bbPress, I have GD Power Search Pro/Lite for bbPress for setting up advanced search for the forums. And, it can be expanded with meta fields. Problem is that one metabox can be used for one forum, and different metabox for other forums, so using single form to search multiple forums is not possible or practicle.
If anyone has suggestion on how the metabox based search/filter should work in forums, I am open to suggestions. So far, users asked for the features, but no one really knows how it should look or work. Implementing code to search is easy, having good interface and logic for it is something I don’t have now, and I have not seen anyone offering some good proposal on how to do.