Problem with NEW Tabs element

[Houston]

I have a plugin that I have been using for years now that will take an uploaded Excel spreadsheet and display it as a chart on the website. All I have to do is put in the shortcode to show a specific page in the Excel sheet. However, if I put the exact same code that I used in the Tabs Classic element into the new TABS element it ignores the shortcode and just shows it as raw text.

You can see the example here on this page.

Note that the TABS element on the top is the new TABS element and the one on the bottom is the Classic. It works just fine in the classic.

Here is the code that I am using in both:
`

Masters Color Prints

{tabulizer:data_source[TiI7f9XISeKzQopoYRJv7OLl]}

Advanced Color Prints

{tabulizer:data_source[RGBOTOm5rQPZxlakfHJTFXku]}

Beginners Color Prints

{tabulizer:data_source[Z9mpKxNvElE16xHvNflgytfb]}`

Many thanks,
Houston

[ruenel]

Hello Houston,

Thanks for writing in!

Please be informed that {tabulizer:data_source[TiI7f9XISeKzQopoYRJv7OLl]} is not a shortcode. A shortcode uses square brackets (https://codex.wordpress.org/Shortcode).

Curly braces is used for plugin integration to display dynamic data. Please have your code updated and use double curly braces and see how it goes.

<h4 style="text-align: left;">Masters Color Prints</h4>
{{tabulizer:data_source[TiI7f9XISeKzQopoYRJv7OLl]}}
<h4>Advanced Color Prints</h4>
{{tabulizer:data_source[RGBOTOm5rQPZxlakfHJTFXku]}}
<h4>Beginners Color Prints</h4>
{{tabulizer:data_source[Z9mpKxNvElE16xHvNflgytfb]}}

Hope this helps.

[Houston]

I am not sure if you looked at the website but if you did you would have noticed that the plugin works just fine using the “Classic Tabs” but not in the NEW Tabs element. So if I have the coding wrong it would not work in either case. I am calling it a shortcode but I suppose it could be called something else, honestly I am not sure what to call it. All I know is that the identical code works in the CLASSIC TABS element but not in the new one. How would you explain that if all I need to do is add a set of curly brackets? Is the NEW Tabs element more strict with code or something. I am not really understanding why it works in one but not the other? Seems to me these symptoms point to some incorrect interpretation going in within the NEW Tabs element.

Just for the heck of it I tried your solution and as I suspected, it still does not work as you can see in my screen shot.

Many thanks,
Houston

[paul.r]

Hi Houston,

May I know what plugin you are using so we can test this in our test sites.

For the mean time please try to contact the plugin developer, they will be able to detect what is causing the issue better than us as they know how the that code is being rendered on the front end.

Thanks

[Houston]

The plugin is called “Tabulizer”

[rad]

Hi @Houston,

It’s a conflict with V2 elements and the way your plugin calls its shortcode. Right now, what its doing is finding the existence of strings that matches its preferred shortcode, like {{tabulizer ...... }}. Once it’s found, it will then parsed and execute the corresponding function. In other words, it implemented its own standard for shortcodes instead of using Wordpress standard (https://codex.wordpress.org/Shortcode_API).

You can check it this as well https://wordpress.stackexchange.com/questions/30364/shortcodes-between-square-and-curly-brackets.

Now, the issue is with v2 elements content, they aren’t accessible from the outside, hence, your plugin is unable to identify or search its own implemented shortcode. Something like

str_replace('{{tabulizer ...... }}', tabulizer_shortcode_execute(), $v2_content);

And with Wordpress standard shortcode, it doesn’t need to search and identify it, it’s part of the system that once the shortcode is present, it will be executed. It doesn’t need an external or remote function to call those shortcodes.

But yes, it’s an incompatibility between V2 elements and the way your plugin is calling their custom shortcodes. There is a similar issue in ACF Pro (curly bracket shortcodes) but there is an integration in place to make them work. Hence, for your plugin to work, it would need a similar integration which, unfortunately, there is no temporary workaround and we can provide a solution for a 3rd party plugin. All we could do is add this as a feature request.

Thanks!