Cornerstone 7.8.0, Pro 6.8.0, and X 10.8.0 Beta (1)

[charlie]

It’s still pretty cold outside (for some of us). So stay inside and boot up those testing sites because Cornerstone enters it’s next beta. There’s a lot to go through on in this release. I’ll post the full changelog below this message. Thanks for joining us for the ride.

See how to test the beta here.

Test the Beta | Themeco Docs

Pressed on time? Check out the beta playground to test the new features on our sandbox site.

Cornerstone Live Demo

Quality of Life

There’s a lot to Cornerstone, especially with the release of Cornerstone Forms. And this year we decided we wanted to really cleanup some of the rougher edges. There’s more to come in this regard, but here are some starters in this release.

• Element parameters Dynamic Content will display a list of available parameters. Instead of manually typing in all your parameters
• Autosave builder preference.
• Box and Text shadow have new defaults so when you enable those features, something actually changes on the page.
• Video and Audio element will utilize SVG icons when in Font Awesome SVG mode

Our Looper Dominance Continues

Some of you probably forgot we were in a Looper Renaissance. In this release we’ve added in the Menu and User looper. Create a user directory page or a user selectbox using Cornerstone forms. Build a menu completely from scratch. Both are great additions to our growing collection of Loopers.

(No Longer) Lost in Translation

We make a big move in how we handle translations in Cornerstone and WPML. We are deprecating the WPML manual editing system that worked entirely in Cornerstone. There are fundamental issues with this approach and we are going to move to something more simpler and standarized with WPML. Translations will now be handle entirely through WPML in their dashboard. We are currently working with them to get Layouts and Components translatable here. And in this release every element data that should be translated will be sent to WPML from us. Meaning Cornerstone Forms and any new element going forward will be completely translatable.

In it’s place for more advanced pages, we will have Localization Dynamic Content and Localization Conditions. Using one page you can create completely different sections based on Conditions or Dynamic Content.

As we move to this new system with WPML we’ll let you enable this older system in our settings. Sites built before this release will automatically enable this setting. We will not be adding features to this manual system. Instead focusing on making sure all Elements, Layouts, and Components are able to be translated by WPML. It might take some time working with WPML to make sure that’s possible, but we’re currently working with them closely to make sure their translation dashboard works properly.

Cornerstone Forms

Thanks for the initial feedback on Cornerstone Forms. As we parse this feedback, we’ll be making some changes to the core of Cornerstone Forms and while we do that we might need to change most of the forms we supplied for you.

Have a great day.

[charlie]

Beta 1

• Feature - Autosave builder preference
• Feature - Element Dynamic Content. Which will output data from your element.
• Feature - Menu Looper
• Feature - User Looper
• Feature - Is Cornerstone Preview condition
• Feature - Menu custom icons uses our icon picker
• Feature - New dynamic options for Cornerstone controls, db_options, post_type, terms.
• Feature - WooCommerce layouts have checkout endpoint assignments
• Feature - Control partial list-style
• Feature - function cs_render_child_elements_as_data for usage in data based element rendering
• Feature - valid_ancestor control option which requires the element type to have a parent be a certain element type
• Updated - A URL parameter that was 0 would not be returned properly
• Updated - Control type select will enter breakout mode when using value __custom__ as a select option
• Updated - cs_element_library_group_arrangement filter to change the elements group order
• Updated - cs_element_should_hide filter to add custom element hiding code
• Updated - sql can be use as a mode type in the ‘code-editor’ control type
• Updated - Cornerstone control type date-time has a timeFormat and a dateFormat option
• Updated - Element prefabs have their own custom Icon
• Updated - Our special post types will show a post list inside the WordPress dashboard
• Updated - Preview based settings code moved out of preview to App
• Updated - You can utilize light-dark as a color value in our color picker
• Updated - Audio and Video element did not utilize SVG icons when in Font Awesome SVG mode
• Updated - Parameter dynamic content will display as a select box of available parameters
• Updated - Box and Text shadow have new default values so the App can seem more responsive when enabling those features
• Updated - Template tab renamed to Library
• Updated - Component name setting will try to create a slugged version of it’s title
• Updated - The Query Builder post list will utilize the current post types selected to limit the number of posts in the list
• Updated - WPML Cornerstone manual editor is turned off for new sites. Sites built with previous versions will have this enabled when upgrading during this transition period
• Updated - WPML integration will send info about our elements so all elements going forward will be translatable by WPML by default
• Bugfix - You couldn’t use a bool value in a ‘list’ type control
• Bugfix - The menu custom icons were causing severe performance issues
• Bugfix - Alt colors not working on a breakpoint when it’s the same as the base value

