Jens Vagelpohl wrote at 2008-10-11 09:21 +0200:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 11, 2008, at 08:16 , Dieter Maurer wrote:
Jens Vagelpohl wrote at 2008-10-8 14:57 +0200:
...
As far as the feature itself is concerned, I've never seen a
situation
where this is useful or
Jens Vagelpohl wrote at 2008-10-8 14:57 +0200:
...
As far as the feature itself is concerned, I've never seen a situation
where this is useful or needed.
As so often -- we need it :-)
Our MembershipTool instance is (together with the portal)
in a read only mounted storage
while the Members
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 11, 2008, at 08:16 , Dieter Maurer wrote:
Jens Vagelpohl wrote at 2008-10-8 14:57 +0200:
...
As far as the feature itself is concerned, I've never seen a
situation
where this is useful or needed.
As so often -- we need it :-)
Our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 8, 2008, at 13:36 , 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).
Previously Raphael Ritz wrote:
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
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
Wichert Akkerman wrote:
Previously Raphael Ritz wrote:
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'
Jens Vagelpohl wrote:
[..]
Please keep in mind the true nature of CMFDefault: It's a sample
application of the framework laid down in CMFCore. So IMHO _if_ this
kind of configurable members folder location feature is added, it
should be in CMFCore and thus available to CMFDefault.
Am 08.10.2008 um 14:57 schrieb Jens Vagelpohl:
Please keep in mind the true nature of CMFDefault: It's a sample
application of the framework laid down in CMFCore.
True but an eminently usable one.
So IMHO _if_ this
kind of configurable members folder location feature is added, it
should
