Overview of Woo360 2.1

Here's a summary of the new and changed features in the Woo360 2.1 plugin.

New features

Gutenberg support

This release works with the Gutenberg plugin or without it. See the Related Article on Gutenberg support for more information about how Woo360 works with Gutenberg.

Inline editing

You can choose whether to edit text fields and text areas inline or in the settings window. See the article on inline editing in the Related Articles below for more information.

Ability to save columns

You can now save columns. See the Related Article below for more information.

Font Awesome 5 icons

As of Woo360 2.1, you can use Font Awesome 5 icons. Note that Font Awesome 5 is not compatible with Font Awesome 4. See the Related Articles for more information about the FA5 subsets and how to activate the Pro version.

Posts module: Ability to exclude current post

The Posts module has a new option to exclude the current post from the query. This makes it easier to create a related posts section in your layout using a Posts module. See the Related Article below for more information.

Valid code enforcement

In Version 2.1, not only is there a validator that checks code that you enter into certain modules but also you won't be allowed to save a module with invalid code.

Code validation and enforcement applies to so-called ACE Editor fields, in particular, the following modules:

  • HTML module
  • Custom post layout window in the Posts module

It does not apply to text areas such as in the Text Editor module. It also does not apply to the Woo360 Theme.

Changes to user access settings

There's a new field called Builder access on the User access tab of Settings > Woo360, which lets you control the ability to open the Woo360 editor depending on user role. For more information, see the article on controlling user access in Woo360.

UI changes

Page Builder -> Woo360 UI labeling

Throughout the UI, the Page Builder and Builder labels have been changed to Woo360. For example, you'll see Settings > Woo360 instead of Settings > Page Builder, and you'll see a Launch Woo360 button instead of Launch Page Builder. Also, the Builder menu in the WordPress admin panel now displays Woo360.

Previously, the term Woo360 Plugin referred to the plugin itself, while Page Builder referred to the layout editor installed by the plugin. The current change consolidates the branding such that Woo360 refers both to the plugin and to the layout editor.



Anonymous usage data request

This release introduces a request for permission to collect anonymous usage data. See the Related Article for more information.

Developer features

Activate or deactivate a Woo360 license with WP-CLI

This release adds a new command that can be used with WP-CLI to activate or deactivate the Woo360 license on a site. See the WP-CLI article in the Related Articles below.

Alternative to how CSS and JavaScript get loaded

Developers: Instead of loading Woo360 CSS and JavaScript as an asset file, you can render the CSS inline in the <head> tag and the JavaScript inline right before the closing <body> tag. This can be a solution to some rare caching issues, but in most cases you don’t need to do it.

Add the following line of code to your functions.php file in your child theme:

add_filter( 'fl_builder_render_assets_inline', '__return_true' );

You'll also see a change in the name of the installed Woo360 Themer plugin on the Plugins page. It's now displayed as Woo360 - Themer Add-On. This change makes it more apparent that Woo360 Themer requires the Woo360 Plugin to work.