delete did not reorder the existing activities. This would allow duplicate
sequenceNumbers in the db.
The upgrade script will resequence and fix all activities in all workflows.
the assetSize in the db was set wrong. This happened when a File/Image
was added, and when it is committed. Editing the Asset would fix it, but
once it was committed, the files in the Storage area were not added.
List of Changes:
1) Removed setSize from File/Image.pm. It can inherit from File.
2) In Asset::File::processPropertiesFromFormPost, set _storageLocation to the Storage
object. Remove the call to setSize since it's done in ->update
3) In Asset::File::setSize, fetch the current storage object via getStorageLocation.
4) In Asset::File::update, move the call to update after the filesystem work. This
way changes in the size of the permissions file get accounted for.
5) In Asset::update, call setSize after all changes, regardless of whether or not
properties have changed.
6) In Asset::setSize, refactor out the size calculation and update $self's properties
cache so that long running scripts have the right size.
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.
but can be enabled in the CS. If the option is turned on, and metadata is
enabled on the site, then sets of template variables will be made available
to the Post Form template, the Thread view template, and the CS view template.
