Problem: I have a custom search WP Archive for a taxonomy that uses custom search. I have set the search feature to display only those options that would produce results. If I select one option, the options update as expected, but when the page loads all options are displayed. I have included other Views on the page.
Solution: In this case, it seems that omitting the filters from other Views included on the page is responsible for producing the problem in the archive filters. The filters were omitted by removing the wpv-filter-meta-html shortcode in the Output Editor. Replace the filter shortcode in the Output Editor of the other Views to solve the problem:
Problem:
We could not connect to the Google Maps error - Accessing the address field shows error "We could not connect to the Google Maps autocomplete service, but you can add an address manually"
Solution:
User do not activated the Places API with his map key. Please make sure that Places API is activated with that map API key(s) you registered.
Problem:
The user is using a checkboxes custom field for users.
He then created a view of users and applied a query filter on this field, but their results were wrong.
Solution:
First of all, the checkboxes field should not save 0 when an option is not selected.
Checkboxes fields are saved as a serialized array where each selected option has a unique ID and a value. Check this screenshot https://prnt.sc/131l2xn
It turns out that the user was importing the values of the checkbox from a user-made XML file instead of a Toolset Export. This file was using unique IDs, built from the same base and an incremental suffix.
This makes the view fails, because it use SQL LIKE "%option-ID%"
Problem:
The user is user a form to register new users, he would like to automatically login the user after registration.
Solution:
This will need custom code to be implemented. It will need to log in the user WITHOUT a password. Check this thread it explains how to use wp_clear_auth_cookie, wp_set_current_user , and wp_set_auth_cookie to login the user without password.
Problem:
The user has a form with an image field and he would like to trigger the camera on mobile devices when trying to upload an image.
Solution:
Accessing the camera is not managed by the browser, it has to be implemented by the mobile platform(Android). On Chrome mobile on Android, when trying to upload an image the phone suggests several applications, the camera included.
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.
