I want to have both a pager and a prev-/next button on my slideshow. I started out with the ddblock-cycle-pager-content-gradient-blue30p theme but have stripped it down quite a lot. I don't use the supplied style sheets at all. I display my slideshow in a block.
I have successfully used the link:
<a href="#" title="Click for next image" class="pager-link"></a>
I tried to fix it by using the following code from ddblock-cycle-block-content.tpl.php:
<!-- prev next pager. -->
<div id="ddblock-<?php print $pager ."-". $delta ?>" class="ddblock-<?php print $pager ?> ddblock-pager clear-block" style="height: <?php print $pager_height ?>px; width:<?php print $pager_width ?>px;">
<a id="prev2" href="#">Previous</a>
<a id="next2" href="#">Next</a>
</div>And sure enough, I do get the buttons and when I'm on the first image of the slideshow I only see the link for the next and vice versa when I'm on the last image of the slideshow. The problem is that the links don't go anywhere! ;)
So, if someone has a clue on how to separately take in prev/next-buttons without disturbing the pager I already have working I would be a very happy gal!
And I also would like to...
...be able to always have both the prev and next buttons visible so that if I'm on the first image of the slideshow, the prev-button would take me to the last slide and if I'm on the last image, the next-button would take me to the first slide. I already have the slideshow looping so there is no real beginning or end.
Thank you! :)
Re: prev/next buttons
The next version of the ddblock slideshow module for Drupal will have multiple pager functionality and also a scrollable pager.
You can help to make this next version being released by testing the development version of the module and let us know your comments.
RC6 and the dev version are not compatible and you can not run them on the same site. You can download the themes for the dev version at the download page.
You can see an example of multiple pagers at: http://themes.myalbums.biz/content/vsd-upright60-scrollable-pager
Thank you for your reply! I
Thank you for your reply! I will certainly try this new version and see if that solves my problems. I'm just sorry I didn't ask before I made all the modifications to the template of my current version of ddblock. ;)
But is the dev version safe to use on a production site?
Re: thank you for your reply
It's a development version for half a year now, I solved all bugs I encountered and which are posted by other users who tested the module. I still need to implement the solutions for bugs in version RC6 of the module and this will then be version 1.0 of the module. The current dev version will become version 2.0 but still want to include the developments of version 2.0 of the views_slideshow_ddblock module.
There is also a dev version of the views_slideshow ddblock module, which will soon be released as version 1.0 of this module, and I have new developements for this module which will then be released as version 2.0 for this module.
This version 2.0 will have mappings for views fields to fields in ddblock template files, will use themed field data from view fields instead of raw data, it does not require preprocess functions anymore in the template.php file and it will have an example module which installs a content type, a view with 6 slideshow blocks for each upright theme, and it will install example nodes.
I will try to make this all happen within this and next month.
So it's a little bit difficult to advise which version to use at the moment.
Depends highly on how quickly you need the functionality.
Really can't make it work...
The goal is to have a slideshow with a numbered pager on top and a prev- and next-button on each side of the image showing. Nothing more (but also nothing less! ;).
Sorry for bombarding you with all these messages but I really can't get it to work. I've installed the dev version on a clean drupal installation and followed the video tutorial with the aim of getting the upright60 theme on my slideshow. I get the slideshow to work but there seems to be no theme on it (i.e. no buttons no nothing - just the images fading in and out as I've set them in the block settings.
The only way I could get it to work at all was by using the page-option and pasting the bit of php-code to call the block. Just trying to display the block wouldn't work - I got nothing. If I enable the page AND the block (from administer/site building/blocks) I see my page-slideshow plus the title of my block (with no content).
I have a feeling all of this is because the slideshow can't find the template files or that the settings for the block doesn't agree with the template files but I can't find a reference as to where I should put the template files which are NOT custom and/or what options the different templates have for the settings.
I'm trying to use the template: upright60 which at the moment (I've tried a lot of different options) is placed in sites/all/themes/mytheme/custom/. I have also tried with the name "ddblock" instead of "custom" for the folder inside mytheme with the same result.
Maybe I've searched badly for the answer and if so I apologize but if someone could point me in the right direction I would very much appreciate it!
Thank you!
/Lisa
Re: Really can't make it work...
For your requirements you can use the upright10 theme which has a number pager and you can you the setting to use a second pager on the slide with the prev/next buttons.
The upright themes have to go in the directory sites/all/themes/mytheme/custom/, so that is correct. (you need to use the upright themes for the dev version)
The preprocess functions have to be placed in the template.php file of your theme. (again the preprocess functions for the dev version)
After this you need the clear your cache at administer > Site configuration > Performance.
You can also enable the debug setting in the slideshow configuration page.
Hope this helps you further, please let me know.
If not please make an issue in the issue queue of the module.
Attach the results of the debug lines
Attach your template.php file
Add a link to your Drupal site.
One thing that I notice does
One thing that I notice does differ between the dev-version and the RC6 is that in the dev-version I find no field to set the template for my dynamic display block (it did in the other version and that's also in the video).
Is this automated now so I don't need the field anymore or is it a bug?
Thank you!
Sorry, I missed that if I
Sorry, I missed that if I choose custom, I have to save and then come back in order to set the template. However, I wanted to try the upright60 theme for the dev version of ddblock and I'm not sure I have the template in the right folder... As far as I have understood I should put the files in the custom folder of my theme.
I don't see any images though, can I really use the video tutorial for the dev version or is there another tutorial for this version?
Re: custom template can not be set bug
That you first have to save the configuration when choosing custom, before you can fill in the custom template is a bug. The field should be shown directly when you choose custom.
Can you make an issue in the issue queue of the module for your issues.
Can you enable the debug lines (setting at the top of the configuration page of the ddblock slideshow block) and attach the result of the debug lines and your template.php file? A link to your Drupal site would also be helpful.
Please provide the additional information, so I can help you better.
I have to install and use it
I have to install and use it now but I'm a bit confused about how to do it – can I use the same video tutorial for the dev-version as I did for the RC6?
I tried to install it the same way as I did before but I can't get the images to display (i do see prev- and next-links though so something from ddblock is showing. I'm guessing I missed some crucial part of the installation and will start from the beginning with the video tutorial.
I guess the views-slideshow will be a lot easier to implement but maybe that one still has a bit to go?
Thanks for a great job though, even if it's a bit of a struggle setting it up, once it's there it's a great module!