mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #66244
[Bug 1969702] Re: Error in "Locked until" date on locked collections
** Changed in: mahara
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1969702
Title:
Error in "Locked until" date on locked collections
Status in Mahara:
Fix Released
Bug description:
Related to this bug here:
https://bugs.launchpad.net/mahara/+bug/1928270
When locking a portfolio, the "Locked until" date is set to the date
that the collection was locked, i.e. the rolloverdate. It should be
this date + 6 months (htdocs/lib/view.php:6092)
To replicate:
1. Create an institution template collection (set to 'Current auto-copied template') with portfolio completion.
2. Add 1 review block and set 'Lock portfolio' to 'Yes'.
3. Create a new account and run the cron so that the portfolio is created.
4. Share the portfolio with a person who can do a review.
5. Log in as the reviewer and approve the review statement.
6. As portfolio author, check that the portfolio is locked.
by going to 'Shared by me'.
Result:
- Says "Locked until (date it was locked)"
Expected:
- Says "Locked until (date it was locked + 6 months)"
The cron job for unlocking based on rolloverdate is correct and
working fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1969702/+subscriptions
References