Thread

I’m just trying to get an idea for the best way to handle a potential problem I can see I might need to solve.

Imagine I have a site which has the classic situation of a number of events, each event can have 1 or 2 bands playing.  Popular bands might well come back several times

I’d put the events in one weblog, bands in another.  I’d put two ‘related’ fields in the events weblog to link to the bands for that evening.  Reverse related would enable me to list all the events a band has played in on that bands page.  That’s clear.
.
.
Now obviously we would want to have a picture gallery - and it would be nice to classify pictures by both event and band, so that if you looked at a past event page you could see thumbnails of the pics for that event AND if you looked at a band page you would see thumbnails related to that band.

I’d like to use the EE gallery module to handle the thumbnail generation and picture display, but as far as I can see in an image gallery I can only categorise pictures one way [in this case either by band OR by event]. 
.
.
Soooo what I’m wondering is how to get around this, given I’m not a PHP buff.

One possibility, I guess, is to set up two image galleries within the module, one for events events and one for bands.  However would I then have to upload a picture twice?  That does not seem to be very elegant.

Is there a neater way within EE?

Maybe the solspace tag module would work for you.

Rather than use the categories in the gallery, use a separate weblog just to display pictures. You can grab pictures from a gallery using gallery relationships, sure, but now you are going to assign your categories via the weblog on the publish/edit page. Then, you can build relationships to that picture weblog from the others. (It’s really “OK” to have a weblog having only a single custom field - which can be a gallery relationship field. But think of it - you can have other custom fields as well, which can act further similar to categories as descriptors or keywords to trigger conditional comparisons later on as well.)

Also, I’ve come to the conclusion that having several galleries simply to use for making gallery relationships is a better approach than using categories in a single gallery, at least if you are going to create gallery relationships from them. I never even use the gallery module for anything other than its batch and other tools anymore. But for those, and the ability to create gallery relationship fields, it is priceless!

Terry

I have a similar setup on my site. You probably won’t be able to read it, but an excellent example might be this page. On this page you’ll see most of my weblogs:
- The main weblog is called “Production”
- Then there’s a weblog for “News” (translation = “Nieuws”)
- One for “Articles” (translation = “Artikelen”)
- One for “Photos”; this one relates to both Production AND to Articles.

The weblogs News, Articles and Photos all have a relationship to the weblog “Production”. So whenever there’s a new event we have to write about, we add it to Articles/News with a relation to the corresponding production. For every photo we add we make a relation to the production AND to the article where the photo belongs to.

And on this page you’ll see that the main weblog Production is wrapped around reverse relationships to News, Articles and Photo’s.

I simplified things a bit in this post, I have a couple of more weblogs I use but you’ll get the idea…

Thanks for those replies - definitely food for thought.

I’m going to have to think about this more - especially as I’ll be letting end users loose on this, and want it to be as simple as possible 😊