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

No need for the "add-on" term at so many places

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      • Visit the Plugins overview page. Make sure the "add-on" is not mentioned in the UI.
      • Use the Install plugins admin page and try to install a plugin from the plugins directory. Again, check for consistency, no "add-on" should be mentioned in Moodle UI during the process.
      Show
      Visit the Plugins overview page. Make sure the "add-on" is not mentioned in the UI. Use the Install plugins admin page and try to install a plugin from the plugins directory. Again, check for consistency, no "add-on" should be mentioned in Moodle UI during the process.
    • Affected Branches:
      MOODLE_27_STABLE
    • Fixed Branches:
      MOODLE_27_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-45599-master-addons
    • Pull Master Diff URL:

      Description

      When I was implementing the new Plugins overview screen, there was a need to distinguish plugins installed as a part of Moodle standard distribution from those that were installed (added) manually by the admin. Various alternatives like "3rd party", "contributed", "non-standard", "extension" etc were considered (with Helen Foster and Martin Dougiamas involved) and finally it was decided to use the "add-on".

      However, after some time, it now appears to me that we (well, it was just me actually) overacted a bit and used the term at much more places in the admin UI. This sometimes lead to confusion as people are asking what's the difference between a plugin and an add-on (I've seen some sophisticated slides about it even).

      The true is, there is no conceptual difference. Or better, nothing that deserve so much attention as it is now.

      So, my proposal in this issue is:

      1. Use terms "add-on" and "standard" only (and only) in that table that lists all installed plugins (the "Source" column)
      2. Change all other occurrences of the "add-on" string to "plugin". So the admin Settings block node would read "Install plugin" etc.

      I believe that such consistency would help. Looking forward your comments here.

        Attachments

          Activity

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                14/Jul/14