To replicate this problem: 1. Create a collection C 2. Create a page P 3. Put page P in collection C 4. Add a navigation block to page P and make it point at collection C. 5. Export collection C to a leap2a file 6. Re-import the leap2a file into your portfolio (or a different user's portfolio) 7. Change the name of the imported copy of collection C to "C2" 8. Look at the navigation block on page P
Expected result: It should now show that it's pointed at collection C2 Actual result: It will either be broken, or it will be pointing at collection C. -- 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/1333424 Title: Navigation block broken after Leap2a import Status in Mahara: Confirmed Status in Mahara 1.10 series: Confirmed Status in Mahara 1.9 series: Confirmed Status in Mahara 15.04 series: Confirmed Status in Mahara 15.10 series: Confirmed Bug description: Version: master (1.10), 1.9, 1.8, 1.7 After importing the attached leap2a file which has a collection and a navigation block pointed to this collection, I found the navigation block now pointed to the old collection id. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1333424/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
