[Zope-CMF] Re: [dev] delete members: small proposal

[Chris Withers]

Yuppie wrote:
>> When you do this, how will you handle ownership issues for the various 
>> objects owned by the user you're about to delete?
> 
> I hope someday someone will fix <http://collector.zope.org/CMF/25>, that 
> would make ownership of content items less important.

Well, you could always do that now. It's not a big change and would only require 
a couple of new tests ;-)

That said, ownership is ownership, It _should_ be correct regardless of it's 
importance.

> I can't see a general solution for the ownership issues, so I was going 
> to ignore that inside the deleteMember method. If you need to fix the 
> ownership of some objects, you have to do it separately.

Hmmm, don't agree, I think deleteMember should have parameters that specify what 
you'd like to have happen, and implement the various options, rather than 
ignoring the problem and hoping it'll go away...

>> How will you handle the situation when the user object you need to 
>> delete comes from:
>>
>> - an acl_users not within the portal
> 
> I see 2 cases:
> 
> 1.) There is no acl_users within the portal:
> If the User Manager has no permission to delete the member, deleteMember 
> will do nothing and return 0.

What's the User Manager?
What does 'return 0' do?

> 2.) There is a second acl_users outside the portal:
> This is not well supported in CMF. DeleteMember will do nothing if the 
> member is not in the first acl_users and return 0.

This sounds about right.

>> - another type of user folder, such as LDAPUserFolder
> 
> CMFLDAP has to handle that. CMFCore just works with normal acl_users.

Well, CMFCore currently works with most userfolders.
I'd like to see it stay that way... provided deleteMember uses the standard 
acl_users interfaces, there shouldn't be a problem...

cheers,

Chris