Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This is a one-way relationship to signify "attachments".

Read it on import, and while I was there, fixed the broken blog post
attachment importing.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Previously, they were being exported as portfolio:artefactnull, which is
hardly desirable.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This looks in the artefactid and artefactids fields only (which we know
are either a lone artefact ID, or a list of them, based on the field
name). This is somewhat of a limitation if blocks are storing artefact
IDs elsewhere, but it's not insurmountable.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This might have misled Penny:
http://wiki.cetis.ac.uk/2009-03/LEAP2A_relationships#relation



I have e-mailed the list asking whether it should be renamed to
'related'.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Why exactly is this trying to catch an exception anyway??

This is documented at
http://wiki.mahara.org/Developer_Area/Import//Export/LEAP_Extensions#ownerformat

This is legal, I'd previously thought otherwise.

Moodle outcomes integration: view submission/release to/from mnet hosts; hidden view access keys; export of additional artefacts with views

Removed the old system for this and implemented one that is similar to how it's being done for HTML export.

We're not exporting as xhtml any more - that work would unfortunately conflict with future work we have planned.

Now there's a new method, get_content_type, which elements should define to say what type they should be. The default implementation of get_content is now applicable in many more cases. All escaping and cleaning is done in the template, where it should be.

The system still supports exporting content with type=xhtml - we're just not going to use it.

This allows them to inform code on the outside about what's going on. This is used by the export UI.

This makes sense, as people may have data in them and they will still want to get at that data even if their administrator disables the plugin.
(cherry picked from commit 61a608972d8a86daec2919a439533af826114021)

It now works the way it worked for import. If the file exists, it has to implement the class. If the plugin doesn't want to implement it, it doesn't provide the file.