Mark Phillips wrote:
> I installed membrane 1.1b3 and remember 1.1b1 on a new plone 3.1.5.1. I
> want to use member_approval_workflow for all members, and I have a
> remember product patterned after the remember-example. It all works, but
> I have a "best practices" question.
> 
> What workflow should I associate with the Member object type? The
> default comes up member_auto-workflow. Does it matter?

if i understand correctly, you don't want to use the Member type at all, you 
want all users to get an instance of your custom type.  is this correct?

if it is, then you're right that the workflow associated w/ the Member type 
isn't really very important.  you can use the remember configlet to specify 
what the default member type should be, so that your custom type will be used. 
  if you really want to protect yourself from someone nefariously creating a 
Member object, you can change the set of allowed types in MemberDataContainer 
so that Member isn't allowed.

> Should I remove this object type from portal_types?

that's another option, although there are less drastic ways to prevent Member 
objects from being instantiated.

> My fear is that somehow a setting will be changed and someone could join
> the site as a Member type instead of going through the remember based
> workflow.

adding member objects is essentially no different than adding any other piece 
of Plone content.  as such you can use any of the regular Plone mechanisms 
(tweaking add permissions, restricting allowed types in the types tool, 
removing the type from the site altogether, etc) to ensure that people aren't 
creating objects that you don't want them to create.

-r