Views is a WordPress plugin that lets you easily display content on your website's front-end in any way you choose.
Views User Guides include detailed documentation for creating lists of content, templates for content and archive page and also explain how to create parametric searches for any content type.
When you ask for help or report issues, make sure to tell us the versions of the Toolset plugins that you have installed and activated.
Viewing 15 topics - 1,786 through 1,800 (of 2,809 total)
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: After migrating an existing site to a new server, I have noticed that some markers that were displayed on my maps on the old site do not appear on my maps on the new site. In the server logs, I can see repeated messages about missing functions ST_X and ST_PointFromText:
...FUNCTION **.ST_X does not exist
...FUNCTION **.ST_PointFromText does not exist
Solution: Toolset's mapping features make use of functions provided in MySQL 5.6+. If your site runs a version of MySQL lower than 5.6, several maps features may not work as expected and you may find errors in the PHP logs. Check the server's current MySQL version and update if necessary. Ask your hosting provider for assistance with that upgrade, if needed.
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%"
