Views is a WordPress plugin that lets you easily customize the standard WordPress listing pages using WordPress archives. You can redesign any WordPress archive, including custom post archives, taxonomy archives, author archives and search results.
When you ask for help or report issues, make sure to tell us what you have created so far and what you want to achieve.
Viewing 15 topics - 331 through 345 (of 390 total)
Problem:
The user would like to add some text to some taxonomy archives for SEO reasons. The text should be conditionally displayed depending on the current archive term.
Solution:
If the texts that you intend to add for SEO reasons, will be added for each term? I mean, if there will be a different text for each borough?
If that's the case, why not use taxonomy term fields, check this article https://toolset.com/documentation/user-guides/views/term-fields/
If you only want to have a condition on one or a few terms, you can use conditional blocks and choose the "Views shortcode", then the archive title, and make it equal to a static value in this format "{taxonomy name} : {term name}". Check this example from my install, where the taxonomy name is "Catégorie" (in French) and the term name is "Auto" http://prntscr.com/un1wkn
Problem:
One Custom Post disappears after clicking radio filter
Solution:
User was using the outdated Toolset plugins.
We always recommend running your site with the latest stable release plugin version.
*** Please make a FULL BACKUP of your database and website.***
Please make sure you update ALL Toolset plugins to it's latest officially released version. You can download the latest plugin release from your accounts page:
=> https://toolset.com/account/downloads/
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 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.
Problem:
The user would like to order the WooCommercearchive template in several fields, including the price.
Solution:
Make sure that the default WooCommerce order is disabled in Toolset->WooCommerce Views->Frontend Sorting. Check this screenshot http://prntscr.com/uizqgf