Dependencies

On a local development system I've installed the latest (1.0,18) version of VVJS and have succesfully tested setting up a slideshow. Not without climbing a learning curve of course.

The project page states:

''This module remains independent — no contrib dependencies required."

I have been testing various releases of the Vanilla Javascript modules for some time and had the contrib Paragraphs module installed to make those tests possible. I thought that before I experimented with disabling the paragraphs module I'd check here ... it's hard for me to see how it wouldn't be needed. It's hard for me to see how various "fields" such as image, image narrow, hero would be available to the slideshow if the paragraphs module was not active. In other words, could you just be using Solo as a theme and install VVJS and be able to set up and run a slideshow based on VVJS without any dependencies. If so, you've achieved magic.

Also, could you provide a little more information on the Awesome Slideshow Engine ... who maintains it, where does it reside, etc. I help maintain the now-ancient Juicebox contrib module that's dependent on a non-open source Javascript engine. The people who maintain it do a great job but the non-open source nature does represent an obstacle.

Seems clear that there are "dependencies" and that the user would want to start with Solo, then Paragraphs, then Paragraphs Bundles and finally VVJS. All these are in Drupal parlance "contrib". If nothing else, the Drupal extend screen shows the dependencies between modules.

I can get the bottom navigation tabs to show, but it would be helpful to have clearer documentation about what they depend on.

Hello,

It sounds like there’s been a mix-up between VVJS Slideshow (Views-based) and Paragraphs-based slideshow workflows, so let me clarify to keep your setup clean and scalable.

VVJS Slideshow vs. Paragraph Slideshow
VVJS Slideshow is designed to display slides using a Views display directly, not using Paragraphs. If you are creating a “gshow” content type and adding images there, you will typically create a View listing those images filtered by your content type or tags, then attach the VVJS Slideshow display to render those images as slides.

Paragraph-based slideshows, in contrast, require a Paragraph type with images embedded in each Paragraph item, which is a separate module and workflow entirely.

Both slideshows use a single JavaScript file, which is included with the module.

Best wishes
Alaa

Thank you for the clarification. Indeed I was confused by this. I have been going back and forth betweeen the paragraph based slideshow and the views based one. Thanks to the great facilities of ddev I am able to experiment freely and quickly on a local system.

Just to confirm: when doing a paragraphs based slideshow the code that drives it is coming from the paragraphs_bundles modules, which as of today is at "1.0.12 Stable release covered by the Drupal Security Team released 30 June 2025"

while the views based module is VVJS at: "1.0.12 Stable release covered by the Drupal Security Team released 30 June 2025"

I will experiment further using your comment in #5 as a guide.

I will take advantage of this being a "support request" and extend it a bit. My overall objective is to have slideshows with "names" or "links accessed from a menu" which the users of my site can access. I would not want them having access to views directly. They would click on a link in a menu and see the slideshow directly, then return to the menu and use other features of the site.

I created a content type named "gshow" which just has a field named "slideshow". I can use that to create a working slideshow and within
the slideshow I have multiple slideshow sections. I just uploaded one "page" or rather the first section from a complete slideshow. The slideshow displays the four images within it in the right order and with the requested delay. I labeled the

Automatically closed - issue fixed for 2 weeks with no activity.