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

blog visibility link leads to "Section error!"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.2
    • Component/s: Blog
    • Labels:
    • Environment:
      upgrade from moodle 1.9.10+ to 2.0.1+
      php: 5.3.3
      mysql: 5.5.9
      server: MacOS 10.6.6
    • Database:
      MySQL
    • Affected Branches:
      MOODLE_20_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE

      Description

      During a successful upgrade from 1.9.10+ to 2.0.1+, a warning appeared in red:

      "Your site is using an old blog visibility setting, the blog visibility upgrade is recommended." (see screen shot 1)

      "blog visibility upgrade" was a hot link to: http://vle.c.fun.ac.jp/moodle2/admin/bloglevelupgrade.php

      I opened this link in a new tab and got an "Section error!" (see screen shot 2)

      I closed this tab and let the upgrade continue in the original window. The upgraded completed successfully.

      On logging into the upgraded site, I clicked on 'Notifications' and saw the same "blog visibility" warning (see screen shot 3). Again, clicking on the link leads to a "Section error!".

      We have hardly used the blog feature, so I am not too worried - at the moment. But, if someone upgrading comes across this warning (recommendation) and clicks on the link, they could be taken out of the upgrade process, and believe that it has failed,

        Attachments

          Activity

            People

            Assignee:
            skodak Petr Skoda
            Reporter:
            stuart Peter Ruthven-Stuart
            Tester:
            Eloy Lafuente (stronk7)
            Participants:
            Component watchers:
            Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              21/Feb/11