Problem:
The user is using several combinations of conditions on custom fields, and wonders if there is any performance impact between nesting or combining conditions.
Solution:
You can nest the conditions to avoid long statements and to have much readable code. But from a performance perspective, I don't think there will be an impact between combining or nesting the conditions. Primarily, because the values will be cached in memory after they are first pulled from the database. And they won't be pulled again.
Nesting the conditions may gain a couple of instructions executions, but I don't think it will be considerable.
I recently updated my wordpress version to 5.5 and since that update I've found an issue with the elementor toolset view widget.
Solution:
Since Toolset Blocks plugin is based on WordPress Blocks editor(Gutenberg), view block won't work as expected in other page editor(Elementor), it is not recommended to use both page editors(Blocks editor and Elementor) to design the same page/post.
Hello, I'm trying out the Toolset blocks in Gutenberg, but am having trouble translating what works in straight HTML vs what I need to place inside the Toolset Conditional block.
Solution:
Please try these:
( ( '[types usermeta="userfield1" output="raw" current_user="true"][/types]' = '1' ) AND ( '[wpv-search-term param="_success"]' != '' ) )
And test again.
Tip: Within shortcode [types ...][/types], you need to use double quotes instead of single quote
