Problem:
When my users try to reach a certain Posts Edit form the are presented a message "permission denied".
I am sure the Access settings are not at fault as the issue persists with Just Toolset Forms and no other plugin.
Solution:
Make sure the ShortCode of Toolset Forms is not malformed, since for example not closing (missing the last bracket for example) ShortCodes will throw the same error "permission denied"
Problem: I would like to use the Forms API to validate each image that is uploaded in a single or repeating custom field. It doesn't seem to be working, in the logs I see a PHP notice about trying to get property of a non-object.
Solution: Make sure the User has permission to publish Media if you are using Toolset Access Control. Make sure the Form's markup structure doesn't include any extra closing div tags. Use the following custom code to validate a repeating image field:
add_filter('cred_form_ajax_upload_validate','rep_img_size_validation',10,2);
function rep_img_size_validation($error_fields, $form_data)
{
error_log(' validation script is invoked ');
$forms = array( 29, 49 );
$size = 1024000;
$field_slug = 'your-repeating-image-slug';
$error_msg = 'Maximum size is 1MB, please try again.';
//field data are field values and errors
list($fields,$errors)=$error_fields;
//validate if specific form
if (in_array( $form_data['id'], $forms ) && isset($fields['wpcf-' . $field_slug]['field_data']['size']))
{
//check if this field instance img is bigger than $size (bytes)
$instance_size = array_pop($fields['wpcf-' . $field_slug]['field_data']['size']);
if ( $instance_size > $size )
{
//display error message for this field instance
$errors['wpcf-' . $field_slug] = $error_msg;
}
}
//return result
return array($fields,$errors);
}
To validate a single field, copy the code above and make the following adjustments:
- Change the function names to prevent a PHP error
- Change the field slug
- Remove array_pop from the instance_size definition like this:
// for repeating images
// $instance_size = array_pop($fields['wpcf-' . $field_slug]['field_data']['size']);
// for single images
$instance_size = $fields['wpcf-' . $field_slug]['field_data']['size'];
Problem: I have conditional HTML in place in a custom search View's filter area, but it doesn't seem to be working as expected.
Solution: Conditional HTML is designed to respond to the properties of posts, not selected search filters. Using conditional HTML to respond to selected filters is not going to work consistently, even if you find certain edge cases where it appears to be working briefly. If you'd like to see more filter dependency features built into the system, I encourage you to submit your request here: https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
I created two views. One only shows the results, and the other is for search and show results. When I add both of them to the same page, the custom search doesn't work and the site breaks. The button doesn't work either.
Solution:
It is a compatibility problem with custom theme:
You can locate the problem by this:
deactivate other plugins, and switch to wordpress default theme 2019, deactivate all Custom code snippets, and test again
Problem:
How can we apply conditionals in a Toolset Form so to hide single form fields depending on other fields values (in the form)?
Solution:
You can wrap any field in Forms into so called "Conditional Groups".
They will allow you to listen to particular other fields present in the form, inclusive generic fields
To edit such conditions or their content more advanced you need to turn on "Expert Mode" for the editor.
En Toolset erratas, documentamos problemas conocidos y sus soluciones. Ahorre tiempo consultando allí primero y viendo si el suyo es un problema conocido. Mantenemos la lista corta. Hacemos lo mejor que podemos para resolver todos los problemas conocidos con cada lanzamiento de los plugines de Toolset.
Política de soporte
Nuestro personal le ayudará a usar los plugines de Toolset correctamente, le proporcionará la información que necesite, le ayudará a resolver problemas y lo asesorará con respecto a las mejores prácticas.
Sírvase asegurarse de incluir solamente un tema en cada solicitud de soporte.
