We are adding translations to our site. We have a number of views that are using Flexslider to make a slideshow. The english / default view is fine and works as expected. The change of behavior is because the Multiple Field Settings will only display all values in the same row for translations.

When the language is switched the slideshow is no longer a slideshow but a list of the content. The field is a paragraph that is a rendered entity. We have the translation properly configured within the paragraph field so that it is translated. I am not receiving any errors from the chrome inspector console or watchdog and the jquery.flexslider-min.js and flexslider.load.js are loaded for both pages.

The expected behavior is that when switching languages the slideshow would continue to be a slideshow.

Here is the view setup:
View setup

Here is the expected behavior:
View in english

Here is the unexpected behavior:
View in German

CommentFileSizeAuthor
#2 translated_view.png201.21 KBoheller
#2 source_view.png146.6 KBoheller
German.png925.19 KBoheller
English.png427.51 KBoheller
view.png380.72 KBoheller
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

oheller created an issue. See original summary.

oheller’s picture

oheller CreditAttribution: oheller commented
Title: Flexslider not working for translated language » Multiple Field Settings only displays all values in the same row for translated language
Project: Flex Slider » Views (for Drupal 7)
Version: 8.x-2.x-dev » 8.x-3.x-dev
FileSize
source_view.png146.6 KB
translated_view.png201.21 KB

Updating this issue. When I unselect the "Display all values in the same row", I expect a new row for each item for the source language and for translated languages. The current behavior is that the source language acts correctly but the translated languages are put inside a row.

Here's the html output:

Source View

Translated View

oheller’s picture

oheller CreditAttribution: oheller commented
Issue summary: View changes
Lendude’s picture

Lendude
Primary language Dutch
Location Amsterdam
CreditAttribution: Lendude at Dx Experts commented
Project: Views (for Drupal 7) » Drupal core
Version: 8.x-3.x-dev » 8.4.x-dev
Component: Code » views.module

Thanks for the very clear bug report!

Views is in Drupal core now, moving to the right queue.

Not sure if this is a Views or Paragraphs issue (or a bit of both). Will leave it in Views for now, but some steps to reproduce this issue without any Paragraphs or Flexslider would really help narrow down where we should be looking for this.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

eastdrive’s picture

eastdrive CreditAttribution: eastdrive commented
Version: 8.5.x-dev » 8.3.7

I can confirm this behaviour WITHOUT paragraphs.

Drupal 8.3.7
Flexslider 8.x-2.0-beta1

Using an entity reference field to >1 content items.

English works fine but any other language shows items in the same row, despite check box to the contrary.

Could still be a flexslider issue?

eastdrive’s picture

eastdrive CreditAttribution: eastdrive commented
Version: 8.3.7 » 8.5.x-dev
eastdrive’s picture

eastdrive CreditAttribution: eastdrive commented

Here's the output for English:

<div id="flexslider-1" class="flexslider optionset-default">
    <ul class="slides">
        <li>
            <article class="blog-article-banner">...</article>
        </li>
        <li>
            <article class="blog-article-banner">...</article>
        </li>
    </ul>
</div>

And the output for Spanish:

<div id="flexslider-1" class="flexslider optionset-default">
    <ul class="slides">
        <li>
            <span class="views-field views-field-field-home-page-blog-rotator">
                <span class="field-content">
                    <article class="blog-article-banner">...</article>,
                    <article class="blog-article-banner">...</article>
                </span>
            </span>
        </li>
    </ul>
</div>

Note the 2 extra <span> tags and the comma separating the 2 articles.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.