ImageField type not visible on the content type when creating/editing
bikingbadger - May 16, 2009 - 19:05
| Project: | ImageField |
| Version: | 6.x-3.0 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
1. CCK version: 6.x-2.2
2. imagefield version: 6.x-3.0
3. permissions for your tmp and files directory: drwxrwxr-x
4. download method (public or private files) ??
5. imagefield configuration: see attached
6. expected results: To see the image field created for the content type
7. the unexpected actual results: The field does not show up
8. Steps to reproduce the problem: Install module and add image to content type
| Attachment | Size |
|---|---|
| Example.jpg | 49.14 KB |
| ManageFields.jpg | 54.05 KB |

#1
Do you have the "Field access" module installed? It might be blocking access to fields. I can assure you that this problem does not exist on a fresh installation of Drupal, CCK, and ImageField, since thousands of sites are using the 3.0 version without this problem.
#2
Sorry I meant do you have the "Content Permissions" module installed (it comes with CCK)? It controls field-level access.
#3
The module is installed. I understand that it is something that I'm doing incorrectly so I'm not blaming the ImageField module but rather my lack of experience developing with Drupal. Should I disable this module and if so what will the effects be on others parts of the system.
UPDATE: I turned it off and it started to work. Can you explain this? How would I be able to have these working together?
#4
Content Permissions is a module that controls field-level access. The unfortunate thing about the module is that when it's enabled it automatically *denies access to ALL fields*. You have to visit admin/user/permissions and grant access to each field individually after enabling the module. However, I'd recommend leaving it off (and any other modules you don't absolutely need) because it's a rather taxing module that will slow down your site if enabled.
#5
I'm having the same problem. I just disabled Content Permissions, but the problem persists. Despite having an active ImageField module, there is no image Field Type available when creating new Content Types.
I'd offer more information, but at this point, I'm really not even sure what would be the relevant information to offer. It just seems like one of those things that should "just work" and it's "just not working."
No idea what to do.
#6
Oh, blargh. Never mind.
I'm working my way through the O'Reilly book and there must be some version changes at play. They have the configuration options appearing quite differently than what is actually happening on my screen. They have you needing to select "image" from the field type dropdown, as well as "image" from the widget dropdown. It appears that you actually have to select "File" from the field type dropdown.
My bad. Stupid non-dynamic printed book pages!
#7
I ran into the same problem following instructions in Chap. 7 of the O'Reilly book Using Drupal.
I just filed errata against the book for this problem using O'Reilly's handy errata reporting at http://tr.im/xb9m
#8
The same problem.
I've had imagefield working on previous sites, but I can't get it to work on a new site, even with a clean installation
The only steps i've taken are...
I've installed drupal 6.14
added cck 2.5, filefield 3.2 and imagefield 3.2 to the sites/all/modules folder
I've enabled only the modules content, filefield, and imagefield
When I navigate to content management - content types and try to add a field to say 'story', the only option in the drop-down menu called 'select a field type' is 'file'.
#9
Yep, select "File" as the type, and then "Image" as the widget. Unfortunately Using Drupal was written against an alpha(!) version of ImageField, since the official versions (3.0 and higher) were not out yet. So there are discrepancies between the book version and the way things are currently.
#10
Oh yes, nothing like a simple solution, even if it is a little embarrassing! Thanks for the quick response, it's really appreciated.
#11
#12
Automatically closed -- issue fixed for 2 weeks with no activity.