Skip Navigation

[Escalated to 2nd Tier] Have both automatic transition and manual transition

This support ticket is created 5 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 1 reply, has 2 voices.

Last updated by Waqar 5 years ago.

Assisted by: Waqar.

Author
Posts
#1413907

Tell us what you are trying to do?

I am trying to get a slider to do an automatic transition, but also allow users to manually transition using Navigation controls using dots. Currently for me, if a user does not click any dots, the slide will transition automatically, but after clicking a dot, the slide will no longer transition automatically. I was wondering if this was expected behavior or perhaps has to do with my pagination settings. Ideally, if the slider could continue to transition automatically, that would be great.

Here are my settings:

Pagination and Sliders Settings: Pagination enabled with automatic AJAX transition

Custom Search Settings: Full page refresh when visitors click on the search button

Search and Pagination:
[wpv-filter-start hide="false"]
[wpv-filter-controls][/wpv-filter-controls][wpv-pager-nav-links output="bootstrap" links_type="dots"]
[wpv-filter-end]

Is there any documentation that you are following?

https://toolset.com/documentation/user-guides/views/creating-sliders-with-types-and-views/

What is the link to your site?

Here is a page where the slide is shown: hidden link

#1414319

Hi Michael,

Thank you for contacting us and I'd be happy to assist.

I've performed some tests on my own website and was able to reproduce the same behavior.

I've escalated this to the concerned team for further review around whether this is the expected behavior or needs some changes.

Unfortunately, I don't have any workaround to share at this time, but I'll keep you updated through this ticket.

regards,
Waqar