I am building a directory site using Toolset and the Kadence theme, with a custom post type called 'People' and a Toolset content template to display custom fields. However, the Kadence theme layout overrides my Toolset template, preventing my custom fields and layout from appearing.
Solution:
After troubleshooting, it was found that the "Event Tickets" plugin was causing the issue. Disabling this plugin allowed the Toolset content template to render correctly. Upon re-enabling the Event Tickets plugin, the Toolset template continued to display correctly for the 'People' custom post type. It’s unclear why disabling and re-enabling the plugin resolved the conflict, but this approach has been successful in other cases.
I am interested in creating a form to enter product details into a database. The form should capture details such as model, engine, and wheels, with each entry needing a unique ID for later searches.
Solution:
To set up a form in Toolset that allows product entry, first create custom fields specific to the product details (e.g., engine, model, wheels) and assign them to a custom post type, such as "Product." Then, use Toolset to create a form that includes these fields, enabling users to add products directly to the database. Each entry will have a unique ID, making it searchable later. For more detailed guidance, review Chapter #7 of Toolset's Custom WooCommerce Sites course.
I am trying to update my Toolset plugins, but I am receiving an error indicating that my site key is invalid.
Solution:
- Ensure you are logged in at toolset.com.
- Visit: https://toolset.com/account/sites/
- Click the trash icon next to your website name to remove the site key.
- Re-register the site:
- Go to "WordPress Dashboard > Plugins > - Add New > Commercial (Tab)".
- Click "Register Toolset" on the right.
- Click "Get a key for this site" to generate a new key.
- Copy the key and paste it into the "Site Key" input box.
- Click "OK" to complete the registration.
As an author, I am unable to use the datepicker in a front-end form for the "autoresponder" post type. Although I can open the datepicker, selecting a date does not insert it into the field, and a console error appears. However, this works fine when logged in as an admin.
Solution:
After testing on a minimal installation, I identified a function in a custom plugin that was causing the issue by redirecting authors to the front end when they accessed the backend. Disabling this function resolved the problem, allowing the datepicker to work as expected for authors.
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.
