Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-35208

Choice responses in changed order after backup/restore

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.5, 2.3.1, 2.4
    • Fix Version/s: 2.2.6, 2.3.3
    • Component/s: Choice
    • Labels:

      Description

      We updated a moodle 1.9.12 to 2.2.4, and then to 2.3.1 (= updated moodle). We make course backups and restore them on a native 2.3.1 (= native moodle).

      When backing up courses from the updated moodle to a native moodle 2.3.1 installation, the responses of the choices are displayed in a different order. For example: updated moodle order = 1,2,3,4; native moodle order = 3,2,1,4

      In contrary: If choices are created in the native moodle 2.3.1, backed up and restored in the native 2.3.1, responses are displayed in correct order.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            hoberg Marcus Hoberg added a comment -

            Implemented the changed code into our running moodle 2.3.1, and it works: order of choices after backup now is correct.
            Thanks for fixing so quick!

            Show
            hoberg Marcus Hoberg added a comment - Implemented the changed code into our running moodle 2.3.1, and it works: order of choices after backup now is correct. Thanks for fixing so quick!
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

            TIA and ciao

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week. TIA and ciao
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Integrated (22, 23 & master), thanks!

            Side note: crazy SQL alignment, btw... note that will be enforced soon by coding guidelines... surely in 1-2y we'll agree a format, lol.

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Integrated (22, 23 & master), thanks! Side note: crazy SQL alignment, btw... note that will be enforced soon by coding guidelines... surely in 1-2y we'll agree a format, lol.
            Hide
            fred Frédéric Massart added a comment -

            Test passed on 2.2, 2.3 and master. \o/

            Show
            fred Frédéric Massart added a comment - Test passed on 2.2, 2.3 and master. \o/
            Hide
            stronk7 Eloy Lafuente (stronk7) added a comment -

            Gutta cavat lapidem, non vi sed saepe cadendo - Ovidio

            This issue has been integrated upstream and is now available both via git and cvs (and in some hours, via mirrors and downloads).

            Thanks!

            Show
            stronk7 Eloy Lafuente (stronk7) added a comment - Gutta cavat lapidem, non vi sed saepe cadendo - Ovidio This issue has been integrated upstream and is now available both via git and cvs (and in some hours, via mirrors and downloads). Thanks!

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  12/Nov/12