With the Views plugin you can create different Views elements to display all your custom types and content on the front-end, without coding. You can also create powerful parametric searches and add pagination to your content lists.
When you ask for help or report issues, make sure to tell us the options of your View.
Viewing 15 topics - 6,091 through 6,105 (of 8,123 total)
Problem:
Is it possible to force alphabetic sort, regardless of whether an item is a parent or a child (via some function)? Like: B always comes after A and before C, no matter which one is a parent.
Solution:
Right now Views use the same logic as WP has for parent/child terms, I have submitted a request to our development team to improve it if possible. This might be possible using JS but I am not certain how.
This type of JS code or modifications falls into Custom coding & custom development and it is out of support policy (https://toolset.com/toolset-support-policy/). So we recommend to contact Toolset recommended service providers to further discuss the custom approach. We have some recommended list of service providers here if you would like to take a look: https://toolset.com/consultant/
Problem:
When using the Jetpack option to "Speed up images and photos" outputting the images in a template with Views shortcodes resulted in garbage text.
Solution:
The crop attribute of the Views wpv-post-featured-image shortcode cannot be used in conjunction with the Jetpack image optimisation service.
Problem:
I created a post type called "Stores" that displays store info and a Google map for each store. I created a second post type called "Upcoming Events" that shows event information and date of each event. I would like to display Upcoming Events for each store based on the value of a field (Store Number) from the Store post type. The store number is part of the information entered for each store, it is not the post ID. I would like to be able to create an Upcoming Event and enter a comma separated list of Store Numbers in order to display the event on one or more store pages.
Solution:
In your case, one "Upcoming Event" post can connect to multiple "Stores" posts, and one "Stores" post can connect to multiple "Upcoming Event" posts, that is many-to-many relationship,
I suggest you follow our document to setup many-to-many relationship between post type "Upcoming Event" and "Stores", within many-to-many relationship, it is not required to re-entering the same Upcoming Event info for each store location.