At the moment, we have some work arounds in place, and removing the
destructors could cause problems. We'd need to be careful when we tackle
that.
** Changed in: mahara
Milestone: 19.04.0 => None
--
You received this bug notification because you are a member of Mahara
Contributors, which is
** Changed in: mahara
Milestone: 18.10.0 => 19.04.0
--
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
** Changed in: mahara
Milestone: 18.04.0 => 18.10.0
--
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
** Changed in: mahara
Milestone: 17.10.0 => 18.04.0
--
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
** Changed in: mahara
Milestone: 17.04.0 => 17.10.0
--
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
** No longer affects: mahara/16.10
** No longer affects: mahara/16.04
** Changed in: mahara
Assignee: Aaron Wells (u-aaronw) => (unassigned)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions:
** Changed in: mahara/16.10
Milestone: 16.10.1 => 16.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
** Changed in: mahara/16.04
Milestone: 16.04.4 => 16.04.5
--
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
** Also affects: mahara/16.10
Importance: Undecided
Status: New
** Changed in: mahara/16.10
Milestone: None => 16.10.1
** Changed in: mahara
Milestone: 16.10.1 => 17.04.0
** Changed in: mahara/16.10
Status: New => Confirmed
** Changed in: mahara/16.10
Importance:
** Changed in: mahara
Milestone: 16.10.0 => 16.10.1
--
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
** Changed in: mahara/16.04
Milestone: 16.04.3 => 16.04.4
--
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
** Changed in: mahara/16.04
Milestone: 16.04.2 => 16.04.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
** Changed in: mahara/16.04
Milestone: 16.04.1 => 16.04.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
** Changed in: mahara/16.04
Milestone: 16.10.0 => 16.04.1
--
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
** No longer affects: mahara/15.04
** No longer affects: mahara/15.10
** Changed in: mahara/16.04
Milestone: 16.04.0 => 16.10.0
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all
** Changed in: mahara/15.04
Milestone: 15.04.5 => 15.04.6
** 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
I ran the Behat tests again, with the destructors changed to throw an
exception if there were uncommitted changes.
No problems at all. So, I think we should be fairly safe getting rid of
them.
However, rather than just deleting them, I'm first going to look into
whether there's a safe way to
The Behat test suite ran through successfully with no errors with the
destructors commented out.
Although, I guess what I should do, is run it with the destructors set
to throw an error if there is uncommitted changes.
--
You received this bug notification because you are a member of Mahara
Okay, for blog posts in particular, I've found the specific new code
that's causing it. I've filed a separate bug 1513716 to take care of
that.
With that known issue out of the way, this greater issue becomes Medium
priority because it's not known to cause any problems, it just has the
major
19 matches
Mail list logo
