Use safer dom manipulation techniques when re-arranging the items in the authlist element. Speculative fix for #1930.

In reality, the javascript there is really messy and should be rewritten the MochiKit Way(tm).

I suspect Heinz hasn't deleted some old images, and has just untarred over the top of the codebase.

Link to the artefact viewing script instead of to view.php, which has been out of date for a while...

* Force password change: if checked, users are forced to change their password on next log in. This was mandatory before, now people uploading CSV files can choose.
* E-mail users about accounts: if checked, users are sent an e-mail about their new account. This was never an option before and never happened, now it is on by default.

We send a slightly different e-mail based on whether the user needs to change their password or not. This affects the Add User script a tiny bit.

Make it so display_name doesn't require the user to have staff and admin properties set. That was really pissing me off.

Don't show the 'user was suspended because' message if there is no reason for why the user has been suspended.

Make sure the group links open in a new window so people don't lose their changes when editing view access.

Put TBODYs on the table that holds the calendar inputs for the access list items. Fixes them not being displayed in IE7.

Also make sure the links to users when searching open in a new window, which prevents people losing their changes if they click on one after having added or removed a few items via javascript.

It's too confusing when they're down the bottom on a narrower screen width and so people don't see them added.

Also added a border between them to make it more obvious where the splits are.

This means session timeouts are ok on the view access screen.

In reality I should make it work for any amount of dimensions, but this will handle the vast majority of cases for now.

It's more than likely that nobody has uploaded anything yet.

Fix cleaning up external feeds that we don't need anymore, if someone has added an RSS blocktype and hasn't actually put a feed in it.

I suspect there are bad queries in there hoggin' all the interRAMs, but no time to look now through all the cronjobs!

Default users' activity preferences to 'email' for all non-admin related message types. I wonder how many complaints this will get...

The general idea is that users interact with a system more if they know what's going on. So if by default we tell them what's going on, they will be encouraged to visit the system. Hey, it works for just about every other social networking application. Users can still turn e-mail notifications off if they don't want them.

Increased the size of description text to something more readable. Made the special case rule for the t&c element more specific.

Reduced the size of the group create and edit description WYSIWYG textareas. This makes sure they stay within the left column.

I18n-ise the 'submit view for assessment' form. Added a note about how suckily it's generated. Fixes #1940.

Moved the detection of artefacts not existing when rendering blocktypes to outside the calls to render_instance.

This means all blocktypes instantly get the protection required if a bug elsewhere in the system means the artefacts they want don't exist. They can catch the ArtefactNotFoundExceptions themselves and do something more clever if they want to.

Prevent the image blocktype from treating a missing artefact as a failure condition. Blocktypes are not allowed to do this.

This fixes the problem of going to a view with an incorrectly deleted image in it, and not being able to see the view as a result.

Delete profile icons using the proper delete() method on the Artefact class. This ensures that blockinstances get told about the deletion.

Show the name of the current default theme on the 'site default' option in the dropdown for institution theme.