Problem: I would like to make the post parent field and featured image field required in my CRED form.
Solution: The parent post CRED field shortcode will accept a required='true' attribute like this:
[cred_field field='_wpcf_belongs_slug_id' value='' select_text='--- not set ---' class='form-control' output='bootstrap' required='true']
The featured image shortcode will not accept a required='true' attribute, so the only way to require a featured image is to use custom code. The CRED API cred_form_validate can be used to make the featured image required. Add this code to your child theme's functions.php file:
Problem: I would like to use CRED to allow my site Users to upload multiple images, and associate those images with CPTs. Some of those CPTs are child posts, some are parents, some are grandparents. What is the best way to associate the images with all levels of the CPT hierarchy?
Solution: It depends on your site's requirements. There are several things to consider.
- It is easier to create custom search filters using custom fields attached to the same post type shown in the View.
- However, it is not possible to use repeating fields in child posts in the current stable version of Types. The new beta M2M features will address some of this issue.
- Taxonomies can be used to relate the images to multiple CPTs, but they must be managed by your Users.
- Galleries and Carousels in Divi Builder have limited options for filtering the results, and it is not possible to use shortcodes as filters. So Divi cannot access custom fields effectively in the Gallery or Carousel module.
- Elementor ACF Gallery modules may or may not work with Types custom fields. Types custom fields are stored in the postmeta table using the previx "wpcf-".
Problem:
What are the options for displaying different content to different users on the front-end?
Solution:
To display different content on the front-end according to some criteria you essentially have two options.
If the thing being tested relates to the person doing the looking (the user browsing the website is registered and has a certain role because they have paid for a particular membership, for example) then you can use Access to restrict the visibility of whole pages, or to selectively show certain content on a page (as described here: https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/).
If the thing being tested relates to the thing being looked at then you would need to add custom fields to the content being viewed and then use the wpv-conditional shortcodes to test the content of those custom fields and selectively display what is wrapped in the shortcode, as described here: https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
Problem:
Is it recommended to use taxonomies (with checkboxes) or checkboxes custom fields?
Solution:
If you intend to filter a View using these checkboxes you should probably use taxonomies rather than a checkboxes custom field, because within WordPress taxonomy filters are more performant that meta query filters (https://tomjn.com/2017/02/27/not-post-meta-bad/).
See the answer below for a more detailed discussion.
Problem:
Can we create breadcrumbs, or chained navigations with a "backtrace" with Toolset?
Solution:
Toolset does natively not provide any form of navigation, menu or BreadCrumb.
However, you can, for example, use YOAST with Toolset:
They provide a BreadCrumb ShortCode
Problem:
Why repeating fields should not be used in child posts? Could you please explain.
Solution:
You can no use repeating fields in child posts as it will update all all fields resulting in malformed output. This is not supported by design.
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.
