In fact, is a shortcode rendered from a post_content. This means that if I put some dynamic data inside a post content will be rendered right?
A fix I could implement is to avoid parsing the post_content, right?
It’s working properly if I modify your file
includes/integrations/dynamic-data/providers
adding this in render function:
...
preg_match_all( '/{([\w\-\s\.\/:|,]+)}/', $content, $matches );
//my "filter"
if(strpos($content, "gooogleMapOption") > -1){
// var_dump( $matches);
// var_dump($content);
return $content;
}
So this means this render function happens once the post_content is got. I don’t understand properly why you should parse tags for the post_content if in theory you only add dynamic data from the builder, not from the post content itself.
This also makes parse a lot of tags from a lot of shortcodes that use js…
And more… If some js code has “existent_tags”, because in their code uses something like
<script>
let myPlugin = {
post_content: "don't touch this"
}
</script>
the filter
add_filter( 'bricks/dynamic_data/replace_nonexistent_tags', '__return_false', 10, 1 );
will still break the code…
Please some solution for this!
Thanks