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 - 3,706 through 3,720 (of 3,838 total)
Problem: I have used Access to hide posts from Guest users, but I would can still see post information in search results. I would like to hide this information from Guest users.
Solution: A WordPress Archive is used to display search results. That archive is built in the legacy shortcode version, so you can use Access Control shortcodes in the archive's contents to suppress any visible information. The syntax is as follows:
[toolset_access role="Guest" operator="deny"]
Guests will never see anything inside this shortcode.
[/toolset_access]
If the archive is built using the Blocks Editor, you may use conditional blocks to achieve the same effect.
Problem:
The user has configured a content template, but some of the fields do not render in the frontend.
Solution:
It turns out that the user was using a conditional with a big content inside. Currently, we have a limitation on the content of a conditional block and we need to keep it under a certain limit.
Problem:
Making Custom Author Fields Show Up on Author Profile Pages etc
Solution:
To get the currently displayed author ID of author profile page, you will require to write a custom shortcode that returns the current author profile ID.
Problem:
The user has a form that creates a post and asks if he can implement a recurring post feature. For example, create a post for a user that has date times set for every Monday until next month
Solution:
First of all, note that a Toolset form is meant to create or edit only ONE post. To be able to create multiple posts, you will need to create custom code hooked to the cred_save_data action, that will create the additional posts. https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data
To pass data from the form to your action function, you can use generic fields.
Now, it is a matter of how you intend to do it. You may want to calculate the additional posts' arrival and departure dates/times on the frontend with Javascript, and pass them to the action function.
Or you may want to pass the rule(every week until a certain date) and calculate the date on the server end inside your action function.
Problem:
The user configured the products archive template to be ordered by the price but that did not work for him.
Solution:
It turns out that the price was ordered as a string instead of a number, I updated the wpv-sort-orderby to include the following argument orderby_as_numeric_for="field-views_woo_price" and it is giving correct results.
[wpv-sort-orderby type="select" options="post_date,post_title,field-views_woo_price" label_for_post_date="Newest" label_for_post_title="A to Z" label_for_field-views_woo_price="Price" orderby_as_numeric_for="field-views_woo_price" orderby_ascending_for="post_date,post_title,field-views_woo_price"]
Note, that a product does not have a price, it is considered to have a price equals to 0.
If I add a separator, for example " | " in the Repeating field block>Display settings>Separated by>Separator, it does add a separator but not between the custom fields (So, in my case, between the custom images for the documents) but at the end... How can I add a separator or space between them?
