It's still not great, but at least it's no longer "a bug in the system". Instead reindexing says when it failed and suggests to check the error log.

More safety when errors occur early on, like when config sanity is being checked. Prevents ugly warnings and a fatal error if dataroot isn't defined.

It's an integer check, and it's useful for dates.

Applied it to the resume composites, thus fixing bug #1344.

Handle the case where we call ensure_record_exists with the same object as $where and $data. update_record was getting teh angry.

Make sure users are made members of groups they create. Also make sure admins are tutors in said groups, if they're controlled.

Pass staff/admin flags to the template so the dropdown to choose viewing submitted views etc. are available.

Also added some access checking for the other functions in this file.

Make the profile icon on the profile page link to the profileicon tab so people can upload new ones. Thanks to Manjula-Jayne

Format the whitespace in view/artefact feedback properly. No wonder it looked so wierd on myportfolio.

Change the URL of where the installation instructions are, they've moved to the new wiki. Part of a fix for #1738

This was caused by the tablerenderer calling get_string to get defaults, before the javascript that set the strings was output. Solved by putting the javascript that outputs the JS language strings before any including of other javascript files.

The resume composites were broken when editing a resume (although they were working in the views). Fixed.

Make sure we check for the correct langconfig.php, regardless of whether we're retrieving a plugin string or not.

Fixes a gazillion warnings to the logs when using language packs other than English.

Eduforge Bug 1716

Namely: the string saying how many results there are, and the string that says there are no artefacts to choose from.

Also removed styles for the old administer templates screen that I found along the way.

Those exceptions are safe to translate, other exceptions can't easily be translated without testing, as you have to make sure everywhere they should be used the translation infrastructure is working.

As it is, if the translation code throws an exception, everything will probably go to hell.

I was actually looking to fix a bug about it displaying the currently logged in user in search results, but there's a change on the forums branch that will allow this, and I don't want conflicts.