Is this scenario plausible (uploads applied to categories / groups) Is this scenario plausible (uploads applied to categories / groups)
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Is this scenario plausible (uploads applied to categories / groups)

Started by faidwen, September 21, 2010, 05:44:39 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

faidwen

I have searched the forums, and found quite a few somewhat similar queries, but nothing that specifically addresses this scenario.  If I have missed it in my searching, please accept my humblest of apologies.

The scenario is as follows:

- I have multiple categories based on specific teams (TEAM A, TEAM B, etc)
- I have a generic group (VIEW) that can view all of the categories and albums
- I wish to have specific groups (TEAM A CONTRIBUTORS) that can ONLY upload to specific categories (TEAM A)

The issue that I am stumbling upon is...  There does not seem to be a method to assign an album to VIEW & TEAM A CONTRIBUTORS.  I can make the album public, which means that the TEAM A CONTRIBUTORS and TEAM B CONTRIBUTORS can all upload to it.  But I would think that there would be a linked list somewhere where you could specifically assign groups to an album or vice versa.

Thanks in advance.

http://www.southlondonsoccer.com/coppermine
L: test
P: testme

Jeff Bailey

We can't support you with the powered by Coppermine footer turned off.
Additionally it looks like you used an auto installer, which we also don't support.

Your answer is in the documentation.
Thinking is the hardest work there is, which is probably the reason why so few engage in it. - Henry Ford

faidwen

Theme issue on that one, it has been corrected.

It has not been auto installed, it was installed via the package downloaded here.

Thank you for the quick reply :)

Jeff Bailey

Maybe someone else will help you but I am a firm believer in => http://documentation.coppermine-gallery.net/en/theme_copyright.htm#theme_copyright_unfair_use

If it wasn't an auto installer then your custom theme deliberately changed the footer. The footer can not be changed by mistake.
Thinking is the hardest work there is, which is probably the reason why so few engage in it. - Henry Ford

faidwen

Yes, I agree wholeheartedly, and the responsible parties have been severely chastised (IE: my  son).  It's hard to get support when you intentionally disregard the hard work and circumvent credit-where-credit is due!!!

Joe Carver

Try this related topic for a workaround solution.
http://forum.coppermine-gallery.net/index.php/topic,67072.0.html

And yes, Jeff was good to go out of his way to give you a break on the footer faux pas.

Normally requests that have uncredited links or no links just go unanswered.

ΑndrĂ©

What you're asking for is currently not possible in the way you want. You can only set per album if other people are allowed to upload to that album or not. You cannot specify which people/groups are allowed to contribute to your album or not.

The easiest solution would be to create upload accounts for each team.

Otherwise you have to modify core files. If you decide to use this solution, here is the theoretical approach what has to be done and changed:
1) The user/group needs permissions to upload to public albums.
2) The album must allow uploads from other people.
3) Now we have to check if the contributor is in the same group as the creator of that album. If so, he is allowed to upload. If not, don't list the album for upload.

We just need code modifications for point 3. All we do is to add an additional check if the user groups match. Shouldn't be that hard to code if you don't want to have non-personal accounts.

faidwen

Thank you gentlemen...

I think part of the issue where I thought it may have already been possible, is because of the ALBUM PERMISSIONS BY GROUP and the ASSIGNED ALBUMS tabs within USER and GROUPS areas respectively.

I will look into the code areas for what you are suggesting, and try and get my head around what is already there.

Thanks for looking into this.