Package: collective.pfg.signup
collective.pfg.signupContentscollective.pfg.signupIntroductionUse CasesDestination groupDynamic Destination GroupRegistration Approval WorkflowPost approval actionsMembership management viewContributorsChangelog1.6.1 (2021-02-05)1.6 (2021-02-03)1.5 (2017-03-08)1.4 (2016-07-25)1.3 (2016-05-04)1.2 (2015-09-10)1.1 (2015-08-27)1.0 (2013-06-20)0.1 (2013-02-05)IntroductionFlexible member registration, membership workflow and membership management in Plone.Features:Customisable user registration forms (via PloneFormGen);different registration forms for certain areas of the site;user approval workflow and user management based on groups;collecting additional information about members.This plugin provides a PloneFormGen save adapter that uses the details from the
submitted form to add Plone members.It can be configured to:put the user in a predefined group, andallow members of a group to approve users before they are added.The destination group or the group of approvers can be predefined, orpolcies of groups based on naming conventions by using python expressionsUse CasesThere are 3 use cases for adding users:User is automatically created with the password supplied in the form.User is created, password is randomly generated, and a password reset email is sent.User is held within the adaptor, pending approval.Destination groupOnce someone is signed up, they are added to adestination group.
The id of the destination group is determined by thedestination group id templatein your signup adapter.If you enterMembersinto thedestination group id templatefield, all
users will be added to theMembersgroup.Dynamic Destination GroupYou can vary the group that a user gets added to by using variable substitution
in yourdestination group id templateTAL expression.For example, if you
- create a registration form
- with a selection box calledorganisation- with the valuesIBM,APPLE,GOOGLE,
- configure the adapterdestination group id templateto`Members_${organisation}`- Users will be added toMembers_APPLE,Members_IBM,Members_GOOGLEbased on the registration formThe substitutions need to correspond to fields on your registration form
and the groups need to existIf the group doesn’t exist the registrations will be held
for approval and an error email sent to the portal administrator.Registration Approval WorkflowTo hold registrations temporarily before the user accounts are added you can set aApproval Groupon your adapter. This specifies the policy on which group manages
users being added to another group.Approval Groupis a python expression returning a dict of`python:{manager_group:[group1, group2,...]}`Create a registration formSet adapterApproval Groupto`python:{'Administrators':['*']}`Upon registration the user is emailed to say their registration is pending approvaland email of the group is sent an email to notify that a registration needs to approvedif the group has no email, every memeber of group will be notifiedSomeone from the adminstrators group can login, view a list of waiting registrationsOnce approved they are able to be edited or deactivated by the managerNote if the approval group doesn’t exist then email will be sent to the portal administrator instead.Post approval actionsIf you want to store the information entered into a signup form,
or take any other actions based on this information,
you can configure an additional PFG save action adapter.
Instead of directly activating that on the form,
configure it as theapproved save action adapterin the signup adapter
and this adapter will be activated only once the user has finally been approved.
You can use this with a scriptable adapter for example to do scriptable actions
on user approval.Membership management viewThis plugin adds the@@user_search_viewbrowser view, which improves upon the
default PloneUsers and Groupssettings page for member management.User profile pages are filtered by theManage Group Templatefield.
Members have the fieldsAccess approved by,Access approved
date,Access last updated byandAccess last updated dateto have a
record of membership management actions.There areactivateanddeactivatebuttons to disable user for accessing
the site.ContributorsPretaweb, AuthorChangelog1.6.1 (2021-02-05)Use SemVer1.6 (2021-02-03)Fix bug with user not auto-created when user approve group is not set
[nngu6036]Fix deprecation errors related to plone.app.controlpanel and Products.CMFPlone.
[b4oshany]Add email domain verification option.
[ivanteoh]Display Login ID rather than User ID on search, profile view and profile edit view.
[JeffersonBledsoe]Fix users not being able to be deactivated if their login id is different to their user id.
[JeffersonBledsoe]1.5 (2017-03-08)Fix aaData contains unicode.
[ivanteoh]Default to ‘Administrators’ when the TAL expression miss out the approval group.
[ivanteoh]1.4 (2016-07-25)Use Plone 5 valid email regular expression.
[ivanteoh]1.3 (2016-05-04)Change ‘approval_group’ to accept a list of groups instead of one group in
string.
[ivanteoh]1.2 (2015-09-10)Remove unused JavaScript file.
[ivanteoh]1.1 (2015-08-27)User management
[ivanteoh]1.0 (2013-06-20)User sign up management
[davismr, ivanteoh, djay]0.1 (2013-02-05)Initial implementation
[Pretaweb]