MoodleDocs - Recent changes [en]

Events and Signup Plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 18:05:46 GMT

Updated links to Moodle Marketplace for plugins

← Older revision		Revision as of 18:05, 10 August 2026
Line 1:		Line 1:

	===A summary of some of the options around Plugins to manage events and signups===		===A summary of some of the options around Plugins to manage events and signups===
	~~A work in progress--[[User:Derek Chirnside\|Derek Chirnside]] ([[User talk:Derek Chirnside\|talk]]) 12:23, 12 March 2015 (AWST)~~

	====Organizer: https://moodle.~~org~~/plugins~~/view~~/mod_organizer====		====Organizer: https://marketplace.moodle.com/plugins/mod_organizer====
	Help: http://www.academic-moodle-cooperation.org/module/organizer/		Help: http://www.academic-moodle-cooperation.org/module/organizer/

	====Scheduler: https://moodle.~~org~~/plugins/~~view.php?plugin=~~mod_scheduler====		====Scheduler: https://marketplace.moodle.com/plugins/mod_scheduler====

	====https://moodle.~~org~~/plugins~~/view~~/mod_reservation====		====https://marketplace.moodle.com/plugins/mod_reservation====

	====~~Face to Face:~~ https://moodle.~~org~~/plugins~~/view~~/mod_facetoface====		====https://marketplace.moodle.com/plugins/mod_facetoface====
	*

	====Groups Self Selection: https://moodle.~~org~~/plugins~~/view~~/mod_groupselect====		====Groups Self Selection: https://marketplace.moodle.com/plugins/mod_groupselect====
	*

	====Group Choice: https://moodle.~~org~~/plugins~~/view~~/mod_choicegroup====		====Group Choice: https://marketplace.moodle.com/plugins/mod_choicegroup====
	*

	====~~Booking:~~ https://moodle.~~org~~/plugins~~/view~~/mod_booking====		====https://marketplace.moodle.com/plugins/mod_booking====
	*We only support uneven Moodle versions. That means, there is a version for Moodle 2.5, 2.7, and so on.
	*Possibly the nicest looking, genuine 'Events" list page

MoodleDT - Development Tools Plugins for Moodle

Gunjan Sarojwal — Mon, 10 Aug 2026 17:55:27 GMT

Updated links to Moodle Marketplace for plugins

