Bug #354
Extra, "anonymous role" on staging
| Status: | Closed | Start date: | 26/09/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Enrique García | % Done: | 100% |
|
| Category: | - | Spent time: | 1.00 hour | |
| Target version: | - |
Description
Chiliproject usually has 1 "anonymous" role for users not logged in.
This morning I found two of those on the staging database - one of them with the correct permissions, and another one without permissions. Users couldn't do any of the tasks associated with anonymous access (for example reading a public wiki)
I suspect something (a plugin, a faulty initialization/clonage process) at some point creates the "extra" role.
We have to investigate what is creating this extra role and fix it.
In the meantime, a workaround consists on manually eliminating the anonymous role with no permissions from the database, using the database backend interface.
History
Updated by Enrique García 7 months ago
- % Done changed from 0 to 100
- Status changed from New to Closed
I could not find the cause of the problem, but have found a workaround: Since the spureus anonymous role is created only when cloning production into staging, I've made the clonning task automatically call another task that cleans it up (or does nothing if it doesn't exist).
Closing down this issue.