Maybe I must mention that this is the first time I have tried building a custom DDBlock theme for Drupal 7 so if I am being a moron please excuse me this time ;)

Hi I have used the following steps to create a custom DDBlock theme.

I have created a custom content type and a view, Created a instance and configured the DDBlock. I also copied the ddblock themes into my theme folder.

I needed to use a image pager so I tested the upright40p theme which worked quite well with the image pager but the sizes was quite different to what my designer designed in the mock-up.

I then proceeded to copy the ddblock-cycle-block-content--upright40p.tpl.php file and renamed it to:
ddblock-cycle-block-content--beadsforyou.tpl.php (beadsforyou is the custom Drupal theme I'm using)

I also copied ddblock-cycle-pager-content--upright40p.tpl.php and renamed it to:
ddblock-cycle-pager-content--beadsforyou.tpl.php

I looked inside these two templates and it seemed that I did not have to change anything like the procedure for Drupal 6.

I then copied the upright40p folder and renamed it to beadsforyou and the renamed the ddblock-cycle-upright40p.css file to:
ddblock-cycle-beadsforyou.css

I also replaced all css selectors in the css file from upright40p to beadsforyou

I resized the needed elements and the DDBlock displayed correctly except for not showing the pager.

I then went back to the DDBlock settings page to see if I can choose a custom pager this is when I noticed that the Dropdown at the Pager settings section labeled "Pager *" is empty. The strange thing is that it does display a value when I choose the upright40p as the "Slideshow theme layout" the value is then "Custom pager"

Am I just missing something or should this be considered as a bug?

Sorry for the lengthy explanation but I thought it might help someone replicate the problem.

I am also aware that I could probably just change the upright40p Slideshow theme layout directly but Iwould rather be able to use a custom theme.

TIA Julian

CommentFileSizeAuthor
PagerSettings01.jpg15.22 KBjlab
SlideShowThemeLayout.jpg25.39 KBjlab
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ppblaauw’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

The slideshow themes have a naming convention which is used for the pager.
10p - 10 = number pager, p is portrait layout with pager at top or bottom
20p - 20 = prev/next pager
30p - 30 = text pager
40p - 40 = image pager
50p - 50 = image-text pager
60p - 60 = scrollable pager

This convention is also used in the admin pages to set the possible pager type ad pager position

You would need to call your custom slideshow theme: beadsforyou40p

so it becomes
ddblock-cycle-block-content--beadsforyou40p.tpl.php
ddblock-cycle-pager-content--beadsforyou40p.tpl.php
beadsforyou40p
-- ddblock-cycle-beadsforyou40p.css

Inside the ddblock-cycle-beadsforyou40p.css change all css selector from beadsforyou to beadsforyou40p

Hope this helps you further, please let me know

jlab’s picture

Thank you very much this information was most valuable you have my sincere and utmost gratitude for this fast and useful reply.

DDBlock is truly a killer module and I thank you for that.

And if you need any help with the D7 Documentation please feel free to push my button I would gladly help with this any where I am capable of doing so.

ppblaauw’s picture

Title: Creating a custom ddblock theme creates a empty pager drop down » Creating a custom ddblock theme creates a empty pager drop down (fixed)
Status: Postponed (maintainer needs more info) » Fixed

Thanks for your offer helping with the documentation. I just created the Drupal 7 - Advanced slideshow tutorial at http://ddblock.myalbums.biz
This is a quick step by step tutorial, which assumes you have basic drupal knowledge.
It could use some review.
Set status to fixed for this issue.

jlab’s picture

I will go through the tutorial instructions and post anything I didn't understand or was unclear to me here.

jlab’s picture

Hi this is a great tutorial I used the 10 steps and everything worked like a charm.

I especially like the fact that it is not necessary to use the theme pre-process functions in the theme's template.php file like the previous version for Drupal 6.x.

This is a great module and appreciate the effort that has been put into the new D7 port.

I tried posting a comment on the tutorial page but kept getting this message.

"Your submission has triggered the spam filter and will not be accepted."

So I'm leaving my feedback here...

I think I might make take some time and create a screen-cast of this over the weekend I'm sure someone will find it useful.

Let me know if I should send you a copy or can upload it to Vimeo or something.

ppblaauw’s picture

Thanks!

Would be great to have a screencast for ddblock drupal 7. It will be very useful.

Status: Fixed » Closed (fixed)

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

NandaKher’s picture

Assigned: Unassigned » NandaKher
Issue summary: View changes
Status: Closed (fixed) » Active
Issue tags: +Custom theme doesn't work

DDblock works fine for me, except custom theme in drupal 7.

- I copy upright60p folder and rename it into upright60me.
- rename css file in this folder into "ddblock-cycle-upright60me.css"
- modify every element in the css file from upright60p to upright60me.
- copy "ddblock-cycle-block-content--upright60p.tpl.php" and rename it into "ddblock-cycle-block-content--upright60me.tpl.php"
- copy "ddblock-cycle-pager-content--upright60p.tpl.php" and rename it into "ddblock-cycle-pager-content--upright60me.tpl.php"

Everything seems ok, but whenever I use this custom theme, my slideshow block disappears. Is there something wrong? Can anyone out there help me please...

ppblaauw’s picture

Status: Active » Fixed

The last three character are part of the naming convention like described above

use uprightme60p for the themename instead of upright60me
css: ddblock-cycle-uprightme60p.css
etc.

Hope this helps you further

set status to fixed.

Status: Fixed » Closed (fixed)

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