Tim in Seattle

+1

Thanks, sounds great.

People who use GenerateBlocks usually use it as their primary block package, so it’s used on every page and post. Therefore, if Wayfinder was incompatible with GenerateBlocks, there would be no reason to install it. So really, I don’t think a disable feature is needed. I’ve been testing the Editor Block Outline plugin by Kalimah Apps, and while it is compatible with the new GenerateBlocks, I don’t like it as much as Wayfinder.

@themolitor, I’ve heard back from the GenerateBlocks team. Here’s their reply, which might give you insight into what has changed in GenerateBlocks and why Wayfinder is now conflicting with it. Their example is with their Button block, but the same is true for their Container block.

The old GenerateBlocks Button block used to always be inside the Buttons wrapper block, so they had this selector:
.gb-button-wrapper .gb-button {
/* CSS */
}

Now that the Button block can be by itself, it has a simpler selector:
.gb-button {
/* CSS */
}

Unfortunately, this makes it less specific and can leave it prone to being overwritten by more specific selectors. This is what’s happening with the Wayfinder plugin – they’re using a very specific selector. It may be worth reporting to them to see if they can lower the specificity.

@themolitor, thanks for the reply. Wayfinder worked perfectly with GenerateBlocks prior to their version 1.7. They totally rebuilt the way their Container block works and now there is an issue. The GenerateBlocks team is looking into the issue today as I’ve given them access to my sandbox website. I can’t imagine I’m the only person impacted since GenerateBlocks is a 5-star rated blocks plugin with 100K+ installs. I just tested by turning off “Display block type” and it made me realize how much I actually depend on the block type display.

@ndiego, thank you for the detailed reply.

Thank you @fernandoazarcon2, that works. Of course, making a message field part of the GB Query Loop block would be the best solution. While working in the editor, the GB Query Loop block does display “No results found” when there are no posts.

@diggeddy, I don’t see the GenerateBlocks Query Loop block having an Advanced > Additional CSS field. I’m using GenerateBlocks 1.6.0 and GenerateBlocks Pro 1.4.0.

In version 1.0.8 of Carousel Slider Block for Gutenberg, I see the Responsive Settings panel where the “Slides to show” and “Slides to scroll at a time” can be adjusted for one screen width; mobile for example. It would be great to add at least one more break point for tablet.

Perfect. Thank you.

Hello, removing some of the delayed JavaScript files did get the pop-up to show, but now it is showing at the bottom, below the page. I have even deactivated all JavaScript delays and the pop-up still shows at the bottom. This is the website: AuthenticID.com.

Thank you for the fix. I am really enjoying using Nelio Popups. You have done a good job in designing this blocks plugin. I like the attention to user interface detail I can see in the plugin. I wish more developers would create single-use block plugins like Nelio Popups that do one thing, do it well, and naturally fit into the WordPress Blocks ecosystem.

Uh oh, the Nelio Popups v1.0.5 update totally broke GenerateBlocks on my site.

@demian85, thanks for that shortcode. I did modify it (changed echo to return) to make it work better for inserting within the content using the Shortcode block.

function nested_shortcode_gravity_acf(){
	return do_shortcode('[gravityform id="' . do_shortcode('[acf field="gravity_form"]"') .' title="false" description="true"]');
}
add_shortcode('gravity_acf','nested_shortcode_gravity_acf');

Ahhh, it does work when added as a mu-plugin. Thank you.