Problem: I have a custom role that should be able to submit a Form to add or edit a child post, but the parent post options are not shown in the select field in the Form. This was working before a recent update.
Solution: Check your custom code to confirm that redirects set up to block access to the back-end of the site are not applied to admin-ajax.php requests. Add some conditional logic to prevent those redirects as needed, like in the following code example:
/**
* Block wp-admin access for non-admins (not while doing AJAX, see https://toolset.com/forums/topic/custom-role-no-longer-able-to-perform-same-tasks/)
*/
function ace_block_wp_admin() {
if (!current_user_can('edit_users') && ( !defined('DOING_AJAX') || !DOING_AJAX ) ) {
wp_safe_redirect( '/my-account');
exit;
}
}
add_action( 'admin_init', 'ace_block_wp_admin' );
I want to hide some of many posts displayed in a Toolset View.
How can I do this easily, so I do only need to update those Posts I do not want to display (because these are the less in number), instead of updating ALL posts with a Show/No Show value?
Solution:
The easiest is to use a Taxonomy.
Tag the Posts you want to hide with a "no show" tag and leave the Posts you want to show or simply make sure they do not have that tag (which will be the default).
Then create a View and query the posts by Terms "no one of these {your no show term}"
Problem:
I cannot select a field in the "Product to buy when submitting the form" in a Toolset Form, so the users could choose the product to purchase.
Solution:
You should create several products and either a select or radio Toolst Types custom field (not a Generic Forms Field) with values corresponding to the Product IDs you want to offer as choice.
Problem:
Client is developing a site which will have thousands of posts with address fields that will be used in distance searches. Is Toolset able to handle a site of that size?
Solution:
Yes, since the address storage and distance querying were completely refactored in Maps 1.8 it can handle very large sites (subject to the usual server limitations).
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.
