We’re happy to announce the latest update to Conductor, version 1.1. This release introduces our brand new Add-Ons panel, automatic updates for add-ons and other improvements/bug fixes.
Update: We’ve updated the verbiage used within this post to better reflect the update process for Conductor Add-Ons.
Add-Ons Panel
Throughout our beta program and for the past few releases, the Add-Ons section within Conductor was marked as “coming soon”. We’re proud to announce that we now have a working add-ons panel within the plugin that will be updated regularly.
If you have a valid Conductor Power Pack or Conductor Developer Pack license, you’ll have access to our add-ons. Simply head on over to the Account page to download.
Browse Add-Ons on our Site
You can now also browse available add-ons right here on the Add-Ons page.
Automatic Updates for Add-Ons Updates in Your Dashboard
Update: Conductor Add-Ons do not currently support automatic updates. You will, however, see updates for add-ons in your Dashboard when they are released.
We’re also proud to announce automatic updates for all of our add-ons. Your valid Conductor Power Pack or Conductor Developer Pack license will now allow for updating of add-ons. You’ll need to manually install the newest versions of these add-ons in order to enable automatic updates in the future. You can head on over to the Account page to download and install the add-ons.
Manually updating your add-ons should go through without a hitch, but we recommend making a backup of your site before updating any aspect of WordPress as a precaution.
Besides adding automatic updates, we’ve added a bunch of improvements to our add-ons. See the changelog within each add-on for more details.
Notable Bug Fixes
This release also fixes a large number of bugs. A “thank you” goes out to everyone who has submitted feedback so far. Here are some of the most notable bug fixes:
- Fixed bug when conducting content layouts without a permalink structure (Previewer always re-directed to home_url())
- Fixed a bug where pagination did not function properly without a permalink structure
- Fixed bug where content type was incorrect sometimes due to loss of focus on select box after a widget was saved in the Customizer
- Fixed a display conflict with some plugins by tightening up CSS on Conductor Dashicons in the Customizer and Appearance > Widgets
- Fixed bug where CSS was not loaded when a Conductor widget was placed in any sidebar that was not registered by Conductor; Thanks Martin Avery
- Fixed jQuery Sortable data that was generated after sorting output elements to ensure correct data and data types were stored on the widget (added data-value HTML5 attribute to output elements that were associated with a value); This fixes a scenario where post content was displayed even though “excerpt” was selected as the displayed content type on a Conductor Widget
Having issues after upgrading?
We have tested version 1.1 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.
Official Changelog
- General:
- Tidied up various in-line documentation/comment verbiage
- Added clearing element before closing elements on all Conductor sidebars/content areas (templates)
- Small JavaScript optimizations
- Created script that is loaded on each Conductor admin page for general bits of functionality
- Content Layouts
- Removed trailing slash from permalink on built-in “blog” page
- Customizer General
- Fixed bug when conducting content layouts without a permalink structure (Previewer always re-directed to home_url())
- Customizer Controller
- Adjusted [removed: customize-base, customize-controls] dependencies on Customizer content layout control script enqueue
- Fixed variable name in JavaScript closure (was ‘exports’ now ‘wp’)
- Conductor Widget
- Ensured admin script was enqueued after Customizer Widgets when in Customizer
- Extended ‘formSyncHandlers’ to add callback for Conductor Widgets in Customizer
- Fixed bug where content type was incorrect sometimes due to loss of focus on select box after a widget was saved in the Customizer
- Fixed a bug where “post_id” setting was not reset after switching content type during a session in the Customizer
- Fixed a display conflict with some plugins by tightening up CSS on Conductor Dashicons in the Customizer and Appearance > Widgets
- Fixed bug where CSS was not loaded when a Conductor widget was placed in any sidebar that was not registered by Conductor; Thanks Martin Avery
- Fixed jQuery Sortable data that was generated after sorting output elements to ensure correct data and data types were stored on the widget (added data-value HTML5 attribute to output elements that were associated with a value)
- Fixed a bug where max_num_posts setting could be set to 0 (zero) and pagination would not function correctly on default Conductor Widget Query class
- Fixed a bug where pagination did not function properly without a permalink structure
- Fixed bug on single posts where pagination did not function properly with any permalink structure
- Add-ons
- Created working add-ons panel
- Updates
- Switched to HTTPS for updates
- Modified Conductor Updates class to allow add-ons to extend/create instances of updater
- Introduce get_version(), get_conductor_version(), get_author(), get_plugin_file(), and get_conductor_plugin_file() functions
- Fixed issue where update_plugins transient was constantly emptied which resulted in update checks on every page load
Conduct your content!