Hi Beda,
Thanks for escalating the priority !
I can understand, but if it could be accepted for the ajax update pagination, it's not the same for all the filters that are linked to this issue.
Adding a refresh button to change the display each time the user is modifying a setup is not something I can propose to my client.
Another issue there : I'm trying to place the pagination control and face a pb :
On my shop page, I have the filter of the Views in the sidebar (as a widget) and the Views result in the page itself. I have tried to place the pagination controls either in the filter section (no display) or in the content page (display but without action).
Can you help to define the best way to use pagination on this specific example?
Hope this fix will come soon !
Regards
Pat
1. Having the View's Filter in a sidebar will only allow redirecting to a certain results page. It will not allow (even if it accidentally works) to filter a View that is set on a certain page with for example AJAX updates.
This means, that yes you can filter the results of a View by using a Search placed in a Widget but it requires to reload a certain results page, which always will be the same
I hope I did not misunderstand, and you mean that you just a split view on the same page, meaning, sidebar and main content but not the widgetized sidebar.
2. The Shop in WooCommerce is not a page per se but an Archive, and that is what should be styled with a Views Archive (rather than with a View).
In Toolset > WooCommerce settings you will choose the WCV (WooCommerce Views) default template for archives, then create an archive in Toolset > WordPress Archives and assign it to Products.
That will replace/style the native WooCommerce shop "page" (which in fact is not a page, but an archive)
3. Widgets will not accept paginations - and only Views can be split, not so archives. Hence, I suspect you would have to change the approach here and rather use an Archive to style the shop "page" (archive) OR create a separate page, where you insert a View, which lists the Products. But that would mean to duplicate the Shop (as already there in archives)
4. Pagination itself, if used on a View, will work both on the Search or Loop section but, if the View is split, and inserted on an Archive, this won't work
It will only work if used on a Page.
You can do the following test:
- create a view with any post type and paginate that
- insert pagination links to the search or loop section
- insert this to a page and test it
==> It should (also according local tests= work both with WC and without.
- In an archive instead (such as the shop) you will need to enable pagination in the archive itself, and insert the links in that archive (but that cannot be used as split mode like a view can, and it depends also on the Themes/WordPress settings of pagination
I hope the above observations help to resolve the problem, otherwise please do not hesitate to correct me.
(I am off tomorrow until and inclusive Monday, and could request a colleague to have a look in case you need more time/are in a time-schedule)
Hi Beda,
Any news concerning the ajax issue?
I need to launch the new site as soon as possible and need a solution to avoid reloading the page using filters !
Regards
Pat
Hi Beda,
I have updated the plugins with the new version (as mentioned in the new created ticket) and it's working now.
Thanks
Pat
