internalmedia blocks ending up with a blogpost as the connected artefact

[Robert Lyon]

This is another issues with the internalmedia blcoktype. See https://bugs.launchpad.net/mahara/+bug/1364609

When looking at the data of a large site I found that some internalmedia block instances had configdata for artefactid pointing to a blogpost artefact.

I'm not sure why this is but it's clearly not correct as a blogpost artefact is not a valid artefacttype for an internalmedia block.

This needs to be sorted out as to why it is happening and how to update existing date to correct the problem.

On check of large myportfolio database 8 internalmedia blocks out of 11,200 had this problem.

[Robert Lyon (robertl-9)]

One can also end up with a textbox having a blog artefact as an attachment - I suspect same problem could be occurring for non internalmedia blocktypes.

[Robert Lyon (robertl-9)]

See https://mahara.org/interaction/forum/topic.php?id=6426 for more information

[Son Nguyen (ngson2000)]

All wrong artefacts in myportfolio.school were imported via leap2a in 2011.

The Leap2A import feature was first introduced in mahara 1.2 (2009)

[Son Nguyen (ngson2000)]

Yes, we should also check the compatibility of the blocktype and artefacttype

[Son Nguyen (ngson2000)]

It'd be hard to find which old code caused this issue, and it seems fixed in the newer version 1.3.0 (patches for attaching files in blogposts)

I would only provide the database update for removing these wrong artefacts from the internalmedia blocks

[Mahara Bot (dev-mahara)]

Patch for "master" branch: https://reviews.mahara.org/4412

[Aaron Wells (u-aaronw)]

As discussed on the gerrit patch, so we can't replicate the cause of this problem, and it's a rare problem even on our largest sites, I think that it's best to share the tool we've written to fix it (which is in the gerrit patch), but not upstream it into core.

So, having done that, I'm going to close this bug.