Ticket #4331 (closed Bug: fixed)
Opened 9 years ago
Method aliases must not be permitted as object ids
|Reported by:||optilude||Owned by:|
Currently, you can create an object with id 'sharing', 'edit', 'properties', etc. When this happens, the object becomes inaccessible, because the CMF 1.5 method aliases with the same name on the parent folder/portal object will take precedence. We need to disallow these names, probably by adding a test for parent method aliases to check_id. Need to test that this stops both the title -> id generation from generating these ids, and that a rename won't permit these names.