The issue here is that the user wanted to paginate their post slider 1 slide at a time while maintaining 5 slides visible.
Solution:
Unfortunately this isn't possible to do based on how the view pagination works. The view works by loading pages of posts and not the individual post itself.
What I mean by this is that if you have 15 posts and you're displaying 5 posts per page, then you will have 3 pages. Each click will load 5 posts rather than the next immediate post.
Based on the custom field i'm assuming that you're getting the email from the current post that is being created by the form. In this case you should be able to do this.
Problem: I have a View that displays results in 4 different styles. I would like to repeat the pattern of style 1, style 2, style 3, and style 4 in the results. Another ticket discusses a solution for repeating 2 styles: @https://toolset.com/forums/topic/changing-row-colors-in-a-view/
How can I extend this solution to work with 4 styles in a repeating pattern?
Solution: Use wrap="4" to indicate you want to repeat the pattern every 4 items in the results, and use the wpv-item shortcode to define each iteration of the 4-item loop.
I'm trying to display product attributes (each with a different price) directly within the view. Not in the single-product itself.
So I want the user to be able to select the appropriate attribute in the view's page.
Solution:
There isn't such kind of built-in feature within Toolset plugins.
The shortcode [wpv-woo-buy-or-select] works just like the default Woocommerce shop page.
In the default Woocommerce shop page, it displays same "Select options" button for variable products, user can click this button, then redirect to the single product page
When I click "Add to cart"([wpv-woo-buy-options] shortcode), it displays a link "see cart". but this link is /prodcuts/null instead of /cart, giving a 404.
Problem: I would like to display a 2-column list of posts grouped by custom field value, showing the custom field value in one column and a link to the post title in the other column.
Solution: You can use a View of this post type with a Query Filter based on your custom field, set by a shortcode attribute. Type the custom field value manually, then insert the View shortcode with the custom field filter just after the custom field value you typed manually, like this:
Milan [wpv-view name="School View" wpvcity="Milan"]
The issue here is that the user was a little confused about the Difference between toolset blocks, views and layouts.
Solution:
Our Blocks plugin was made specifically to integrate our other plugins better with the wordpress gutenburg editor. This means that through blocks you can create views and add custom field content to your page through the GUI.
So it serves as a better way to integrate our other plugins with the gutenburg editor. So its not going to replace Layouts or Views but rather help to boost integrations.
Relevant Documentation:
Read how you can use Toolset Blocks to display custom fields, design templates, create archives, build searches and more.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
