we all know that node_gallery is a great module to let users have their own gallery, especially on Social Networking sites. I'm looking for a way to integrate image-gallery content-type with other types like Blog, Stories, etc.

For the case on my site, every user can create their own unlimited numbers of gallery. But I'm looking for a way for them to have a "Blog" gallery for all pictures that they upload when creating a Blog content. This will have a standard gallery name (able to filter in Views).

Meaning, for every and ALL blogs they created, the images they uploaded will go to their own "Blog" gallery, and not creating another new one.

Comments

scroogie’s picture

How do you integrate the images in the blog content type? Is it a nodereference field, or directly an image type? In any case, the "Blog gallery" sounds more like a View than like a node.

sadist’s picture

After I posted this thread, I realized it's going to be more complicated than I thought.

It's a gallery node-type instead of Views, and every user will have their own. This gallery, is only meant for their blog, so it will contain all the images that they uploaded through Blog.

Is this going to be more complicated? An image-node type will have a reference to it's gallery itself (named Blog), and it must also be referenced to the blog.

Another alternative way to explain is, imagine having Imagefield in a blog node-type, and all images uploaded in it, will be Image-Gallery node, inside the user's own gallery called Blog.

scroogie’s picture

I meant how you include the images in the blog post, not the other way around. :)

sadist’s picture

By reference just like the relationship between gallery and image? At the time of adding or editing the Blog, there should be a field or form to upload images.

justintime’s picture

Status: Active » Closed (won't fix)

@sadist, I do understand what you're asking for, but it's just not feasible for this module to do that. You're basically talking about changing imagefield so that when a new imagefield is attached to a node of a certain content type, it links the same imagefield to a node titled "'s Blog". That's quite a ways outside the scope of this module on a few different levels.

Marking as won't fix.