Problem: I would like to allow my site visitors to download a PDF file that includes some custom user fields.
Solution: Use a View or a Content Template to output the desired custom User field values, and use print stylesheets to style the output. Users can print to PDF using the native browser print features.
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.
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
Use option "After visitors submit this form: Keep displaying this form" in post form, Why is _1 added to my form inside the parameter? Is this always the case, or would it ever be different? How can I best refer to a specific form ID inside the URL parameter?
Solution:
The _1 is form instance number, for example if you are displaying same post form(ID 3351) in same page multiple times, you will get multiple instances post form(ID 3351), you will get different URL parameters: 3351_1, 3351_2 ...
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
