A very needed block, but with two big issues…

  • I just installed this plugin for a simple solution to be able to add any type of block into a slider. It’s a very needed feature and really should be a default block in Gutenberg IMO. My compliments to the author on recognizing this need.

    Unfortunately I found two frustrating issues:

    Issue 1:

    If you’re already using other types of sliders that rely upon slick.js, there will be css conflicts. This plugin adds a lot of css directly to the slick selectors (ex. .slick-next). The problem is that this will conflict with any other slider using slick.js by overriding its styles.

    What has to happen here is that the css for this particular slider needs to be limited solely to this block. I hope that the plugin author reads this and makes the change.

    The main benefit of the plugin is its simplicity. But this issue with the css is an oversight that should be corrected.

    Issue 2:

    I’ve also discovered that this block will not function properly within a default Gutenberg row block or a Kadence Blocks row/section block combination. This is major drawback since using rows/sections is a basic part of using a block editor. I’m using Kadence Blocks and rely upon its row and section blocks for overall design structure.

    Putting the above issues aside, this is still a very useful block and I hope the author will address these issues I’ve identified.

Viewing 1 replies (of 1 total)
  • Plugin Author Virgildia

    (@virgildia)

    Hi @Michael Samson, thank you for using the plugin and the feedback!

    1. I’ve resolved the issue with the default Gutenberg row block in the latest version. However, compatibility with custom blocks such as Kadence Blocks has not been confirmed. The Carousel Slider plugin uses core Gutenberg blocks, ensuring compatibility with core and any plugins that adhere to standard practices. For issues related to Kadence Blocks rows, please consult their support.
    2. Regarding CSS, Carousel Slider Block actually is not set up to override slick styles used by other plugins. It uses a unique selector wp-block-cb-carousel to apply any custom styles, for example to the arrows. It also loads the default Slick stylesheet only when the block is used. If another plugin is using a modified version of the default Slick CSS (not standard practice), the Slick vendor stylesheet loaded by the Carousel Slider Block may reset the default styles. Carousel Slider Block may use its own custom slide JS in future version updates, eliminating any conflicts entirely with Slick.
    • This reply was modified 11 months, 2 weeks ago by Virgildia.
    • This reply was modified 11 months, 2 weeks ago by Virgildia.
Viewing 1 replies (of 1 total)
  • The topic ‘A very needed block, but with two big issues…’ is closed to new replies.