[devinelston]

So. Much. Awesomeness.

@charlie

Feature - Menu Looper

– been waiting for this for a long time. LOVE IT!

@charlie

Feature - Is Cornerstone Preview condition

So this unlocks the ability to do in-context notation, right? I could have a whole section that would only appear in the builder, and not on the front end?

@charlie

• Feature - New dynamic options for Cornerstone controls, db_options, post_type, terms.
• Feature - WooCommerce layouts have checkout endpoint assignments
• Feature - Control partial list-style
• Feature - function cs_render_child_elements_as_data for usage in data based element rendering
• Feature - valid_ancestor control option which requires the element type to have a parent be a certain element type

Will there be documentation for these? I’m unclear on what a few of them are.

[scotbaston]

Loving some of these new additions

Can we have some clarity please about autosave - does it update the published page or store the changes as a ‘cornerstone draft’ for recovery purposes only? I prefer the latter

Menu loopers, Am I right in thinking we can have conditions on each menu items so that certain menu items only show when the criteria exists - ie Christmas or Valentines options for a restaurant navigation. Also how does menu loopers work with the navigation elements? How would it process sub menus and below?

[charlie]

@devinelston Yes the Is Cornerstone Preview condition will let you create in builder notes. I’ll have most of those docs finished this week. They are advanced features primarily used by Cornerstone Forms.

@scotbaston Autosave just saves. If you had revisions turned on in your WordPress site, there would be revisions, but Cornerstone does not have a way to review revisions in the Builder.

When looping a menu, checkout the Looper Field Dynamic Content. It’ll show you the available data for each menu item. You can create conditions based on that data. To process a sub menu, you would double loop over the children key. The navigation elements don’t utilize the menu looper, they work exactly the same as they have been used.

[devinelston]

@charlie

When looping a menu, checkout the Looper Field Dynamic Content. It’ll show you the available data for each menu item. You can create conditions based on that data. To process a sub menu, you would double loop over the children key. The navigation elements don’t utilize the menu looper, they work exactly the same as they have been used.

Would be awesome to see an example of this. I’m having a heck of a time figuring out how to actually do that.

[quentosity]

Is Cornerstone Preview condition

This is great not just for hiding things on frontend but especially for the reverse for adding any frontend scripts that you don’t want to run while in the backend.

[whitemedia]

Hi @charlie,

How does this beta affect CS Forms beta testing? Is it fully compatible?, or do the two need to be kept separate - currently on 6.7.10-d4d0cc6 for CS Forms testing.

All best,
Christopher

[Misho]

@devinelston

Would be awesome to see an example of this. I’m having a heck of a time figuring out how to actually do that.

Yes indeed! I am trying to get the Menu item name into the looper consumer content. “Looper Field Dynamic Content” doesn’t expose it. Anyone found the way?

[charlie]

I have a very rudimentary looped menu. It doesn’t display properly in the preview, but I’ll figure out what’s wrong with that.
http://theme.co/app/uploads/share/menu-looped.tco

Glad you guys like the Cornerstone Preview condition. I wasn’t sure how much use we would get out of that.

The latest beta will work with the Forms beta. For the most part the Pro build I sent is the same, minus a couple of fixes that are in the current beta.

Have a great day.

[devinelston]

Very cool, thank you!

@charlie

I have a very rudimentary looped menu. It doesn’t display properly in the preview, but I’ll figure out what’s wrong with that.

In case it helps you run it down, it only previewed woo commerce pages as children of the parents when I both used yours and built my own test. Regular pages or archives it left out of the preview, but rendered fine on the front end.

[Regnalf]

Maybe i missed that information, but CS Forms is not in the current beta, right?

[charlie]

We just wanted to do a small beta for forms this time around and then focus on the latest release. We’re doing some heavy work on based on feedback, so what you see in the full launch might be different from what you would experience in the full launch.

[charlie]

RC1!

• Feature - Unit slider inputs can be incremented or decremented by the up and down keys on your keyboard
• Feature - Gradient builder can have it’s color stops dragged to certain positions
• Bugfix - Components that were also slots wouldn’t display their correct elements if only specific elements were allowed in that element
• Bugfix - You couldn’t use Element Dynamic Content in a condition