Using this causes modules to be unselectable in library

  • Resolved kindred

    (@kindred)


    3 years, 6 months ago

    This plugin is great and does exactly what it says.
    HOWEVER, it also has an unintended side effect….

    When I create a Library layout (row) of buttons with visibility defined by script, the layout-row becomes UNSELECTABLE for addition into pages….
    There seems to be a conflict. ??

    the moment I disable this plugin, the layout-row becomes selectable again.

    in module: is_amazon()
    script added to functions.php:

    // Divi module visibility
function is_amazon() {
	global $post;
	
	$r = false;
	if ( function_exists('get_field') ) {
		if ( get_field('amazon-link') ) {
			if ( !empty(get_field('amazon-link')) ) {
				$r = true;
			}
		}
	}
	
	return $r;
}
    • This topic was modified 3 years, 6 months ago by kindred.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Hi @kindred,

    We have just released v3.20 of Content Visibility for Divi Builder which resolved issues with the Theme Builder. It may also solve your issue here; could you please update and let us know how it goes? Thank you!

    Thread Starter kindred

    (@kindred)

    Sorry it took me so long to respond. Life is busy.

    I updated to v3.20.
    This does NOT solve the issue.

    specifically:
    Create a divi row object in the library (called Test1).
    Add a series of divi modules to the row. Each divi module has a conditional (in my case, referring to an advanced info field — links to vendor sites)

    Open a new layout in the library or edit an existing layout/page.
    Attempt to add a new row from the library
    (Test1 is listed as an option)
    Test1 is NOT selectable. Clicking on the button has no result.
    Row objects int he library which doe snot have conditionals associated ARE selectable for addition to the layout.

    Plugin Author Jonathan Horowitz

    (@jhorowitz)

    Hi @kindred,

    We have just released v3.21 of Content Visibility for Divi Builder which should resolve your issue. Please update and let us know how it goes; thank you!

    Thread Starter kindred

    (@kindred)

    Sorry to take so long to respond, again.

    I have updated to 3.2.1 — and the issue seems to be fixed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Using this causes modules to be unselectable in library’ is closed to new replies.