to send an email to their friends and invite them to create an account
on the site. The feature is enabled or disabled in the site Settings.
(Operation/Settings.pm)
It is implemented as a new operation, Invite (Operation/Invite.pm,
Help/Invite.pm, i18n/English/Invite.pm), and the option is displayed
as an option on the user's account screen. (Operation/Shared.pm).
The form is templated, and lives in the Invite namespace. Once
the invitation is submitted, if the user's email address is not
already in WebGUI, an email is sent and a record is stored in
the userInvitations table.
When the friend gets the invitation, they are taken to the account
creation screen, which conveniently has their email address already
filled in. This required changes in the Auth modules (Auth.pm, Auth/*.pm),
and ProfileField.pm. The latter was so that profile fields can have
their values manually set. The former changes handle inserting the
email address, bypassing the anonymous registration check, and
updating the record in ther userInvitations table.
I refactored some code out of the AdminConsole for finding the url
back to the site and added it to Session/Url.pm. The method is
called getBackToSiteUrl.
Note: this fix was implemented by refactoring the _submenu method to use a properties hash for params and eliminate use of stow. If any problems crop up with managing users, I would start looking here. All of my testing indicates everything is working though.
- Shift ProfileField API so that new returns undef on invalid fields.
This makes it possible for Shortcut::www_saveUserPrefs to execute.
The class methods in ProfileField are now also actually class methods.
+ Also fix up other modules that created dummy ProfileFields so that
they don't need to do that anymore, because it's now invalid.
- Merge contradictory-looking code from Shortcut's view and www_view
into a reasonable compromise in view, and then have www_view call
$self->view in a manner similar to that of the default Asset::view.
+ The profile field overrides still don't work, because there's no
obvious mechanism for "transclude asset in context". This may
require some fiddling to get right...
- Perform RFE "js-confirmation-operation/user.pm".
- Perform RFE "js-confirmation-operation/group.pm".
- Perform RFE "locked-by-who".
(Displays in title and alt of img, but not in body text.)
