Copernicus

OK, thank you for looking into it.

Yes — the override mode is working to negate this (for anyone else who might experience the issue before it can be fixed).

Thanks again for your work on this plugin – it fills a gap in what, as others have noted, “should be in core.” ??

Small updates/notes:

• When I check in the ‘Code Editor’ view (instead of the ‘Visual Editor’), it shows the attribute values displaying as expected (i.e. not duplicated)
• I’ve found that if I switch to use the ‘override‘ mode on the attribute and then re-save the issue no longer occurs (it accurately displays one instance of the value on the front-end).

Wow – thanks for the addition of the feature & for the notification of the new version/updates, Nick.

Looking forward to trying it out!

I was coming here to make the same request: more of a visual indicator within the admin when a block is disabled.

I definitely do see the icon indicator, but like the original poster, I was hoping for something a bit more obvious – especially when handing off a site to a client or other user that might not intuitively look for the indicators.

Possible Solution

While this won’t work for everyone, since I’m using an editor style sheet, I just added:

.block-visibility__is-hidden { opacity: .25; }

and got a very workable result.

Again: this is for a style sheet that is specific to the WordPress backend/editor view – not for a theme’s general style sheet.

Hope this helps anyone else seeking a similar indicator.

And thanks again, Nick, for a great plugin!

• This reply was modified 2 years, 12 months ago by Copernicus.

Thank you for the point of information. I switched to the Twenty Twenty One theme and confirmed that its functions.php includes a call to add_theme_support('editor-styles'); and do see that the Lazy Blocks UI displays accurately.

As you noted: it appears to be an issue with my installed theme (which, to help anyone else out in the future, is the Astra theme with a child theme active).

Thanks again for your help.

That’s excellent news: THANK YOU for adding in this helpful modification to the plugin’s options!

We’ve updated & tested it out – it works perfectly.

Thanks again!

@rockiger Making it optional would be great (otherwise we can never update!). And, it seems like it would be a fairly reasonable use case to have a need for non-React-based subpages (for other/future users of this plugin).

Thanks again for your work & helpful support!

Thanks for your assistance, ThemeHigh.

Yes – I know that the visual style can be changed via CSS, but I am hoping that there’s a solution so that we can set the actual coded tag of the headings as something other than H1.

The headings of these product field groups are not appropriate for h1 tags (instead, h3 or h4 would be more appropriate). So, I was hoping to find a solution for changing from h1 to h3 (for example) rather than just changing the displayed size.

THANK YOU, @davidlillo – that was it exactly.

The plugin settings are such at there’s some sample/placeholder text in that Chat Window > Call to Action field.

It’s not obvious that we have to customize/replace that in order to get the chat interface to work properly. But, thank you for intuiting exactly what was needed!

@specialk YES – regarding the issue with the Prismatic plugin interfering with code added via the Divi Builder’s “Code” module – the new version solves/fixes that.

Thank you!

• This reply was modified 3 years, 7 months ago by Copernicus.

If it helps in the exploration of this issue, we’re also finding that the latest update to Prismatic is mangling code added via the Divi Builder plugin (within Divi’s ‘code’ module). We rolled back to 2.7 and the issue was no longer present.

Well, shoot – I thought I could get this working with something like

<?php the_widget( 'orgSeries_widget_seriestoc' ); ?>

in the template, but it’s not working.

I guess, what we’re ultimately seeking is a way for the “Post Title in Widget” override to work across all of the tables of contents for posts within a series. But, perhaps that’s just not possible at this time (which is understandable, given how much this plugin can already do).

I tried searching the extensions docs to see if there was an existing shortcode or token that could accomplish this, but I’m not seeing a solution.

Anyone who comes along & can determine or fashion a solution – I’m appreciative of the input!

Thanks so much for your help, @nerrad ! I know that your time is limited & this insight is very helpful and welcome.

My immediate guess as a way to proceed in getting the ‘override’ text to display in other areas of the page is to call the widget via shortcode and/or call the widget with a template layout. I’ll work on this and report any progress in this thread in the event that it is helpful to others.

Thanks again, @nerrad !

YES! That did it. THANK YOU!

For any others who may find this in the future, here’s the change that I made to the code above to work in the manner that I was seeking.

If my original code was:

wp_list_pages( array(
   'title_li'    => '',
   'child_of'    => '1',
   'show_date'   => 'modified',
   'exclude'    => '2,3,4,5',
   'depth'    => 1,
   'date_format' => $date_format
 ) );

The modified code (from sterndata’s assistance), is:

$excludes = "2,3,4,5," . $post->ID;
wp_list_pages( array(
   'title_li'    => '',
   'child_of'    => '1',
   'show_date'   => 'modified',
   'exclude'    => $excludes,
   'depth'    => 1,
   'date_format' => $date_format
 ) );

Thanks again, sterndata!

Right, yes, that’s the same as what I referenced above.
I completely understand how to exclude specific pages with something like <?php wp_list_pages( 'exclude=17,38' ); ?> and I understand how to exclude the current page with exclude=".$post->ID.".

What I’m trying to do is exclude BOTH the specific list AND the current page.

If it help clarifies the issue, this is what I currently have:

wp_list_pages( array(
   'title_li'    => '',
   'child_of'    => '1',
   'show_date'   => 'modified',
   'exclude'    => '2,3,4,5',
   'depth'    => 1,
   'date_format' => $date_format
 ) );

If I changed “'exclude' => '2,3,4,5',” to “'exclude' => $post->ID” then it would exclude the current page instead of that specific lists of page IDs. But, I want to do both.