** Changed in: mahara/15.10
Status: Fix Committed => Fix Released
--
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
** No longer affects: mahara/16.04
** Changed in: mahara
Status: Fix Committed => Fix Released
--
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
** Changed in: mahara/16.04
Status: In Progress => Fix Committed
** Changed in: mahara/15.10
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription
** Changed in: mahara/15.10
Milestone: 15.10.2 => 15.10.3
--
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
I haven't been able to replicate the issue yet and thus can't really
test whether the patch works or not.
--
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 --
There's a patch that might solve this:
https://reviews.mahara.org/#/c/6021/
--
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
** Changed in: mahara/16.04
Status: Triaged => In Progress
** Changed in: mahara/16.04
Assignee: (unassigned) => Robert Lyon (robertl-9)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions:
** Changed in: mahara/15.10
Milestone: 15.10.1 => 15.10.2
--
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
Hm, that could be it. I think when you copy a page, in some cases it
continues to point to the original artefacts instead of giving you a
copy. (Specifically, some of the blog blocks can do this.) If that's the
case, then perhaps there's a bug in the institution page delete code
that fails to
Okay, since it's just a warning I'll mark this bug "Low" priority.
Cheers,
Aaron
** Changed in: mahara/15.10
Importance: Undecided => Low
** Changed in: mahara/16.04
Importance: Undecided => Low
--
You received this bug notification because you are a member of Mahara
Contributors, which
Hi Aaron,
We're upgrading a Mahara site from 1.10 to 15.10.
In 1.10, we are getting this:
Nov 10 12:25:28 TQIDEB001 mahara-site-acttqi: [Tue Nov 10 12:25:28 2015]
[error] [client 203.29.131.142] [DBG] 43 (blocktype/lib.php:692) Artefact not
found when rendering a block instance. There might
Hi Aaron,
It's a warning in the log files (in 1.10).
But, because we've got debugging on while upgrading (15.10), we just
noticed it now.
You can still edit the page.
Ghada
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Hi Ghada,
Do you have any instructions on how to replicate this error? I tried
putting an image in an image block and then deleting the image, but it
seems like that particular use case successfully unsets the block
instance so this error doesn't happen.
Cheers,
Aaron
** Also affects:
13 matches
Mail list logo
