[Resolved] Toolset Views 2.9 Beta – pagination should not move with slide

[Author]

Posts

[michaelW-23]

I am trying to: build a slider using Views 2.9 Beta

Link to a page where the issue can be seen: hidden link

I expected to see: pagination dots which stay in place when the content transitions horizontally above it.

Instead, I got: pagination moves with each slide, which is very distracting for the end-user.

[Minesh]

Hello. Thank you for contacting the Toolset support.

Can you please share access details so I can check how you set up the pagination?

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

[Minesh]

Can you please check now:
=> hidden link

I've added the pagination code to view's output editor as you can see with your view:
=> hidden link

<div style="text-align:center" class="wp-block-toolset-views-pagination-dots">[wpv-filter-start hide="false"] [wpv-pager-nav-links output="bootstrap" links_type="dots"] [wpv-filter-end]</div>

I can see now dot pagination works just fine.

[michaelW-23]

Thanks Minesh. So it looks like you edited the view separately. If I edit the page where the view is inserted, it looks like it is automatically moving the pagination back to the section of the loop that moves.

If that is the correct diagnosis of what is happening, then please can you flag this up as something that needs to be fixed in Views 2.9-beta.

[Minesh]

Do you mean that when you just save the view - the pagination is added back to view's loop editor section?

Please note that:
Toolset Blocks is in a dynamic stage so you can expect frequent beta updates but you should not yet use it for live production sites.

[michaelW-23]

Apologies for the delayed reply.

This is a support ticket about Views 2.9 BETA

The intended purpose of this plugin is to build views within the WP editor. It is a Gutenberg-style block. I am flagging up a problem that needs to be fixed before this comes out of Beta:

It is difficult / impossible to position pagination correctly within the WP block editor.

I can subsequently edit the view in Toolset views UI to put the things in the right place.

However, if I go back to the page where the editor was inserted and try to edit that page, the view gets broken / or all the corrections I made in the Views UI are overwritten.

This is a major problem that needs to be sorted before it comes out of Beta.

[Minesh]

I know you are talking about the issue that belongs to Views 2.9 BETA.

Please allow me to run few tests (with the latest beta if available) and I will get back to you as soon as I know more.

[Minesh]

Thanks for all the inputs you have given.

Regarding:
However, if I go back to the page where the editor was inserted and try to edit that page, the view gets broken / or all the corrections I made in the Views UI are overwritten.
==> For this issue, will report your concerns to our Devs and see what we can do. As when you build view using blocks editor it will have a certain code and once you try to add something in the normal Views UI mode - there is a possibility that it will get broken. We will try to find a way what we can do in this case and fix it accordingly.

Regarding the Pagination issue - if you see the image you shared, you will notice that you added the pagination inside the view's loop.
=> https://toolset.com/wp-content/uploads/2019/07/1284661-views_beta_problem.jpg

We just tested the pagination with the latest branch source code and we do not find any issue. The pagination must be added outside the loop in order to work properly.

Please feel free to report if you able to spot any other possible issues, we would be really happy to see it and fix it if confirmed.

[michaelW-23]

Thanks for looking at this in detail. Two final comments for the devs to consider:

1. The current blocks interface makes it difficult to tell if something is inside or outside the loop.

2. Please make it clear what special code needs to be retained to avoid breaking the view if edited in the standard UI.