Instead of attache to new node, attache to node that the text box is on

Howdy,

When this module was conceived, the project it was made for had a couple nodetypes to contain CCK imagefield images, like galleries.
And we wanted to use that images in other nodetypes, like articles.

So the upload feature was made to fulfill the need of creating new images not contained in galleries, but available to any other post of any nodetype.

But this case is very specific and we can redesign this module to be more relevant for use out of the box.

There could be a couple upload modes, including new nodes of a certain type, appending to an existing gallery node, or appending to current node.

Thanks,

Lourenzo Ferreira
http://chuva-inc.com
http://lourenzo.blog.br

Hello Lourenzo,

I agree with that0n3guy, appending to current node would be very nice to have !

Hi!

I was thinking about this issue, and got some ideas.

Because the initial idea was the user inserting content to be able to reuse all site's fields, uploading proccess normally would occur on nodes' forms through ImageField widgets.

Later the need of uploading content on via the popup from this module appeared, and I'm assuming we can improve this upload feature.

I've got the idea of adapting the upload proccess to suport both creating a new node or appending to the current node if applicable, since the imagefield assist is not exclusive to node forms.

In case of creating a node, the user could select a nodetype, defaulting to the type the module creates on install.
Other way is the content type of new nodes be selected in settings form.

What do you think? Have any better ideas or improvement to those?

Thanks,

Lourenzo Ferreira
http://lourenzo.blog.br

In case of creating a node, the user could select a nodetype, defaulting to the type the module creates on install.
Other way is the content type of new nodes be selected in settings form.

This kind of confused me. Are you saying that:

Option 1: We can select a content type that will append all images too (similar to the way the module works now)?

Option 2: We add an imagefield_field to a content type (story for example) and then every time we a story node and want to add images they will be attached to that spacific node?

If that is what your saying, that sounds pretty good to me :) .

For new images (not yet uploaded), the only option that is really meaningful to me is attaching to the current node being edited. I don't really think it's nice to have a content type created on install, since imagefield works on the inverse logic, which is NOT creating content types, but fields instead. It doesn't have to be so automatic, but there could be a setting of which node types would support adding new images (by IFA), and IFA could simply hide the imagefield (via nodeapi) widget so it can uses it internally only.

subscribing, waiting desperately for it.

It would be possible, but think of nodes without imagefields set, or think of blocks that even aren't nodes.

Perhaps this option could be shown if the subject is a node with a imagefield configured, in a quick menu after clicking 'Upload'.

I didn't mean using existing imagefields on content_types. That would be a bad choice, since you can't predict the reason for someone to add an imagefield. Perhaps it's a profile picture of something. You can potentially annoy users if IFA use an arbitrary imagefield.

What I meant is creating a multiple imagefield "on demand" inside the content_type. If IFA is called to insert a new image, it should smartly and transparently create the imagefield in the content_type, save it, and proceed to inserting it. That, of course, would be really difficult to implement in the current state of development, but and easy way would be pre-creating these imagefields on all content_types.

I support this method and the extinction of the former, which is, the IFA content-type. =)

This is a must. I would like to help, but unfortunately I can't do PHP.