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

Add environment check for versions where PHP 7.2 is NOT supported

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      These testing instructions are different from MDL-55121 because on PHP 7.2 you get fatal error before you even get to any env check

      1. Use PHP 7.0 or earlier. Install Moodle 3.1 (integration)
      2. Upgrade it to 3.2 (integration) and then to 3.3 (integration), upgrade should complete successfully
      3. Use PHP 7.1 or earler. Do a fresh install of Moodle 3.2 (int) and 3.3 (int)
      4. Use PHP 7.2 and cherry-pick d28eb51dd to all integration sites (3.1, 3.2, 3.3)
      5. On each site (3.1, 3.2, 3.3) go to Site administration>Server>Environment and try to switch between versions - for Moodle 3.2 and 3.3 you should see a php7.2 warning, for Moodle 3.4 there should be no warning
      Show
      These testing instructions are different from MDL-55121 because on PHP 7.2 you get fatal error before you even get to any env check Use PHP 7.0 or earlier. Install Moodle 3.1 (integration) Upgrade it to 3.2 (integration) and then to 3.3 (integration), upgrade should complete successfully Use PHP 7.1 or earler. Do a fresh install of Moodle 3.2 (int) and 3.3 (int) Use PHP 7.2 and cherry-pick d28eb51dd to all integration sites (3.1, 3.2, 3.3) On each site (3.1, 3.2, 3.3) go to Site administration>Server>Environment and try to switch between versions - for Moodle 3.2 and 3.3 you should see a php7.2 warning, for Moodle 3.4 there should be no warning
    • Affected Branches:
      MOODLE_32_STABLE, MOODLE_33_STABLE
    • Fixed Branches:
      MOODLE_31_STABLE, MOODLE_32_STABLE, MOODLE_33_STABLE
    • Pull Master Branch:
      wip-MDL-60543-master

      Description

      On Moodle 3.2 and 3.3 add an environment check that PHP 7.2 is not supported

      See also MDL-50624 and MDL-55121

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  13/Nov/17