Skip Navigation

[Resolved] Using Visual Composer Shortcodes in Custom Post Fields Not Working after update

This support ticket is created 5 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 4 replies, has 2 voices.

Last updated by Luo Yang 5 years, 6 months ago.

Assisted by: Luo Yang.

Author
Posts
#1258615
Screen Shot 2019-06-04 at 11.10.40 AM.png
Screen Shot 2019-06-04 at 11.10.50 AM.png

We use Visual Composer Shortcodes in our Custom Post Fields (see screenshot). These have worked flawlessly for 2+ years however upon recently updating our Types and other Toolset plugins the shortcodes appear to not be outputting.

Link for live example is here - hidden link

Screenshot of issue also attached.

#1258715
Screen Shot 2019-06-04 at 12.07.28 PM.png

Also attached is the actually Code being called in the Content Template if helpful.

#1259067

Hello,

It is not recommended to use other shortcode in "Custom field content" input box, as a workaround, you can setup simple static value insider "Custom field content" input box, for example:
- option "Abbott", "Custom field content" value: abbott
- option "Ackerly, Henry S.", "Custom field content" value: ackerly
...

Then display the your custom shortcodes using [wpv-conditional], like this:

[wpv-conditional if="( $(ephemera-category) eq 'abbott' )"]
Display your custom abbott shortcodes here...
[/wpv-conditional]
[wpv-conditional if="( $(ephemera-category) eq 'ackerly' )"]
Display your custom ackerly shortcodes here...
[/wpv-conditional]
...

More help:
https://toolset.com/documentation/user-guides/conditional-html-output-in-views/

#1260403
Screen Shot 2019-06-05 at 2.16.38 PM.png
Screen Shot 2019-06-05 at 2.16.46 PM.png
Screen Shot 2019-06-05 at 2.17.03 PM.png
Screen Shot 2019-06-05 at 2.17.10 PM.png

We changed the custom field content to be just normal content i.e. erard.

We then created in the Content Template a Conditional Output for the visual composer shortcode as described above using:

[wpv-conditional if="( $(ephemera-category) eq 'erard' )"]
SHORTCODE FROM VISUAL COMPOSER WAS PASTED HERE (SEE SCREENSHOT)
[/wpv-conditional]

And it is still outputting the Visual Composer Shortcodes as text and not as a functioning shortcode (which is the same problem we are having as when trying to use custom field content as the shortcode). We didn't have any issues with this prior to updating.

Link to page - hidden link

#1260659

The problem you mentioned above is abnormal, please check these:
1) In case it is a compatibility problem, please deactivate all other plugins, and switch to wordpress default theme 2019, deactivate all custom PHP/JS code snippets, and test again

2) Also check if there is any PHP/JS error in your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

3) If the problem still persists, please provide database copy file(ZIP file) of your website, also point out the problem page URL and Content Template URL, I need to test and debug it in my localhost, thanks
https://toolset.com/faq/provide-supporters-copy-site/