← Older revision		Revision as of 17:55, 10 August 2026
Line 1:		Line 1:
	{{Infobox plugin		{{Infobox plugin
	\|type = Tool		\|type = Tool
	\|entry = https://moodle.~~org~~/plugins/~~view.php?plugin=~~tool_moodledt		\|entry = https://marketplace.moodle.com/plugins/tool_moodledt
	\|tracker = https://tracker.moodle.org/browse/CONTRIB/component/13030		\|tracker = https://tracker.moodle.org/browse/CONTRIB/component/13030
	\|discussion = https://moodle.org/mod/forum/view.php?id=44		\|discussion = https://moodle.org/mod/forum/view.php?id=44
Line 13:		Line 13:

	== Instalation ==		== Instalation ==
	* Get last version of plugin in [https://moodle.~~org~~/plugins/~~view.php?plugin=~~tool_moodledt plugin entry].		* Get last version of plugin in [https://marketplace.moodle.com/plugins/tool_moodledt plugin entry].
	* Unpack in admin/tools folder of your Moodle dir.		* Unpack in admin/tools folder of your Moodle dir.
	* Under role '''administrator''', go to the '''Site administration''' and click on '''Notifications'''.		* Under role '''administrator''', go to the '''Site administration''' and click on '''Notifications'''.
Line 84:		Line 84:
	* New tools suggested by reviewers.		* New tools suggested by reviewers.

	Please for suggestion, use comments in [https://moodle.~~org~~/plugins/~~view.php?plugin=~~tool_moodledt plugin entry] or [https://moodle.org/mod/forum/view.php?id=44 plugin forum]		Please for suggestion, use comments in [https://marketplace.moodle.com/plugins/tool_moodledt plugin entry] or [https://moodle.org/mod/forum/view.php?id=44 plugin forum]

plugins/tinymce tiny mce wiris

Gunjan Sarojwal — Mon, 10 Aug 2026 17:49:11 GMT

Updated links to Moodle Marketplace for plugins

← Older revision		Revision as of 17:49, 10 August 2026
Line 1:		Line 1:
	{{Infobox plugin		{{Infobox plugin
	\|type =rich text editor		\|type =rich text editor
	\|set=https://moodle.~~org~~/~~plugins/browse.php?list=set&id=66~~		\|set=https://marketplace.moodle.com/
	\|entry =		\|entry =
	https://moodle.~~org~~/plugins/filter_wiris, https://moodle.~~org~~/plugins/tinymce_tiny_mce_wiris		https://marketplace.moodle.com/plugins/filter_wiris, https://marketplace.moodle.com/plugins/tinymce_tiny_mce_wiris
	\|tracker = https://github.com/wiris/moodle-tinymce_tiny_mce_wiris/issues		\|tracker = https://github.com/wiris/moodle-tinymce_tiny_mce_wiris/issues
	\|discussion = https://moodle.~~org~~/plugins/tinymce_tiny_mce_wiris		\|discussion = https://marketplace.moodle.com/plugins/tinymce_tiny_mce_wiris
	\|maintainer = [[User:WIRIS team SUPPORT\|WIRIS team SUPPORT]]		\|maintainer = [[User:WIRIS team SUPPORT\|WIRIS team SUPPORT]]
	\|float = right		\|float = right
Line 17:		Line 17:
	WIRIS plugin for Moodle 2.X & Moodle 3.X contains two different components that '''should''' be separately downloaded and installed:		WIRIS plugin for Moodle 2.X & Moodle 3.X contains two different components that '''should''' be separately downloaded and installed:

	1- The [https://moodle.~~org~~/plugins/filter_wiris WIRIS filter] (this filter must be enabled at the end of the process)		1- The [https://marketplace.moodle.com/plugins/filter_wiris WIRIS filter] (this filter must be enabled at the end of the process)

	2- The [https://moodle.~~org~~/plugins/atto_wiris WIRIS plugin for Atto] / [https://moodle.~~org~~/plugins/tinymce_tiny_mce_wiris WIRIS plugin for TinyMCE] - Depending on your Moodle version and configuration you may install the WIRIS plugin for ATTO editor or a configured version of the WIRIS plugin for TinyMCE		2- The [https://marketplace.moodle.com/plugins/atto_wiris WIRIS plugin for Atto] / [https://marketplace.moodle.com/plugins/tinymce_tiny_mce_wiris WIRIS plugin for TinyMCE] - Depending on your Moodle version and configuration you may install the WIRIS plugin for ATTO editor or a configured version of the WIRIS plugin for TinyMCE
	Requirements		Requirements
	*mbstring extension must be installed and enabled in the server.		*mbstring extension must be installed and enabled in the server.
Line 29:		Line 29:
	==WIRIS filter installation (required)==		==WIRIS filter installation (required)==

	[https://moodle.~~org~~/plugins/filter_wiris WIRIS plugin filter ] for Moodle is a Moodle filter.		[https://marketplace.moodle.com/plugins/filter_wiris WIRIS plugin filter ] for Moodle is a Moodle filter.
	To begin, it is '''necessary''' to have it installed to use the WIRIS Editor.		To begin, it is '''necessary''' to have it installed to use the WIRIS Editor.

	Filter Installation:		Filter Installation:
	*[https://moodle.~~org~~/plugins/filter_wiris Download the WIRIS filter package]		*[https://marketplace.moodle.com/plugins/filter_wiris Download the WIRIS filter package]
	*copy the contents of [https://moodle.~~org~~/plugins/filter_wiris WIRIS filter package ] into the folder 'filter' under the root of Moodle.		*copy the contents of [https://marketplace.moodle.com/plugins/filter_wiris WIRIS filter package ] into the folder 'filter' under the root of Moodle.


Line 44:		Line 44:

	Plugin Installation:		Plugin Installation:
	*[https://moodle.~~org~~/plugins/tinymce_tiny_mce_wiris Download the WIRIS plugin for TinyMCE - Math & science package]		*[https://marketplace.moodle.com/plugins/tinymce_tiny_mce_wiris Download the WIRIS plugin for TinyMCE - Math & science package]
	*Copy the contents of [https://moodle.~~org~~/plugins/tinymce_tiny_mce_wiris WIRIS plugin for TinyMCE - Math & science package] into '''lib\editor\tinymce\plugins''', under the root of Moodle.		*Copy the contents of [https://marketplace.moodle.com/plugins/tinymce_tiny_mce_wiris WIRIS plugin for TinyMCE - Math & science package] into '''lib\editor\tinymce\plugins''', under the root of Moodle.

Moodle Workplace release notes

E milio — Mon, 10 Aug 2026 15:15:42 GMT

5.2.2

← Older revision		Revision as of 15:15, 10 August 2026
Line 131:		Line 131:
	* An issue causing the recertification scheduled task to fail on sites where course completion conditions had been modified after initial setup has been resolved. Affected users can now complete their recertifications without errors.		* An issue causing the recertification scheduled task to fail on sites where course completion conditions had been modified after initial setup has been resolved. Affected users can now complete their recertifications without errors.
	* An issue causing the completed course count shown in a program to be inconsistent with the actual number of courses completed by the user has been resolved.		* An issue causing the completed course count shown in a program to be inconsistent with the actual number of courses completed by the user has been resolved.

			== 5.2.2 ==
			Moodle Workplace 5.2.2 is built on top of Moodle LMS 5.2.2 and has all the new features of the core version. In addition, it contains all exclusive features from Moodle Workplace.

			== Bug fixes ==

			* Fixed an issue where course images could fail to load in the Learning Catalogue, and ensured these images are only served to users who are allowed to view the course.
			* Fixed an issue where course names using multi-language content showed the raw language tags instead of the translated name on the enrolment page.
			* Fixed an issue where a custom title on the Chart block was not displayed with its text formatting applied.
			* Fixed an issue where the Learning Catalogue category selector could not be scrolled on mobile or at high zoom levels, leaving some categories out of reach.
			* Hardened My Courses display preferences so the filter and sort settings only change through the intended actions, not by opening a link.
			* Program names are now safely escaped wherever they appear in the program content view.
			* Hardened custom page permission checks so access is always evaluated against the correct user.
			* Hardened the custom page audience form so it only accepts valid audience types.
			* Custom page configuration is now only returned to users who have access to that page.
			* Notifications sent to managers and department leads by dynamic rule actions now respect the recipient's 'Receive notifications' permission.

Moodle Workplace rolling release notes

E milio — Mon, 10 Aug 2026 15:14:58 GMT

5.2.2 rolling

← Older revision		Revision as of 15:14, 10 August 2026
Line 131:		Line 131:
	* An issue causing the recertification scheduled task to fail on sites where course completion conditions had been modified after initial setup has been resolved. Affected users can now complete their recertifications without errors.		* An issue causing the recertification scheduled task to fail on sites where course completion conditions had been modified after initial setup has been resolved. Affected users can now complete their recertifications without errors.
	* An issue causing the completed course count shown in a program to be inconsistent with the actual number of courses completed by the user has been resolved.		* An issue causing the completed course count shown in a program to be inconsistent with the actual number of courses completed by the user has been resolved.
			== 5.2.2 rolling ==
			Moodle Workplace rolling 5.2.2 is built on top of Moodle LMS 5.2.2 and has all the new features of the core version. In addition, it contains all exclusive features from Moodle Workplace.

			== Improvements ==

			* '''Improved tenant switch.''' Administrators who work across tenants can now switch between them from the user menu, keeping the primary navigation simpler and the switch easier to find.
			* '''Sort the Learning Catalogue.''' Learners can now sort catalogue items by newest, name, or price (where pricing is enabled), giving them more control over how courses and programs are ordered.
			* '''Tile and list views.''' Learners can switch the Learning Catalogue between a tile grid and a list layout, and their choice is remembered across sessions.
			* '''Improved category selector.''' The Learning Catalogue category selector has been rebuilt to be more accessible and easier to navigate by keyboard, on both desktop and mobile.
			* '''Tenant descriptions.''' Administrators can add a description to each tenant, making it easier for users to tell tenants apart when switching between them.
			* '''Tidier user menu for long tenant names.''' Long tenant names are now truncated in the user menu so they no longer stretch its width.

			== Bug fixes ==

			* Fixed an issue where course images could fail to load in the Learning Catalogue, and ensured these images are only served to users who are allowed to view the course.
			* Fixed an issue where course names using multi-language content showed the raw language tags instead of the translated name on the enrolment page.
			* Fixed an issue where a custom title on the Chart block was not displayed with its text formatting applied.
			* Hardened My Courses display preferences so the filter and sort settings only change through the intended actions, not by opening a link.
			* Program names are now safely escaped wherever they appear in the program content view.
			* Hardened custom page permission checks so access is always evaluated against the correct user.
			* Hardened the custom page audience form so it only accepts valid audience types.
			* Custom page configuration is now only returned to users who have access to that page.
			* Notifications sent to managers and department leads by dynamic rule actions now respect the recipient's 'Receive notifications' permission.

Antivirus plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 15:07:16 GMT

Updates on Moodle Marketplace Antivirus plugins

← Older revision		Revision as of 15:07, 10 August 2026
Line 3:		Line 3:

	{{Security}}		{{Security}}
	An administrator can enable and configure virus scanners for use on uploaded files ~~via ''Site administration > Plugins >~~ Antivirus plugins ~~> Manage antivirus plugins''~~.		An administrator can enable and configure virus scanners for use on uploaded files through Antivirus plugins available on [https://marketplace.moodle.com/ Moodle Marketplace]

	~~ClamAV antivirus is available as a standard plugin. It's likely that more antivirus plugins will be available in future from the [https://moodle.org/plugins/ Moodle plugins directory].~~		==Sophos SAV-DI antivirus==
			This plugin adds virus scanner support for the Sophos Anti-Virus Dynamic Interface (SAV-DI). The plugin supports the scanner daemon installed locally to the web server as well as remotely. It is available as Sophos SAV-DI antivirus.
	==~~ClamAV~~ antivirus==

	~~To make use of ClamAV antivirus, ClamAV® should be~~ installed ~~on your~~ server. ~~See http://www.clamav.net for more information~~.

	== See also ==		== See also ==
			[https://moodle.atlassian.net/wiki/external/YTI4MmY4MWU2MDQyNDk5MTllZWY4YTBiNjA5ZDRjNWY Moodle Marketplace documentation] (external link)

	* RHEL/CentOS and [https://en.wikipedia.org/wiki/Security-Enhanced_Linux SELinux]: https://moodle.org/mod/forum/discuss.php?d=316066
	* RHEL/CentOS and [https://access.redhat.com/blogs/766093/posts/1976243 PrivateTmp]: https://moodle.org/mod/forum/discuss.php?d=364706
	* Improve performance by using ClamDScan https://moodle.org/mod/forum/discuss.php?d=382731

	[[Category:Site administration]]		[[Category:Site administration]]

Workplace plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 14:46:32 GMT

Updates on Moodle Workplace plugins link in Moodle Marketplace and more

← Older revision		Revision as of 14:46, 10 August 2026
Line 6:		Line 6:
	Moodle Workplace has been built on top of Moodle LMS. Moodle Workplace contains all Moodle LMS features of the same version, that is, Moodle Workplace is always kept in sync with Moodle LMS.		Moodle Workplace has been built on top of Moodle LMS. Moodle Workplace contains all Moodle LMS features of the same version, that is, Moodle Workplace is always kept in sync with Moodle LMS.

	Like Moodle LMS, Moodle Workplace can be extended via plugins. While there is a high degree of compatibility between the Moodle LMS and Moodle Workplace, special consideration has to be given to some contributed plugins from [https://moodle.~~org~~/~~plugins Moodle LMS].~~		Like Moodle LMS, Moodle Workplace can be extended via plugins. While there is a high degree of compatibility between the Moodle LMS and Moodle Workplace, special consideration has to be given to some contributed plugins from [https://marketplace.moodle.com/?q=workplace Moodle Marketplace].

	Moodle ~~Workplace comprises a set of plugins, some of which are open-source and available in the plugin directory, for example~~
	* [https://moodle.org/plugins/mod_coursecertificate Workplace course certificate] and [https://moodle.org/plugins/tool_certificate Workplace certificate manager]
	* [https://moodle.org/plugins/block_rbreport Reporting block]
	* [https://moodle.~~org/plugins/tool_datewatch Date Watcher]~~
	* [[Workplace list course format]] (legacy plugin, no longer part of Workplace and not supported any more)


			Moodle Workplace comprises a [https://marketplace.moodle.com/user/1087 set of plugins], some of which are open-source and available in the plugin directory, for example:
			* [https://marketplace.moodle.com/plugins/mod_coursecertificate Workplace course certificate] and [https://marketplace.moodle.com/plugins/2233 Workplace certificate manager]
			* [https://marketplace.moodle.com/plugins/2793 Reporting block]
			* [https://marketplace.moodle.com/plugins/2517 Date Watcher]

	One of the plugins included in Moodle Workplace is the [[Workplace theme]]. Moodle Workplace sites must either use the Workplace theme or a custom theme that is a child theme thereof. An example of a child theme can be found at https://github.com/moodleworkplace/moodle-theme_wpchild.		One of the plugins included in Moodle Workplace is the [[Workplace theme]]. Moodle Workplace sites must either use the Workplace theme or a custom theme that is a child theme thereof. An example of a child theme can be found at https://github.com/moodleworkplace/moodle-theme_wpchild.
Line 30:		Line 27:

	=== Multitenancy ===		=== Multitenancy ===
	As a rule of thumb, Moodle LMS plugins work in Moodle Workplace if they don't collide with multi-tenancy. For example, activity modules are not affected by multi-tenancy and should work as-is. Authentication plugins should also work, but won't support multi-tenancy.		As a rule of thumb, Moodle LMS plugins work in Moodle Workplace if they don't collide with multi-tenancy. For example, activity modules are not affected by multi-tenancy and should work as-is. Authentication plugins should also work, but won't support multi-tenancy. The exceptions are Manual accounts, Email-based self-registration, OAuth 2, and SAML, which are already multi-tenancy-aware in Moodle Workplace.

	Below are some examples of core or standard plugins that had to be patched since they were breaking under multi-tenancy. Similar problems can occasionally be found in add-on plugins:		Below are some examples of core or standard plugins that had to be patched since they were breaking under multi-tenancy. Similar problems can occasionally be found in add-on plugins:
Line 40:		Line 37:


	'''Note''': Moodle Workplace relies on a separate group mode for separate users from different tenants in the shared courses. When installing add-on Activity module plugins the admins need to ensure that they either support separate group mode or do not expose the participant list.		'''Note''': Moodle Workplace relies on a separate group mode for separate users from different tenants in the shared courses. When installing add-on Activity module plugins the admins need to ensure that they either support separate group mode or do not expose the participant list. By default, tenants are fully isolated from one another, including this kind of participant visibility, but administrators can choose to enable cross-tenant sharing, for example allowing users to see people from other tenants in forum posts, course participant lists, gradebooks, and reports. Plugin developers should account for this configurable exception rather than assuming isolation always holds.

	An example of Moodle repository with lightweight multitenancy implementation is located on [https://github.com/moodleworkplace/multitenancy GitHub], it can be used for testing plugin multitenancy support, there is also an [https://github.com/moodleworkplace/moodle-local_tenantexample example of plugin] that supports multitenancy (as of 06/24 this is outdated, but still useful as reference, we endeavour to update it). Developers may find useful a ~~recoded~~ session [https://www.youtube.com/watch?v=sCwa755F8-o "Multi tenancy - Overview & Introduction for Plugin Developers"] from MoodleMoot India 2020 that explains use of this multitenancy support testing setup.		An example of Moodle repository with lightweight multitenancy implementation is located on [https://github.com/moodleworkplace/multitenancy GitHub], it can be used for testing plugin multitenancy support, there is also an [https://github.com/moodleworkplace/moodle-local_tenantexample example of plugin] that supports multitenancy (as of 06/24 this is outdated, but still useful as reference, we endeavour to update it). Developers may find a useful a recorded session [https://www.youtube.com/watch?v=sCwa755F8-o "Multi tenancy - Overview & Introduction for Plugin Developers"] from MoodleMoot India 2020 that explains use of this multitenancy support testing setup.
	[[Category:Workplace]]		[[Category:Workplace]]

Installing plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 12:15:32 GMT

← Older revision		Revision as of 12:15, 10 August 2026
(One intermediate revision by the same user not shown)
Line 10:		Line 10:
	==Choosing the best plugins for your site==		==Choosing the best plugins for your site==

	~~Note: It is recommended that you proceed with caution~~ and ~~always try installing these~~ plugins on a ~~test server~~ before ~~installing~~ them in a production ~~server~~.		Install and test plugins in a non-production environment before using them on a production site.

	* ~~From the [https://moodle.org/plugins~~ Moodle ~~plugins directory] you can sort plugins by~~, ~~for example, [https://moodle.org/plugins/index.php/?q=sort-by:sites plugins used by the largest number of sites], or [https://moodle.org/plugins/index.php/?q=sort-by:release recently~~ updated ~~plugins]. Use the 'Sort by'~~ to ~~help you identify reliable plugins. (Note that the number of downloads isn't necessarily a good indicator of a plugin's quality, as this can~~ be ~~falsified.)~~		When choosing a plugin in Moodle Marketplace:
	* ~~When viewing plugins, scroll down to~~ its Awards section. Does it have the [https://moodle.org/plugins/browse.php?list=award&id=11 Privacy friendly award]? Does it have the [https://moodle.org/plugins/browse.php?list=award&id=6 Mobile app award?]
	* ~~You can test and try more than 50 of the most popular Moodle plugins at [http://plugins.moodlebites.com plugins.moodlebites.com]~~		* check that it supports your Moodle version
			* review its description, documentation and installation requirements
			* check when it was last updated and whether it appears to be actively maintained
			* review its support information
			* check whether it requires an external service, license or additional payment

	===Plugins for school teaching===		===Plugins for school teaching===
Line 31:		Line 35:
	== Considerations for production sites (skip if you're just moodling) ==		== Considerations for production sites (skip if you're just moodling) ==

	'''VERY IMPORTANT''' ~~Warning: Please be aware that some~~ plugins have not been reviewed~~, and the~~ quality ~~and/~~or suitability for your Moodle site ~~has not been checked. Please be careful. It~~ may not ~~do what you expect~~, ~~it may have serious~~ security issues ~~or it may even not work at all~~. This is ~~however~~ improving ~~over time with~~ the ~~evolving new plugins directory system~~.		'''VERY IMPORTANT!'''

			'''Some plugins in the directory have not been reviewed for quality or suitability for your Moodle site, so please use discretion when installing them because a plugin may not behave as expected, and in rare cases could introduce security issues. This is improving as the Moodle Marketplace evolves.'''

	* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time.		* If you have a large site for production purposes consider if you '''really''' need the plugin? More functionality means more things to support, more things to (potentially) go wrong and more things to worry about at upgrade time.
	* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?		* Is the plugin supported and maintained? If something goes wrong can you get support? Will bugs be fixed?
	* If the plugin does not work in a future version of Moodle, what will you do about it?		* If the plugin does not work in a future version of Moodle, what will you do about it?
	* Beware of ''patches'' ([https://moodle.org/plugins/browse.php?list=category&id=38 Moodle Plugins Directory Other category]) ! If a plugin modifies or replaces core files then be very careful. It can only be guaranteed to work with the exact build (version) of Moodle it was created for and is highly unlikely to survive a Moodle upgrade.
	* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.		* Look at [https://moodle.org/mod/forum/discuss.php?d=340821#p1373707 this] and [https://moodle.org/mod/forum/discuss.php?d=346296 also this] forum threads of users worried about installing a plugin.

Line 42:		Line 47:
	{{MediaPlayer \| url = https://youtu.be/p2FDsAiwGpA?feature=shared \| desc = Installing plugins from admin interface}}		{{MediaPlayer \| url = https://youtu.be/p2FDsAiwGpA?feature=shared \| desc = Installing plugins from admin interface}}

	To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. ~~There are three ways how the~~ plugin ~~code can be deployed into Moodle.~~		To install a plugin, its source code must be put (deployed) into the appropriate location inside the Moodle installation directory and the main administration page ''Administration > Site administration > Notifications'' must be visited. You can deploy a plugin by:

	~~Plugin code may be deployed from within Moodle, either directly from the Moodle plugins directory or by~~ uploading a ZIP file~~. The web server process has to have write access to~~ the plugin ~~type folder where~~ the ~~new~~ plugin is to ~~be installed in order to use either of these methods.~~		* uploading a plugin ZIP file through the Moodle administration interface
			* installing a compatible plugin with Composer, if your Moodle site is Composer-managed
			* copying the plugin files to the server manually

	~~Alternatively~~, ~~a plugin may be deployed manually at~~ the server.		To upload a ZIP file through the administration interface, the web server process must have write access to the relevant plugin-type directory.

	{{Note\|Whenever you install or download a plugin from the Moodle plugins directory, it is extremely important that you have correctly chosen your [[Moodle version]]. If you mistakenly download and install the wrong version of a plugin for your Moodle server, this may lead to some serious problems, even freezing of the Moodle site.}}		{{Note\|Whenever you install or download a plugin from the Moodle plugins directory, it is extremely important that you have correctly chosen your [[Moodle version]]. If you mistakenly download and install the wrong version of a plugin for your Moodle server, this may lead to some serious problems, even freezing of the Moodle site.}}

	~~===Installing directly from the Moodle plugins directory===~~

	~~# Login as an admin and go to ''Site administration > Plugins > Install plugins''. (If you can't find this location, then plugin installation is prevented on your site.)~~
	~~# Click the button 'Install plugins from Moodle plugins directory'.~~
	~~# Select your current [[Moodle version]], then search for a plugin with an Install button, click the Install button, then click Continue.~~
	~~# Confirm the installation request~~
	~~# Check the plugin validation report~~

	=== Installing plugins with Composer (Packagist) ===		=== Installing plugins with Composer (Packagist) ===
Line 105:		Line 104:
	===Installing via uploaded ZIP file===		===Installing via uploaded ZIP file===

	# Go to the ~~[https://moodle.org/plugins~~ Moodle ~~plugins directory]~~, select your current [[Moodle version]], then ~~choose a plugin with a Download button~~ and download the ZIP file.		# Go to the Moodle Marketplace, select your current [[Moodle version]], then Sign in and download the appropriate plugin version as a ZIP file.
	# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.		# Login to your Moodle site as an admin and go to ''Administration > Site administration > Plugins > Install plugins''.
	# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.		# Upload the ZIP file. You should only be prompted to add extra details (in the Show more section) if your plugin is not automatically detected.
Line 151:		Line 150:
	===A file permissions error has occurred===		===A file permissions error has occurred===

	On certain 3.0.x versions, when installing plugins via the administration interface, ~~the~~ Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).		On certain 3.0.x versions, when installing plugins via the administration interface, Moodle uses the configuration settings <tt>$CFG->directorypermissions</tt> and <tt>$CFG->filepermissions</tt>. If these are not defined explicitly in your config.php, the default value is set automatically to 777 (rwxrwxrwx) for directories and 666 (rw-rw-rw-) for files (see lib/setup.php).

	If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as		If this default behaviour does not fit your needs and hosting environment, you may wish to specify more strict setting such as
Line 169:		Line 168:
	* Check the file permissions. The web server needs to be able to read the plugin files. If the rest of Moodle works then try to make the plugin permissions and ownership match.		* Check the file permissions. The web server needs to be able to read the plugin files. If the rest of Moodle works then try to make the plugin permissions and ownership match.
	* Did you '''definitely''' unzip or install the plugin in the correct place?		* Did you '''definitely''' unzip or install the plugin in the correct place?
	* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you ~~deleted~~ the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.		* Because Moodle scans plugin folders for new plugins you cannot have any other files or folders there. Make sure you delete the zip file and don't try to rename (for example) an old version of the plugin to some other name - it will break.
	* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.		* Make sure the directory name for the plugin is correct. All the names '''have''' to match. If you change the name, then it won't work.

Line 207:		Line 206:

	==See also==		==See also==
	* [https://moodle.org/mod/forum/discuss.php?d=325804 list of (year 2015) favorite plugins] by Gavin Henrick
	* [[Notifications]] for further details of update notifications		* [[Notifications]] for further details of update notifications
	* [[Plugin Review Criteria]]		* [[Plugin Review Criteria]]

Workplace plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 06:19:04 GMT

← Older revision		Revision as of 06:19, 10 August 2026
Line 1:		Line 1:
			{{Update}}
			{{Note\|1=This page is currently being updated to reflect the launch of [https://marketplace.moodle.com Moodle Marketplace], which replaces the Moodle plugins directory referenced throughout this page. Please check back soon for updated instructions.}}

	{{Workplace}}		{{Workplace}}
	{{Target Audience\|Administrators}}		{{Target Audience\|Administrators}}

Translating plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 06:18:05 GMT

← Older revision		Revision as of 06:18, 10 August 2026
Line 1:		Line 1:
			{{Update}}
			{{Note\|1=This page is currently being updated to reflect the launch of [https://marketplace.moodle.com Moodle Marketplace], which replaces the Moodle plugins directory referenced throughout this page. Please check back soon for updated instructions.}}

	{{Translation}}		{{Translation}}

Antivirus plugins

Gunjan Sarojwal — Mon, 10 Aug 2026 06:17:20 GMT

← Older revision		Revision as of 06:17, 10 August 2026
Line 1:		Line 1:
			{{Update}}
			{{Note\|1=This page is currently being updated to reflect the launch of [https://marketplace.moodle.com Moodle Marketplace], which replaces the Moodle plugins directory referenced throughout this page. Please check back soon for updated instructions.}}

	{{Security}}		{{Security}}
	An administrator can enable and configure virus scanners for use on uploaded files via ''Site administration > Plugins > Antivirus plugins > Manage antivirus plugins''.		An administrator can enable and configure virus scanners for use on uploaded files via ''Site administration > Plugins > Antivirus plugins > Manage antivirus plugins''.

Plugins FAQ

Gunjan Sarojwal — Mon, 10 Aug 2026 06:16:24 GMT

← Older revision		Revision as of 06:16, 10 August 2026
Line 1:		Line 1:
			{{Update}}
			{{Note\|1=This page is currently being updated to reflect the launch of [https://marketplace.moodle.com Moodle Marketplace], which replaces the Moodle plugins directory referenced throughout this page. Please check back soon for updated instructions.}}

	{{Installing Moodle}}==What is a plugin?==		{{Installing Moodle}}==What is a plugin?==

Step-by-step Installation Guide for Ubuntu

Steerpike — Sun, 09 Aug 2026 02:22:38 GMT

Replace call to r.php

Show changes

Catalogue

Openumlaut — Fri, 07 Aug 2026 04:22:01 GMT

← Older revision		Revision as of 04:22, 7 August 2026
(One intermediate revision by the same user not shown)
Line 20:		Line 20:
	* The '''catalogue search''' lets you narrow down the search using Moodle’s standard search operators. Once executed, the results page will be displayed.		* The '''catalogue search''' lets you narrow down the search using Moodle’s standard search operators. Once executed, the results page will be displayed.
	* The '''item cards''' show details about each course or program. The attributes displayed, depend on the [[Catalogue#Learning catalogue settings\|learning catalogue settings]].		* The '''item cards''' show details about each course or program. The attributes displayed, depend on the [[Catalogue#Learning catalogue settings\|learning catalogue settings]].
			* The '''sorting selector''' lets you order the shown items by the selected sort criterion. Details, see on the results page, below.
			* The '''card/list view toggle''' lets you switch between tile and list layouts.
	* The main page is divided into up to 2 sections:		* The main page is divided into up to 2 sections:
	** '''Featured learning''': Selected courses and programs you wish to promote or highlight appear at the top of the catalogue		** '''Featured learning''': Selected courses and programs you wish to promote or highlight appear at the top of the catalogue
Line 38:		Line 40:
	* The '''category selector''' lets you choose a single category or sub-category. Once selected, the results page will be refreshed.		* The '''category selector''' lets you choose a single category or sub-category. Once selected, the results page will be refreshed.
	* The '''catalogue search''' lets you narrow down the search using Moodle’s standard search operators. Once executed, the results page will be displayed.		* The '''catalogue search''' lets you narrow down the search using Moodle’s standard search operators. Once executed, the results page will be displayed.
			* The '''sorting selector''' lets you order the shown items by the selected sort criterion. The dropdown appears in all the catalogue pages and always includes the following options:
			** '''Newest first''': sorts items from newest to oldest.
			** '''Name (A-Z)''': sorts items alphabetically from A to Z. The following sorting options are restricted to some conditions:
			** '''Price (Low to High)''': sorts items from cheapest (free being the cheapest price) to more expensive. It only appears if the catalogue setting <code>pricecustomfield</code> is configured with a custom field (see [[Catalogue Configuration#Payment Support\|Payment support]] for details).
			** '''Relevance''': sorts items based on how well they match the search term, using the priority defined in the “Fields to search for keywords” setting. This option is only available when a catalogue search is active.
			* The '''card/list view toggle''' lets you switch between tile and list layouts.
	* The '''item cards''' show details about each course. The attributes shown, depend on the [[Catalogue#Learning catalogue settings\|learning catalogue settings]].		* The '''item cards''' show details about each course. The attributes shown, depend on the [[Catalogue#Learning catalogue settings\|learning catalogue settings]].
	* The filter lets you narrow down the shown results further. There are up to three types of filters that will be displayed:		* The filter lets you narrow down the shown results further. There are up to three types of filters that will be displayed:

File:Learning Catalogue - Main Page.png

Openumlaut — Fri, 07 Aug 2026 04:19:32 GMT

Alex Büchner 2 deleted page File:Learning Catalogue - Main Page.png Deleted old revision 20260807041918!Learning_Catalogue_-_Main_Page.png: content was: "Learning Catalogue - Main Page", and the only contributor was "Openumlaut" (talk)

File:Learning Catalogue - Main Page.png

Openumlaut — Fri, 07 Aug 2026 04:19:18 GMT

Alex Büchner 2 uploaded a new version of File:Learning Catalogue - Main Page.png

New page

Learning Catalogue - Main Page

File:Learning Catalogue - Results Page.png

Openumlaut — Fri, 07 Aug 2026 04:19:02 GMT

Alex Büchner 2 uploaded a new version of File:Learning Catalogue - Results Page.png

New page

Learning Catalogue - Results Page

File:Learning Catalogue - Main Page.png

Openumlaut — Fri, 07 Aug 2026 03:57:41 GMT

Alex Büchner 2 uploaded a new version of File:Learning Catalogue - Main Page.png

New page

Learning Catalogue - Main Page

Site details & registration

Openumlaut — Thu, 06 Aug 2026 08:36:56 GMT

← Older revision		Revision as of 08:36, 6 August 2026
(One intermediate revision by the same user not shown)
Line 10:		Line 10:

	* '''Workplace version''': Installed version including build		* '''Workplace version''': Installed version including build
			* '''Support information''': The dates shown indicate how long general core bug fixes and security updates will be provided for this release. For more information about Moodle Workplace release cycles and end-of-life dates, see https://moodledev.io/general/workplace/releases
	* '''Active users''': Number of users who have logged in to the site in the last 12 months		* '''Active users''': Number of users who have logged in to the site in the last 12 months
	* '''Site environment''': '''Production site''' or '''Non-production site'''		* '''Site environment''': '''Production site''' or '''Non-production site'''

File:Site details.png

Openumlaut — Thu, 06 Aug 2026 08:32:05 GMT

Alex Büchner 2 uploaded a new version of File:Site details.png

New page

Site details

Multi-tenancy Configuration

Openumlaut — Thu, 06 Aug 2026 08:11:57 GMT

Added tenant description field

← Older revision		Revision as of 08:11, 6 August 2026
Line 18:		Line 18:
	*'''Tenant name''' (Required): Name of the tenant. This is the name of the tenant. While multiple tenants can share the same name, it is advisable to use distinct names for different tenants.		*'''Tenant name''' (Required): Name of the tenant. This is the name of the tenant. While multiple tenants can share the same name, it is advisable to use distinct names for different tenants.
	*'''Site name''' and '''Site short name''': These are essentially the full site name and the short name used in the site settings for the front page, found under '''Site administration > Front page settings'''. Once a tenant is active (either by selecting it via the tenant switcher or when a user belongs to a tenant), the tenant settings will override the site settings. The site shortname will be displayed in the header if the field 'Header logo' (in the [[Multi-tenancy Configuration#Tenant Branding\|tenant branding configuration]]) is left empty.		*'''Site name''' and '''Site short name''': These are essentially the full site name and the short name used in the site settings for the front page, found under '''Site administration > Front page settings'''. Once a tenant is active (either by selecting it via the tenant switcher or when a user belongs to a tenant), the tenant settings will override the site settings. The site shortname will be displayed in the header if the field 'Header logo' (in the [[Multi-tenancy Configuration#Tenant Branding\|tenant branding configuration]]) is left empty.
			*'''Description:''' A descriptive summary of the tenant's purpose.
	*'''ID number''': This is a unique identifier for your tenant. It is used when uploading users via the upload user tool or connecting to external systems through web services, as well as in the login URL. Two HTML data attributes, <code>[data-tenantid="{tenant_id}"]</code> and <code>[data-tenantidnumber="{tenant_idnumber}"]</code>, help customize styles for specific tenants. However, the tenant ID number must be specified for these attributes to function.		*'''ID number''': This is a unique identifier for your tenant. It is used when uploading users via the upload user tool or connecting to external systems through web services, as well as in the login URL. Two HTML data attributes, <code>[data-tenantid="{tenant_id}"]</code> and <code>[data-tenantidnumber="{tenant_idnumber}"]</code>, help customize styles for specific tenants. However, the tenant ID number must be specified for these attributes to function.
	*'''Login URL''': There are two options for accessing the login directly: one includes the ID number, and the other uses an internal numeric tenant ID (the default tenant always has ID=1 and cannot be changed). The internal tenant ID is not available during tenant creation, so the login URLs are displayed as tenantid={ID} and tenant={IDNUMBER}, respectively		*'''Login URL''': There are two options for accessing the login directly: one includes the ID number, and the other uses an internal numeric tenant ID (the default tenant always has ID=1 and cannot be changed). The internal tenant ID is not available during tenant creation, so the login URLs are displayed as tenantid={ID} and tenant={IDNUMBER}, respectively

File:Multi-tenancy - New tenant.png

Openumlaut — Thu, 06 Aug 2026 08:06:57 GMT

Alex Büchner 2 uploaded a new version of File:Multi-tenancy - New tenant.png

New page

Multi-tenancy - New tenant

Moodle app security

Jleyva — Wed, 05 Aug 2026 08:35:47 GMT

← Older revision		Revision as of 08:35, 5 August 2026
Line 84:		Line 84:
	* Automated vulnerability alerts surfaced through GitHub (Dependabot and code scanning), which we monitor and action on an ongoing basis as part of our standard development workflow.		* Automated vulnerability alerts surfaced through GitHub (Dependabot and code scanning), which we monitor and action on an ongoing basis as part of our standard development workflow.
	* Use of npm audit before every new release to ensure there are no third-party libraries with known security issues affecting the app		* Use of npm audit before every new release to ensure there are no third-party libraries with known security issues affecting the app

			== SCA frequency and remediation SLA ==

			* Software Composition Analysis (SCA) via ''npm audit'' is run automatically as part of the CI/CD pipeline before every app release.
			* In addition, GitHub Dependabot continuously scans the repository between releases and raises alerts for newly disclosed CVEs in dependencies.
			* Remediation SLA: Critical severity findings are fixed within 2 business days, High severity fixed within 4 business days; either through a dependency update or a documented compensating control if no upstream fix is available yet.
			* Confirmed critical/high findings are treated under our standard [[Moodle app security#What is the Moodle app security issues process?\|security issues process]], which can trigger an emergency release outside the normal schedule.

	[[es:Seguridad de Moodle app]]		[[es:Seguridad de Moodle app]]
	[[de:Moodle App - Sicherheit]]		[[de:Moodle App - Sicherheit]]