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

Add ability to check environment before installing addons

XMLWordPrintable

    • MOODLE_25_STABLE
    • MOODLE_28_STABLE
    • wip_MDL-39840_m28_addonenv
    • Hide

      Testing requires knowledge of standard core environment.xml structure and related UIs.

      0/ execute phpunit tests and test normal install and upgrade
      1/ add environment.xml to some plugin
      2/ test upgrade via version bump
      3/ test admin page with environment

      sample env file is in patch in MDL-46660, the structure of the XML file is the same as core environment.xml

      Show
      Testing requires knowledge of standard core environment.xml structure and related UIs. 0/ execute phpunit tests and test normal install and upgrade 1/ add environment.xml to some plugin 2/ test upgrade via version bump 3/ test admin page with environment sample env file is in patch in MDL-46660 , the structure of the XML file is the same as core environment.xml

      Occasionally an addon will require the installation of an additional PHP extension or have version requirements. Currently, we have the maintainer manually marking PHP version in Moodle Plugins; however, I would like to see an additional option where a maintainer could provide an environment.xml file that lists any additional requirements beyond that particular version of Moodle. For example, a plugin may take advantage of a later version of PHP than core does. This would protect sites from installing code for which the environment does not support it.

            skodak Petr Skoda
            aborrow Anthony Borrow
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Damyon Wiese Damyon Wiese
            Simey Lameze Simey Lameze
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:

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