Hi Ismael,
I confirm that the fields have the same values for all the CPTs using the same Custom Layout. For more details here are the found values for each custom fields provided :

• _aviaLayoutBuilder_active : active
• _aviaLayoutBuilderCleanData : [av_custom_layout link=\’alb_custom_layout,653\’ av_uid=\’av-m3u7m8lu\’ sc_version=\’1.0\’]
• _avia_builder_shortcode_tree : a:1:{i:0;a:3:{s:3:\”tag\”;s:16:\”av_custom_layout\”;s:7:\”content\”;a:0:{}s:5:\”index\”;i:0;}}
• _alb_shortcode_status_content : 0 occurence of this meta_key found
• _alb_shortcode_status_clean_data : 0 occurence of this meta_key found
• _alb_shortcode_status_preview : 0 occurence of this meta_key found
• _avia_sc_parser_state : disabled
• _av_alb_posts_elements_state : a:1:{s:16:\”av_custom_layout\”;b:1;}
• _av_el_mgr_version : 1.0

I’m now able to mass import all entries in a row ! this is marvellous ! Thank you Ismael ! You can mark this thread as solved.

I have a secondary question about my mass data import project but I’m opening another thread about this.

Thanks !!!

Thank you Ismael for your answer.
I’ll analyse the values of these fields and try to determine how to set them programmatically.

The meta fields I’m the less sure about are the following (the values displayed below are from a CPT where I activated ALB manually) :

• _avia_builder_shortcode_tree : a:1:{i:0;a:3:{s:3:”tag”;s:16:”av_custom_layout”;s:7:”content”;a:0:{}s:5:”index”;i:0;}}
• _av_alb_posts_elements_state : a:1:{s:16:”av_custom_layout”;b:1;}

Do you know if there is any Enfold documentation about the way their values are generated ?

Best regards,

• This reply was modified 2 weeks, 6 days ago by agencelarsen.

Hello Ismael,
thank you for your quick answer !
Unfortunately I can’t use the import/export tools for this CPT because it’s an Excel database of hundreds of entries from my customer that I need to transform into this freshly created CPT.

So I’ve prepared my Custom Layout for this CPT (as well as all my custom fields, with ACF) and I’d like to be able to import the data and programmatically activate the Advanced Layout Editor.

Using only the custom field _aviaLayoutBuilder_active with the “active” value, the Advanced Layout Editor is well activated but not rendered in frontend. I have to open the edition page of each CPT manually and then click “Update” in order to generate the proper avia custom fields.

It’s quite frustrating to see that all my CPTs are ready, with the right content, but that because of this small detail there’s still a manual operation to perform on hundreds of posts.

Best regards,

Hi Yigit, thank you for your answer. I must have made a mistake while trying to add event categories…

I’ll add some tags to my events with the artists names and I would like to add an “upcoming events” element to the artists pages showing up the next events they are playing in. Do you think that the event filtering could be done with tags like its done with categories ? It would be looking like the masonry filtering options using tags or categories… ?

Thank you very much

Hi yigit.
The problem occus only while you use their premium service that redirects every woocommerce email through their own server. It seems to overwrite the sending process of WP and/or the Enfold contact form.

Do you have a way to force the sending method for your theme ?

Thank you.

Arsène

I red that on your suggestions on other topics. This would be nice for a little blog but we are launching a cosmetic brand and can’t afford having any unwanted visitor. Especially because some payment plugins are already enabled on our Woocommerce, plus, we are using several accesses by user roles and really need to work on the whole customer funnel, starting from our real homepage.

Sadly, we need to use a bunch of plugins that are slowing down our website but we compensate by a great server and some fine tuned caching tools. WordPress isn’t known for being really “lite” as an e-commerce platform.

Best regards,
Arsène Lesueur

Hello, my developer found a workaround by adding the filter below :

 add_filter( 'template_include', 'override_wplauncher_options', -1000000000000000000000);

function override_wplauncher_options($template)
    {
        global $wp_launcher;

        return $wp_launcher->launch($template);
    }

I guess this is not a permanent fix but I hope it’ll help improving your product.

Regards,
Arsène