grok.Permission: grok ordering broken
Bug #188701 reported by
Christian Theune
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grok |
Fix Released
|
High
|
Martijn Faassen |
Bug Description
This is a problem that was introduced when switching to base classes for permissions:
grok's processing order seems to depend on the name of the object in the module's namespace. Therefore this construct will fail:
class Manage(
grok.
class Edit(grok.View):
grok.
When changing the name of the `Manage` class to `AManage` it will work.
Changed in grok: | |
assignee: | nobody → faassen |
milestone: | none → 1.0 |
To post a comment you must log in.
We fixed this issue a while ago, so closing it.