Viewing 19 posts - 1 through 19 (of 19 total)
  • Author
  • #993073

    So with Gutenberg being actively promoted with WP 4.9.8, albeit as a plugin, I think we can consider this to be in the wild now – clients are certainly going to start to try it.

    Unfortunately, as I found out when I did so today, Enfold and the Gutenberg plugin do not play well together.

    Guess I was expecting to see the Gutenberg UI with a nice big clear Advanced Layout Editor button to switch to the avia page builder instead but no – turns out that the enfold page builder is not an option at all with Gutenberg enabled so the theme is unusable with it.

    I hope you are way ahead of the curve with this and are poised to release a Gutenberg compatible version but comments from moderators like this from June: We have been busy with bug fixes and new functionality for the theme, so we haven’t been able to test it yet unfortunately. I would assume that there will be some problems with it …” and the fact you are still referring customers to a statement from April are starting to worry me a bit.

    So what exactly is the plan guys? We need to know. Thanks.

    • This topic was modified 4 years ago by  M1000000.

    Gutenberg and Avia Layout Editor are not compatible? Let’s wait and see, … I did not activate Gutenberg.


    Hello Kriesi Team,

    I am also interested in info on this topic – I’m sure you are already working on compatibility with Gutenberg, please inform us about your plans!
    I’m running different Enfold versions on different Websites and would like to be ahead of the game, if possible.



    Also interested in this as have a lot of clients who will want to be updated.


    At least one of our hosting providers (siteground) is now actively encrouraging clients to “give it a go” so more important than ever for Enfold team to get on top of this with a plugin compatibility release asap IMHO.


    To be fair to the team behind Enfold, I love their UI when creating content using the Advanced Layout Editor so would be disappointed if that changed much. I haven’t really looked into much yet, but it looks like WordPress new Gutenberg editor plugin is pretty much the same idea as what Enfold already had. I think the problem will be when WordPress eventually remove support for the ‘Classic’ editor layout. Tats when Enfold should need to be worried.


    Me too.
    I spended a lot of money and time for my website and really dont want to start from scratch.


    All visual page builders are affected (95% of all websites from themeforest). I love Avia cause it has plenty of neat features all other page builders do not have. It is such a time saver and pretty much zero support for my clients. Explaining how to use it.
    The enfold staff is great!
    I would like to see this solution: Avia will not only be compatible with the Gutenberg but also allows us to use the power of Gutenberg within the avia page builder.

    Kriesi’s statement to this topic: https://kriesi.at/support/topic/wordpress-gutenberg/#post-900941

    Visualcomposer has a solution already: https://visualcomposer.io/docs/content-elements-structure/gutenberg-element/
    I stick to Avia.

    • This reply was modified 4 years ago by  royaltask.

    All I want to see is the advanced layout editor option so I can switch to it in place of gutenburg (which after a bit of familiarisation will be fine as a replacement for current text editor in WP). The two can then live side by side and separately as far as I’m concerned.


    Stupid Question for the editor now (TinyMCEAdvanded). When i use the AVIA Builder and change Theme what will happen to the design? When i so back to the normal editor? Will it look the same ?
    What if i have AVIA built Sites and now change to Gutenberg? how will it look? Will it ruin my site by changing something?

    I like the AVIA very much, but to be honest the Gutenberg editor is very simple and nice, for me its enough, maybe faster because you see what you do .


    Guttenberg extremely basic compared to “proper” page builders in my view – nothing more than useful enhancement for text editor / content where page builder not used – we keep all posts as native and only use page builders for pages for example.

    I don’t think there is any reason avia or other page builders will be overshadowed by Guttuenberg for some time to come – they will coexist.

    As for Enfold – sites still render as expected with GB plugin enabled – just no way to access Advanced Page Builder which I hope will be fixed with a release in the not too distant future. Avia shortcodes just appear in a text block in the same way as they always have when you switch off advanced builder.



    Thank you for using Enfold.

    The new editor alters the default page/post edit link automatically, but you can override that with this in the functions.php file so that you can edit the pages in the advance layout builder while having the option to switch to the gutenberg editor.

     * Registers an additional link in the post/page screens to edit any post/page in Gunterberg
     * and reverts the default edit link back to the classic editor.
     * @since 4.4.2
     * @param  array   $actions Post actions.
     * @param  WP_Post $post    Edited post.
     * @return array          Updated post actions.
        remove_action( 'admin_init', 'gutenberg_add_edit_link_filters' );
        function avia_builder_gutenberg_add_edit_link( $actions, $post ) {
            if ( ! is_plugin_active('gutenberg/gutenberg.php') ) {
                return $actions;
            $gutenberg = get_edit_post_link( $post->ID, 'raw' );
            // Build the classic edit action. See also: WP_Posts_List_Table::handle_row_actions().
            $title       = _draft_or_post_title( $post->ID );
            $edit_action = array(
                'classic' => sprintf(
                    '<a href="%s" aria-label="%s">%s</a>',
                    esc_url( str_replace('&classic-editor', '', $gutenberg) ),
                    esc_attr( sprintf(
                        /* translators: %s: post title */
                        __( 'Edit &#8220;%s&#8221; in the new editor', 'avia_framework' ),
                    ) ),
                    __( 'Gutenber Editor', 'avia_framework' )
            // Insert the Classic Edit action after the Edit action.
            $edit_offset = array_search( 'edit', array_keys( $actions ), true );
            $actions     = array_merge(
                array_slice( $actions, 0, $edit_offset + 1 ),
                array_slice( $actions, $edit_offset + 1 )
            return $actions;
        add_filter( 'page_row_actions', 'avia_builder_gutenberg_add_edit_link', 10, 2 );
        add_filter( 'post_row_actions', 'avia_builder_gutenberg_add_edit_link', 10, 2 );
        add_filter('get_edit_post_link', 'avia_builder_gutenberg_edit_post_link', 999, 3);
    if(!function_exists('avia_builder_gutenberg_edit_post_link')) {
         * Set the edit post link to the classic editor.
         * @since 4.4.2
         * @return string $link.
        function avia_builder_gutenberg_edit_post_link($link, $id, $context) {
            return add_query_arg('classic-editor', '', $link);

    After adding the filter, you should see these changes in the pages/posts panel.

    Screenshot: https://imgur.com/a/rj8KSuY

    Best regards,


    Hi Ismael,

    Have tested this and unclear what exactly it is supposed to do. As you say it changes the options in the page/posts panel but the same functionality is already acheivable without this code – when presented with the native Edit | Classic Editor | Quick Edit | Bin | View options, selecting Classic Editor on a page built with avia builder takes you to the advanced page editor as expected.

    But this is not the whole issue – there are more than one entry points to editing a page – clicking “Edit Page” in the admin top bar for example – which takes you to the Guttenberg editor. Although page builder is displaying in a tab below this it requires a long scroll through pages of shortcodes so is not going to work for client sites as it undermines the simplicity that is key to using avia and will confuse non technical editors.

    So, somehow, the default option needs to be applied per page/post so that they open in the appropriate view depending whether they have been created using Advanced builder or Default editors as is currently the case.

    Thanks, M



    clicking “Edit Page” in the admin top bar for example – which takes you to the Guttenberg editor.

    That is the whole point of the code above. As we’ve said, the plugin alters the default post editor links, making “Gutenberg” as the default editor, so clicking on the “Edit” panel or the post/page title will redirect you to the new editor instead of opening the advance layout builder, contrary to what you would expect when using the Enfold theme. The above filter reverts the links back to default so that the “Edit” and the post/page title open the classic editor and then creates a new “Gutenberg Editor” button so that you can still choose the new editor when necessary.

    clicking “Edit Page” in the admin top bar for example

    Use this filter to change the admin toolbar link.

        function avia_builder_gutenberg_admin_bar_link($wp_adminbar) {
            if( ! is_admin() && AviaBuilder::get_alb_builder_status( get_the_ID() ) == 'active' ) {
                $edit_node = $wp_adminbar->get_node('edit');
                $title = is_home() ? 'Frontpage' : get_the_title();
                $link = add_query_arg('classic-editor', '', $edit_node->href);
                $args = array(
                    'id'    => $edit_node->id,
                    'title' => $edit_node->title,
                    'href'  => $link,
                    'parent' => false,
                    'group' => false,
                    'meta'  => array( 'target' => 'blank' )
                $wp_adminbar->add_node( $args );
        add_action('admin_bar_menu', 'avia_builder_gutenberg_admin_bar_link', 999); 



    Thanks Ismael – makes sense – on a deadline right now so will test and feed back next week.


    I also note a new statement here: https://kriesi.at/support/topic/enfold-4-4-1-gutenberg/
    Looking good!


    Hi M1000000,

    Thanks for the feedback. Please let us know if you should need any further help on the topic.

    Best regards,


    I have updated my first site with WP 5.0.2, along with the newest Enfold version. So far, it all looks fine. However, do you recommend that I use Disable Gutenberg plugin? Have you found it to work with Enfold now?

    Thanks much,



    It’s not necessary unless you’re having trouble editing the pages. There is going to be a new option where you can disable/enable the classic and block editor.

    Best regards,

Viewing 19 posts - 1 through 19 (of 19 total)

You must be logged in to reply to this topic.