Raphael Ritz wrote: > Hi, > > today I'm facing the situation where I want to support a Members folder > (rare these days) but this folder should be deeper down in the site > (very rare; for me this is the first time ever). > > Currently, CMF(Default - and Plone for that matter) does not support > this OOTB because CMFDefault's MembershipTool uses a simple getattr > call for the 'membersfolder_id' on the site object. > Changing this to use 'unrestrictedTraverse' instead resolves > the problem including the possibility to specify the path (or > relative content URL) to the folder in ZMI. > > It does break two tests, however, as the DummySite's > 'unrestrictedTraverse' used for testing isn't clever > enough to deal with relative paths/URLs correctly. > > Now my question: Is this something CMFDefault should support? > If so, I'm happy to file a ticket with a patch (and test; > I don't have repository access). > If not, I will simply keep on patching my local installation. > > Just thought I'll let you know. Opinions anyone? > > Raphael
We've needed this functionality recently too. +1 for both using a configurable path and moving the implementation to CMFCore. While we're on the subject I think we should change the defaults to match the common case of not having a members area. So change memberareaCreationFlag to False, and do not create the Member folder at all in the default profile. Laurence _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests