mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Public bug reported:

In the view constructor for 17.04+ there is some code that regenerates
the view_rows_columns info if missing but that relies on the view id
being known.

During the Leap2A import process the view id is not known yet - so we
need the constructor to ignore fixing up view_rows_columns data at this
point.

** Affects: mahara
     Importance: High
         Status: In Progress

** Affects: mahara/17.04
     Importance: High
         Status: Confirmed

** Affects: mahara/17.10
     Importance: High
         Status: In Progress

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

** Also affects: mahara/17.10
   Importance: High
       Status: In Progress

** Changed in: mahara/17.04
    Milestone: None => 17.04.3

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

** Changed in: mahara/17.04
       Status: New => 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/1696587

Title:
  Problem with Leap2A import and creating custom layout option for user

Status in Mahara:
  In Progress
Status in Mahara 17.04 series:
  Confirmed
Status in Mahara 17.10 series:
  In Progress

Bug description:
  In the view constructor for 17.04+ there is some code that regenerates
  the view_rows_columns info if missing but that relies on the view id
  being known.

  During the Leap2A import process the view id is not known yet - so we
  need the constructor to ignore fixing up view_rows_columns data at
  this point.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1696587/+subscriptions