May be this question (in one form or another) has been asked before but I couldn't find an answer. It boils down again to image handling in Drupal. Here is the situation:
1) I have a picture node type build using CCK+Imagefield+Imagecache. My users can upload pictures ONLY this way (no free-standing image uploads).
2) I have a node type with a text field for writing stories. Let's call it a blog.
3) I want my users to be able to insert some pictures of their choice in the blog as inline images.
I know that at least three modules exist to support similar functionality: IMCE, Image Assist and Image Browser. The problem is that they all give you the option to browse the file system, which I don't find user-friendly. My users should not be required to know how Drupal's files are structured internally.
Some of them can actually work with Drupal's Image module but because of it's limitations I prefer to use the new "standard" combination: CCK+Imagefield+Imagecache. None of these modules seem to support Imagefield. For similar reasons I want to stay away from Image Upload and other similar modules.
So my question is: has anyone figured out a way of having Imagefield integrated with some image-browsing solution? Ideally an user should be able to browse only through the Imagefield-nodes that he/she created (using a view to restrict the browsing scope would be perfect).
Thanks!
Comments
AFAIK
As far I know you'd have to code or sponsor your own browser, IMO should be based on Views. And note that directly linking to the file in the filesystem is not as manageable as referring to entries in the database (e.g. fid).
And IMO this functionality would be much easier with Image module, perhaps with ImageAssist, as image nodes can be classified, not only by user but taxonomy, date etc, many other advantages.
I'm in the process of building a handbook section comparing the different ways to handle images, and this page has a section on "the case for images as nodes".
Of course this paradigm could be followed using Imagefield, but as there isn't currently a standard way to create a one-image-per-node using anything but Image module, there aren't all the support modules that have emerged for Image.
Edit - here's the issue in Imagefield's queue: http://drupal.org/node/119539 and perhaps some progress possible here via Inline API (although it doesn't help with the browsing part) http://drupal.org/node/80170#comment-1124808
So I guess the answer to my
So I guess the answer to my question is "No, there is no way to do that with the existing set of modules" ;-)
That's right. So why not use
That's right. So why not use Image if it actually enables you to do what you want to do? It's so mainstream there's no danger of your data being orphaned down the road. . .