• I created an elementor header template and set the conditions to show on all pages–on Site#1. Site#1 shows the header on pages as expected. The template was then published to Site#2. Site#2 does not show the header on any pages.

    As a workaround, I can go to each site that the template was published to, go to elementor site settings and edit the template. There I have to add a condition as none exists.

    It appears that the condition is stored in the options Site#1 table (i.e. wp_54_options) with the option_name of ‘elementor_pro_theme_builder_conditions’ and value of ‘a:1:{s:6:”header”;a:1:{i:63;a:1:{i:0;s:15:”include/general”;}}}’

    After broadcasting to Site#2, (wp_58_options table), the same setting has a value of ‘a:0:{}’

    Apparently, Broadcast is not updating this value.

    The Broadcast Elementor plugin is enabled.

    Thanks for any help you can provide!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author edward_plainview

    (@edward_plainview)

    Wow. Elementor support just gets more and more complicated. I thought that conditions were bound to each template.

    I think, perhaps, adding some code to the Elementor add-on that interacts with the copy options add-on is the best way to solve this, user interface wise.

    When using the Copy Options add-on to copy the elementor_pro_theme_builder_conditions option between blogs, the Elementor add-on detects the option and then modifies the IDs on each child.

    If that sounds logical, could you make up a whole bunch of various conditions for different things, and then send me the contents of that option? It appears to be similar, but not quite the same, as the conditions of a single template.

    Thread Starter dmayhak

    (@dmayhak)

    Will do! I’ll get some samples to you as soon as i get a chance to work on that again. Thanks!

    Thread Starter dmayhak

    (@dmayhak)

    Had a few minutes to throw this together. There are a ton more combinations that can be made. Will try to get more examples later tonight.

    I am assuming that stuff like the custom post types (like saints below) would include the id for selecting singular items. (i.e. include/singular/saints/[nn])

    let me know if you want any other additional info. Thanks!

    elementor_pro_theme_builder_conditions option value (with comments):

    a:2:{
        s:6:"footer";
        a:1:    {
            i:105; // id of the site footer template
            a:6:{
                i:0;
                s:15:"include/general";
                i:1;
                s:22:"exclude/archive/author";
                i:2;
                s:30:"exclude/singular/in_category/1"; // uncategorized
                i:3;
                s:21:"include/singular/post"; // include on all singular post
                i:4;
                s:23:"include/singular/saints"; // custom post type
                i:5;
                s:31:"include/singular/e-landing-page";
            }
        }
        s:6:"header";
        a:2:{
            i:99; // id of the home page header template
            a:1:{
                i:0;
                s:24:"include/singular/page/11";
            }
            i:69;
            a:2:{ // id of the site header template; excluded on home page
                i:0;
                s:24:"exclude/singular/page/11"; // home page id
                i:1;
                s:15:"include/general";
            }
        }
    }
    Thread Starter dmayhak

    (@dmayhak)

    I added some more items such as popups and singular posts, etc. It appears that the elementor_pro_theme_builder_conditions value is somewhat of an aggregate of the _elementor_conditions entry in the postmeta table. Looks like both are being used now.

    adding more details on the workaround

    1. set up a template (footer in this example) on SiteA
    2. set the conditions as normal
    2a. postmeta => _elementor_conditions is set
    2b. options => elementor_pro_theme_builder_conditions is set
    3. publish to SiteB
    3a. postmeta => _elementor_conditions is set
    3b. options => elementor_pro_theme_builder_conditions is not set
    4. go to SiteB theme builder and select Footer in left menu
    5. on the footer overview area, the instances (conditions) text is correct
    6. click Edit Conditions
    7. broadcasted conditions appear
    8. hit save & close
    8a. postmeta => _elementor_conditions is set (already was)
    8b. options => elementor_pro_theme_builder_conditions is now set correctly

    I am thinking this is not just a simple “update the option being broadcast and save it” as the destination site may have templates of its own that need to remain in the options setting. Seems like it has to weave together the broadcasted settings with the settings for the destination. And also remove the settings for the templates being “un-broadcasted”

    Let me know if I can be of any assistance with this. (testing, etc.)

    Thanks!

    • This reply was modified 3 years, 1 month ago by dmayhak.
    Plugin Author edward_plainview

    (@edward_plainview)

    I’ve had a nice long look at this. Copying the options is fine, and normally so would translating the options – but some of the conditions require knowing equivalent taxonomy term IDs.

    Unfortunately, this is only known during broadcasting.

    Copying of options does is a separate tool from broadcasting, therefore the equivalency information is not available.

    If this is going to be possible, I’ll have to figure out a way to “fake” a broadcast in order to access the temporarily saved equivalency data, or massively redo the Broadcast linking data so that it permanently saves all equivalency data as it occurs.

    The first option is far more realistic than the second, since there is no great way of storing such data internally in WP and I don’t want another external table.

    This is difficult. :/

    Thread Starter dmayhak

    (@dmayhak)

    Thanks for looking into it. Sorry it seems to be a pain…

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Elementor pro display conditions not broadcasting’ is closed to new replies.