Copying a collection is creating extra duplicates
Bug #1020102 reported by
Stacey Walker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Stacey Walker |
Bug Description
User A has one collection and two pages:
* Page One (In Collection One)
* Page Two
Cloning of a single page works correctly, can rename and re-edit.
Cloning of the collection creates two extra collections instead of the one specified:
step 1: asks for new collection name (entered: Collection Two)
step 2: asks to manage pages (Page One is missing when it should show a copy, Page Two is correctly an option to select - User A chooses no new page)
Done + Save.
Now User A can see:
- 'Collection Two' with no pages
- Copy of 'Collection One' with 'Copy of Page One'
Should see only 'Collection Two' with Copy of Page One'. Images attached.
Issue seen on 1.6.0dev
Changed in mahara: | |
assignee: | nobody → Stacey Walker (stacey) |
Changed in mahara: | |
milestone: | none → 1.6.0 |
Changed in mahara: | |
status: | Invalid → Won't Fix |
status: | Won't Fix → Fix Committed |
To post a comment you must log in.
Hi Stacey,
Can you please pull the very latest code from today? I had a similar issue during the review of the group / institution / site collection changes, but that is fixed. I couldn't reproduce your issue on the latest code locally.
Cheers
Kristina