Thread

I have a project on the horizon which will require that a site has a database of bands and that each band has a individual blog, gallery and events diary. How can I best incorporate these requirements?

The obvious solution would seem to be to create a section (blog) for bands and then create relationships between that and a blog and events section. However it would be ideal if there was a way to add admin users and restrict access to adding and editing content for a single band.

Confused! :!

However it would be ideal if there was a way to add admin users and restrict access to adding and editing content for a single band.

Confused! :!

You can easily create admin users with any kind of privileges you want, even excluding from posting in certain weblogs.
Check the docs for Member Groups.

Sure, I realise that you can assign weblogs to member groups but I’m not keen on the idea of creating a weblog for every single band (there are 60+ bands) . Sorry, I should have mentioend this in my initial post! 😊

Ideally I’d like to create a section for bands, a gallery for each band and a general events and blog section. There would be a relationship between bands (the parent) and events (the child) and a link of some kind between bands and the band gallery.

My dilemma is with regards to how to handle the band blogs. Because band members need to be able to post to their individual blogs without having access to other band blogs logic would suggest that I create a seperate blog for each band, thus allowing me to easily creat member groups with the relevant access privs. However this would mean creating over 60 blogs, 1 for each individual band, and all with identical preferences which seem overkill really.

I guess what I might need is some kind of hack, perhaps I could create a bespoke admin area for bands using the SAEF that allows them to add and edit blog entries and general band info.

Any thoughts would be greatly appreciated.

😊

My dilemma is with regards to how to handle the band blogs. Because band members need to be able to post to their individual blogs without having access to other band blogs logic would suggest that I create a seperate blog for each band, thus allowing me to easily creat member groups with the relevant access privs.

I’m sure other people will chime in, but for now I don’t really see how to avoid creating 60+ blogs. It may be a bear to set up, but it does give you the flexibility and control you need.

Possibly use each band name as a category name, and in the SAEF form, hard code the category_id for each band.

Now you’d need more coding to restrict access, etc. It might just be easier to create the weblogs.