Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The options as listed here http://nivo.dev7studios.com/support/jquery-plugin-usage/ are not all configurable.
Of the variables;
- effect: 'random', // Specify sets like: 'fold,fade,sliceDown'
- slices: 15, // For slice animations
- boxCols: 8, // For box animations
- boxRows: 4, // For box animations
- animSpeed: 500, // Slide transition speed
- pauseTime: 3000, // How long each slide will show
- startSlide: 0, // Set starting Slide (0 index)
- directionNav: true, // Next & Prev navigation
- directionNavHide: true, // Only show on hover
- controlNav: true, // 1,2,3... navigation
- controlNavThumbs: false, // Use thumbnails for Control Nav
- controlNavThumbsFromRel: false, // Use image rel for thumbs
- controlNavThumbsSearch: '.jpg', // Replace this with...
- controlNavThumbsReplace: '_thumb.jpg', // ...this in thumb Image src
- keyboardNav: true, // Use left & right arrows
- pauseOnHover: true, // Stop animation while hovering
- manualAdvance: false, // Force manual transitions
- captionOpacity: 0.8, // Universal caption opacity
- prevText: 'Prev', // Prev directionNav text
- nextText: 'Next', // Next directionNav text
- randomStart: false, // Start on a random slide
- beforeChange: function(){}, // Triggers before a slide transition
- afterChange: function(){}, // Triggers after a slide transition
- slideshowEnd: function(){}, // Triggers after all slides have been shown
- lastSlide: function(){}, // Triggers when last slide is shown
- afterLoad: function(){} // Triggers when slider has loaded
Only the following are configurable
- effect: 'random', // Specify sets like: 'fold,fade,sliceDown'
- slices: 15, // For slice animations
- boxCols: 8, // For box animations
- boxRows: 4, // For box animations
- animSpeed: 500, // Slide transition speed
- pauseTime: 3000, // How long each slide will show
- pauseOnHover: true, // Stop animation while hovering
- captionOpacity: 0.8, // Universal caption opacity
Specifically we would like the controlNav to be configurable especially given that this module forces behavior that is not consistent with the default nivo slider settings in regard to the controlNav default. This can be seen in media_invo_slider.js where controlNav is explicitly set to false.
Comment | File | Size | Author |
---|---|---|---|
#2 | media-nivo-slider-1414756-1.patch | 607 bytes | jgraham |
Comments
Comment #1
jgraham CreditAttribution: jgraham commentedAttached patch changes media_nivo_slider.js to use the nivo slider default for controlNav.
This patch is not the ideal solution since this is still not configurable.
Leaving open to address the larger UI/UX config issue of so many configuration options. This likely should be not exposed on every node.
Comment #2
jgraham CreditAttribution: jgraham commentedmissed patch from last comment
Comment #3
peronas CreditAttribution: peronas commentedHi jgraham, thanks for the feedback and patch to resolve this issue.
As you noted the ideal solution would be to have all the settings be configurable via the interface rather than having to change this at the code/global level.
I'm changing this to a feature request as getting all the configuration options into the interface is in the pipeline of updates for this module. At this point I'm still sorting out the best way to allow for full configuration of the slider in a way that's not overwhelming in terms of the interface while still trying to maintain the full customization ability of each individual slider.
I'm definitely open for feedback and input on the UI/UX front so if you have ideas feel free to share.
Comment #4
peronas CreditAttribution: peronas commentedMeant to update the title as well...
Comment #5
jgraham CreditAttribution: jgraham commentedJust a thought regarding the UI/UX. Perhaps have global sets of configuration that were named and then at the node/instance level the user chose one of the pre-configured global configurations.
This solves two things that I see as potential pitfalls of the per-instance config;
In summary, the site builder would still have full control over all the nivo slider options, but less technical users are presented with a selection of which slider config to use.
Comment #6
peronas CreditAttribution: peronas commentedI like this idea and had been thinking similarly for how to address the desire to have a global reusable configuration.
Taking my initial thinking one step further, and moving all the configurations over to something like you suggested and simplifying the fields that are on the node form itself is favorable in my opinion and will clean up and trim the module as well.
Seeing as this workflow would be very similar to other media related modules such as image styles it should be mostly straight forward and familiar from the user perspective.
Given all that I think I'll start moving this direction, likely in a 2.x branch since the change over from using individual fields to stored configurations will be a somewhat big change. Should have something together in a couple of days.
Comment #7
peronas CreditAttribution: peronas commentedOk I've added a beta release for the 2.0 branch which implements configurable presets and exposes all of the Nivo Slider options to be configured in Drupal.
Give it a test when you have a chance and let me know if you experience any issues with the new workflow or the upgrade from v1 of the module.
Thanks!
Comment #8
peronas CreditAttribution: peronas commentedFixed one outstanding issue and made a stable v2.0 release that provides full customization of the Nivo Slider options. Marking this as implemented.
Comment #9
peronas CreditAttribution: peronas commentedComment #10
vipuldawar88 CreditAttribution: vipuldawar88 commentedHi all.
I have used nevo slider in one of my project, but I want some make some modifications as per my profect.
can anyone help in how to start nevo slider transitions on click of an image and not automatically on loading of page containing the nevo slider.
pls suggest.
Thank you.
vipul
Comment #11
peronas CreditAttribution: peronas commentedvipuldawar88,
First, please do not re-open closed tickets that are unrelated to your bug/support request/feature request. Search the tickets first, but if you don't find an existing ticket related to your issue please create a new ticket.
For the question you asked you may look at setting 'manual transitions' to true. This would turn off the automatic transitions and make it so the user has to either click the thumbnail, next/prev arrow, or use the keyboard.
A quick note though, if you are still using a 7.x-1.x version of the module not all of these options are configurable. All the available configuration options have been made available in the version 2 of this module.