mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: mahara
     Importance: High
         Status: Confirmed

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1364615

Title:
  internalmedia blocks ending up with a blogpost as the connected
  artefact

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1364615/+subscriptions