Compatibility: Change “slick” CSS handle

  • Resolved robertrosanke

    (@robertrosanke)


    2 years, 6 months ago

    Hello,

    we have detected a conflict with a theme.

    With our theme, the slick css file of your plugin will not be included because the theme has already registered the handle “slick”.

    This causes display errors – e.g. the prev-next arrows are not visible in the carousel block.

    If “Carousel Slider Block for Gutenberg” changes the existing handle from “slick” to e.g. “carousel-block-slick” it works again.

    Please adjust the handle for /dist/assets/vendor/slick/slick.min.css in carousel-block/init.php, line 45.

    In addition, it might also be advisable to nest the CSS rules integrated with the file under “.wp-block-cb-carousel” in order to reduce side effects.

    I suggest the same to the theme author.

    Thanks for the easy to use plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Virgildia

    (@virgildia)

    Hi @robertrosanke . Thank you for your suggestions! I will update the CSS handle in the next version. Initially, the carousel was made to use the default Slick CSS. If a theme is already using Slick, the carousel block is meant to inherit the style and any custom CSS. You can add custom styling to the carousel by including the class name wp-block-cb-carousel to your CSS.

    • This reply was modified 2 years, 5 months ago by Virgildia.
    • This reply was modified 2 years, 5 months ago by Virgildia.
    Thread Starter robertrosanke

    (@robertrosanke)

    Thank you for your support and for explaining the thinking behind the “slick” handle!

    Plugin Author Virgildia

    (@virgildia)

    @robertrosanke You’re very welcome! I have released a new version with some small improvements. I also renamed the Slick CSS stylesheet handle to something unique.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Compatibility: Change “slick” CSS handle’ is closed to new replies.