Please document requirements and compatibility

> If a module depends/uses ImageField/ImageCache its usually safe to assume it is incompatible (unless otherwise stated)
> with Image.module I find.

Sorry, but I have to disagree. ImageField and Image.module *do* work fine on the same Drupal instgallation since ImageField by itself does not enforce a node type named "Image" - I've both running together on several sites. Also, ImageCache works very well together with Image.module. The incompatibility just applies to very limited use cases.

Greetings, -asb

I'm currently trying to transcribe Jeff's screencast at Howto: Node-based galleries with CCK and Views, I hope that's fine with Jeff and you?

However, there are still a couple of things in Jeff's screencast I can't reproduce yet so the "Howto" currently has an "Incomplete" flag set (e.g. I'm not getting the "Add photo" button).

> This module no longer defaults to 'image' for the image content type, which was the only problem using it with the image module.

Sorry, I can not reproduce this with the current release available, at least not in my D6 sandbox with running "image" module.

# drush info views_gallery
 Projekt        Release  Datum
 views_gallery  6.x-1.0  2009-Jul-24

Trying to download and enable results in...:

# drush dl views_gallery
Project views_gallery (6.x-1.0) downloaded to                        [success]
/var/www/test/sites/all/modules/.
# drush enable views_gallery
The following modules will be enabled: views_gallery
Do you really want to continue? (y/n): y
Views Gallery was enabled successfully.                              [ok]
The content type image already exists in this database.              [error]
Exiting. No import performed.                                        [error]
An error occurred at function : drush_pm_enable                      [error]

> This *is* the solution in Jeff's screencast, and there is no configuration to do, the module does it all.

Sorry, I have to disagree again. At least the version I have running seems to use other content types (if I remember correctly - I'll have to re-check this). Also, I'm getting a "Broken/missing handler" in the "Fields" configuration of the view. Hm, maybe I should set up a fresh sandbox... Or maybe there's a fresher release in the works...?

Greetings, -asb

Edit: Note to others looking for the mentioned fixes: Karen has just checked this into CVS, so it's not yet available in a release.

Hi Karen,

thank you for the new release and sorry for nagging about documentation, but I would simply get some basic information to get started without having to read and understand the code. That's not out of lazyness, but simply because I don't speak PHP and do not understand the CCK database model. A short README.txt would suffice, then we coding analphabets could jump in and start to write handbook pages.

Basic information needed to get started:

Just to explain this: After installing and enabling 6.x-1.2 I'm seeing the following elements in my testing-new-modules sandbox:

• ./node/add : Bild (an 'image' module based content type), CCK Gallery (type: cck_gallery), CCK Image (type: cck_image), Node Gallery (type: node_gallery_gallery), Gallery Image (type: node_gallery_image), ...
• /admin/settings/views_gallery : defaulting to "Views Gallery Gallery Type": "Amazon Example" (that's most probably not correct). On the views administration screen there's a view labeld 'gallery' which doesn't show up in the 'Views gallery' setting pull-down menu; the view reports an error in the field configuration: "Error: handler for node_data_field_gallery_image > field_gallery_image_fid doesn't exist!"; not sure if this view has been created by the 'views_gallery' module

(If "fresh checkout" in #6 referrs to a fresh Drupal installation: I haven't tried this yet since I'd like to use the module on existing sites. If the module requires a fresh Drupal installation, this would be a relevant requirement to be mentioned in a README.txt).

The only content type with an CCK imagefield is 'CCK Image', but I can't upload images into this field since it requires to select gallery, but there's no gallery available (and so on; I'm not troubleshooting here, simply describing what I'm seeing). So the basic information in a README.txt would be:

• What content types are being created when the module is being installed? How are they labeled?
• What content types have to be created manually by the user? How are they supposed to be labeled?
• What view(s) are being created when the module is being installed? How are they labeled?

I need this to distinguish the 'views_gallery' content types and views from other/older content types and views created by other modules (which possibly have not been removed when uninstalling the module, or which are needed for other purposes, like an prallelly installed 'image' module). Also it'd be nice to know what would have to be done to customize the module; e.g.: If I change the settings at ./admin/settings/views_gallery, will this affect the (pre-) configureed view, or will the view be modified accordingly?

Upgrading and compatibility information needed:

More interestingly: Can I install the module on a site where Jeff's screencast has been implemented? Should I try this, or will there be conflicts? Can 'views_gallery' fully take over the existing Node-based galleries with CCK and Views?

Also, if there are known or to-be-expected conflicts with other content types (like those from 'image' module) or other modules, I'd like to know about them so I can try to resolve them.

This basic information would help to understand what the module is supposed to do and what might be a bug (ar an incompatibility, or an unrelated site-specific problem). And it hopefully would prevent feature requests like this one ;)

Thanks & greetings, -asb

(fixing version and attaching a quick draft for a README.txt, based on the project page)

Quick draft for a README.txt (with missing parts to be added).