search

donhinkelman / moodle-block_sharing_cart

Content sharing plug-in for Moodle LMS. Now at version 4.4, release 3 (actually this is for Moodle LMS version 4.3. Requires PHP 7.4.
7 stars 38 forks source link

Improvement: Sharing cart should respect ordering of items within a section #11

Closed Kathrin84 closed 5 years ago

Kathrin84 commented 5 years ago

Hi Don,

while testing your plugin for the Moodle 3.6 version, I stumbled over this behavior.

Encountered problem A section contains several activities and resources. When you add the whole section to the sharing cart, the ordering of the items is not the same anymore. Then, when you restore the section to another section or course, the structure of the sharing cart will be restored. So the initial ordering is muddled up and the teacher needs to rearrange his copied section.

Steps to reproduce

  1. Create a new course and merge this backup into the course: test_sharing_cart.mbz.zip Your course should look like this now: sharing_cart_course_structure
  2. Turn editing on and add the block sharing cart to this course
  3. Add the whole section to the sharing cart
  4. Verify that the structure within the sharing cart is different to the structure of the copied section. In my case it looks like this: sharing_cart_copied_section
  5. Restore the whole section into another course or into another section Verify that the structure of the restored section is the same as the one in the sharing cart.

Propopsal The sharing cart should backup the items within a section in the same order.

Best, Kathrin

donhinkelman commented 5 years ago

Thank you Kathrin. We are now working on this issue.

donhinkelman commented 5 years ago

Thank you all for work on this issue. It is now closed.

Kathrin84 commented 5 years ago

Thank you very much for this improvement! 👍

neeesn commented 5 years ago

We stille have this issue - we have updated sharing_cart to version 2019012000 3,6 Release 1 billede

We are currently using moodle 3.4.3+

bfriesenvcc commented 4 years ago

We also still have this issue, using 2019012000, 3.6, release 1.

donhinkelman commented 4 years ago

Thank you for reporting and confirming that this issue still remains. I don't know when the programmers can work on this, but I hope it will be fixed in the next release.