This album has been locked for editing This album has been locked for editing
 

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

This album has been locked for editing

Started by Visitor, September 02, 2011, 08:18:05 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Visitor

Well, I have had the album running for a while now, and today I made a new catogary, and a new album for it. The I used FTP to add old photos to the right place. Then used Batch to add them..

All worked just fine, approved them all, and all seams ok

However an old catogary/album now has "This album has been locked for editing" and I cannot find anything that need to be changed.

Also, while new uploads show the FTP photos ok, the album I selected to put them in shows empty..

Clicked everything, cant see anything that needs to be changed?

Αndré

QuoteThis album has been locked for editing
Do you get that as "regular" user or as admin?

Leonard Will

I have just upgraded to Coppermine 1.5.16 and I am now seeing "This album has been locked for editing" beside some of the album thumbnails when I view a group of albums while logged in as an administrator but with admin controls hidden. The message does not appear when I choose "Show admin controls" and it does not appear when I view the site logged out, as a guest. I can see all pictures and everything else appears normal.

Αndré

Please post a link to your gallery, the affected albums and the album properties of that albums and also check the permissions of the parent categories. That message usually appears if you (e.g. as regular user) created the album while you were able according to the category permissions, but that permissions don't apply anymore.

Leonard Will

Gallery is at
http://www.enfieldsociety.org.uk/photographs/

Two affected albums are "Baker Street and Willow Estate" and "Holly Walk", both in the category "Home > places"; there are several others, but not all.

Album properties are:

Permissions for this album
Album can be viewed by     Everybody (public album)
Password protect this album (Tick for yes)     [not ticked]
Visitors can upload files *     No
Visitors can post comments *     Yes   
Visitors can rate files *     No

The parent category "places" has

"Group(s) allowed to create albums in this category" followed by a box containing the group names:

Registered
Guests

There seems to be no way of removing these two group names from the box. The help instructions are ambiguous, as it is not clear whether this is a list of the group names allowed to create albums or just a list of all groups, in which those allowed to create albums should be highlighted. In any case, whether they are highlighted or not does not make any difference to the appearance of the "This album has been locked for editing" message.

Creation of albums is restricted to administrators anyway, and have never, as far as I can recall, been possible by users in other groups.

I hope this gives you enough information to tell what the problem is - let me know if you need more.

Αndré

Quote from: Leonard Will on September 05, 2011, 11:15:44 PM
a list of all groups, in which those allowed to create albums should be highlighted.
That applies.


Please try to enable admin controls and that message should go away.

Leonard Will

Thanks for clarifying the first point.

The message has never appeared when admin controls are shown. It still appears against some albums when I am logged in as administrator and admin controls are hidden. It does not appear when I am logged out and accessing the system as a guest.

Αndré

If you hide the admin controls, Coppermine treats you like a regular user (without any admin privileges). That's why this applies:
Quote from: Αndré on September 05, 2011, 07:39:49 PM
That message usually appears if you (e.g. as regular user) created the album while you were able according to the category permissions, but that permissions don't apply anymore.
as you created the album as admin with admin controls enabled.

Leonard Will

But then why does the message not appear when I log out and access the system as a user without any admin privileges?
Why has it only recently appeared, against only some albums? I created all the albums as admin with admin controls enabled.  How can I get rid of it?

Αndré

Quote from: Leonard Will on September 06, 2011, 11:30:14 AM
But then why does the message not appear when I log out and access the system as a user without any admin privileges?
Because that user has not created the album.


Quote from: Leonard Will on September 06, 2011, 11:30:14 AM
Why has it only recently appeared, against only some albums?
Depends on the parent category settings.


Quote from: Leonard Will on September 06, 2011, 11:30:14 AM
How can I get rid of it?
Enable "Allow users to edit their albums when in a locked category " in config.

Leonard Will

Can I change the ownership of an album?
How do I lock or unlock categories? I can't see any option for this in the edit categories dialogue.

Αndré

Quote from: Leonard Will on September 06, 2011, 11:48:45 AM
Can I change the ownership of an album?
Yes and no. Coppermine has no form/GUI to do that, but you can of course manipulate the database as you wish (just recommended if you really know what you're doing!).


Quote from: Leonard Will on September 06, 2011, 11:48:45 AM
How do I lock or unlock categories? I can't see any option for this in the edit categories dialogue.
It's the "Group(s) allowed to create albums in this category" box. You (un)lock a category by (de)selecting the user group(s).

Leonard Will

Thanks for your prompt help. I'm fairly confident with SQL so I changed the ownership of all the albums in the database (assuming from what you say that this would not have any adverse consequences), and that has fixed the problem. It looks as though this message, or the check that gives rise to it, must have been due to some change in Coppermine between my previous version 1.5.8 and the latest version, 1.5.16.