I am now trying to create a form for adding users on the front end. On this form, user-newsletter checkbox field defaults to unchecked. Is there a way to have the front-end form pickup the same default value as on the Dashboard?
Solution:
You can create some JS codes to setup the checkbox field as checked by default, for example, edit your Toolset user form, click "JS Editor", add below JS code:
Problem:
The issue here is that the user is getting the error The package could not be installed. PCLZIP _ERR_BAD_FORMAT (-10): Unable to find End of Central Dir Record Signature Solution:
Problem: I have a checkbox field set up to "save 0 to the database" when unchecked. I would like to edit that field to save nothing when unchecked, I would like to know what I need to change in the database to update my existing posts, and I would like to know how to update an existing View filter to show only items with the checkbox field unchecked.
Solution: Since there is no serialization involved with single checkboxes, you can simply delete all the "0" entries from postmeta for this meta_key. Then in the custom field editor screen, change the checkbox setting to save nothing when unchecked. It's not simple to create a View that filters by an unchecked checkbox. You can use the wpv_filter_query API to modify the meta_query criteria to use "NOT EXISTS" in the comparison field.
I have a CPT, dogs, which users can edit via a post form. I have added a notification email which should send an email when one of two fields, Deceased (Checkbox) or Date of Death (Date) is modified. I thought it was working, but it seems that it also is sending the email if another field, Pre-titles, is changed. Maybe be for other fields as well, though Pre-titles is the only one I know for sure.
Solution:
You can setup the custom checkbox field, using options:
There is a custom field, wpcf-full-name, which is not shown on the CRED forms but is calculated from 4 other fields. I do this calculation using "save_post" action hook.
The problem comes when I use the backend form to update the data. In this case it seems to grab the OLD values for the fields used in calculating wpcf-full-name rather than the NEW values.
Solution:
In case it is a compatibility problem, please deactivate other plugins, and switch to wordpress default theme 2017, and test again, you can also test it in a fresh wordpress installation.
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.
