Skip Navigation

[Resolved] Special characters within my conditional causes the output to disappear

This support ticket is created 4 years, 7 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
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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/Kolkata (GMT+05:30)

This topic contains 2 replies, has 2 voices.

Last updated by MichaelR9215 4 years, 7 months ago.

Assisted by: Minesh.

Author
Posts
#1640359

Hello,

AI started with the following:

[wpv-conditional if="( '[wpv-taxonomy-archive info='description']' ne '' )"]

Which works if there are not special characters, but a description that contains an apostrophe breaks my conditional.

I found a lot of variations, and I have tried more of them. The following is an example of one:

[wpv-conditional if="('[types termmeta='mar-product-cat-desc' output='raw'][/types]' ne '')"]

I created a custom term field to replace the default product category description.

I also tried:

[wpv-conditional if="( $(wpcf-mar-product-cat-desc) ne '')"]

I am currently informing my client to not use special characters in their descriptions, but I'd like to get this working.

Please advise.

Thanks!

#1641157

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This is known issue to us and there is no workaround available for now.

Please check the following errata page for more details.
=> https://toolset.com/errata/conditionals-including-special-characters-might-fail/

However, I just checked the internal ticket and I can see our Devs is suppose to offer a way to fix this and the fix is proposed but not added to current release yet. I will get back to you once I see the fix is added to in near future release.

#1641911

Thank you Minesh. I will look forward to the release of this fix.