Zack Pyle

Thanks Kevin! I’ve created a PR that adds a filter to handle this globally. You can check it out here. The PR adds a code_block_pro_load_fonts filter that is backwards compatible but gives an easy way to disable the fonts from loading globally. Let me know what you think!

Ok thanks. I’ll give it a try!

I have used it in like 100 posts, so it’s not feasible to go in to each and set them all to system :/

@benbodhi Still having the issue. I just wrote some php to delete the inline_featured_image meta from all pages and not seeing the issue anymore

Looks like that function has been moved/renamed. It used to live in the main plugin file, but I don’t see it there anymore in the latest version.

Maybe use seopress_init()since that’s unlikely to change since it’s not tied to a feature?

Yes, no need for you to do anything. I’m fine with doing the triple square bracket when adding a Beaver Builder shortcode. It’s not often. Thanks for checking though

@kbat82 Beaver Builder support responded:

Its been like this since around July 2015 when WP blocked the use of shortcodes in HTML attributes and styles.

The workaround is to?escape the escape using triple square brackets

Yeah, looks like they have their own functions for rendering shortcodes at the right time in the page build and they are respecting the double square brackets for standard shortcodes, but not their own. I have submitted a ticket for them to look at and see if they consider it a bug (I do)

Either way, I have hooked into their filter to escape them if they have the double square bracket for now:

function pre_escape_beaver_builder_shortcodes($content) {
return preg_replace_callback('/[[(wpbb\s+[^]]+)]]/i', function($matches) {
return '[' . $matches[1] . ']';
}, $content);
}
add_filter('fl_builder_before_render_shortcodes', 'pre_escape_beaver_builder_shortcodes', 9);

Fwiw, I don’t think this is something you need to solve. I think this is a Beaver Builder issue.

Your solution works for “normal” shortcodes. So thank you!

I will also ask the BB team about it, because those shortcodes also don’t escape with the double square bracket way either. So it must be something they are doing

• This reply was modified 1 month, 3 weeks ago by Zack Pyle.
• This reply was modified 1 month, 3 weeks ago by Zack Pyle.

I just tested your updated version. I created a simple just shortcode returning text, and it correctly escapes. But it’s not escaping shortcodes from Beaver Builder

For example [wpbb post:title]

Thoughts?

@kbat82 I just tried the double square bracket and it still rendered the shortcode for me?

Just checking in on this. Thanks!

Gotcha. Ok, thanks!

@kbat82 Thanks! But it stripped out your meantime solution. Can you screenshot it instead?

And yeah, I think making it a checkbox of “Stop Shortcode Execution” for each block is probably smart. It also is backwards compatible.

@kbat82 Another small item when you get around to it -> it would be awesome if cmd + / would comment out the line you’re on and use the appropriate commenting style // vs /* */ etc based on the code language selected for that block ????