Site A generates this view query ..
SELECT node.nid AS nid,
node.title AS node_title,
node_data_field_pager_item_text.field_pager_item_text_value AS node_data_field_pager_item_text_field_pager_item_text_value,
node.type AS node_type,
node.vid AS node_vid,
node_data_field_pager_item_text.field_slide_text_value AS node_data_field_pager_item_text_field_slide_text_value,
node_data_field_pager_item_text.field_image_fid AS node_data_field_pager_item_text_field_image_fid,
node_data_field_pager_item_text.field_image_list AS node_data_field_pager_item_text_field_image_list,
node_data_field_pager_item_text.field_image_data AS node_data_field_pager_item_text_field_image_data,
node_revisions.body AS node_revisions_body,
node_revisions.format AS node_revisions_format,
node.created AS node_created
FROM drup_node node
LEFT JOIN drup_content_type_ddblock_news_item node_data_field_pager_item_text ON node.vid = node_data_field_pager_item_text.vid
LEFT JOIN drup_node_revisions node_revisions ON node.vid = node_revisions.vid
WHERE (node.status <> 0) AND (node.type in ('ddblock_news_item'))
ORDER BY node_created ASC
Site B generates this query ..
SELECT node.nid AS nid,
node.title AS node_title,
node_data_field_pager_item_text.field_pager_item_text_value AS node_data_field_pager_item_text_field_pager_item_text_value,
node.type AS node_type,
node.vid AS node_vid,
node_data_field_slide_text.field_slide_text_value AS node_data_field_slide_text_field_slide_text_value,
node_data_field_image.field_image_fid AS node_data_field_image_field_image_fid,
node_data_field_image.field_image_list AS node_data_field_image_field_image_list,
node_data_field_image.field_image_data AS node_data_field_image_field_image_data,
node_revisions.body AS node_revisions_body,
node_revisions.format AS node_revisions_format,
node.created AS node_created
FROM node node
LEFT JOIN content_field_pager_item_text node_data_field_pager_item_text ON node.vid = node_data_field_pager_item_text.vid
LEFT JOIN content_field_slide_text node_data_field_slide_text ON node.vid = node_data_field_slide_text.vid
LEFT JOIN content_field_image node_data_field_image ON node.vid = node_data_field_image.vid
LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid
WHERE (node.status <> 0) AND (node.type in ('ddblock_news_item'))
ORDER BY node_created ASC
Site A works, Site B does not work. I am using provided txt files. I want to know why site B generates different query when I have done the exact same things for each site? Module versions are the same except views is newer on site B and Drupal is 6.15 site B, 6.14 site A.
Comments
Comment #1
ppblaauw commentedIn your first sql statement the image field is selected as
In your second sql statement the image field is selected as
CCK (Content Construction Kit) creates fields as
In your second case the image field is probably used in more content types and did get his own table while in case 1 the image field is part of the containing content type.
In case two you need to change in the preprocess functions for the ddblock slideshow module in your template.php file the occurrences of:
into
To make the images show up in the slideshow.
Hope this helps you further, please let me know.
Comment #2
OnlineWD™ commentedYes that's what I did, if in configure settings I use Default the block looks exactly like a normal view i.e. listed items, no animation. If I set it to Cycleblock everything disappears except for the block title. Is there something I have missed? If I try to use a template it gives an error on line 40 of template file.
Comment #3
airen2011 commentedPlease follow the steps in the advanced slideshow tutorial.
In the troubleshooting part of the faq you can find answers on frequently asked questions. The question about the error on line 40 can be found here. Also first search in this issue queue itself (all issues, also the closed ones) for similar issues. This way you can get direct answers and don't have to wait till your questions gets answered.
Hope this helps you further, please let me know.