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

Update upgrade_stale_php_files_present() before 4.1 release

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • 4.1
    • 4.1
    • Installation
    • MOODLE_401_STABLE
    • MOODLE_401_STABLE
    • Hide

      Note: TARGET for this issue is:

      1. master

      web

      1. Create/check out a 4.0.x site. For example: 

        git checkout v4.0.0

      2. Install the 4.0 site.
      3. Check out the TARGET branch 

        git checkout TARGET

      4. Create any of the following files that are being detected by the patch. (e.g. on Linux, use the "touch" command):
        • mod/forum/classes/task/refresh_forum_post_counts.php 

          touch mod/forum/classes/task/refresh_forum_post_counts.php

        • user/amd/build/participantsfilter.min.js 

          touch user/amd/build/participantsfilter.min.js

        • ...
      5. Open your Moodle instance on your browser.
      6. Log in as admin and proceed with the upgrade.
      7. Verify that a notice ("Mixed Moodle versions detected....") is displayed saying that there are problems upgrading and a proper procedure for upgrading to a major release.
      8. Delete the touched file(s) in point 4.
      9. Click "Reload".
      10. Verify that the upgrade now proceeds ok.

      cli

      1. Repeat points 1-4 from the "web" instructions.
      2. Run the CLI upgrade 

        php admin/cli/upgrade.php

      3. Verify that a text ("Mixed Moodle versions detected....") is displayed saying that there are problems upgrading and a proper procedure for upgrading to a major release.
      4. Delete the touched file(s) in point web - 4.
      5. Run the CLI upgrade again 

        php admin/cli/upgrade.php

      6. Verify that now the process runs ok, with a prompt asking you for confirmation and then a number of upgrade steps and settings being setup.
      7. Verify that the process ends with a text like this (the numbers are not important), the "successfully" is.:

        Command line upgrade from XXXXX (Build: XXXXX) (XXXXX) to XXXXX (Build: XXXXX) (XXXXX) completed successfully.

      Show
      Note: TARGET for this issue is: master web Create/check out a 4.0.x site. For example: git checkout v4.0.0 Install the 4.0 site. Check out the TARGET branch git checkout TARGET Create any of the following files that are being detected by the patch. (e.g. on Linux, use the " touch " command): mod/forum/classes/task/refresh_forum_post_counts.php touch mod/forum/classes/task/refresh_forum_post_counts.php user/amd/build/participantsfilter.min.js touch user/amd/build/participantsfilter.min.js ... Open your Moodle instance on your browser. Log in as admin and proceed with the upgrade. Verify that a notice ("Mixed Moodle versions detected....") is displayed saying that there are problems upgrading and a proper procedure for upgrading to a major release. Delete the touched file(s) in point 4. Click " Reload ". Verify that the upgrade now proceeds ok. cli Repeat points 1-4 from the "web" instructions. Run the CLI upgrade php admin/cli/upgrade.php Verify that a text ("Mixed Moodle versions detected....") is displayed saying that there are problems upgrading and a proper procedure for upgrading to a major release. Delete the touched file(s) in point web - 4. Run the CLI upgrade again php admin/cli/upgrade.php Verify that now the process runs ok, with a prompt asking you for confirmation and then a number of upgrade steps and settings being setup. Verify that the process ends with a text like this (the numbers are not important), the "successfully" is.: Command line upgrade from XXXXX (Build: XXXXX) (XXXXX) to XXXXX (Build: XXXXX) (XXXXX) completed successfully.

      Simply verify we have a number (4-5) of files for the next major release. They all must be files deleted since last stable version (400) and current master.

      git diff --name-status MOODLE_XX_STABLE..master | grep ^D

      And, then, simply, add them to upgrade_stale_php_files_present().

      Note that it's better not to pick any plugin file that maybe reinstalled manually (exception being forum files because that plugin is mandatory).

      Note: (to avoid forgetting it in next iteration of this issue). Don't forget the leading slashes in the paths.

        1. cli_1_MDL-76015.png
          cli_1_MDL-76015.png
          62 kB
        2. cli_2_MDL-76015.png
          cli_2_MDL-76015.png
          38 kB
        3. cli_result.png
          cli_result.png
          250 kB
        4. web_1_MDL-76015.png
          web_1_MDL-76015.png
          67 kB
        5. web_2_MDL-76015.mp4
          1.31 MB
        6. web_result.png
          web_result.png
          276 kB

            stronk7 Eloy Lafuente (stronk7)
            stronk7 Eloy Lafuente (stronk7)
            Paul Holden Paul Holden
            Huong Nguyen Huong Nguyen
            John Edward Pedregosa John Edward Pedregosa
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours, 15 minutes
                2h 15m

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