Explicitly commit artefact to avoid buggy destructor (Bug 1513716)
Since this blog post object wasn't committed after having its
description updated, it causes the destructor to try to save
the changes to the database, and that sometimes throws a fatal
error if PHP garbage-collects the global $db variable before it
calls this constructor.
behatnotneeded: Covered by existing "edit_journal.feature"
Change-Id: I5056ecce91b823b245cb5bd29f0676a35a6afd45
(cherry picked from commit 294fa9a4edc5580cdc7a1c3c0c021e2f4b562884)
Reviewed: https:/ /reviews. mahara. org/6163 /git.mahara. org/mahara/ mahara/ commit/ 875f1806be1e5a6 931bb863b78698d 67e1a96c24
Committed: https:/
Submitter: Robert Lyon (<email address hidden>)
Branch: 15.10_STABLE
commit 875f1806be1e5a6 931bb863b78698d 67e1a96c24
Author: Aaron Wells <email address hidden>
Date: Fri Nov 6 18:55:40 2015 +1300
Explicitly commit artefact to avoid buggy destructor (Bug 1513716)
Since this blog post object wasn't committed after having its
description updated, it causes the destructor to try to save
the changes to the database, and that sometimes throws a fatal
error if PHP garbage-collects the global $db variable before it
calls this constructor.
behatnotneeded: Covered by existing "edit_journal. feature"
Change-Id: I5056ecce91b823 b245cb5bd29f067 6a35a6afd45 cdc7a1c3c0c021e 2f4b562884)
(cherry picked from commit 294fa9a4edc5580