This appears to be an intermittent or at least platform-specific problem. But if you were going to try to replicate it, these would be the steps:
1. Create a blog post. 2. Save the blog post. 3. Open the blog post back up for editing. 4. Make a change to the blog post. 5. Save the blog post again. If you use xdebug or another debugging tool, you can see that on that second save attempt, at least one ArtefactTypeBlogPost object will get its destructor called while $this->dirty is true, causing a database commit to happen during the destructor call. -- 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/1513716 Title: Intermittent error "Call to a member function StartTrans() on a non- object" when saving a blog post in 15.04 Status in Mahara: New Bug description: See https://mahara.org/interaction/forum/topic.php?id=7397 Also https://bugs.launchpad.net/mahara/+bug/1513710 The Embedded Image code ( https://reviews.mahara.org/#/c/5128/ ) adds a line to blog/post.php that does "set()" on an artefact without subsequently calling "commit()". This causes the (buggy) artefact destructor method to try to save the object to the database when the script ends, and that can cause an intermittent fatal error if $db got garbage collected before the artefact destructor was called. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1513716/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp