Bulk import fails when one user fails to import
Bug #823013 reported by
Richard Mansfield
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mahara |
Fix Released
|
Low
|
Richard Mansfield | ||
Bug Description
In the bulk import script, if one user fails to import due to a bad or missing leap2a file, the script dies because it executes a continue statement when not inside a loop.
| Changed in mahara: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| assignee: | nobody → Richard Mansfield (richard-mansfield) |
| milestone: | none → 1.5.0 |
Revision history for this message
| Mahara Bot (dev-mahara) wrote A change has been merged | #1 |
| Changed in mahara: | |
| status: | Confirmed → Fix Committed |
| Changed in mahara: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Hugh Davenport (<email address hidden>)
Branch: master
commit 87e948831c709b7
Author: Richard Mansfield <email address hidden>
Date: Tue Aug 9 12:10:10 2011 +1200
Let bulk import continue processing after bad leap2a file (bug #823013)
A couple of 'continue' statements look to be leftovers from a previous
version of this script that added users in a loop. Now that they each
user is added with a redirect back to the page, we should do this
correctly after a failure to unzip or process a leap2a file.
Change-Id: I4d412bcfe56483
Signed-off-by: Richard Mansfield <email address hidden>