Remove the title on filedownload blocks with more than one file in them. Correctly set the profile icon for profileinfo blocks. The general template now mostly migrates.

Make sure that when images are placed in views in 'listself' mode, they get put in filedownload blocks, which is more consistent for the upgrade. This makes the 'filelist' template migrate nicely.

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

It gets converted to a five column view (regardless of how many columns are actually used). The images are shown without their titles. All in all, this one migrates quite nicely, with the exception of images that are tall - the grid like effect is somewhat lost.

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

Move installing view column widths into its own function, so it can be called by the 0.8 - 0.9 migration.

handle_exception isn't really an API method for exception classes, so make it final in MaharaException.

The only other class using it was SQLException, this has been changed to rollback any existing transaction in the constructor.

This means that we can safely call db_begin() and db_commit() anywhere, and as long as the calls balance, the transaction will only be committed when the last one is committed.

If a rollback is asked for at any time, the entire transaction is rolled back.

Make sure that transactions use db_begin() and db_commit(), so that transaction level counting can apply.

This was a very annoying bug to find, it manifested itself as transactions that appeared to commit at some random point despite me not having asked for this. I'd blame DDL but it's not its fault that we made db_begin() and friends.

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.

Penny started this work but I'm taking up the rest of it, so there's some changes to how certain things work that I made while trying to understand the way the migration works.

Also commented everything.

Next work - test the PPAE migration, then on to the other templates.

Check for both the mysql and mysql5 db types when doing a mysql hack. Will be mysql5 only later, of course.

 * Make sure that the root user has their authinstance ID set correctly.
 * Make sure that the root user is forced to have ID 0

A couple of checks to make sure that having blocktype code running when blocktypes aren't installed doesn't kill the admin section completely.

Changed all requires.
Also removed not used json/renderartefact.php

Rather than (the only example was artefact) lib/artefact.php which is non standard

Add support to the artefact chooser for a 'search' tab that allows drilling through the artefacts that can be chosen.

It works in firefox fine, and works without javascript fine (therefore it works in ie6). Opera also works. Konqueror and IE7 do not work properly.

Add a two character prefix to each log line, that remains the same over the lifetime of the request. This makes it easy to distinguish lines between requests that happen at the same time.

allow public views setting now prevents adding and using public views

fixed the upgrade - I have just commented this out for now because I'm pretty sure that blocktypes install themselves separately, not as part of the artefacts

Added basic workings for the search, so that the search tab sort of works. It's not scalable yet though - table scan of artefact using ILIKE.

Use the key 'javascript' instead of 'js' everywhere, for consistency with the vast majority of stuff we already have doing things this way (render_self)

Build the form controls separately from the artefact chooser template itself, cleaning up all the artefactchooser templates quite a bit. Make sure that the message for the resumefield blocktype isn't stored as configdata also.

& updated call to it in artefact/blog

This uses the postgres SELECT FOR UPDATE syntax to ensure we don't have a race condition when inserting a record that previously didn't exist. The other database one is a bit more race condition-ey.

Moved contacts/* to user/ and contacts/groups/* to group/, as groundwork for the new interaction api.

Lots of url/path moving, so there might be some brokenness for a while. Test cases certainly broken.