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: I am trying to use a generic field in my Form. The field has a slug of page, but when I try to submit the Form I am shown an error stating that the page does not exist.
Solution: Avoid using WordPress-reserved terms like page or post for generic field slugs. See the link below for a more comprehensive list of terms that are reserved in WordPress.
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
Problem:
When showing ShortCodes conditionally with a HTML conditional, those ShortCodes are not rendered in the front end.
Solution:
If you are sure the HTML conditional is well-formatted and the condition matching your content, then it could be due to character limitation as explained here:
Problem:
How can we insert a View using Blocks passing a ShortCode Query Attribute to the View?
Solution:
That's not possible with Blocks.
This is possible only if you insert the actual ShortCode of the View and use the "Fields and Views" GUI of Toolset in, for example, a classic block, instead of using a View Block.
En Toolset erratas, documentamos problemas conocidos y sus soluciones. Ahorre tiempo consultando allí primero y viendo si el suyo es un problema conocido. Mantenemos la lista corta. Hacemos lo mejor que podemos para resolver todos los problemas conocidos con cada lanzamiento de los plugines de Toolset.
Política de soporte
Nuestro personal le ayudará a usar los plugines de Toolset correctamente, le proporcionará la información que necesite, le ayudará a resolver problemas y lo asesorará con respecto a las mejores prácticas.
Sírvase asegurarse de incluir solamente un tema en cada solicitud de soporte.
