Kevin Worth wrote:
> Hi-
> 
> I'm trying to move up from a CMFMember based site to a remember site.  
> I'm having issues with the migration.  I have a feeling it is either in 
> my MIGRATION_MAP for my custom member types or the way I am handling the 
> new remember-based members.
> 
> I regenerated my member types (faculty and staff) using ArchGenXML 1.5.2 
> by changing the stereotype for member to remember.  I then replaced the 
> existing faculty.py and staff.py with the newly generated files.  Should 
> the original faculty.py and staff.py be somewhere?

yes, i'd recommend creating your new, remember-based classes in a different 
module, alongside the original CMFMember-based classes.  things can get a bit 
confusing when you change the class out from under existing objects in the 
ZODB.  you should still have the CMFMember product present in your Products 
directory, as well.

once the migration is successful, remember provides a 'remove_cmfmember' 
external method you can use.  this will clear out the CMFMember remnants that 
are left in your site.  once this is complete, then you can safely remove the 
CMFMember code from your Products directory, as well as the CMFMember-based 
classes that are now obsolete.

-r