mahara-contributors team mailing list archive

[Mahara Bot <1900786@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/11405
Committed: https://git.mahara.org/mahara/mahara/commit/af6cb4a52ba69e895f79e3fd94b84ef5f146911b
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    20.10_STABLE

commit af6cb4a52ba69e895f79e3fd94b84ef5f146911b
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Mon Oct 26 10:27:09 2020 +1300

Bug 1900786: Adding in the default $timestamp on constructor

And adding param comment

Change-Id: If26513010f79dc58e405476cf26e2581f9c15490
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
(cherry picked from commit ef7cb8730da50c2826ee069d844caba3889f7184)

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

Title:
  combined exports: timing issues causing leap2a to be put into wrong
  directory

Status in Mahara:
  Fix Committed
Status in Mahara 20.10 series:
  Fix Committed
Status in Mahara 21.04 series:
  Fix Committed

Bug description:
  For combined exports, when we are creating an export we use timestamps
  to create a folder in our site data directory that helps us gather the
  files together when we create our .zip archive etc... If even a split
  second passes when the next export type goes to create its export
  directory, i.e leap2a, the timestamp named folder is something
  different and thus sends the leap2a to a different location.

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