The customer created a view with two query filters: (1) the page must be a subpage of the page on which the view resides, and (2) the custom field "Card Exclude" must not have the value "1." Despite having four subpages, with only one marked as excluded, the view displayed no pages. Additionally, the unchecked state of the checkbox field was not saving a value to the database.
Solution:
The issue stemmed from how checkbox field values were stored in the database. If the checkbox was never saved, it remained absent in the database. If checked and then unchecked, it stored a value of 0, while being checked saved a value of 1. The workaround applied involved manually saving the field as true (1) and then unchecking it to store false (0), allowing the query filter to function correctly. Additionally, two other solutions were suggested:
1- Using a conditional statement in the Loop Editor: [wpv-conditional if="( $(wpcf-exclude-card) ne '1' )"].
2- Custom code in the query to handle cases where the field might be NULL or 0.
I want to create a custom search for the "Service" posts based on the "Audience" taxonomy. The search is functional with radio buttons, but I would prefer to display clickable visual buttons for the options rather than standard radio buttons.
Solution:
Toolset doesn’t provide a PHP filter to alter the radio button HTML directly. However, you can achieve a visual button style using CSS and Javascript to replace standard radio buttons.
I am trying to set the maximum number of characters for a generic text field on a CRED user form I would like to know if there is a way to achieve this without using JavaScript, possibly by using a filter or extending the PHP class responsible for the generic text field.
Solution:
The best way to accomplish this is by adding JavaScript code to the JS Editor of your form to include the desired attribute.
document.addEventListener('DOMContentLoaded', function() {
var textField = document.querySelector('input[name="job_title"]');
if (textField) {
textField.setAttribute('maxlength', '50');
}
});
Replace "job_title" with the field name that you have.
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.
