Hello everybody,
my problem in short is this: I wanted to have a news headline on my first page (~featured article with a big picture) just like the one on the demo page with Steve Jobbs. Now, I successfully created such an article but without any picture! I just can't make it happen!
I go to the "Main Image" section when creating the article and try to upload an image - voilá, nothing happens. Or rather it begins to upload the image but finally only flickers and that's it, nothing happens.
Maybe this is related, maybe not but when I check the article//main image field settings -> /admin/content/node-type/article/display/basic I can see an error:
This content type has inactive fields. Inactive fields are not included in lists of available fields until their modules are enabled. (in red)
Thumbnail Image (field_thumbnail_image) is an inactive image field that uses a Image widget. (in green)
Again, maybe it's unrelated (and there is no unabled CCK image module) it's just I saw the descreption under the "Main Image" section when creating articles: "Appears at the top of detail pages and as a thumbnail on list pages". That's why I thought...
Any idea?
Comments
Comment #1
lorand commentedComment #2
lorand commentedComment #3
lorand commentedOkay, guys, I became frustrated enough to reinstall the whole thing.
(1) Now the "Steve Jobs feature" (Main Image) works, halleluja; :)
(2) The "inactive field" problem still persists. I.e. out of the box. :(
You win some, you lose some, eh...?
Comment #4
febbraro commentedOn the modules page, is your Imagefield module enabled (under CCK) also is the Image API module enabled?
Comment #5
myersca commentedI am having the same problem and both of those modules are enabled. It has happened with multiple clean installs, without install errors.
The field_main_image does appear on the field list.
Also in the "Article" view, there is the following error:
Error: handler for node_data_field_thumbnail_image > field_thumbnail_image_fid doesn't exist! under the "Fields" box when editing the view.
Comment #6
lorand commentedHi febbraro,
thank you for replying!
Yes, both are enabled. Also having the same problem as myersca.
Comment #7
lorand commentedComment #8
febbraro commentedHey everyone, thanks for being patient.
I think the problem has to do with CCK module upgrades without us exporting those types again. Attached is a zip file containing all of the CCK types required. If you unpack this in [drupal-home]/profiles/openpublish and overwrite the cck *.inc files, these should install correctly with no inactive fields.
Can someone give this a whirl and let me know if a fresh install with updated CCK types works for them? If all is good a new release is imminent.
Thanks.
Comment #9
febbraro commentedComment #10
myersca commentedThanks!
I can confirm that on a new install, these files *do* work and the missing fields do disappear.
On a current install:
I don't know what exactly got it to work on my current install, but I had to recreate the different content tables from a default install:
content_type_article
content_type_audio
content_type_blog
content_type_event
content_type_feeditem
content_type_op_image
content_type_package
content_type_resource
content_type_video
and I recreated content node field and instance tables, specifically:
content_node_field
content_node_field_instance
and I cleared the caches.
Of course that hosed my content and if anyone has a better idea, feel free to say here. :)
Most likely, if I only recreated the content tables above from a default install, cleared the cache, I probably could have kept my data and everything should have worked. It should not have been a problem because they mostly defined the fields and not really touched the data. I would start there first if you already have an install with some valuable content. I would start there. It was not a big loss for me to delete all of the content.
Thanks again, this is a really nice setup.
Comment #11
febbraro commentedOn a current installation you can simply go to Admin -> Content Management -> Content Types -> Import and for each content type select the name at corresponds to the file name copy the content inside each of those files (without the leading <?php ) into the import data field.
That will update the definition of each of your types.
These updates are in your code base waiting for the next build.