Mahara

Upgrade failure to 17.10+ when event logging for 'all' is on

Bug #1747320 reported by Robert Lyon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Invalid
Undecided
Unassigned

Bug Description

When an existing site has event logging set to 'all' and is upgrading to 17.10+ the upgrade can fail if there are event log data with password info in it.

See https://mahara.org/interaction/forum/topic.php?id=8137&offset=0&limit=10#post32645

Robert Lyon (robertl-9)
Changed in mahara:
status: New → In Progress
milestone: none → 18.04.0
importance: Undecided → High
Revision history for this message
Mahara Bot (dev-mahara) wrote : A patch has been submitted for review

Patch for "master" branch: https://reviews.mahara.org/8504

Revision history for this message
Robert Lyon (robertl-9) wrote :

I think the problem for the user came about when an upgrade failed part way thru and column had changed from time => ctime.

I could not replicate on upgrade that didn't fail

Changed in mahara:
importance: High → Undecided
status: In Progress → Invalid
Kristina Hoeppner (kris-hoeppner)
Changed in mahara:
milestone: 18.04.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.