[Resolved] conditional block don’t shows even if debug information is activated
This thread is resolved. Here is a description of the problem and solution.
Problem:
The user has created a conditional block on datetime field using "<=".
Solution:
This is a bug that we escalated to our developers and will be fixed in the future.
As a workaround, we can use the "lte" operator. Or we can use ">" with negation, which is equivalent to "<="
0% of people find this useful.
This support ticket is created 3 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.
if is set the relation to">=" the debug information shows up but the values don't hidden link
I use the same condition with "<=" at the single page and there it works fine. hidden link
see debug information at the right side under "kontakt" button
Hello and thank you for contacting the Toolset support.
If the condition debug info does not appear, it means that there is an error with the condition. If you are using the legacy editor, please check if using "lte" instead of "<=" and wrapping 'TODAY()' in single quotes will help:
Otherwise, please allow me temporary access to your test site to check this closely. Your next reply will be private to let you share credentials safely.
Thank you for the credentials and the provided tests.
I edited the condition on "<=" and used "lte" in the advanced editor, then saved. It worked in the frontend, but it crashed the view on the backed. Check this screenshot
I run another test on our platform and changing "<=" to "lte" did not crash the view for me, maybe that's a different issue on your website that we can check later.
And I have also added a view, that uses another workaround, using ">" and evaluating to false, which is equivalent to "<=" and that worked without issues, you can check it at the bottom of this page hidden link
Please let me know if ">" evaluating to false is a viable workaround for you?
I have escalated the issue with "<=" to our 2nd Tier and I'll keep you posted as soon as I have any news.
Just want to let you know that the last update, published yesterday, has had some improvements on the user interface and now generates conditions based on letter operators(gt, gte, lt, lte) instead of symbols(<,>,<=, >=) as they are treated as HTML entities by WordPress.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.