I have multiple flex slider views on one page, and the dots below the slider work as they should on the first slider, with the 'flex-active' class being set to the correct dot.

But the other sliders on the page, have no 'flex-active' class set on any dot, even when the slides are scrolled through, or the dot clicked.

Comments

minorOffense’s picture

minorOffense CreditAttribution: minorOffense commented
Status: Active » Postponed (maintainer needs more info)

Do the controls on the other sliders have any affect on the first slider? I'm thinking the controls are being mapped incorrectly.

modstore’s picture

modstore CreditAttribution: modstore commented

Yes, the controls seem to affect all sliders on the page. I added play/pause control, and when I click one of them, all pause/play links are toggled.

minorOffense’s picture

minorOffense CreditAttribution: minorOffense commented

Can you provide and export of your configuration?

plopesc’s picture

plopesc
he/him
Primary language Spanish
CreditAttribution: plopesc commented

Same for me.

I have 3 different flex slider in my front page. However the dots do not work. When I remove two of them, the other one works fine.

I use the default config for the first flexslider. The other two uses a custom preset, where I only have disalbled the playback behavior.

In my case, the paging

    is added three times in all the flexslider, one for each flexslider. Then ther is a bug or conflict between the different flexslider.

    Here is the HTML generated:

    <div class="flexslider flexslider-processed">
<ol class="flex-control-nav flex-control-paging">
  <li>
    <a>1</a>
  </li>
  <li>
    <a>2</a>
  </li>
  <li>
    <a>3</a>
  </li>
</ol>
<ol class="flex-control-nav flex-control-paging">
  <li>
    <a>1</a>
  </li>
  <li>
    <a>2</a>
  </li>
</ol>
<ol class="flex-control-nav flex-control-paging">
  <li>
    <a>1</a>
  </li>
  <li>
    <a>2</a>
  </li>
</ol>

    Regards

plopesc’s picture

plopesc
he/him
Primary language Spanish
CreditAttribution: plopesc commented

Hello
Finally I was able to fix the bug.

Problem came from the controlContainer defautl value. By defautl, this value in FlexSlider module is .flex-nav-container.

However, to avoid these prblems, he value should be .flex-control-nav-container as explained in this FlexSlider library request https://github.com/woothemes/FlexSlider/pull/85.

Regards

minorOffense’s picture

minorOffense CreditAttribution: minorOffense commented
Status: Postponed (maintainer needs more info) » Needs review

Should be fixed in the latest commit. Please test and report back.

Thanks.

danwonac’s picture

danwonac CreditAttribution: danwonac commented

I had the same problem on 7.x-1.x and followed plopesc's advice (once I understood it :-) To be clear:
for each option set

  • edit the option set
  • click advanced options
  • change the 'controls container' field to .flex-control-nav-container
minorOffense’s picture

minorOffense CreditAttribution: minorOffense commented
Status: Needs review » Closed (fixed)

  • Commit 4de01a0 on 7.x-2.x, youtube, 8.x-2.x, startslide by minorOffense: 
    Fixed issue [#1805964]
gb2world’s picture

gb2world CreditAttribution: gb2world commented
Issue summary: View changes

I have this issue with:
Flexslider 7.x-2.0-alpha3

Setting up a page view with multiple flexslider instances:
Format:Unformatted list
Show:Display Suite -> Full Content Node View

and the Display Suite uses a field of multiple images set up to display with Flexslider

The controls on the last instance of Flexslider on the page controlled all the instances of Flexslider. Controls on all other flexsider instances had not effect.

The solution in #5 cleared up the problem. (Thanks!)