Group Guests - could not be named to Anonymous Group Guests - could not be named to Anonymous
 

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

Group Guests - could not be named to Anonymous

Started by mcarter, June 25, 2006, 03:04:22 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

mcarter

I am running Coppermine Photo Gallery v1.4.5 (unbridged).

After a fresh install of CPG 1.4.5, when I click on the "Groups" button at the top of the administrator's console, I get to a Group Management page.  On that page, the "Guests" group is listed with a red circle containing a white 'X' next to it.  Parking the mouse cursor over that red circle, the following message pops up: "Reset to default name (Anonymous) - recommended!".  Following that recommendation, I click the red circle, and the text field containing the group name changes from "Guests" to "Anonymous".  I then click the "Apply modifications" button at the bottom of the screen.  However, when I click the "Groups" button at the top of the administrator's console again, I am right back where I started:  The group is named "Guests" again, and the same red circle and 'X' and warning message appear.

This problem was previously reported in another thread (http://forum.coppermine-gallery.net/index.php?topic=25294.0) about 6 months ago.
It was marked as "solved", but nobody indicated which version it was solved on or how it was solved.  When one user (TuXi) noted that the problem still exists in 1.4.3, an administrator reprimanded him for posting a comment on a "solved" case.

Since I don't administrate my web server (it's hosted by GoDaddy), I can't check whether the problem has been solved in the latest version of CPG (1.4.8).  No mention of a solution for this problem appeared in the release notes for CPG 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, or 1.4.8 .

Joachim Müller

It's safe to ignore this minor issue you report. You should upgrade though asap to the most recent version (currently cpg1.4.8)