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

Be more cautious about saying 'your moodle is up to date'

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.3
    • Component/s: Administration
    • Labels:
    • Testing Instructions:
      Hide

      Difficult: HARD - requires manual DB queries

      1. Simulate no update data yet by doing: DELETE FROM mdl_config_plugins where plugin = 'core_plugin';
      2. Simulate outdated update data by doing': UPDATE mdl_config_plugins set value = '1' WHERE name = 'recentfetch' AND plugin = 'core_plugin';
      Show
      Difficult: HARD - requires manual DB queries Simulate no update data yet by doing: DELETE FROM mdl_config_plugins where plugin = 'core_plugin'; Simulate outdated update data by doing': UPDATE mdl_config_plugins set value = '1' WHERE name = 'recentfetch' AND plugin = 'core_plugin';
    • Affected Branches:
      MOODLE_23_STABLE
    • Fixed Branches:
      MOODLE_23_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-32337-uptodate

      Description

      Currently its displaying 'Your moodle code seems to be up-to-date' when it has no fetch data at all or if the fetch data is highly outdated.

      In those cases I think it should only display 'check for available updates'. For sure there are going to be people where they haven't the proxy configured correctly or whatever and moodle can't get the update check so we shouldn't be reporting this.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    25/Jun/12