Flickrfield

Also having this problem. Kinda serious if it displays the code instead of the photos.

it seems that replacing

l($img, 'node/'. $node->nid, array('title' => $title), NULL, NULL, TRUE, TRUE)

by

l($img, 'node/'. $node->nid, array('attributes' => array('title' => $title), 'absolute' => TRUE, 'html' => TRUE))

in the 'theme_flickrfield_photo' and 'theme_flickrfield_photoset' functions could work...
Don't ask me why: I just took this out from the 'theme_flickr_photo' function of the flickr.module

I hope this will help...

I don't know how it works. So I don't know either what should happen exactly.

At mines, it works fine when using it in a view (adding the flickrfield as a field), but displaying the node, it doesn't pop out. I would expect it to appear here to, like any other CCK field set to visible in the display property of the content type.
Thanks :)

I played with the module. It doesn't work right now if we just add a field without special setup. But if we change the size of the image to display (in the content type settings), then it works.
It looks like it doesn't choose a formatter...
strange...

OK, I've got it...

I believe it's more a CCK bug than a bug specific to the flickrfield.module

Indeed: there is no 'default' formatter proposed in the flickrfield_theme function (nor in the flickrfield_field_formatter_info nor in the theme_flickrfield_field_formatter function), but by default, when inserting a new field to a content type, its default formatter is set to 'default' although for example here, we can see that 'square' is selected...

A way to go around this limitation is to create a formatter attached to 'default'. It's not very clean but it functions...

Or a best way would be to force the selection of another formatter than 'default' when creating a new field in a content type. But I don't know how this can be achieved. If anybody would have a solution. it could be interesting...

The problem is that it is not a flickrfield specific issue.... If we rename the default size "default", that's all the flickr module that has to be changed, not only flickrfield.

And if we don't want to modify the whole flickr module, it's the CCK module that would need to be patched so that it behaves differently with "default". Or may we warn this issue to the CCK.module dvper team?