#14 — Anyone can unlock a locked conversation
by
Marshall Mayer
—
last modified
Jan 07, 2009 11:35 AM
| State | Resolved |
|---|---|
| Version: | |
| Area | Functionality |
| Issue type | Bug |
| Severity | Low |
| Submitted by | Marshall Mayer |
| Submitted on | May 08, 2006 |
| Responsible |
—
|
| Target release: |
—
|
Anyone that is logged in, even at the member level. Since you can't actually lock a conversation with that permission, I assume you also want to restrict the locking of topics to only certain permissions, not all permissions.
Added by
Marshall Mayer
on
May 11, 2006 07:17 PM
As a corollary to this, any regular member that is logged in can make active a pending conversation, whether they initiated it or now. This should be limited only to the member that initiated the conversation (as edits are no longer possible after the conversation is made active) and others with more permissions (owners/managers).
Added by
Edward Muller
on
May 12, 2006 04:05 AM
I don't see this with svn trunk revision 23313. Normal members can't unlock a conversation, they don't get the plone bar with the different actions on them.
Added by
(anonymous)
on
May 12, 2006 01:02 PM
Odd again, as when I reported this i was using revision 23313 from yesterday. I might just reinstall and update via svn again.
Added by
Marshall Mayer
on
May 19, 2006 10:39 PM
Someone should resolve this issue. A clean install works fine.
Added by
Jarn
on
May 24, 2006 10:22 PM
Until we have unit tests for workflow there is no way of actually knowing what works and what doesn't.
Issue state:
open
→
resolved
No responses can be added.
If you can, please log in before submitting a reaction.
