http://localhost/ticket/1115 <p> If you've got edit permission on an authzgroup, then you can change its name to be the same as another existing authzgroup. </p> <p> This causes some strange UI effects at worst, and probably causes worse problems somewhere else. </p> <p> Is there any reason why changing the names of existing authzgroups should be allowed? And if so, name collisions should presumably be guarded against in both the name-changing and creation functions </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1115 Trac 0.12.3 thejimmyg Wed, 20 Jul 2011 15:04:20 GMT http://localhost/ticket/1115#comment:1 http://localhost/ticket/1115#comment:1 <ul> <li><strong>milestone</strong> <em>ckan-v1.5</em> deleted </li> </ul> Ticket dread Fri, 16 Dec 2011 16:58:24 GMT http://localhost/ticket/1115#comment:2 http://localhost/ticket/1115#comment:2 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> </ul> <p> Authorization groups deprecated with the Group refactor <a class="closed ticket" href="http://localhost/ticket/1477" title="enhancement: [Super] Group refactor (closed: fixed)">#1477</a> </p> Ticket