It's the tablerenderer responder script. The plan is to ditch the tablerenderer and thus remove this later.

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.

Only remove the loading message if we know it's not going to be removed by an updateOnLoad callback later. This might have to be rolled back later if it causes problems with loading messages hanging around, but I haven't seen any yet.

Made the pagination constant for blog posts per page exist in only the ArtefactTypeBlog class, so make sure we only use that now.

Corrected another mistake I made with renaming the view= parameter to id= when the URL wasn't actually to view/view.php

Made attaching and detaching files add a record in the artefact_parent_cache linking the entire blog to the attachment. This means that attachments can be shown in views instantly.

If the artefact is a profile icon in the artefact chooser, add that info to it so that people can tell the difference between the profile icon and images they have uploaded

Fix the path to the profile image in the profileicon blocktye. It doesn't need a view id and it should be 'profileiconbyid', not 'profileicon'

Profileinfo blocktype, first go. Allows inputting some free text as well, and you can choose what profile icon to put in.

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.

Added another smarty plugin - this one to allow the path blocktype:blocktypename:template.tpl for blocktypes to have their own smarty templates.

Remove the 'multiple allowed' from the email address language string, given it's used in places other than the profile now.

Add a spinner to the loading message, since I seem to be staring at the loading screen more often...

Better handling when the user is logged out and they try a json request. Ajax login is lying around somewhere, must integrate that some time.

Put a count of the number of blocktypes in each category on the category tabs. Hide the ones that have not blocktypes in them

Add a hover title to all clickable titles in a view telling the user that they can click for more information and to place feedback.

Copy/paste complete wtf man. Fix the limit/offset problem with artefact pagination properly this time.

Make sure that users can't put a wierd offset in, causing pagination wierdness. Good reason to use page= rather than offset= I spose.

Renamed the 'view' parameter for view/view.php to be 'id'. 'view' will continue to work for a while.

view/blocks.php uses id, and id is used for other objects in the system, so it doesn't make much sense for this one to remain this way.

* In the non javascript version, make sure that request variables are not passed through, which can result in the newly chosen form artefact chooser starting on the wrong page
* In the javascript version, close the old form when opening a new one.

Also, added a 'loading' spinner/message to be displayed while the configuration form is being retrieved.

Added customised templates for the artefact chooser for blog and file blocktypes (a.k.a. all of them).

Call the new artefactchooser_element method to establish the data required to render the pagination. This means less data has to be passed to the script.

Also format the json_reply call a bit better.

Changed the artefactchooser-element template to be a safe default, now that the template can be customised by blocktypes if they choose.

 * Parameters are taken as a hash now - eight or nine function parameters is a whorepile. The parameters are sourced from the new artefactchooser_element api method for blocktypes
 * Because of this, much less data has to be passed through as 'extradata', so removed a bunch of that
 * Removed 'offsetname' configuration, not required anymore.
 * Added a hook to allow blocktypes to affect the sort order for artefacts in the chooser, and a hook to allow them to configure data before it goes to the chosen smarty template for displaying each element in the chooser.

Removed the 'offsetname' configuration parameter. The artefactchooser element will only work if it's the only thing on the page anyway.

Allow configuration of the template used to show results in the artefact chooser also. This allows files to show results formatted differently to blogposts, for example.

It must be implemented to return the artefactchooser form element for the blocktype. This is so the pagination json script can also retrieve this data.

Implemented the method in the System blocktype class as a final method that does nothing. System blocktypes don't deal with artefacts.