forum.coppermine-gallery.net
Support => cpg1.5.x Support => cpg1.5 permissions => Topic started by: smantscheff on November 05, 2010, 02:33:55 pm
-
On a fresh install I created a new group with permission to upload to their own album, but not to public albums.
This is the database entry for it:
group_id: 4
group_name: Agenturen
group_quota: 1024
has_admin_access: 0
can_rate_pictures: 0
can_send_ecards: 0
can_post_comments: 0
can_upload_pictures: 0
can_create_albums: 1
pub_upl_need_approval: 1
priv_upl_need_approval: 0
access_level: 3
As to be expected, can_create_albums is 1, but can_upload_pictures is 0, so that users cannot upload to their own albums.
How can I set permissions so that users of this group may upload to their own albums but not to anywhere else?
-
The database entries are a little bit misleading (historical reasons). Please post a screen shot of that group in your group manager. Basically you have to allow this group to have a personal gallery, but aren't allowed to upload to public albums. As far as I can judge this should be the case for your group. Maybe a bug crept in while working on that permissions lately.
Please describe what happens. Users can create albums... what happens then?
-
Attached are a groups manager screenshot and a group database entry screenshot.
A member of the group can successfully add an album.
When a member of this group tries to upload a picture, the album drop down list contains exactly one entry with their own album.
When trying to upload in their own album, this message appears (in debug mode):
Fehler
Du hast kein Recht, diese Operation auszuführen.
Datei: /srv/<dirname>/htdocs/db_input.php - Zeile: 511
-
Cannot confirm on my testbed. Which Coppermine version do you use? If it's cpg1.5.8, can you please perform an update with the latest svn revision (http://documentation.coppermine-gallery.net/en/dev_subversion.htm#dev_subversion_download)?
-
I don't get it. I tested it again, switched the user group write permission (can_upload_pictures) from true to false again, and now it works as it should. Very strange.
The version is 1.5.8, revision 7805.