I am trying to: have number of child posts in my search page. Search page shows number of parent posts. I am using this shortcode to display a view [wpv-view name="number-of-reviews"] with filter:
filter:
Select posts that are children of the Post where this View is shown
This works in single parent post but does not show number of reviews in search page.
Solution:
You can change the filter to:
Select posts that are a children of the current post in the loop.
Display child posts submitted through cred form. One label in one line. But only name label and output shows correctly. Other labels and outputs are shown in new lines. Details and output should be one line. review and output should be in another line.
I expected to see: Each line having a label and output.
Solution:
Types shortcode for custom textarea field will output the field value wrapped in a HTML
..
tag, you can disable it by adding attribute output="raw" in the Types shortcode, for example:
[types field='details-of-court-case-or-consultation' output='raw'][/types]
Problem: I would like to use CRED to create comment posts, and I would like those comments to be children of the current Lawyer CPT.
Solution: Create a new CRED form that creates CRED Comment posts. Auto-generate the form markup, and wrap the parent select field in a hidden div. Define the value of the parent select field using the ID of the current post:
<div style="display:none">
[cred_field field='_wpcf_belongs_lawyer_id' value='[wpv-post-id id="$current_page"]' select_text='--- not set ---' class='form-control' output='bootstrap']
</div>
The issue that here is that the user was using the Enfold theme but created a custom layout for his CPT. He added a custom Sidebar using Layouts but when previewing on the frontend the default theme's sidebar is overlaid her as well.
Solution:
The solution to this would be to disable the sidebar by going to your enfold theme options.
The issue here is that the user had created some rows and columns using our Layouts plugin but on the frontend the Rows and columns are not showing up.
Solution:
Our Layouts plugin uses the bootstrap class elements in order to do the columns and rows. If bootstrap is not loaded on the side then these items won't display correctly.
Our Toolset plugins include bootstrap but you will need to enable it by going to Toolset -> Settings -> Bootstrap Loading.
How can I validate a field in a Toolset Form, so that when for example the user would have to submit an image but doesn't, it automatically adds a "dummy" image to that field?
How can I do that?
Solution
You could simply add a default value to the Custom Field, so if it’s not edited, that value is used.
But that may look not so smooth, hence a „in the background“ action is required.
Since this is not really a validation where we throw an error but just ensuring that the field is somehow populated, we can apply a CRED cred_save_data() action.
Otherwise - if we want to throw an error, we use the cred_form_validate() hook.
This hook allows you to fire any PHP at the moment when the post is saved to the database.
This means you can check the Field in the $_POST and if empty, you can then update_post_meta() that field with anything you want.
The hooks allow you to perform your custom code a the right moment, that is all that our API does, along with providing several data sets in those hooks so you can use it in the code.
Let me give a simple example.
add_action('cred_save_data', 'my_save_data_action',10,2);
function my_save_data_action($post_id, $form_data)
{
// if a specific form
if ($form_data['id']==12)
{
if (!isset($_POST['my_custom_field']))//Change "my_custom_field" to your wpcf-field
{
// since $_POST['my_custom_field'] is not set (!isset())
update_post_meta($post_id, 'my_custom_field', 'whatever-value-you-like-or-url-to-image');
}
}
}
Above PHP code checks if the $_POST input (my image field) is set, and if not, it adds a value.
The entire code is based on PHP and WordPress API - but hooks into our Toolset Forms API to ensure it fires at the right moment.
I want to show default values for my fields, in case the field is not edited when saving the post (is empty).
I am editing and creating posts with CRED.
Solution
There are 2 possible ways to achieve this, one while adding the value of the Field, the other when displaying the field on the front end.
1. While adding the field value (edit the field on the front end thru a CRED form)
- create the custom fields and include them in the CRED Form
- pass a default value to them by using the "value" attribute
==> Since you had set a default value, the field will always show that default value if not changed
==> You can achieve the same by setting the default value in Toolset > Post Fields directly
Or, you can skip the above steps and update the Custom Field (if empty) with a custom hook to
update_post_meta()
with your default value, using the
cred_save_data()
filter
2. When outputting the field value on a post
- create the custom fields and include them in the CRED Form
- submit the cred form with eventually empty optional fields
- display the fields as used to, but wrap them in an HTML conditional
In the conditional, check if the field is empty to display your custom default text, or if it's not empty you can display the value of the field.
How can we control what HTML tags are allowed to be submitted with CRED Forms?
Solution
All HTML tags that you check in Toolset > Settings > Forms > Content Filter, will be allowed, all that are unchecked will be stripped, when the form is submitted.
There will be no error message to the user.
The content will simply be stripped by the unwanted tags.
I have a Repeating Custom Field and want to output it as a list (each of its items should be a list item) or I want to add an Icon on the front of each.
How can I do that?
Solution
To create a list or other HTML structures with Repeating Fields we suggest using the Separator and the Loop intelligently to combine HTML and opening/closing tags in the Field's separator.
The logic is this:
- get the final HTML you want
- make sure you open the HTML before the actual field renders
- as separator use firstly the closing tags, then, reopen the tags for the next item
- make sure the Loop closes with a Closing set of tags.
Note that you need to add NOT encoded characters (hence, natural HTML) to the GUI’s separator input field, it will then automatically convert to encoded characters when you insert the ShortCode!
The same logical approach can be taken with other HTML or even FontAwesome Items.
Note that this is limited, do not expect to have too much control over the resulting HTML.
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.
