mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #60929
[Bug 1900786] A change has been merged
Reviewed: https://reviews.mahara.org/11396
Committed: https://git.mahara.org/mahara/mahara/commit/eb597081dc1b1f376323aad4666d8ff87284dc87
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: master
commit eb597081dc1b1f376323aad4666d8ff87284dc87
Author: Lisa Seeto <lisaseeto@xxxxxxxxxxxxxxx>
Date: Wed Oct 21 12:36:11 2020 +1300
Bug 1900786: combined exports: timing issues causing leap2a to be put
into wrong directory
fix timestamp for export folder path names
Change-Id: I70e773bfa81e5258e0862a82ababd75a0e581a06
Signed-off-by: Lisa Seeto <lisaseeto@xxxxxxxxxxxxxxx>
--
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
References