Patch for "master" branch: https://reviews.mahara.org/7789
--
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
Public bug reported:
I've noticed that this test often fails on the step And I click the panel "A's
Page 01".
After watching the test run a few times, I see why:
22 pages are created, and when Portfolio is chosen from the menu, 10 of these
show up on the page, but they are in no particular
Public bug reported:
Mahara 16.10.4.
Used https://github.com/JakubOnderka/PHP-Parallel-Lint to lint the
Mahara codebase, found these issues:
Parse error:
** Also affects: mahara/15.04
Importance: Undecided
Status: New
** Changed in: mahara/15.04
Status: New => Fix Released
** Changed in: mahara/15.04
Importance: Undecided => High
** Summary changed:
- Account settings sub menus not shown in mobile in 16.10
+ Account settings
Patch submitted to reviews process https://reviews.mahara.org/#/c/7788/.
Pushing changes to Gerrit were rejected as it didn't like hash in the
description area - Bug #1693426: destroy mahara session when Single
Logout is initiated by IdP. As per documentation this is allowed but
had to take out
Patch for "master" branch: https://reviews.mahara.org/7788
--
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/17.04
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
** Changed in: mahara
Status: Fix Committed => Fix Released
** Changed in: mahara/16.04
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
** Changed in: mahara/16.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
** Changed in: mahara/16.10
Status: Fix Committed => Fix Released
** Changed in: mahara/16.04
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:
** Changed in: mahara/16.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
** Changed in: mahara/17.04
Status: Fix Committed => Fix Released
** Changed in: mahara/16.10
Status: Fix Committed => Fix Released
** Changed in: mahara/16.04
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mahara
** Changed in: mahara/17.04
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
** Changed in: mahara/16.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
** Changed in: mahara/16.04
Status: Fix Committed => Fix Released
** Changed in: mahara/16.10
Status: Fix Committed => Fix Released
** Changed in: mahara/17.04
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mahara
** Changed in: mahara/17.04
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
Public bug reported:
For our Single Sign-on implementation, we encountered this bug where
Mahara session is not destroyed for another SP initiated logouts.
For example, consider a scenario where two applications Mahara (SP1) and
Moodle (SP2) are setups as service providers and connected with
17 matches
Mail list logo