[Mahara-contributors] [Bug 1494152] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "15.04_STABLE" branch: https://reviews.mahara.org/5254

-- 
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/1494152

Title:
  Fatal error upgrading from 1.4 or earlier to 1.10 or later, with
  objectionable content reports

Status in Mahara:
  Invalid
Status in Mahara 1.10 series:
  In Progress
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  Invalid

Bug description:
  In Mahara 1.10, when we added objectionable item reporting to the
  forums, we migrated all the old objectionable item view_access records
  into the new "objectionable" table. Part of this upgrade took
  view_access.ctime and used it for the "reportdate" column in the
  objectionable table, because view_access.ctime is supposed to be not
  null.

  But, if you upgraded from Mahara 1.4 or earlier, view_access.ctime is
  NULL (see https://bugs.launchpad.net/bugs/1494128 ). So, this causes
  the upgrade to crash.

  To replicate:

  1. Install Mahara 1.4
  2. Create a page
  3. Go to the page and use the "Report objectionable" button on it.
  4. Upgrade to Mahara 1.10

  Expected result: Successful upgrade
  Actual result: Fatal error.

  [WAR] bb (lib/dml.php:1046) Failed to get a recordset: postgres7 error: [-1: 
ERROR:  null value in column "reportedtime" violates not-null constraint] in 
adodb_throw(INSERT INTO "objectionable" ("objecttype", "objectid", 
"reportedby", "report") VALUES (?, ?, ?, ?), Array)
  [WAR] bb (lib/dml.php:1046) Command was: INSERT INTO "objectionable" 
("objecttype", "objectid", "reportedby", "report") VALUES (?, ?, ?, ?) and 
values was (view,6,0,)
  Call stack (most recent first):
* insert_record("objectionable", object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/db/upgrade.php:3383
* xmldb_core_upgrade("2011061015") at 
/home/aaronw/www/mahara/htdocs/lib/upgrade.php:359
* upgrade_core(object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/mahara.php:253
* upgrade_mahara(array(size 14)) at 
/home/aaronw/www/mahara/htdocs/admin/cli/upgrade.php:50

  A nonrecoverable error occurred. This probably means you have
  encountered a bug in the system(1.10_STABLE)aaronw@vega

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494152/+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

[Mahara-contributors] [Bug 1494133] Re: Fatal error upgrading 1.3->15.04 or 1.4->15.04

2015-09-10 Thread Aaron Wells 
** Changed in: mahara/15.10
 Assignee: (unassigned) => Aaron Wells (u-aaronw)

** Changed in: mahara/15.10
   Status: New => In Progress

-- 
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/1494133

Title:
  Fatal error upgrading 1.3->15.04 or 1.4->15.04

Status in Mahara:
  In Progress
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  In Progress

Bug description:
  To replicate:

  1. Clean install of Mahara 1.3 to 1.4
  2. Upgrade to Mahara 15.04 (via CLI; I haven't tested via the web upgraded)

  Expected result: Successful upgrade
  Actual result: Crashes with this fatal error:

  PHP Fatal error:  Uncaught exception 'SQLException' with message 'Failed to 
get a recordset: postgres8 error: [-18: ERROR:  relation "institution_config" 
does not exist
  LINE 1: SELECT field, value FROM "institution_config" WHERE "institu...
   ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
  Command was: SELECT field, value FROM "institution_config" WHERE 
"institution" = ? ORDER BY field  and values was (mahara)' in 
mahara/htdocs/lib/dml.php:480
  Stack trace:
  #0 mahara/htdocs/lib/dml.php(429): get_recordset_sql('SELECT field, v...', 
Array)
  #1 mahara/htdocs/lib/dml.php(393): get_recordset_select('institution_con...', 
'"institution" =...', Array, 'field', 'field, value', '', '')
  #2 mahara/htdocs/lib/dml.php(719): get_recordset('institution_con...', 
'institution', 'mahara', 'field', 'field, value')
  #3 mahara/htdocs/lib/institution.php(277): get_records_menu('instit in 
/home/aaronw/www/mahara/htdocs/lib/dml.php on line 480

  Works fine when upgrading from 1.1, 1.2, or 1.5. So it's probably
  caused by some discrepancy between the 1.3 & 1.4 upgrade vs clean
  install.

  I noticed the same problem in a 1.4 -> 15.10dev upgrade. But,
  strangely, not in a 1.3 -> 15.10dev upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494133/+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

[Mahara-contributors] [Bug 1494152] [NEW] Fatal error upgrading from 1.4 or earlier to 1.10 or later, with objectionable content reports

2015-09-10 Thread Aaron Wells 
Public bug reported:

In Mahara 1.10, when we added objectionable item reporting to the
forums, we migrated all the old objectionable item view_access records
into the new "objectionable" table. Part of this upgrade took
view_access.ctime and used it for the "reportdate" column in the
objectionable table, because view_access.ctime is supposed to be not
null.

But, if you upgraded from Mahara 1.4 or earlier, view_access.ctime is
NULL (see https://bugs.launchpad.net/bugs/1494128 ). So, this causes the
upgrade to crash.

To replicate:

1. Install Mahara 1.4
2. Create a page
3. Go to the page and use the "Report objectionable" button on it.
4. Upgrade to Mahara 1.10

Expected result: Successful upgrade
Actual result: Fatal error.

[WAR] bb (lib/dml.php:1046) Failed to get a recordset: postgres7 error: [-1: 
ERROR:  null value in column "reportedtime" violates not-null constraint] in 
adodb_throw(INSERT INTO "objectionable" ("objecttype", "objectid", 
"reportedby", "report") VALUES (?, ?, ?, ?), Array)
[WAR] bb (lib/dml.php:1046) Command was: INSERT INTO "objectionable" 
("objecttype", "objectid", "reportedby", "report") VALUES (?, ?, ?, ?) and 
values was (view,6,0,)
Call stack (most recent first):
  * insert_record("objectionable", object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/db/upgrade.php:3383
  * xmldb_core_upgrade("2011061015") at 
/home/aaronw/www/mahara/htdocs/lib/upgrade.php:359
  * upgrade_core(object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/mahara.php:253
  * upgrade_mahara(array(size 14)) at 
/home/aaronw/www/mahara/htdocs/admin/cli/upgrade.php:50

A nonrecoverable error occurred. This probably means you have
encountered a bug in the system(1.10_STABLE)aaronw@vega

** Affects: mahara
 Importance: Medium
 Assignee: Aaron Wells (u-aaronw)
 Status: Invalid

** Affects: mahara/1.10
 Importance: Medium
 Assignee: Aaron Wells (u-aaronw)
 Status: In Progress

** Affects: mahara/15.04
 Importance: Medium
 Assignee: Aaron Wells (u-aaronw)
 Status: In Progress

** Affects: mahara/15.10
 Importance: Medium
 Assignee: Aaron Wells (u-aaronw)
 Status: Invalid

** Also affects: mahara/15.10
   Importance: Undecided
   Status: New

** Also affects: mahara/1.10
   Importance: Undecided
   Status: New

** Also affects: mahara/15.04
   Importance: Undecided
   Status: New

** Changed in: mahara/1.10
Milestone: None => 1.10.7

** Changed in: mahara/15.04
Milestone: None => 15.04.4

** Changed in: mahara/15.10
Milestone: None => 15.10.0

** Changed in: mahara/1.10
   Status: New => Confirmed

** Changed in: mahara/15.04
   Status: New => In Progress

** Changed in: mahara/1.10
   Status: Confirmed => In Progress

** Changed in: mahara/15.10
   Status: New => In Progress

** Changed in: mahara/1.10
   Importance: Undecided => Medium

** Changed in: mahara/15.04
   Importance: Undecided => Medium

** Changed in: mahara/15.10
   Importance: Undecided => Medium

** Changed in: mahara/1.10
 Assignee: (unassigned) => Aaron Wells (u-aaronw)

** Changed in: mahara/15.04
 Assignee: (unassigned) => Aaron Wells (u-aaronw)

** Changed in: mahara/15.10
 Assignee: (unassigned) => Aaron Wells (u-aaronw)

** Changed in: mahara/15.10
   Status: In Progress => Fix Released

** Changed in: mahara/15.10
   Status: Fix Released => Invalid

-- 
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/1494152

Title:
  Fatal error upgrading from 1.4 or earlier to 1.10 or later, with
  objectionable content reports

Status in Mahara:
  Invalid
Status in Mahara 1.10 series:
  In Progress
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  Invalid

Bug description:
  In Mahara 1.10, when we added objectionable item reporting to the
  forums, we migrated all the old objectionable item view_access records
  into the new "objectionable" table. Part of this upgrade took
  view_access.ctime and used it for the "reportdate" column in the
  objectionable table, because view_access.ctime is supposed to be not
  null.

  But, if you upgraded from Mahara 1.4 or earlier, view_access.ctime is
  NULL (see https://bugs.launchpad.net/bugs/1494128 ). So, this causes
  the upgrade to crash.

  To replicate:

  1. Install Mahara 1.4
  2. Create a page
  3. Go to the page and use the "Report objectionable" button on it.
  4. Upgrade to Mahara 1.10

  Expected result: Successful upgrade
  Actual result: Fatal error.

  [WAR] bb (lib/dml.php:1046) Failed to get a recordset: postgres7 error: [-1: 
ERROR:  null value in column "reportedtime" violates not-null constraint] in 
adodb_throw(INSERT INTO "objectionable" ("objecttype", "objectid", 
"reportedby",

[Mahara-contributors] [Bug 1494152] Re: Fatal error upgrading from 1.4 or earlier to 1.10 or later, with objectionable content reports

2015-09-10 Thread Aaron Wells 
It appears this was already fixed in 15.10 as part of one of the commits
for Bug 1450680. But it wasn't backported to 15.04 and 1.10.

-- 
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/1494152

Title:
  Fatal error upgrading from 1.4 or earlier to 1.10 or later, with
  objectionable content reports

Status in Mahara:
  Invalid
Status in Mahara 1.10 series:
  In Progress
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  Invalid

Bug description:
  In Mahara 1.10, when we added objectionable item reporting to the
  forums, we migrated all the old objectionable item view_access records
  into the new "objectionable" table. Part of this upgrade took
  view_access.ctime and used it for the "reportdate" column in the
  objectionable table, because view_access.ctime is supposed to be not
  null.

  But, if you upgraded from Mahara 1.4 or earlier, view_access.ctime is
  NULL (see https://bugs.launchpad.net/bugs/1494128 ). So, this causes
  the upgrade to crash.

  To replicate:

  1. Install Mahara 1.4
  2. Create a page
  3. Go to the page and use the "Report objectionable" button on it.
  4. Upgrade to Mahara 1.10

  Expected result: Successful upgrade
  Actual result: Fatal error.

  [WAR] bb (lib/dml.php:1046) Failed to get a recordset: postgres7 error: [-1: 
ERROR:  null value in column "reportedtime" violates not-null constraint] in 
adodb_throw(INSERT INTO "objectionable" ("objecttype", "objectid", 
"reportedby", "report") VALUES (?, ?, ?, ?), Array)
  [WAR] bb (lib/dml.php:1046) Command was: INSERT INTO "objectionable" 
("objecttype", "objectid", "reportedby", "report") VALUES (?, ?, ?, ?) and 
values was (view,6,0,)
  Call stack (most recent first):
* insert_record("objectionable", object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/db/upgrade.php:3383
* xmldb_core_upgrade("2011061015") at 
/home/aaronw/www/mahara/htdocs/lib/upgrade.php:359
* upgrade_core(object(stdClass)) at 
/home/aaronw/www/mahara/htdocs/lib/mahara.php:253
* upgrade_mahara(array(size 14)) at 
/home/aaronw/www/mahara/htdocs/admin/cli/upgrade.php:50

  A nonrecoverable error occurred. This probably means you have
  encountered a bug in the system(1.10_STABLE)aaronw@vega

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494152/+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

[Mahara-contributors] [Bug 1494133] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "15.04_STABLE" branch: https://reviews.mahara.org/5253

-- 
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/1494133

Title:
  Fatal error upgrading 1.3->15.04 or 1.4->15.04

Status in Mahara:
  New
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  New

Bug description:
  To replicate:

  1. Clean install of Mahara 1.3 to 1.4
  2. Upgrade to Mahara 15.04 (via CLI; I haven't tested via the web upgraded)

  Expected result: Successful upgrade
  Actual result: Crashes with this fatal error:

  PHP Fatal error:  Uncaught exception 'SQLException' with message 'Failed to 
get a recordset: postgres8 error: [-18: ERROR:  relation "institution_config" 
does not exist
  LINE 1: SELECT field, value FROM "institution_config" WHERE "institu...
   ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
  Command was: SELECT field, value FROM "institution_config" WHERE 
"institution" = ? ORDER BY field  and values was (mahara)' in 
mahara/htdocs/lib/dml.php:480
  Stack trace:
  #0 mahara/htdocs/lib/dml.php(429): get_recordset_sql('SELECT field, v...', 
Array)
  #1 mahara/htdocs/lib/dml.php(393): get_recordset_select('institution_con...', 
'"institution" =...', Array, 'field', 'field, value', '', '')
  #2 mahara/htdocs/lib/dml.php(719): get_recordset('institution_con...', 
'institution', 'mahara', 'field', 'field, value')
  #3 mahara/htdocs/lib/institution.php(277): get_records_menu('instit in 
/home/aaronw/www/mahara/htdocs/lib/dml.php on line 480

  Works fine when upgrading from 1.1, 1.2, or 1.5. So it's probably
  caused by some discrepancy between the 1.3 & 1.4 upgrade vs clean
  install.

  I noticed the same problem in a 1.4 -> 15.10dev upgrade. But,
  strangely, not in a 1.3 -> 15.10dev upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494133/+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

[Mahara-contributors] [Bug 1489245] Re: Two-way list boxes (eg. in Site staff) have no button labels

2015-09-10 Thread Jono Mingard 
** Changed in: mahara
   Status: Confirmed => In Progress

** Changed in: mahara
 Assignee: (unassigned) => Jono Mingard (mingard)

-- 
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/1489245

Title:
  Two-way list boxes (eg. in Site staff) have no button labels

Status in Mahara:
  In Progress

Bug description:
  For adding and removing users from the staff or administrators list of
  an institution (eg. in Administration -> Site staff), there are two
  list boxes with buttons to move users from one to the other. However,
  the buttons to move users in these list boxes don't have labels, which
  makes it unusable by screen reader users. Descriptive hidden text
  needs to be added to these buttons.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1489245/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5260

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1489245] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5258

-- 
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/1489245

Title:
  Two-way list boxes (eg. in Site staff) have no button labels

Status in Mahara:
  In Progress

Bug description:
  For adding and removing users from the staff or administrators list of
  an institution (eg. in Administration -> Site staff), there are two
  list boxes with buttons to move users from one to the other. However,
  the buttons to move users in these list boxes don't have labels, which
  makes it unusable by screen reader users. Descriptive hidden text
  needs to be added to these buttons.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1489245/+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

[Mahara-contributors] [Bug 1265089] Re: Dual listbox (in Admin) is not easily accessible to screen readers

2015-09-10 Thread Jono Mingard 
** Description changed:

+ *** Superseded and fixed in Bug #1489245
+ 
  In pages such as /admin/users/staff.php and /admin/users/admins.php, staff or 
administrators are chosen by selecting items in one list then clicking a button 
to transfer them to another list. However, the buttons do not have a 
descriptive value so it's hard for screen reader users to figure out how this 
works.
  The "<" and ">" buttons should be given values which describe what they do 
(eg. "Move to administrators") and a note should be added in the user manual 
which explains how to select and move items using the keyboard (including 
selecting multiple items, etc.)
  
  Affects latest master (using Orca 3.10.1)

** No longer affects: mahara

-- 
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/1265089

Title:
  Dual listbox (in Admin) is not easily accessible to screen readers

Status in Mahara user manual:
  Fix Released

Bug description:
  *** Superseded and fixed in Bug #1489245

  In pages such as /admin/users/staff.php and /admin/users/admins.php, staff or 
administrators are chosen by selecting items in one list then clicking a button 
to transfer them to another list. However, the buttons do not have a 
descriptive value so it's hard for screen reader users to figure out how this 
works.
  The "<" and ">" buttons should be given values which describe what they do 
(eg. "Move to administrators") and a note should be added in the user manual 
which explains how to select and move items using the keyboard (including 
selecting multiple items, etc.)

  Affects latest master (using Orca 3.10.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara-manual/+bug/1265089/+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

[Mahara-contributors] [Bug 1487464] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5161
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/4eec36102eadf8da684806afe5600e79e28e7737
Submitter: Son Nguyen (son.ngu...@catalyst.net.nz)
Branch:master

commit 4eec36102eadf8da684806afe5600e79e28e7737
Author: Kevin Rickis 
Date:   Mon Aug 24 09:50:47 2015 +1200

Bug 1487464: SAML creating new email artefact on login

Problem is the dealing with the email artefact type happens after the check
for is_singular(), which 'email' artefact type is not.

behatnotneeded

Change-Id: I4d1ffbb2fb89cc705bf3e2e6211f22e24ca55b26
Signed-off-by: Robert Lyon 

-- 
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/1487464

Title:
  SAML Update user details on login option creating new email artefact
  on every login

Status in Mahara:
  In Progress

Bug description:
  Mahara version: 15.04.1

  Issue: When a user logs in via SAML and the configuration option is
  set to update the user's details then a new email artefact is created
  every time.

  I think I have traced the problem

  saml/lib.php line #234 calls set_profile_field($user->id, 'email',
  $email);

  lib/user.php lines #511-516 are a try{} in which  $email =
  artefact_instance_from_type('email', $userid); is called.

  This fails with the message "This artefact type is not a 'singular'
  artefact type" and so a new email artefact is created.

  It will always fail because artefact/internal/lib.php lines #705-708
  returns false for is_singular()

  class ArtefactTypeEmail extends ArtefactTypeProfileField {
  public static function is_singular() {
  return false;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1487464/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5263

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5262

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5261

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1492102] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5219
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/0dde0f033dae82389313ea5403bfcb6e859a4553
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master

commit 0dde0f033dae82389313ea5403bfcb6e859a4553
Author: Jono Mingard 
Date:   Fri Sep 4 16:55:29 2015 +1200

Improve file browser "move" accessibility (Bug #1492102)

- Moving files and folders with the keyboard now works properly
- Icons now include accessible text descriptions

behatnotneeded

Change-Id: I982ea29bbc45e307db4874cba860e36b538eeb5b

-- 
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/1492102

Title:
  Moving files with the keyboard no longer works

Status in Mahara:
  Fix Committed

Bug description:
  With the new Bootstrap themes, users are no longer able to move files and 
folders in the file browser using the keyboard. The desired functionality is
  - Press Enter on the file icon, which will open a list of possible folders to 
move the file to
  - Select a folder and press Enter to move the file

  However, currently the file "move" icon has no accessible text
  describing it, and although opening the list of folders works,
  clicking on them does nothing.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1492102/+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

[Mahara-contributors] [Bug 1492102] Re: Moving files with the keyboard no longer works

2015-09-10 Thread Robert Lyon 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1492102

Title:
  Moving files with the keyboard no longer works

Status in Mahara:
  Fix Committed

Bug description:
  With the new Bootstrap themes, users are no longer able to move files and 
folders in the file browser using the keyboard. The desired functionality is
  - Press Enter on the file icon, which will open a list of possible folders to 
move the file to
  - Select a folder and press Enter to move the file

  However, currently the file "move" icon has no accessible text
  describing it, and although opening the list of folders works,
  clicking on them does nothing.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1492102/+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

[Mahara-contributors] [Bug 1489243] Re: Incorrect labels in user name filters (Admin -> User search)

2015-09-10 Thread Jono Mingard 
** Changed in: mahara
   Status: Confirmed => In Progress

** Changed in: mahara
 Assignee: (unassigned) => Jono Mingard (mingard)

-- 
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/1489243

Title:
  Incorrect labels in user name filters (Admin -> User search)

Status in Mahara:
  In Progress

Bug description:
  On the User search page it is possible to filter users by the first
  letter of their first or last name. However, these links have the
  aria-labelledby attribute set to the label of the group, so screen
  readers only read out "First name" or "Last name" instead of the
  actual letter. This could probably be fixed just by changing the
  attribute to aria-describedby.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1489243/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5256

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5268

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1492103] Re: Numbers in pagination are read twice by screen readers

2015-09-10 Thread Robert Lyon 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1492103

Title:
  Numbers in pagination are read twice by screen readers

Status in Mahara:
  Fix Committed

Bug description:
  When navigating the paginator in places like "Portfolio", screen
  readers read out each page number twice: when focused on "1" they read
  "11", etc. Presumably there is hidden text somewhere in the element
  that is causing this.

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1492103/+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

[Mahara-contributors] [Bug 1494565] Re: Web services auth uses wrong lang string in auth list

2015-09-10 Thread Robert Lyon 
The 2nd 'description' text is used here -

Go to Administration -> Extensions ->Webservices

Expand the 'Manage service groups' expander

Click on any of the links in the 'Functions' column

And you will be taken to a page explaining the function


** Changed in: mahara
   Status: Confirmed => In Progress

-- 
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/1494565

Title:
  Web services auth uses wrong lang string in auth list

Status in Mahara:
  In Progress
Status in Mahara 15.04 series:
  Confirmed

Bug description:
  Mahara 15.04 and 15.10

  When you are on /admin/users/institutions.php and edit an institution,
  you an choose "Web services" from the list of authentication methods.
  The description only reads "Description" instead of the actual
  description "Web services-only users authenticated against Mahara's
  database".

  I tracked it down to the following (in Mahara 15.10):
  The "description" string on line 16 of 
/auth/webservice/lang/en.utf8/auth.webservice.php is correct. However, the auth 
list uses string "description" from line 153 from the section "wsdoc" instead. 

  When I comment the wsdoc "description" out, the proper description
  shows up in the authlist. So changing the string ID for the wsdoc to
  "wsdocdescription" should all that is needed. Unfortunately, I
  couldn't identify where I could change the string in the code and thus
  couldn't change it myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494565/+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

[Mahara-contributors] [Bug 1494565] Re: Web services auth uses wrong lang string in auth list

2015-09-10 Thread Kristina Hoeppner 
** Changed in: mahara
 Assignee: (unassigned) => Robert Lyon (robertl-9)

** Also affects: mahara/1.10
   Importance: Undecided
   Status: New

** No longer affects: mahara/1.10

** Also affects: mahara/15.04
   Importance: Undecided
   Status: New

** Changed in: mahara/15.04
   Status: New => Confirmed

** Changed in: mahara/15.04
   Importance: Undecided => Medium

** Changed in: mahara/15.04
Milestone: None => 15.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 before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1494565

Title:
  Web services auth uses wrong lang string in auth list

Status in Mahara:
  Confirmed
Status in Mahara 15.04 series:
  Confirmed

Bug description:
  Mahara 15.04 and 15.10

  When you are on /admin/users/institutions.php and edit an institution,
  you an choose "Web services" from the list of authentication methods.
  The description only reads "Description" instead of the actual
  description "Web services-only users authenticated against Mahara's
  database".

  I tracked it down to the following (in Mahara 15.10):
  The "description" string on line 16 of 
/auth/webservice/lang/en.utf8/auth.webservice.php is correct. However, the auth 
list uses string "description" from line 153 from the section "wsdoc" instead. 

  When I comment the wsdoc "description" out, the proper description
  shows up in the authlist. So changing the string ID for the wsdoc to
  "wsdocdescription" should all that is needed. Unfortunately, I
  couldn't identify where I could change the string in the code and thus
  couldn't change it myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494565/+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

[Mahara-contributors] [Bug 1487464] Re: SAML Update user details on login option creating new email artefact on every login

2015-09-10 Thread Kristina Hoeppner 
** Changed in: mahara
   Status: In Progress => Fix Committed

** Also affects: mahara/1.9
   Importance: Undecided
   Status: New

** Also affects: mahara/1.10
   Importance: Undecided
   Status: New

** Also affects: mahara/15.04
   Importance: Undecided
   Status: New

** Changed in: mahara/1.10
   Status: New => Confirmed

** Changed in: mahara/1.9
   Status: New => Confirmed

** Changed in: mahara/15.04
   Status: New => Confirmed

** Changed in: mahara/1.10
   Importance: Undecided => High

** Changed in: mahara/1.9
   Importance: Undecided => High

** Changed in: mahara/15.04
   Importance: Undecided => High

** Changed in: mahara/1.10
Milestone: None => 15.04.4

** Changed in: mahara/1.9
Milestone: None => 1.9.9

** Changed in: mahara/1.10
Milestone: 15.04.4 => 1.10.7

** Changed in: mahara/15.04
Milestone: None => 15.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 before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1487464

Title:
  SAML Update user details on login option creating new email artefact
  on every login

Status in Mahara:
  Fix Committed
Status in Mahara 1.10 series:
  Confirmed
Status in Mahara 1.9 series:
  Confirmed
Status in Mahara 15.04 series:
  Confirmed

Bug description:
  Mahara version: 15.04.1

  Issue: When a user logs in via SAML and the configuration option is
  set to update the user's details then a new email artefact is created
  every time.

  I think I have traced the problem

  saml/lib.php line #234 calls set_profile_field($user->id, 'email',
  $email);

  lib/user.php lines #511-516 are a try{} in which  $email =
  artefact_instance_from_type('email', $userid); is called.

  This fails with the message "This artefact type is not a 'singular'
  artefact type" and so a new email artefact is created.

  It will always fail because artefact/internal/lib.php lines #705-708
  returns false for is_singular()

  class ArtefactTypeEmail extends ArtefactTypeProfileField {
  public static function is_singular() {
  return false;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1487464/+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

[Mahara-contributors] [Bug 1486699] Re: Username character limit preventing login via SAML

2015-09-10 Thread Kristina Hoeppner 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1486699

Title:
  Username character limit preventing login via SAML

Status in Mahara:
  Fix Committed
Status in Mahara 1.10 series:
  Confirmed
Status in Mahara 1.9 series:
  Confirmed
Status in Mahara 15.04 series:
  Confirmed

Bug description:
  Mahara version15.04.1

  This report is in relation to my earlier forum post
  https://mahara.org/interaction/forum/topic.php?id=7310 but I have
  tracked down the problem.

  Issue:

  User is logging in via SAML and the user is being auto-created on first login.
  Remote  username is a unique id  (example: 
51c717bc-425c-4b31-9674-d38ba03b4f1f)
  When the user tries subsequent logins they are rejected with a error message 
that the user already exists and cannot be created.

  Reason:

  When the user is auto-created only the first 30 characters of the unique id 
are stored in the username field so the user is not recognised as being on the 
system when cheaked agains the full username from the login.
  The system then tries to auto-create the user, which fails because the full 
unique id is stored in the 'auth_remote_user' table.

  Solution:

  Changing  $maxlen  from 30 to 40 in function get_new_username() of
  user.php populates the user name with the full unique id.

  Maybe this could be a configurable option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1486699/+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

[Mahara-contributors] [Bug 1494565] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5267

-- 
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/1494565

Title:
  Web services auth uses wrong lang string in auth list

Status in Mahara:
  In Progress
Status in Mahara 15.04 series:
  Confirmed

Bug description:
  Mahara 15.04 and 15.10

  When you are on /admin/users/institutions.php and edit an institution,
  you an choose "Web services" from the list of authentication methods.
  The description only reads "Description" instead of the actual
  description "Web services-only users authenticated against Mahara's
  database".

  I tracked it down to the following (in Mahara 15.10):
  The "description" string on line 16 of 
/auth/webservice/lang/en.utf8/auth.webservice.php is correct. However, the auth 
list uses string "description" from line 153 from the section "wsdoc" instead. 

  When I comment the wsdoc "description" out, the proper description
  shows up in the authlist. So changing the string ID for the wsdoc to
  "wsdocdescription" should all that is needed. Unfortunately, I
  couldn't identify where I could change the string in the code and thus
  couldn't change it myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494565/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5264

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5265

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1487308] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5172
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/0200afb972c4c147b039210c3829b264cefd175d
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master

commit 0200afb972c4c147b039210c3829b264cefd175d
Author: Robert Lyon 
Date:   Thu Sep 3 19:45:56 2015 +1200

Bug 1487308: Setting aria-expanded to false

In the inbox/outbox list as each row is collapsed on page load

behatnotneeded

Change-Id: I9bbd01c4107938cb66492f333a3294873315fdab
Signed-off-by: Robert Lyon 

-- 
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/1487308

Title:
  All inbox messages are ARIA-expanded by default

Status in Mahara:
  Fix Committed

Bug description:
  Related to Bug #1484779

  In the Inbox, messages are now shown as expanders with the aria-
  expanded attribute showing their state. By default they all have the
  attribute aria-expanded="1" even though they are all collapsed. This
  should therefore be changed to aria-expanded="false".

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1487308/+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

[Mahara-contributors] [Bug 1487308] Re: All inbox messages are ARIA-expanded by default

2015-09-10 Thread Robert Lyon 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1487308

Title:
  All inbox messages are ARIA-expanded by default

Status in Mahara:
  Fix Committed

Bug description:
  Related to Bug #1484779

  In the Inbox, messages are now shown as expanders with the aria-
  expanded attribute showing their state. By default they all have the
  attribute aria-expanded="1" even though they are all collapsed. This
  should therefore be changed to aria-expanded="false".

  Affects latest master

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1487308/+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

[Mahara-contributors] [Bug 1494565] [NEW] Web services auth uses wrong lang string in auth list

2015-09-10 Thread Kristina Hoeppner 
Public bug reported:

Mahara 15.04 and 15.10

When you are on /admin/users/institutions.php and edit an institution,
you an choose "Web services" from the list of authentication methods.
The description only reads "Description" instead of the actual
description "Web services-only users authenticated against Mahara's
database".

I tracked it down to the following (in Mahara 15.10):
The "description" string on line 16 of 
/auth/webservice/lang/en.utf8/auth.webservice.php is correct. However, the auth 
list uses string "description" from line 153 from the section "wsdoc" instead. 

When I comment the wsdoc "description" out, the proper description shows
up in the authlist. So changing the string ID for the wsdoc to
"wsdocdescription" should all that is needed. Unfortunately, I couldn't
identify where I could change the string in the code and thus couldn't
change it myself.

** Affects: mahara
 Importance: Medium
 Status: Confirmed

-- 
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/1494565

Title:
  Web services auth uses wrong lang string in auth list

Status in Mahara:
  Confirmed

Bug description:
  Mahara 15.04 and 15.10

  When you are on /admin/users/institutions.php and edit an institution,
  you an choose "Web services" from the list of authentication methods.
  The description only reads "Description" instead of the actual
  description "Web services-only users authenticated against Mahara's
  database".

  I tracked it down to the following (in Mahara 15.10):
  The "description" string on line 16 of 
/auth/webservice/lang/en.utf8/auth.webservice.php is correct. However, the auth 
list uses string "description" from line 153 from the section "wsdoc" instead. 

  When I comment the wsdoc "description" out, the proper description
  shows up in the authlist. So changing the string ID for the wsdoc to
  "wsdocdescription" should all that is needed. Unfortunately, I
  couldn't identify where I could change the string in the code and thus
  couldn't change it myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494565/+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

[Mahara-contributors] [Bug 1465107] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5266

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1465107] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5242
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/60d1fc8eb9b37ec779f67a88e03d1978cda348ab
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master

commit 60d1fc8eb9b37ec779f67a88e03d1978cda348ab
Author: Toni Gardiner 
Date:   Wed Sep 9 11:49:13 2015 +1200

story-22785 task-23312 admin header

behatnotneeded

Bug 1465107

Change-Id: Idff88d30c6a7a7b0a4376ae25a7bfc3cfc7b

-- 
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/1465107

Title:
  Use the Bootstrap CSS framework

Status in Mahara:
  In Progress

Bug description:
  Mahara's CSS, and general front-end coding, is a bit chaotic. So for
  the past several months we've had a couple of front-end developers
  working on rewriting the entire Mahara front end to use the Bootstrap
  CSS framework. http://getbootstrap.com/css/

  This should make all of our front-end development work easier
  henceforth, as well as providing a nice set of standard widgets to
  make Mahara look better right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1465107/+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

[Mahara-contributors] [Bug 1491639] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5204
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/192478742a1a0a851cc06e7c32990112a15fe532
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master

commit 192478742a1a0a851cc06e7c32990112a15fe532
Author: Robert Lyon 
Date:   Thu Sep 3 11:08:22 2015 +1200

Bug 1491639: 'Group pages' block on upgrade problem

We need to default the 'display shared pages' option to 'By anybody'
value=2 as this is the same rules as the before upgrade.

We can leave newly created groups to default page/collection display to
'By members of this group'.

behatnotneeded

Change-Id: I135e459fecb9ac42e2352e570bc998f6568e2524
Signed-off-by: Robert Lyon 

-- 
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/1491639

Title:
  Need to update group 'shared with me' block config values on upgrade
  15.04+

Status in Mahara:
  Fix Committed
Status in Mahara 15.04 series:
  In Progress

Bug description:
  In pre 15.04 versions Group homepages have a 'Group pages' block
  showing the pages that are shared with the group (a yes/no option).
  This includes pages by members and non-members alike.

  After upgrade to 15.04+ there was a new option added so that we have:
  * None
  * By members of this group
  * By anybody

  But the problem is we added the new option, By members of this group,
  to the '1' value (the same as 'yes' before) rather than to the 'by
  anybody' option (which is '2').

  This means on upgrade any pages shared by non-members stop showing up
  on the shared list for this block.

  We need to run an upgrade for the group homepages to make any 'Display
  shared pages' that were set to 'yes' before hand to be set to 'by
  anybody' so that the same display rules are preserved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1491639/+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

[Mahara-contributors] [Bug 1491639] Re: Need to update group 'shared with me' block config values on upgrade 15.04+

2015-09-10 Thread Robert Lyon 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1491639

Title:
  Need to update group 'shared with me' block config values on upgrade
  15.04+

Status in Mahara:
  Fix Committed
Status in Mahara 15.04 series:
  In Progress

Bug description:
  In pre 15.04 versions Group homepages have a 'Group pages' block
  showing the pages that are shared with the group (a yes/no option).
  This includes pages by members and non-members alike.

  After upgrade to 15.04+ there was a new option added so that we have:
  * None
  * By members of this group
  * By anybody

  But the problem is we added the new option, By members of this group,
  to the '1' value (the same as 'yes' before) rather than to the 'by
  anybody' option (which is '2').

  This means on upgrade any pages shared by non-members stop showing up
  on the shared list for this block.

  We need to run an upgrade for the group homepages to make any 'Display
  shared pages' that were set to 'yes' before hand to be set to 'by
  anybody' so that the same display rules are preserved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1491639/+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

[Mahara-contributors] [Bug 1491639] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "15.04_STABLE" branch: https://reviews.mahara.org/5255

-- 
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/1491639

Title:
  Need to update group 'shared with me' block config values on upgrade
  15.04+

Status in Mahara:
  Fix Committed
Status in Mahara 15.04 series:
  In Progress

Bug description:
  In pre 15.04 versions Group homepages have a 'Group pages' block
  showing the pages that are shared with the group (a yes/no option).
  This includes pages by members and non-members alike.

  After upgrade to 15.04+ there was a new option added so that we have:
  * None
  * By members of this group
  * By anybody

  But the problem is we added the new option, By members of this group,
  to the '1' value (the same as 'yes' before) rather than to the 'by
  anybody' option (which is '2').

  This means on upgrade any pages shared by non-members stop showing up
  on the shared list for this block.

  We need to run an upgrade for the group homepages to make any 'Display
  shared pages' that were set to 'yes' before hand to be set to 'by
  anybody' so that the same display rules are preserved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1491639/+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

[Mahara-contributors] [Bug 1493177] Re: Skins don't work at all in 15.10dev

2015-09-10 Thread Robert Lyon 
** Changed in: mahara
   Status: In Progress => Fix Committed

-- 
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/1493177

Title:
  Skins don't work at all in 15.10dev

Status in Mahara:
  Fix Committed

Bug description:
  In the current version of 15.10dev, the dynamically-generated skin
  stylesheet (htdocs/skin/style.php) is not getting included in the
  stylesheets for a portfolio page. So skins don't work at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1493177/+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

[Mahara-contributors] [Bug 1493177] A change has been merged

2015-09-10 Thread Mahara Bot 
Reviewed:  https://reviews.mahara.org/5236
Committed: 
https://git.nzoss.org.nz/mahara/mahara/commit/9a9f87cbc3257be76c804be0acf35b3a0e8ddd20
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:master

commit 9a9f87cbc3257be76c804be0acf35b3a0e8ddd20
Author: Aaron Wells 
Date:   Tue Sep 8 15:46:38 2015 +1200

Fix the smarty() stylesheets method (Bug 1493177)

When this code was extracted from smarty() into its own function,
it missed the $extraconfig variable.

behatnotneeded: Can't test skins in Behat yet.

Change-Id: Id46eb0b0c5103649e5d194c14275e5479e48b507

-- 
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/1493177

Title:
  Skins don't work at all in 15.10dev

Status in Mahara:
  Fix Committed

Bug description:
  In the current version of 15.10dev, the dynamically-generated skin
  stylesheet (htdocs/skin/style.php) is not getting included in the
  stylesheets for a portfolio page. So skins don't work at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1493177/+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

[Mahara-contributors] [Bug 1494133] A patch has been submitted for review

2015-09-10 Thread Mahara Bot 
Patch for "master" branch: https://reviews.mahara.org/5252

-- 
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/1494133

Title:
  Fatal error upgrading 1.3->15.04 or 1.4->15.04

Status in Mahara:
  New
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  New

Bug description:
  To replicate:

  1. Clean install of Mahara 1.3 to 1.4
  2. Upgrade to Mahara 15.04 (via CLI; I haven't tested via the web upgraded)

  Expected result: Successful upgrade
  Actual result: Crashes with this fatal error:

  PHP Fatal error:  Uncaught exception 'SQLException' with message 'Failed to 
get a recordset: postgres8 error: [-18: ERROR:  relation "institution_config" 
does not exist
  LINE 1: SELECT field, value FROM "institution_config" WHERE "institu...
   ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
  Command was: SELECT field, value FROM "institution_config" WHERE 
"institution" = ? ORDER BY field  and values was (mahara)' in 
mahara/htdocs/lib/dml.php:480
  Stack trace:
  #0 mahara/htdocs/lib/dml.php(429): get_recordset_sql('SELECT field, v...', 
Array)
  #1 mahara/htdocs/lib/dml.php(393): get_recordset_select('institution_con...', 
'"institution" =...', Array, 'field', 'field, value', '', '')
  #2 mahara/htdocs/lib/dml.php(719): get_recordset('institution_con...', 
'institution', 'mahara', 'field', 'field, value')
  #3 mahara/htdocs/lib/institution.php(277): get_records_menu('instit in 
/home/aaronw/www/mahara/htdocs/lib/dml.php on line 480

  Works fine when upgrading from 1.1, 1.2, or 1.5. So it's probably
  caused by some discrepancy between the 1.3 & 1.4 upgrade vs clean
  install.

  I noticed the same problem in a 1.4 -> 15.10dev upgrade. But,
  strangely, not in a 1.3 -> 15.10dev upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494133/+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

[Mahara-contributors] [Bug 1494133] Re: Fatal error upgrading 1.3->15.04 or 1.4->15.04

2015-09-10 Thread Aaron Wells 
** Description changed:

  To replicate:
  
- 1. Clean install of Mahara 1.3 or 1.4
+ 1. Clean install of Mahara 1.3 to 1.4
  2. Upgrade to Mahara 15.04 (via CLI; I haven't tested via the web upgraded)
  
  Expected result: Successful upgrade
  Actual result: Crashes with this fatal error:
  
  PHP Fatal error:  Uncaught exception 'SQLException' with message 'Failed to 
get a recordset: postgres8 error: [-18: ERROR:  relation "institution_config" 
does not exist
  LINE 1: SELECT field, value FROM "institution_config" WHERE "institu...
-  ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
+  ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
  Command was: SELECT field, value FROM "institution_config" WHERE 
"institution" = ? ORDER BY field  and values was (mahara)' in 
mahara/htdocs/lib/dml.php:480
  Stack trace:
  #0 mahara/htdocs/lib/dml.php(429): get_recordset_sql('SELECT field, v...', 
Array)
  #1 mahara/htdocs/lib/dml.php(393): get_recordset_select('institution_con...', 
'"institution" =...', Array, 'field', 'field, value', '', '')
  #2 mahara/htdocs/lib/dml.php(719): get_recordset('institution_con...', 
'institution', 'mahara', 'field', 'field, value')
  #3 mahara/htdocs/lib/institution.php(277): get_records_menu('instit in 
/home/aaronw/www/mahara/htdocs/lib/dml.php on line 480
  
  Works fine when upgrading from 1.1, 1.2, or 1.5. So it's probably caused
  by some discrepancy between the 1.3 & 1.4 upgrade vs clean install.
+ 
+ I noticed the same problem in a 1.4 -> 15.10dev upgrade. But, strangely,
+ not in a 1.3 -> 15.10dev upgrade.

-- 
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/1494133

Title:
  Fatal error upgrading 1.3->15.04 or 1.4->15.04

Status in Mahara:
  New
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  New

Bug description:
  To replicate:

  1. Clean install of Mahara 1.3 to 1.4
  2. Upgrade to Mahara 15.04 (via CLI; I haven't tested via the web upgraded)

  Expected result: Successful upgrade
  Actual result: Crashes with this fatal error:

  PHP Fatal error:  Uncaught exception 'SQLException' with message 'Failed to 
get a recordset: postgres8 error: [-18: ERROR:  relation "institution_config" 
does not exist
  LINE 1: SELECT field, value FROM "institution_config" WHERE "institu...
   ^] in EXECUTE("SELECT field, value FROM 
"institution_config" WHERE "institution" = ? ORDER BY field ")
  Command was: SELECT field, value FROM "institution_config" WHERE 
"institution" = ? ORDER BY field  and values was (mahara)' in 
mahara/htdocs/lib/dml.php:480
  Stack trace:
  #0 mahara/htdocs/lib/dml.php(429): get_recordset_sql('SELECT field, v...', 
Array)
  #1 mahara/htdocs/lib/dml.php(393): get_recordset_select('institution_con...', 
'"institution" =...', Array, 'field', 'field, value', '', '')
  #2 mahara/htdocs/lib/dml.php(719): get_recordset('institution_con...', 
'institution', 'mahara', 'field', 'field, value')
  #3 mahara/htdocs/lib/institution.php(277): get_records_menu('instit in 
/home/aaronw/www/mahara/htdocs/lib/dml.php on line 480

  Works fine when upgrading from 1.1, 1.2, or 1.5. So it's probably
  caused by some discrepancy between the 1.3 & 1.4 upgrade vs clean
  install.

  I noticed the same problem in a 1.4 -> 15.10dev upgrade. But,
  strangely, not in a 1.3 -> 15.10dev upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1494133/+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