Problem: I would like to use a conditional to test if a numeric custom field value is empty or greater than zero. If so, I would like to display the value. If not, I would like to display nothing.
Solution: You could use "AND" in the comparison to test both ne '' and ne '0', like so:
{!{wpv-conditional if="( ($(wpcf-listing-price) ne '' ) AND ($(wpcf-listing-price) ne '0' ))"}!}PRICE: [types field='listing-price' format='FIELD_VALUE'][/types]{!{/wpv-conditional}!}
Or testing if the value is greater than zero might be a simpler solution:
Problem:
The issue here is that the user wanted to know how to add a spinner to their search using Toolset Blocks.
Solution:
Currently it is not possible to add the spinners using the block editor for the view. In order to add this you will need to build your search in the classic editor for the view.
As we improve our Toolset blocks functionality we can definitely see return of features such as the spinner, however right now its not possible to add it.
Problem:
I want to add data to the title of the currently submitted post with Toolset Forms, the data should come from the parent (related) post of the currently submitted post.
How can I do that?
Solution:
There are 2 options, both need be hooked to a Forms API hook.
You can listen to the Form's inputs in $_POST and get the value from the select2 Field where you use to select the related post in Toolset Forms (if you have this field present).
Then, you can update the Post you are editing with that of that post by simply using the value returned by the $_POST of the Select2 Parent field, which is the ID of the parent post.
With that ID you can get any information about this post using the WordPress API and populate your post as well using the WordPress API.
The select2 for parent selectors in the $_POST will be available with something link `$_POST['@post-type_right-post-type_parent'];`
You can get it's precise value by dumping the $_POST in the Form, to use the precise slug of your relationship selector.
All these actions need to be hooked to cred_save_data(), to fire at the right moment when the Form saves it's data to the database.
The other approach is using the Toolset Relationships API hook toolset_get_related_post() to get the (one) related post to the currently edited one.
This should be done on a cred_submit_complete() Toolset Forms hook to ensure all data, inclusive relationships, are stored in the database already.
Then we can get the related Post ID, and again with that ID, we can get the post data using WordPress API.
From here on the process is the same as with the first approach.
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.
