GitLab

We haven't been clearing out session files since I first chose to make us hash the session directory back in 2006. Talk about a timebomb...

The cron job uses `find' and `xargs' to do the removing. These tools are required on debian (as part of findutils), and are installed in /usr/bin. I haven't bothered with a configuration directive for specifying a path to them for now, but that might be necessary later.
(cherry picked from commit 335d66a7)

Make usernames unique over their lowercase values, and put validation in everywhere so two users can't do this again.

Usernames _are_ meant to be case insensitive in the system. But at no point where users could be created (except for XMLRPC users), was this actually being enforced. So eventually someone actually did this, which caused login for both users to break.

Now, all entry points for new users are checked to make sure users can't claim names whose lowercase value is the same as another user. And on postgres, we now have a unique index over LOWER(username). This isn't possible in MySQL, so MySQL users miss out (yet again).

fixing bug in upgrade where version wasn't bumped and plugins were trying to be installed unnecessarily

Moved part of the MySQL upgrade around, as per a report by Howard Miller that it fixes the 1.0 upgrade for him. The upgrade still works fine for me, so what harm can it do. Fixes #1928.

Force the installation of the 'fileimagevideo' blocktype category the correct way (using install_blocktype_categories()), so it doesn't fail if the category has already been created, as can happen if we are upgrading from 0.8.

The name is largely irrelevant as it's only the creator of the file.

Fixes to the upgrade process so that it works in MySQL, and produces roughly the same database compared with if it's installed from 1.0.

Fixes to the upgrade so that an upgrade from a pristine 0.9 postgres to 1.0 produces the same schema as installing from 1.0.

Remove the 'institution' column from the usr table (second time around, this time remove from install.xml too!). Remove the redundant (copied from Moodle) 'updateuserinfoonlogin' column from the institution table.

increases the version number

Signed-off-by: Andrew McMillan

Move account expiry from institution to site options; add theme, membership period to institution settings

Turns out I got the table_column call wrong also. Needs to, like with everything else in xmldb, fully respecify the column. Now the view migration works in MySQL

XMLDB and MySQL conspired to make this a horrible process.

Removed a couple of unneeded debugging lines from the view migration. Made sure to make the block column of the view_artefact table not null after the upgrade, and clear out all the null rows

 * Up the memory limit to 64M. The 16M limit was hit when migrating a 600 view Mahara, so I don't imagine 64M will be hit in the wild
 * Move the installation of the blockinstancecommit event to before the view migration. This is so that such events can be fired safely by blockinstances that are being committed
 * Install _all_ of the blocktypes when upgrading

Namely, when a block doesn't migrate properly.

Also reduced the size of resized images in views somewhat to work better on smaller screens.

The template itself is reasonably simple, the problems lie around the translation of certain template blocks to blocktypes - but these problems affect all templates.

Anyway, it now migrates reasonably well. The labels are only output if there's artefacts associated with them.

Also changed a couple of columns in view_artefact to be nullable while the migration is running. Tried this with XMLDB, it ate my face.

Added an upgrade path to move the images stored on the filesysetm into a new directory structure, and set config variables regarding image height and width.

Also removed a newline at the end of the file that was triggering header output.