Re: Re: confusion due to acquired allowed types

Previously Martin Aspeli wrote:
> Wichert Akkerman <wichert@...> writes:
> > what happens is that when building the list of addable types in
> > parent/child getLocallyAllowedTypes looks at the list of allowed types
> > in the parent folder. That folder allows all types, but our user is not
> > allowed to add anything so this returns an empty list. 
> > 
> > I'm not very familiar with that code, but it seems fixable by
> > refactoring it a bit so isConstructionAllowed for the fti is only called
> > in the folder where we want to add something instead of for the folder
> > where we are getting the type list from.
> 
> +1 - This is a bug as far as I can tell. Have you got a unit test for it?

I just added a (currently failing) test for this and added it to the tracker
(http://dev.plone.org/plone/ticket/5255 ).

Wichert.

-- 
Wichert Akkerman <[email protected]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642