Hi everyone! We’re still working on Responsive Styling, but have adopted a new approach to scheduling and updates that will allow us to release more frequent intermediate updates. Next week we’ll be doing this smaller release, but with a lineup of powerful ACF improvements and some under the hood performance improvements. We’ve also merged some refactoring to clear some roadblocks towards powerful workflow improvements down the road like Global Elements and Multiple Element Selections. These features won’t be in this release, but we’re glad to be moving in that direction.
Status
- 3/1 - Official release available is now available
- 3/1 - We are preparing to go to manual updates with the official release. If you were using a beta version, there are two breaking changes you can review here before updating
- 2/25 - Beta 3 now available. Numerous fixes/adjustments. Threads where issues were reported have been updated
- 2/23 - Beta 2 now available. Fixes error saying builder failed to save even though it worked behind the scenes
- 2/22 - Beta 1 now available
Notable Changes
- Loopers support ACF repeater and relational fields
- Pro: The Grid element is now available in all builders
- Saving builders will now store only the fields that have deviated. This means if you resave your pages they will take up less space in the database. Consequently, it will use less resources for your server to serialize/unserialize on the front end and in the builders.
Testing
- Under Dynamic Content, you’ll find new options for ACF. The field enumeration has been updated to properly detect what is available in each context (works with post meta as well)
- There is a new Looper Provider type called Dynamic Content which will allow you to access ACF values that return arrays like Repeaters, or relational fields
- If your ACF relational field provides terms or posts, make sure you set the field output to “Term Object” or “Post Object” instead of ID. This will ensure you can access the data of the respective item inside the looper consumer
- As always, continue sharing your feedback on how you think our products can be improved
Changelog
Pro
- Updated - Performance improvement: Builders only save values that have changed from the default
- Updated - Add Grid Element to all Builder contexts
- Updated - Dynamic Content now shows which meta fields are available in the current context
- Updated - Add Term Slug to Dynamic Content
- Bugfix - Fix missing characters for new social share element that affects email sharing feature.
- Bugfix - Fix nav_menu_link_attributes not applying class from other plugins to navigation elements
- Bugfix - Fix Dynamic Content directives not being parsed in pages with only Classic Sections
- Bugfix - Fix worker script not loading cross origin
- Bugfix - Fix Mobile Button CSS output not specifying px unit
- Bugfix - Fix Bar generated CSS outputting invalid value for border radius when it should be disabled
- Bugfix - Fix Query Builder not specifying tax_query relation
- Bugfix - Fix performance issue with unlimited sidebars
X
- Updated - Dynamic Content now shows which meta fields are available in the current context
- Bugfix - Fix WP Bakery legacy integration missing styles to format backend editor content
- Bugfix - Fix Mobile Button CSS output not specifying px unit
- Bugfix - Fix performance issue with unlimited sidebars
Cornerstone
- Updated - Performance improvement: Builders only save values that have changed from the default
- Updated - Dynamic Content now shows which meta fields are available in the current context
- Updated - Add Term Slug to Dynamic Content
- Bugfix - Fix missing characters for new social share element that affects email sharing feature.
- Bugfix - Fix nav_menu_link_attributes not applying class from other plugins to navigation elements
- Bugfix - Fix Dynamic Content directives not being parsed in pages with only Classic Sections
- Bugfix - Fix worker script not loading cross origin
- Bugfix - Fix Query Builder not specifying tax_query relation
Reporting Issues
- Please let us know of any bugs, regressions, or even just things that don’t feel quite right to you.
- To make a report, open a new topic here in the beta forum.
- Related items or a collection of feedback on the same subject can be combined into a single topic.
Thank-you in advance for helping us with this most important testing phase!