White box in view_slideshow_ddblock

Do you have a link to the Internet site?

The slideshow has no content.

Just some suggestions:

Maybe you have the content permissions module (submodule of CCK) enabled and did not give permissions for the fields used.

Maybe the nodes used for the slideshow are not published.

Did you put the block in a region or did you add it in another way?

The view looks Ok.
Don't know why the content of the slideshow is empty.

Did you have other versions of views_slideshow_ddblock modules installed?
Maybe preprocess functions of version 1.1 are remaining in your template.php file.

Sorry for late reply.

I had precisely the same issue and fixed it by mapping the fields in the configuration for the slideshow. I had passed over this part of the documentation, and it seems to be fix itself when the fields were mapped.

I had the same issue, The slideshow has no content. I had the have the content permissions module (submodule of CCK) enabled. The the nodes used for the slideshow are published. Put the block in a region. I've attached a screenshot of the Error I encounter during configuration. Any help would be appreciated.

In the email you send I see that in the view you use, under filters, your Node type: unknown.
You need to select the content type used for the slides.

The slideshow settings are set in the views configuration page, by clicking the "gear" symbol behind: Basic settings > Style:slideshow.

I don't know where your filefield errors come from.
Try to install the filefield module again and if this does not give the solution have a look in the issue queue of the filefield module.

DDblock and views_slideshow_ddblock module are separate modules.
You don't need the ddblock module to use the views_slideshow_ddblock module.

You can use the example module which comes with the views_slideshow_ddblock module (version 2).

I think it's easiest to use the example module to get started. This allows you to examine views and see how things are working. I had a white box too at first, but it's because I didn't have jquery installed and then I also copied the "custom" folder improperly into the theme folder.

Similar/same problem. Nothing displays in the active block (except for the Prev/Next arrow images), but the Views preview shows all images (stacked horizontally.

I've struggled to diagnose/debug for 2 days and am completely stumped. I would buy a premium theme for my client if I you can help me get this to work. Please help!

My configuration:

• Drupal 6.22
• Content Access 6.x-1.2
• Content Permissions 6.x-2.9
• Image 6.x-1.1
• Dynamic Display Block 6.x-2.0
• Views slideshow 6.x-2.3
• jQuery update 6.x-2.0-alpha1
  - also jQuery plugins 6.x-1.10
• CCK 6.x-2.9
• Views 6.x-2.12
• FileField 6.x-3.10
• ImageField 6.x-3.10
• ImageAPI 6.x-1.10
• ImageCache 6.x-2.0-beta12

Permissions
All CCK field and image permissions for access/view are set to anonymous (+admin).

Theme

1. I downloaded dynamic display block theme package vsd-upright10-60-V2-x.zip and extracted it to a temp directory
2. I and copied the entire "custom" directory/subdirectories into my theme's main directory.
3. The path is /sites/all/themes/mix_and_match/custom/modules/ddblock/..
4. NOTE: I use the "Mix and Match" Fusion sub-theme as the default. It does not have an existing "custom" directory.
5. I cleared all caches including the theme registry.

Views Config
I am using the default View called "ddblock_if_example_slideshows".
I created 1 new node and uploaded an image.
The field mappings look OK.

Filter
Node: Published Yes
Node: Type = ddblock image field example item.

Fields
Node: Nid Nid
Node: Title Title
Content: Image Image
Content: Slide text Default
Content: Pager item Plain text
Node: Link Link

Style
Style: Slideshow
Slideshow mode: ddblock
Display Method: Cycleblock

Note: the attached image says "cloned" but it is actually the default view for ddblock

#10 do you have a link to the slideshow on your site?

All,
I hope this helps someone, but I have been struggling with this module for sometime and the root cause ended up being the permissions on the files in the folder it self. So the "jquery.cycle" file and any other custom changes.