New features and improvements
Theme settings support
Views 2.5, along with Layouts 2.1, provides support for theme options that can be controlled from Content Templates and WordPress Archives. This means you can control theme options per-template you create, so different content types can feature different options.
You can find the Theme Options section at the bottom of the Content Template and WordPress Archive editing pages.
For this first release, Views supports the following themes:
Theme settings are kept when you switch themes. If you change your mind and return back to a theme that defined options for a Content Template or a WordPress Archive, all your existing settings will be restored and applied.
Extended page builders support
Views already supports some page builders to edit Content Templates: you can design them using Visual Composer or Beaver Builder.
You can now create and edit Content Templates using the Fusion Builder from Avada and Divi Builder.
New supported syntax for shortcodes
During development, we noticed a problem when reviewing our compatibility with Divi. In some Divi modules, adding a shortcode into their options or values was not producing the expected output. Divi sanitizes the content of such inputs before saving them to the database, and elements like square brackets, got replaced by their HTML entities. Basically, this resulted in breaking all the Toolset shortcodes.
This is why we are introducing a new shortcodes syntax. All Views shortcodes generated using the Fields and Views button found under Toolset Shortcodes entry in the top admin bar, will be generated using this new syntax.
Basically, the new syntax replaces square brackets with a custom placeholder that passes the Divi sanitization. So a shortcode like {{wpv-post-title}} becomes {{wpv-post-title}}.
Bugfixes
- Missing textdomain in some strings inside the output of password management shortcodes.
- Missing Help tab when editing a Content Template.
- Solved an issue with the CRED Edit Post links when trying to edit posts that do not have a “Published” status, but the current user can edit them as drafts, pending or future posts.
- Fixed an issue with negative numbers used inside Views conditionals.
- Solved a problem related to Content Templates designed with Beaver Builder, and used inside a View loop that loads content using AJAX.
- Fixed a localization problem that caused the button to add conditional shortcodes not being available on German installations.
- Solved an issue related to the Relevanssi integration, as the option to search in fields content was not available when adding a front-end text search filter.
- Fixed an issue with the Checkboxes front-end filters when only options that produce results should be available to select.