Products.MightyCal.User.UserRegistry (version 1.11)		index
/home/zope/lib/python/Products/MightyCal/User/UserRegistry.py

UserRegistry Class.  Contains the Users defined for the MightyCal

 
Modules
            
Acquisition
Dumper
os
re
socket
sys

 
Classes
            
exceptions.Exception
UserException
AccessControl.User.UserFolder(AccessControl.User.BasicUserFolder)
UserRegistry

 
class UserException
      # Signal non-matching passwords in the "password" and "confirm" fields
 
  
__init__(self, value)
__str__(self)

 
class UserRegistry
      UserRegistry Class.  Holds all defined Users for a MightyCal
 
  
__init__(self)
Construct a new instance of UserRegistry
_addUser(self, userInfo, REQUEST=None)
_changeUser(self, userInfo, REQUEST=None)
_createInitialUser(self)
If there are no users or only one user in this user folder, populates from the 'inituser' file in INSTANCE_HOME. We have to do this even when there is already a user just in case the initial user ignored the setup messages. We don't do it for more than one user to avoid abuse of this mechanism. Called only by OFS.Application.initialize().
_doAddUser(self, userInfo, **kw)
Create a new user
_doChangeUser(self, userInfo, **kw)
addUser(self, username, password, roles=None, domains=None)
Simple interface for adding a user
createCocoonUser(self)
Create a user called 'cocoon', so that the Cocoon frontend will be able to call XMLRPC methods on the Zope backend.  This is just called once, during the setup of the MightyCal object.
getUserObject(self, userName)
Return the CalendarUser object identified by the 'userName' parameter
manage_users(self, submit=None, REQUEST=None, RESPONSE=None)
This method handles operations on users for the web based forms of the ZMI. Application code (code that is outside of the forms that implement the UI of a user folder) are encouraged to use manage_std_addUser
notifyApproval(self, username, eventTitle, eventDate, calendarId)
Set up a pending notification of event approval to be sent to the named user. The notifications don't actually get sent until sendNotifications() is called
notifyRejection(self, username, eventTitle, eventDate, calendarId, reason)
Send a notification of event rejection to the specified user
propagatePermissions(self)
Override of the inherited method from PermissionsPropagator... Because a UserFolder holds its objects in a PersistentMapping rather than as Folder subobjects, we have to use a specialized method for applying security policy to our User objects.
sendNotifications(self)
Send all pending email notifications of approved Events

 
Data
             ADD_USER_METHOD = 'addUserDialog'

CALENDAR = 'Calendar'

CALENDAR_REGISTRY = 'CalendarRegistry'

CALENDAR_USER = 'CalendarUser'

COCOON_USER = 'cocoon'

COCOON_USER_PASSWORD = 'cocoon'

CONFIRM = 'confirm'

DEPARTMENT = 'department'

DIALOG_BOX = 'dialogBox'

DOMAINS = 'domains'

DTML_DIR = 'dtml'

EMAIL = 'email'

EVENT_DATE = 'EventDate'

EVENT_TITLE = 'EventTitle'

EXISTING_USER = 'existingUser'

INFO = 0

LOCALHOST_BY_NAME = 'localhost'

LOCALHOST_BY_NUMBER = '127.0.0.1'

MAIL_HOST = 'MailHost'

MessageDialog = <HTML instance at 82c28f8>

NAME = 'name'

OWNER_PROPERTY = 'owner'

PACKAGE_NAME = 'User'

PASSWORD = 'password'

PHONE = 'phone'

ROLES = 'roles'

USERNAME = 'username'

USER_OBJECT = 'CalendarUser'

USER_POLICY = 'Policy for Users and related objects'

USER_REGISTRY = 'acl_users'

XMLRPC_ACCESS_ROLE = 'XMLRPC Access Role'

__file__ = '/home/zope/lib/python/Products/MightyCal/User/UserRegistry.pyc'

__name__ = 'Products.MightyCal.User.UserRegistry'

__version__ = '$Revision: 1.11 $'

permAddUser = 'Add CalendarUser'

permViewMgmtScreen = 'View management screens'