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

Block does not move if using Oracle database

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.0.4, 2.1.1
    • 2.0.1, 2.1, 2.2
    • Blocks, Database SQL/XMLDB
    • None
    • 2.0.1, Linux, Oracle 11g
    • Oracle
    • MOODLE_20_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
    • MOODLE_20_STABLE, MOODLE_21_STABLE
    • Difficult
    • Hide

      1. Using your install of Moodle 2.0 or 2.1 on Oracle ...
      2. Add a block on the course page, and set it to appear on all pages in the coures (page type *, course context and subcontext)
      3. Go into one of the activities (e.g. a Page resource), turn editing on, and try to move the block elsewhere on the page.

      It should work, with no errors.

      Show
      1. Using your install of Moodle 2.0 or 2.1 on Oracle ... 2. Add a block on the course page, and set it to appear on all pages in the coures (page type *, course context and subcontext) 3. Go into one of the activities (e.g. a Page resource), turn editing on, and try to move the block elsewhere on the page. It should work, with no errors.

      Please see the following discuss topic for details on this problem: http://moodle.org/mod/forum/discuss.php?d=169685

      The Block does not move when using Oracle database, and Tim found the reason for this, and already created a patch file. I have put on our test environment, and it works well so far. But, need to do more test before moving to Production.

      Actually, the patch needs to be reviewed.

            timhunt Tim Hunt
            longfeiyu Longfei Yu
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.