Imagefield update fails to populate content type field with image option.
| Project: | ImageField |
| Version: | 6.x-3.2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
This one is already documented, kind of, but it needs to be verified. As it was, I was working through the book USING DRUPAL and the tutorial download provided with the book. I actually had finished this part in chapter 8 on a photo gallery, but then I upgraded some mods and this is what I found out. Working with imagefield 6.x-3.0-alpha1, the book is quite accurate. Upgrade to 6.x-3.2 and it breaks the book, specifically page 242 item #3. It shows under table 7-2 to select a field type 'image'. Except that with the new mod, image is not an option available. I'm a newbie and there can always be something I missed, but this is already documented so well I don't think that I can improve upon it. You can download the versions in question at the books support site at http://usingdrupal.com/source_code It is on the bottom left of the index page.

#1
Yes I've gotten reports of this one at least a dozen times. Instead of selecting "Image" as the field type, select "File". Then select "Image" as the widget type.
It's not a bug at all, it's just a change in the way ImageField works between alpha1 and the official releases of ImageField that were eventually released. I actually wrote that chapter, and I made the API change that caused the book to become inaccurate (note that I was not the maintainer of ImageField at the time I was writing the book though). It was a change that absolutely had to be made to stabilize our APIs and fix quite a few bugs.
So if you're following the book code, you'll select "Image", with all current releases you'll select "File". I'd HIGHLY recommend the current releases over the ones that the book was written against once you actually start building real sites.
#2
Thank you for such a quick and helpful response. I'll be pressing on.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.