Closed (fixed)
Project:
FeedAPI ImageGrabber
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
9 Apr 2009 at 07:04 UTC
Updated:
2 May 2009 at 01:00 UTC
Jump to comment: Most recent file
I've got a site where the feeds are a content type "Feed" and the nodes they make are called "feed item."
Following your directions, I added a CCK imagefield field to feed item and called it "image"
When I go to edit a feed to activate the grabber for it, the dropdown for choosing the Imagefield field is empty. It doesn't show my new field in it.
What's causing this and how do I fix it?
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | feedapi_imagegrabber_6.x-1.0-rc1.patch | 672 bytes | publicmind |
| #5 | feed_item_add_field.jpg | 35.7 KB | bflora |
| #3 | feed_item_fields.jpg | 34 KB | bflora |
| #3 | feed_edit_page.jpg | 29.19 KB | bflora |
Comments
Comment #1
publicmind commentedHi Brad,
Can you provide me some more details with the problem you are facing? Which Drupal core are you using? One more thing that you will have to refresh the feed page once you add a image field to it, so that the image-field array can be re-loaded.
Thanks,
Comment #2
publicmind commentedHey,
Does your feed add page shows the following line below the Imagegrabber settings:
"The module stores the image into this image field of the feed item.The content type for the feed-item of this feed is feed-item(blog/page/story)".
regards,
Comment #3
bflora commentedI'm using Drupal 6.6.
I've attached two screen captures to show what's happening.
In the first one, you see that I've added an imagefield field to my feed-item content type.
In the second, you see that when I try to add or edit a feed, that field isn't appearing in the dropdown for me to select it. Nothing's showing up there, so I can't tell FeedAPI Grabber to put images there.
As I understand it, that dropdown should be showing "field_image" as an option. Instead it shows no options. It's not "seeing" the imagefield I created on my feed_item type.
Comment #4
publicmind commentedHi brad.
First of all, the module is "FeedAPI Imagegrabber" and not "FeedAPI Grabber".
and Thanks, These screenshots really helped. The mistake you are making is the field_image you have made is of type "file", which must be of type "image". So, try changing the field to imagefield, currently its filefield that you are using
Hope that helps,
Comment #5
bflora commentedOk. then what is wrong with my imagefield setup? When I want to add an imagefield, "file" is the only type of field I can add. I've activated imagefield. Why isn't it showing me an "imagefield" option.
And please don't tell me to go ask the imagefield people, as that will take weeks to hear back from anyone. Your module has a dependency on imagefield, so debugging any imagefield problems that relate directly to your new module will be helpful here. Thanks.
Comment #6
bflora commentedAh, it looks like the imagefield beta release I'm using might work differently than the imagefield release you tested with.
http://drupal.org/node/403884
According to a comment in that thread, the new releases of Imagefield only have "file" as an option and then ask you what kind of widget you want to use, file or widget. "Image" is not an option in the beta release. You should look into this. I will downgrade to an older version and see if it works now.
Comment #7
publicmind commentedOh! Did you try to google that a bit, may be that issue is already addressed somewhere?
Anyway, all I can tell you is that its showing both options (file and image) on my server, and I have installed the following modules for Image display:
Try adding a field to default content types like blog/story, if that works then it might be a problem with your custom content type. For more, please try looking into the issue queue of those modules or try to install it according to the steps given in the readme file. However, I don't remember any special step I had to take installing this.
Comment #8
publicmind commentedthanks brad, I will look into it and will try to fix it asap...
regards
Comment #9
publicmind commentedHey brad,
I just checked it out, its working fine with alpha releases of Imagefield. Actually they went through an API change since their beta release, I will try to fix the issue asap,
Comment #10
bflora commentedCool. yes, it'd be great if this would work with the newest version. I'll not downgrade to the older version then just yet. Thanks.
Comment #11
asak commentedOhh... subscribing ;)
This is kinda critical...
Comment #12
asak commentedI doubt this is really this simple, but it seems that changing line 223 of the .module file fixes this...
From
if ($args['type']=='image') {To:
if ($args['type']=='filefield') {(Ha?)
Comment #13
publicmind commentedyes, but that would add non-imagefields too.
here is the patch for the module to make it work with rc1 releases of filefield and imagefield. (it too changes just a single line) It works for me as a charm, tell me if it works for you or not, so that I can integrate it in my next release.
regards,
Comment #14
asak commented+1 for the patch - works great!
+1,000,000 for this module!!
Comment #15
publicmind commentedThanks, so I think we can close the issue.
@Brad, any more problems brad, leave a comment.
Comment #16
equinox commentedI notice that today's download includes the patch above, but sadly this doesn't fix the problem for me. My selection box remains empty. I am on Drupal 6.10 with all modules updated as of today. Of course the first time I did this I added the imagefield to my FEED content type instead of my NEWS, which of course didn't work. But now I have my imagefield of type filefield using widget image FUpload and it is now attached to my News content type. When editing my Feed content type the CCK imagefield selection box remains empty. Any ideas?
*Going to try the other Widget types to see if Image FUpload isn't correct. I chose it thinking it was the one required because it was a required module for this feature.
Comment #17
equinox commentedChoosing type "Image" and not "Image FUpload" resolves this for me. Testing continues. :) thanks.
Comment #18
bflora commentedWorks for me now.