← Back to team overview

mahara-contributors team mailing list archive

[Bug 1190186] Re: Masquerading sessions report fails if database tables have prefix

 

Hello Kevin,

Thanks for finding this bug. We'll fix it and will put it into the next
minor release of 1.7.

** Changed in: mahara
       Status: New => Triaged

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

** Changed in: mahara
     Assignee: (unassigned) => Robert Lyon (robertl-9)

** Changed in: mahara
    Milestone: None => 1.7.2

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

** Changed in: mahara/1.8
       Status: New => Triaged

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

** Changed in: mahara/1.8
     Assignee: (unassigned) => Robert Lyon (robertl-9)

** Changed in: mahara/1.8
    Milestone: None => 1.8.0rc1

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1190186

Title:
  Masquerading sessions report fails if database tables have prefix

Status in Mahara ePortfolio:
  Triaged
Status in Mahara 1.8 series:
  Triaged

Bug description:
  In version 1.7.1 in the script 'admin/users/report.php' on line 165,
  the table name 'event_log' is not enclosed in {} and therefore fails
  if the system have been set up with a table prefix.

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


References