Dieser Thread wurde gelöst. Hier ist eine Beschreibung des Problems und der Lösung.
Problem: The curly bracket conditional syntax is not working when it's inserted in the post content editor.
Solution: Replace the curly brackets with square brackets in a post editor. The curly brackets should be used in a WPBakery module.
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 |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
Dieses Thema enthält 5 Antworten, hat 2 Stimmen.
Zuletzt aktualisiert von vor 6 Jahren, 5 Monaten.
Assistiert von: Christian Cox.
I am trying to:
Add conditionality to a text block in the Visual Composer.
See screenshot for the test.
I expected to see:
Either 'empty' or 'not empty' in the frontend.
Instead, I got:
Nothing is seen in the frontend.
Is the screenshot you provided a post content editor, or a WPBakery text module? I'm not sure, but it looks like maybe it's a post content editor. If it is a post content editor, then you should replace the curly bracket syntax {!{ ... }!} with the standard square bracket syntax:
[wpv-conditional if="( $(wpcf-testfield) eq '' )"]Empty[/wpv-conditional] [wpv-conditional if="( $(wpcf-testfield) ne '' )"]Not empty[/wpv-conditional]
The curly bracket syntax is for use in a WPBakery module. When you use the GUI in the post content editor, it should build the correct shortcode for you. I just tested this out in my local clone and it seems to be working as expected. Maybe these curly bracket conditionals were copy + pasted from a WPBakery module?
Hi Christian,
I indeed changed the syntax to the curly brackets in a attempt to solve the problem before escalating to you.
However, the square brackets result in the same problem (see attachment).
Can you try it on my instance? You can use same creds on: versteckter Link
The post where i tested is: versteckter Link
Thanks!
Marc
