That’s right, Conductor now has a Gutenberg block! We’ve also fixed a couple of small issues with pagination in Conductor Widgets and we have some cool new features in our pipeline which will be released throughout 2019. Read on to find out more!
Introducing The Conductor Gutenberg Block
In version 1.0.5 of the Conductor Query Builder Add-On, we’ve introduced a Conductor Gutenberg block. This block allows you to display queries built with the Query Builder Add-On in your content. This was previously possible (and still is) by using the [conductor] shortcode. When editing or updating our Gutenberg block settings, we’ve also provided the ability to edit the selected query. You can do this by using the sidebar “Edit” feature which opens the query for editing in a new tab/window. Here is a demo of our Gutenberg block:
Click to see a larger version of this demo
Small Pagination Improvements and Fixes
Pagination in Conductor Widgets and Queries has been fixed when previewing content within WordPress. We also fixed AJAX pagination in the Query Builder when Conductor Widgets were not active (e.g. no Conductor Widget in a sidebar).
In our Query Builder Add-On, we fixed a bug where, for queries built using our “advanced” builder, the maximum number of posts was set to the posts_per_page option value by default which caused pagination to break after the posts per page limit was reached. In Conductor Widgets we default the maximum number of posts setting to the posts_per_page option value, but in the “advanced” builder it doesn’t make sense to do this by default.
If you’d like to limit the maximum number of posts displayed in our “advanced” query builder, you can use the “Maximum Number of Posts” parameter in the “Limit” clause group.
Upcoming Add-Ons and Features
We’re working on a calendar add-on for Conductor that’s almost ready for release. This add-on will allow users to display their content in a calendar layout. It’ll be perfect for events type content and even your blog posts if you wanted to display them in a calendar layout. We’ll have more information about this add-on soon.
Along with the calendar add-on, we’re also excited about a nifty feature we’re working on for the core Conductor plugin. This feature is: exposed markup. Exposed markup will allow users and developers to quickly change the markup of Conductor output. You’ll be able to change the markup for individual display components, like the featured image component. You’ll also be able to edit the markup for the entire output.
Exposed markup code preview
We’ve found that, while Conductor does a great job of displaying your queried content, it’s nearly impossible to match the display of all of the different WordPress themes. If Conductor doesn’t 100% match your theme’s display, you’ll be able to customize the markup to fit your needs. Only need to add a single CSS class or adjust a HTML element type? You’ll be able to do that. Want to add content before or after an individual display component? You’ll be able to do that too.
These types of modifications are currently limited to developers via our hooks, but once the exposed markup feature is released, anyone with basic PHP, HTML, or CSS experience should be able to make markup modifications to fit their needs.
While we are working hard on the exposed markup feature, we do not yet have an official release date in mind. Check back on our blog or newsletter for updates as we have them.
Official Changelogs
Conductor
- Improved Conductor Widget pagination logic to help ensure it works across a variety of permalink structures
- Fixed a bug where Conductor Widget AJAX pagination did not work correctly in some cases
Conductor Query Builder
- Added Conductor Gutenberg block
- Fixed a bug where scripts and styles on the front-end weren’t enqueued properly when a Conductor Widget wasn’t active (in use)
- Adjusted logic to check for the Conductor capability (using
Conductor::$capability) - Added Conductor_Query_Builder() instance as a new argument on the “
conductor_query_builder_postmeta_form_limit” filter - Fixed a bug where the maximum number of posts (Conductor Widget “
max_num_posts” setting) was set to the posts per page option (which is the Conductor Widget default) when the query builder mode is set to “advanced” which resulted in incorrect pagination after the number posts per page was met- Note: To limit the maximum number of posts displayed when the query builder mode is set to “advanced”, use the “Maximum Number of Posts” parameter in the “Limit” clause group
Having Issues After Updating?
We have tested all of these updates extensively across many versions and variations of WordPress. If you encounter any unexpected issues after upgrading, please let us know by submitting a support ticket.
Conduct your content!