This thread is resolved. Here is a description of the problem and solution.
Problem:
Use [wpv-conditional] shortcodes as HTML tag attributes within Fields-and-Text block, it does not work.
Solution:
According to our developers feedback, it seems to be an issue of WordPress core:
This is probably due to some sanitization done by WP over its content on post save.
So in your case, please try to use shortcode block.
Relevant Documentation:
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)
Hello,
Where did you put those codes?
I have tried the same codes in my localhost with a fresh WP installation + the latest version of Toolset plugins, it works fine.
for example, add a shortcode block, using below codes:
<div style="max-width: 1290px; min-height: [wpv-conditional if='( "[wpv-post-id item='$parent']" ne "" )']30vh[/wpv-conditional][wpv-conditional if='( "[wpv-post-id item='$parent']" eq "" )']50vh[/wpv-conditional]; ">12345</div>
It outputs different min-height value in different pages, see my screenshot: sub-page.JPG
Just realised that he also "crashes" the html-block if I reedit the template. If I reopen it twice (without saving the first time) he shows me that there is a backup with changes at the second time, without having changed anything myself. There you can see that he edits the html block in the backedup version (red outline) like he probably did with the Fields-and-Text block by saving at the first time.
Maybe that helps
