Administrator cannot see albums once assigned to other group Administrator cannot see albums once assigned to other group
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Administrator cannot see albums once assigned to other group

Started by Francis Fung, April 21, 2004, 07:02:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Francis Fung

Hi,

  Here is my plan, I would like to have the Administrator(s) to create/manage ALL the albums.  And each album can permit multiple groups to see (read only).  for example.

 Groups : Administrator
              Group-A
              Group-B

  Albums : photoA (protected, allows Group-A and Administrator only)
                photoB (protected, allows Group-B and Administrator only)
                photoC (Everybody)

However, the following is what I got :

 for photoA: Administrator created and assign User Group as Group-A (one Group is allowed?)
       once the administrator logged out, he/she cannot see/edit the album again!  If you logon as Group-A member, you have only Read acces, can't change anything.  This lead me created something and wouldn't be able to make changes.  What's wrong with my setting?


My questions are,
1) how can I assign an album to multiple groups?
2) Isn't the Administrator always have control of everything?
3) What's the purpose of the dropdown list with checkbox in User Group when editing the User?  Can I assign a user to multiple groups?

Thanks for helping me in advance.

Francis

Casper

Hi,

This is a known bug with version 1.2.  
Go into config, and change the setting 'show private icon to unlogged user' to YES'.

Now you (admin) can see and edit all albums.  The multi group membership does not work correctly in this version, but is fixed in version 1.3, which is near the end of it's beta testing stage.
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here