https://docs.moodle.org/34/en/api.php?action=feedcontributions&user=Marina.glancy&feedformat=atomMoodleDocs - User contributions [en]2024-03-28T09:25:59ZUser contributionsMediaWiki 1.39.6https://docs.moodle.org/34/en/index.php?title=GDPR&diff=130974GDPR2018-05-17T03:27:15Z<p>Marina.glancy: /* Latest News & Updates */</p>
<hr />
<div><div class="navtrail">[[Main page]] ► [[GDPR]]</div><br />
<div class="sideblock right" style="width: 16em;"> <br />
<div class="header">[[GDPR]]</div> <br />
<div class="content"><br />
</div><br />
* [[GDPR for administrators|GDPR for admins]]<br />
* [[Policies plugin]]<br />
* [[Data privacy plugin]]<br />
* [[GDPR FAQ]]<br />
</div><br />
<br />
== Overview ==<br />
<br />
GDPR stands for General Data Protection Regulation and refers to the European Union regulation for data protection for all individuals within the European Union. The regulation (Regulation (EU) 2016/679)[[#ref2|2]] becomes enforceable on 25 May 2018 and replaces the data protection directive (officially Directive 95/46/EC)[[#ref3|3]] from 1995.<br />
<br />
===Who does it affect?===<br />
<br />
Any individual or organisation that stores or processes personal information on an identifiable person from an EU member state (regardless if the processing or storage of information occurs in the EU or not). It also applies if the individual or organisation themselves is located in an EU member state.<br />
<br />
===What kind of information comprises personal data in a Moodle site?===<br />
<br />
It is all information that can be associated with a natural person. Each user account and all the activity associated with that user account is classified as personal information. This also extends to associated information such as web server log files.<br />
<br />
===How is Moodle HQ assisting with GDPR compliance?===<br />
<br />
Earlier this year we reached out to the community through our forums and social media to gauge the needs of different organisations on how they would need to comply with GDPR. We received direct input from a number of Moodle institutions, our Moodle Partner network and developers.<br />
<br />
We have a plan to meet those needs and are scheduling the development within our Open Source team under the lead of Sander Bangma, our Open Source Development Coordinator.<br />
The plan involves the development of a set of features (made available through plugins and some minimal changes to core) which will assist Moodle sites meeting GDPR compliance needs. The features cover the following areas: <br />
<br />
* Onboarding of new users, including; age and location check to identify minors, versioning of privacy policies and the tracking of user consents;<br />
* Handling of subject access requests and erasure requests, and maintaining a data registry.<br />
<br />
[https://moodle.com/news/moodle-gdpr-approach-plan/ Find out more about our plan.]<br />
<br />
'''Important note:''' Installing the developed plugins alone will not be enough to meet the GDPR requirements. Correct configuration and implementation of the required processes and procedures is also required. <br />
<br />
We at Moodle HQ highly recommend that you also engage your IT and legal departments on what is required for GDPR compliance.<br />
<br />
====GDPR plugins====<br />
<br />
* [[Policies plugin]] - requires Moodle 3.4.2 onwards, and will be included as standard in Moodle 3.5<br />
* [[Data privacy plugin]] - also requires Moodle 3.4.2 onwards, and will be included as standard in Moodle 3.5<br />
<br />
==GDPR for Moodle administrators==<br />
<br />
If you are a Moodle system administrator and have a Moodle site older than the 3.3.5 or 3.4.2 version, or have a site that is not affected by GDPR but would still like to do as much as possible towards compliance, we recommend you read our [https://docs.moodle.org/34/en/GDPR_for_administrators “GDPR for Moodle Administrators”] guide. <br />
<br />
If you are on Moodle 3.4.2 version and above, please refer to our [https://docs.moodle.org/34/en/GDPR_for_administrators_(Moodle_3.4.2%2B) “GDPR for Moodle Administrators (Moodle 3.4.2+)”] guide for information on GDPR functionalities that have been released recently and continuing to develop.<br />
<br />
==Moodle & GDPR for plugin developers==<br />
<br />
If you are a plugin developer, we recommend the following actions to assist you in preparing your Moodle plugin for GDPR:<br />
<br />
* please read through our spec documentation [[:dev:GDPR for plugin developers|GDPR for plugin developers]] in the dev docs and,<br />
* join the discussion [https://moodle.org/mod/forum/discuss.php?d=352538 EU General Data Protection Regulation (GDPR) compliance.]<br />
<br />
==Moodle & GDPR for Educators & Learners==<br />
<br />
If you are an educator or a learner and would like to find out more about your rights under GDPR and how features in Moodle can assist with protecting your data privacy, we recommend you:<br />
<br />
* Check in with your system administrators for information specific to your institution or organisation; <br />
* Read more information on GDPR in the “See also” section below. <br />
<br />
==Latest News & Updates==<br />
<br />
* [https://moodle.org/mod/forum/discuss.php?d=367522#p1482337 Data Privacy and Policy plugins to support GDPR compliance now available]<br />
<br />
==See also==<br />
<br />
* [[GDPR FAQ]]<br />
<br />
References:<br />
<br />
* [https://www.eugdpr.org/ Home Page of EU GDPR]<br />
* [http://data.consilium.europa.eu/doc/document/ST-5419-2016-INIT/en/pdf GDPR Regulation]<br />
* [http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:31995L0046 Directive 95/46/EC]<br />
* [https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/ Guide to the General Data Protection Regulation (GDPR)] from the UK's Information Commissioner's Office<br />
<br />
[[Category:GDPR]]<br />
<br />
[[es:GDPR]]<br />
[[fr:RGPD]]<br />
[[de:DSGVO]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=admin/tool/policy/view&diff=130559admin/tool/policy/view2018-03-27T06:36:07Z<p>Marina.glancy: Redirected page to Policies</p>
<hr />
<div>#redirect [[Policies]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=admin/tool/policy/index&diff=130558admin/tool/policy/index2018-03-27T06:35:40Z<p>Marina.glancy: Redirected page to Policies</p>
<hr />
<div>#redirect [[Policies]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=admin/tool/policy/editpolicydoc&diff=130556admin/tool/policy/editpolicydoc2018-03-27T06:04:09Z<p>Marina.glancy: Redirected page to Policies</p>
<hr />
<div>#redirect [[Policies]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=admin/tool/policy/acceptances&diff=130555admin/tool/policy/acceptances2018-03-27T06:03:22Z<p>Marina.glancy: Redirected page to Policies</p>
<hr />
<div>#redirect [[Policies]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=admin/tool/policy/managedocs&diff=130554admin/tool/policy/managedocs2018-03-27T06:02:51Z<p>Marina.glancy: Redirected page to Policies</p>
<hr />
<div>#redirect [[Policies]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/tool/policy:acceptbehalf&diff=130553Capabilities/tool/policy:acceptbehalf2018-03-27T06:00:26Z<p>Marina.glancy: Created page with "{{Capabilities}} * This allows a user to Agree to the policies on someone else's behalf * This capability is allowed for the default role of manager only * It may..."</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to Agree to the [[Policies|policies]] on someone else's behalf<br />
* This capability is allowed for the default role of manager only<br />
* It may be applied in the system context i.e. as a global role<br />
* This capability may also be applied in the user context, usually as part of a Parent role<br />
<br />
[[Category:Capabilities]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/tool/policy:viewacceptances&diff=130552Capabilities/tool/policy:viewacceptances2018-03-27T05:56:38Z<p>Marina.glancy: Created page with "{{Capabilities}} * This allows a user to View user agreement reports in policies plugin * This capability is allowed for the default role of manager only * It may..."</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to View user agreement reports in [[Policies|policies]] plugin<br />
* This capability is allowed for the default role of manager only<br />
* It may only be applied in the system context i.e. as a global role<br />
<br />
[[Category:Capabilities]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/tool/policy:manageprivacy&diff=130551Capabilities/tool/policy:manageprivacy2018-03-27T05:55:56Z<p>Marina.glancy: Created page with "{{Capabilities}} * This allows a user to Manage privacy settings used in policies plugin * This capability is allowed for the default role of manager only * It ma..."</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to Manage privacy settings used in [[Policies|policies]] plugin<br />
* This capability is allowed for the default role of manager only<br />
* It may only be applied in the system context i.e. as a global role<br />
<br />
[[Category:Capabilities]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/tool/policy:managedocs&diff=130550Capabilities/tool/policy:managedocs2018-03-27T05:54:23Z<p>Marina.glancy: Created page with "{{Capabilities}} * This allows a user to Manage policies * This capability is allowed for the default role of manager only * It may only be applied in the system..."</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to Manage [[Policies|policies]]<br />
* This capability is allowed for the default role of manager only<br />
* It may only be applied in the system context i.e. as a global role<br />
<br />
[[Category:Capabilities]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/tool/policy:accept&diff=130549Capabilities/tool/policy:accept2018-03-27T05:51:01Z<p>Marina.glancy: Created page with "{{Capabilities}} * This allows a user to Agree to the policies * This capability is allowed by default to authenticated users * New roles prohibiting this capabil..."</p>
<hr />
<div>{{Capabilities}}<br />
* This allows a user to Agree to the [[Policies|policies]]<br />
* This capability is allowed by default to authenticated users<br />
* New roles prohibiting this capability can be created and assigned to children who are below age of digital consent, in this case privacy manager or parent will have to agree to policies on their behalf<br />
<br />
[[Category:Capabilities]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Policies&diff=130548Policies2018-03-27T05:45:19Z<p>Marina.glancy: Created page with "''Watch this space...''"</p>
<hr />
<div>''Watch this space...''</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=GDPR_for_administrators_(Moodle_3.4.2%2B)&diff=130547GDPR for administrators (Moodle 3.4.2+)2018-03-27T05:00:26Z<p>Marina.glancy: </p>
<hr />
<div>{{GDPR}}<br />
<br />
==Plugins==<br />
<br />
Two GDPR plugins are available on the plugin database for adding GDPR functionality to Moodle 3.4.2 or 3.3.5 sites. The plugins will continue to be updated and refined over the next few weeks.<br />
<br />
The '''[https://moodle.org/plugins/tool_policy Policies plugin]''' provides a new user sign on process, with ability to define multiple policies (site, privacy, third party), track user consents, and manage updates and versioning of the policies.<br />
<br />
The '''[https://moodle.org/plugins/tool_dataprivacy Data privacy plugin]''' provides the workflow for users to submit subject access requests and for site administrators and privacy officers to process these requests. The subject access request process currently retrieves the user information from the following core plugins:<br />
<br />
* Choice Activity Module<br />
* HTML Block<br />
* User Tours<br />
<br />
Support for retrieving user information from the remaining core plugins will be added soon. The plugin will also be further extended to include functionality for data erasure requests and the data registry to define a purpose and retention period for data stored in a Moodle site.<br />
<br />
User documentation for both the Policy and Data Privacy plugins will be available soon. <br />
<br />
==Core changes==<br />
<br />
Moodle 3.4.2 and 3.3.5 include the following core API changes that are required to support the GDPR plugins:<br />
<br />
* An age and location check to identify minors<br />
* The API to request personal data from all plugins<br />
* Implementation of the API for a subset of Moodle core plugins so far<br />
<br />
Those wanting to explore and use the new plugins should therefore upgrade to either Moodle 3.4.2 or 3.3.5. All GDPR functionality will be integrated in the Moodle 3.5 release.<br />
<br />
''More information coming soon...''<br />
<br />
<br />
[[es:GDPR para administradores (Moode 3.4.2+]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=File:Backup_publication.png&diff=129557File:Backup publication.png2017-11-29T02:11:03Z<p>Marina.glancy: Marina.glancy uploaded a new version of File:Backup publication.png</p>
<hr />
<div></div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=File:published_on_list.png&diff=129556File:published on list.png2017-11-29T02:09:03Z<p>Marina.glancy: Marina.glancy uploaded a new version of File:published on list.png</p>
<hr />
<div></div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Site_registration&diff=129555Site registration2017-11-29T01:49:23Z<p>Marina.glancy: /* 5 reasons to register */</p>
<hr />
<div>{{Managing a Moodle site}}<br />
__NOTOC__<br />
[[File:Boost-Moodle-Registrations.jpg]]<br />
==Why register my site?==<br />
Registering your site gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.<br />
<br />
==5 reasons to register==<br />
# Stay up to date by email whenever there are new releases of Moodle or security alerts. <br />
# Be part of the [https://moodle.net/stats/ statistics of the worldwide community]. <br />
# List your site on our [https://moodle.net/sites/ list of registered sites in your country]. (But if you want to keep it private, that’s fine too!)<br />
# [[Course sharing|Share your courses]] on Moodle.net<br />
# Make use of the messaging server https://messages.moodle.net/ for [[Mobile app notifications|Moodle mobile push notifications]].<br />
<br />
==How about security?==<br />
We don’t share your information with anyone. We don’t go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.<br />
<br />
==How do I register?==<br />
Register your site by logging in as an administrator and going to ''Site administration > Registration''. If you’re not the admin, ask them nicely to check!<br />
<br />
==I don’t want my details public==<br />
Your registration is private to us unless you choose to make it public.<br />
<br />
==Do I have to register? What happens if I don’t?==<br />
Registration is optional, but we wouldn’t want you to miss out on any important security issues or upgrades and put your site at risk. <br />
<br />
The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. <br />
<br />
So registering is a win-win for you as well as for us.<br />
<br />
==I can’t register my site!==<br />
Only sites which are online can be registered. If your site is online and you have problems registering or updating your registration, please email [mailto:support@moodle.org support@moodle.org].<br />
<br />
Note that it can take a while before your site is listed on https://moodle.net/sites/ so please be patient.<br />
<br />
[[Category:Site administration]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja: サイト登録]]<br />
[[de:Moodle-Site registrieren]]<br />
[[es:Registro del sitio]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Community_hubs&diff=129554Community hubs2017-11-29T01:44:12Z<p>Marina.glancy: </p>
<hr />
<div>{{Managing a Moodle site}}<br />
{{Note|In Moodle 3.4 onwards, registration with custom community hubs has been removed from Moodle core. Custom hubs can still be created using the local_hub plugin and Moodle 3.4 sites wanting to register with a custom community hub need to install additional plugins.}}<br />
<br />
==Registering with a custom community hub==<br />
<br />
To register with [https://moodle.net Moodle.net], please see [[Site registration]].<br />
<br />
In Moodle 3.4 onwards, registration with custom community hubs has been removed from Moodle core. Moodle 3.4 sites wanting to register with a custom community hub need to install the following plugins:<br />
<br />
* [https://github.com/moodlehq/moodle-tool_customhub tool_customhub] for registration and course publishing<br />
* [https://github.com/moodlehq/moodle-block_customhub block_customhub] for searching courses published on custom hubs<br />
<br />
==Running a custom community hub==<br />
<br />
Running a hub server is not something you should undertake lightly. <br />
<br />
As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:<br />
* verify all the course content is clean (of porn or malicious javascript)<br />
* manage registered sites and their status <br />
* maintain the quality of the listings through editing<br />
<br />
=== Minimal Requirements ===<br />
<br />
Below is a list of Minimal requirements for running a custom community hub.<br />
<br />
* MySQL - minimum version 5.0.25<br />
* PHP 5.3.2<br />
* Apache<br />
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''<br />
* ensure that the following php.ini variables are set to "On"<br />
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063<br />
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to Moodle.net, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933<br />
<br />
===How the hub software works===<br />
<br />
The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.x. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code. This plugin is no longer supported by Moodle HQ and is not compatible with Moodle 3.4 or later.<br />
<br />
Once installed the whole site gets a new frontpage with a simple search box.<br />
<br />
Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.<br />
<br />
===How to set up a custom community hub server===<br />
<br />
# Install Moodle 3.3 or earlier somewhere on a web server with a nice URL.<br />
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub (this plugin is no longer supported, you may need to modify it locally yourself)<br />
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub <br />
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.<br />
# Uncheck password policy (search 'passwordpolicy' in admin search)<br />
# Allow extended characters in usernames (search 'extendedusernamechars' in admin search)<br />
# Enable web services for the hub (''Administration > Site Administration > Advanced features'')<br />
# Enable the XML-RPC protocol (''Administration > Site Administration > Plugins > Web services > Manage protocols'')<br />
# Set up the SMTP (''Administration > Site Administration > Plugins > Message outputs > Email'')<br />
# Set up the recaptcha (''Administration > Site Administration > Plugins > Authentication > Manage authentication'') <br />
# Set up your hub (''Administration > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.<br />
# You will also need to set up mailing list using software that can be downloaded from https://sendy.co/<br />
<br />
Congratulations! You now have a working hub with no content!<br />
<br />
===Managing sites===<br />
<br />
In ''Site administration > Hub > Manage sites'', you can:<br />
* Prioritise a site, so that it is listed higher than unprioritised sites on the hub. By default, sites are listed in alphabetical order. A prioritised site is always trusted.<br />
* Trust a site: when a site is trusted, any published course is immediately available<br />
* Delete a site: delete a site from the database. A message will be sent to the site administrator.<br />
* Settings: you can change some information as the name, the description, the language...<br />
* Make a site visible: only sites declared as visible appear on the the site list (currently the site list hasn't been implemented)<br />
<br />
===Managing courses===<br />
<br />
In ''Site administration > Hub > Manage courses'', you can:<br />
* Delete a course: delete a course from the database.<br />
* Settings: you can change some information as the name, the description, the language...<br />
* Make a course visible: decide if the course is displayed on search result<br />
<br />
=== Important things about roles, users and web services ===<br />
<br />
A hub server uses [[Web services]] a lot. For this reason it is important to understand the web services administration, and what happens if you change some roles/users/services.<br />
<br />
==== Roles ====<br />
The hub server creates on the fly some roles that you should ''never delete/modify'':<br />
* one role for the hub directory<br />
* one role for registered sites<br />
* one role for public sites<br />
<br />
==== Users ====<br />
The hub server creates on the fly some users that you should ''never delete/modify'':<br />
* one user for the hub directory<br />
* one user for public access<br />
* as many users as registered sites<br />
<br />
==== Services ====<br />
The hub creates during installation some web services that you should ''never delete/modify'':<br />
* one service for Hub directory<br />
* one service for Registered sites<br />
* one service for Public sites<br />
<br />
It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.<br />
<br />
==Community hubs FAQ==<br />
<br />
===What is a hub server?===<br />
A hub server is a Moodle plugin. It transforms a freshly installed Moodle site into a hub server. A hub server is used to store course backups that have been shared by registered Moodle sites. <br />
<br />
===Can I use a hub server as a normal Moodle site?===<br />
<br />
For security reasons it is better not to do so.<br />
<br />
===Where can I download hub server plugin?===<br />
<br />
The hub server plugin is available for download from the modules and plugins database http://moodle.org/plugins/view.php?plugin=local_hub<br />
<br />
===Is the hub server plugin code maintained by Moodle HQ?===<br />
<br />
Not any longer. It is also known that the current code is not compatible with Moodle 3.4 or later.<br />
<br />
===Can anybody register with my hub?===<br />
<br />
For sites running Moodle 3.3 or earlier the registration and course publishing is included in standard Moodle distribution. For sites running Moodle 3.4 or later, as mentioned [[#Registering_with_a_custom_community_hub|above]], additional plugins are required.<br />
<br />
=== Can I share a course with a specific theme? ===<br />
Yes you can. However it is better to indicate in the publication creator notes that the theme will only be activated if:<br />
* The theme is installed <br />
* Course themes are enabled for the site<br />
<br />
=== Can I share a course using a contributed module/block? ===<br />
Yes. If this module/block is Moodle 2.0 compatible (with support for [[Development:Backup 2.0 for developers|backup and restore in 2.0]]), the module and its data will be added to the shared course backup.<br />
<br />
=== Can I share a course using a contributed local plugin? ===<br />
The local plugin would need to be already installed on the destination Moodle site. Then this local plugin would need to be set up. Use publication creator notes to explain it. <br />
Note that sharing does not save information related to a local plugin (i.e. the local plugin database is not backed up).<br />
<br />
=== Can I share Moodle 1.9 courses? ===<br />
It is not possible to share courses directly from a Moodle 1.9 site. However it is possible as follows:<br />
# Backup your course<br />
# Restore your course into a Moodle 2.2 site or later.<br />
# Share your course<br />
<br />
===I get an error when attempting to publish a course===<br />
<br />
The most likely cause of the error "An error occurred during the course publication (Access control exception | DEBUG INFO: Invalid token - token not found). Please try again later." is that the token is shared by multiple sites.<br />
<br />
The solution is to unregister your Moodle site in ''Administration > Site administration > Server > Hubs'' then re-register it.<br />
<br />
==See also==<br />
<br />
* [[Moodle.net]]<br />
* [[Course sharing]]<br />
<br />
[[Category:Plugin]]<br />
<br />
[[ja: コミュニティハブ]]<br />
[[en:Community hubs]]<br />
[[de:Community Hubs]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_registration&diff=129511Hub registration2017-11-27T04:39:54Z<p>Marina.glancy: /* Registering with a custom hub */</p>
<hr />
<div>{{Community hubs}}<br />
==Registering with a custom hub==<br />
<br />
'''For registration with https://moodle.net please see [[Site registration]]'''<br />
<br />
Since Moodle 3.4 registration with custom hubs was removed from Moodle core. Custom hubs can still be created using local_hub plugin.<br />
<br />
There are plugins available for sites that run Moodle 3.4 (or later) and want to register with custom hubs, advertise, publish and search courses on them:<br />
<br />
* [https://github.com/moodlehq/moodle-tool_customhub tool_customhub] for registration and course publishing<br />
* [https://github.com/moodlehq/moodle-block_customhub block_customhub] for searching courses published on custom hubs<br />
<br />
==See also==<br />
<br />
* [[Site registration]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_FAQ&diff=129510Hub FAQ2017-11-27T04:34:26Z<p>Marina.glancy: </p>
<hr />
<div>{{Community hubs}}This document lists some popular questions from the [http://moodle.org/mod/forum/view.php?id=7330 Hub server forum].<br />
<br />
<br />
==What is a hub server?==<br />
A hub server is a Moodle plugin. It transforms a freshly installed Moodle site into a hub server. A hub server is used to store course backups that have been shared by registered Moodle sites. Publishers can also advertise their courses.<br />
<br />
==Can I use a hub server as a normal Moodle site?==<br />
<br />
For security reasons it is better not to do so.<br />
<br />
==Is the hub server plugin code maintained by Moodle HQ?==<br />
<br />
Not any longer. It is also known that the current code is not compatible with Moodle 3.4 or later<br />
<br />
==Should I update the Moodle code hosting a hub server plugin when I update this plugin?==<br />
<br />
Yes, but no do update to Moodle 3.4 or later<br />
<br />
==Should the registered sites be updated when I update my hub server plugin?==<br />
<br />
No, they don't have to be updated as the plugin is backwards compatible. However sometimes new functionalities require changes in both Moodle and plugin code. In these cases, the new functionalities will not be operational until the plugin and the registered sites are updated.<br />
<br />
==Where can I download hub server plugin?==<br />
<br />
The hub server plugin is available for download from the modules and plugins database http://moodle.org/plugins/view.php?plugin=local_hub<br />
<br />
==Can anybody register with my hub?==<br />
<br />
For sites running Moodle 3.3 or earlier the registration and course publishing is included in standard Moodle distribution. For sites running Moodle 3.4 or later [[Hub registration|additional plugins are required]]<br />
<br />
== Can I share a course with a specific theme? ==<br />
Yes you can. However it is better to indicate in the publication creator notes that the theme will only be activated if:<br />
* The theme is installed <br />
* Course themes are enabled for the site<br />
<br />
== Can I share a course using a contributed module/block? ==<br />
Yes. If this module/block is Moodle 2.0 compatible (with support for [[Development:Backup 2.0 for developers|backup and restore in 2.0]]), the module and its data will be added to the shared course backup.<br />
<br />
== Can I share a course using a contributed local plugin? ==<br />
The local plugin would need to be already installed on the destination Moodle site. Then this local plugin would need to be set up. Use publication creator notes to explain it. <br />
Note that sharing does not save information related to a local plugin (i.e. the local plugin database is not backed up).<br />
<br />
== Can I share Moodle 1.9 courses? ==<br />
It is not possible to share courses directly from a Moodle 1.9 site. However it is possible as follows:<br />
# Backup your course<br />
# Restore your course into a Moodle 2.2 site or later.<br />
# Share your course<br />
<br />
==I get an error when attempting to publish a course==<br />
<br />
The most likely cause of the error "An error occurred during the course publication (Access control exception | DEBUG INFO: Invalid token - token not found). Please try again later." is that the token is shared by multiple sites.<br />
<br />
The solution is to unregister your Moodle site in ''Administration > Site administration > Server > Hubs'' then re-register it.<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7330 Hub servers forum]<br />
*[[Moodle.net FAQ]]<br />
<br />
[[Category:FAQ]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Moodle.net&diff=129509Moodle.net2017-11-27T04:32:55Z<p>Marina.glancy: </p>
<hr />
<div>{{Moodle.net}}<br />
==What is Moodle.net?==<br />
[[File:moodle.net search.png|thumb|Moodle.net search for courses]]<br />
[http://moodle.net Moodle.net] (previously known as MOOCH) is the Moodle.org Open Community Hub - a directory of courses for download or to enrol in.<br />
<br />
==How do we get onto Moodle.net?==<br />
<br />
* EITHER go to [http://moodle.net moodle.net]<br />
* OR ensure your Moodle site is registered with Moodle.net in ''Administration > Site administration > Registration'' then add the [[Community finder block]] to courses on your site<br />
<br />
==How can I publish courses to Moodle.net?==<br />
<br />
Managers (and any other users with the capability [[Capabilities/moodle/course:publish| moodle/course:publish]]) can publish courses to Moodle.net as follows:<br />
<br />
# Go to ''Administration> Course administration > Publish''<br />
#Then choose whether you wish to your course to be available for people to enrol in or to download<br />
<br />
{|<br />
| [[File:moochpublish.png|thumb|1. Publish link]]<br />
| [[File:moochpublish2.png|thumb|2. Choosing the publish method]]<br />
|}<br />
<br />
See [[Publishing a course]] for more details.<br />
<br />
==How can a teacher publish courses to Moodle.net?==<br />
<br />
To enable teachers to publish courses to Moodle.net, an administrator needs to allow the capability moodle/course:publish for the teacher role. See [[Publishing a course]] for details.<br />
<br />
==Are there any criteria which courses must satisfy in order to be listed on Moodle.net?==<br />
<br />
Yes, just a few! See the [http://moodle.net/mod/page/view.php?id=2 Moodle.net Course approval criteria].<br />
<br />
==How long does it take for a course to be approved and visible on Moodle.net?==<br />
<br />
We aim to check and approve courses within 48 hours, though it can sometimes take a little longer, so please be patient. If you require your course to be approved urgently, please [http://moodle.net/mod/page/view.php?id=15 contact us].<br />
<br />
== Can I sell courses on Moodle.net? ==<br />
No yet but it is planned. See MDL-25496 for details.<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/course:publish&diff=129508Capabilities/moodle/course:publish2017-11-27T04:22:58Z<p>Marina.glancy: /* See also */</p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to [[Publish a course|publish a course]] to a hub<br />
*This capability is allowed for the default role of manager only<br />
<br />
==See also==<br />
<br />
* [[Capabilities/moodle/backup:backuptargethub|moodle/backup:backuptargethub]]<br />
<br />
[[Category:Capabilities|Course]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja:ケイパビリティ/moodle/course:publish]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Licences&diff=129507Licences2017-11-27T04:21:59Z<p>Marina.glancy: </p>
<hr />
<div>{{Managing content}}<br />
An administrator can enable any/all of the following licences in ''Administration > Site administration > Plugins > Licences > Manage licences'' for user selection when [[Publish a course|publishing a course]] to Moodle.net or uploading a file from a [[Repository|File Repository]].<br />
<br />
[[File:Licences.png]]<br />
<br />
*The default licence is [http://en.wikipedia.org/wiki/All_rights_reserved All rights reserved] but this may be changed in the dropdown. The other options are explained in the links below:<br />
<br />
* [http://en.wikipedia.org/wiki/All_rights_reserved All rights reserved] ''(default option)''<br />
* [http://creativecommons.org/licenses/publicdomain/ Public domain]<br />
* [http://creativecommons.org/licenses/by/3.0/ Creative Commons]<br />
* [http://creativecommons.org/licenses/by-nd/3.0/ Creative Commons - NoDerivs]<br />
* [http://creativecommons.org/licenses/by-nc-nd/3.0/ Creative Commons - No Commercial NoDerivs]<br />
* [http://creativecommons.org/licenses/by-nd/3.0/ Creative Commons - No Commercial]<br />
* [http://creativecommons.org/licenses/by-nc-sa/3.0/ Creative Commons - No Commercial ShareAlike]<br />
* [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons - ShareAlike]<br />
* Other - licence not already listed<br />
<br />
==Licences affecting what users see==<br />
Note: The licence given to a file when uploaded to Moodle does not in any way affect its visibility on a course. It simply creates the default when it is being re-used elsewhere. This default licence can be changed at the time of display.<br />
<br />
[[File:licence23.png]]<br />
<br />
==See also==<br />
<br />
* [http://ltsdevmusings.wordpress.com/2011/12/08/investigating-licenses-in-moodle2/ Investigating licenses in Moodle2] blog post from Jenny Gray<br />
<br />
[[Category:Moodle.net]]<br />
[[Category:Repositories]]<br />
<br />
[[de:Lizenzen]]<br />
[[es:Licencias]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/block/community:addinstance&diff=129506Capabilities/block/community:addinstance2017-11-27T04:20:12Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to add a [[Community finder block]] to a course page<br />
*This capability is allowed for the default roles of manager and teacher<br />
<br />
[[Category:Capabilities|Block]]<br />
[[Category:Block]]<br />
[[Category:Moodle.net]]<br />
<br />
[[de:Capabilities/block/community:addinstance]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/backup:backuptargethub&diff=129505Capabilities/moodle/backup:backuptargethub2017-11-27T04:19:57Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to backup a course when [[Publishing a course|publishing the course to Moodle.net]]<br />
*This capability is allowed for the default roles of manager and teacher<br />
<br />
==See also==<br />
<br />
* [[Capabilities/moodle/course:publish|moodle/course:publish]]<br />
<br />
[[Category:Capabilities|Backup]]<br />
[[Category:Backup]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/community:add&diff=129504Capabilities/moodle/community:add2017-11-27T04:19:31Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to search for courses on a hub via the [[Community finder block]]<br />
*This capability is allowed for the default roles of teacher, non-editing teacher and manager and is not set for the role of student<br />
<br />
==See also==<br />
<br />
*[[Capabilities/moodle/community:download|moodle/community:download]] - allows a user to use the Community finder block to download courses from a hub <br />
<br />
[[Category:Capabilities|Community]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/community:download&diff=129503Capabilities/moodle/community:download2017-11-27T04:19:12Z<p>Marina.glancy: /* See also */</p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to download courses from a hub via the [[Community finder block]]<br />
*This capability is allowed for the default roles of teacher and manager and is not set for the role of student<br />
<br />
==See also==<br />
<br />
*[[Capabilities/moodle/community:add]] - allows a user to use the Community block to search for courses on a hub <br />
<br />
[[Category:Capabilities|Community]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/community:download&diff=129502Capabilities/moodle/community:download2017-11-27T04:18:53Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to download courses from a hub via the [[Community finder block]]<br />
*This capability is allowed for the default roles of teacher and manager and is not set for the role of student<br />
<br />
==See also==<br />
<br />
*[[Capabilities/moodle/community:add]] - allows a user to use the Community block to search for courses on a hub <br />
*[[Community hubs]]<br />
<br />
[[Category:Capabilities|Community]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/course:publish&diff=129501Capabilities/moodle/course:publish2017-11-27T04:18:36Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to [[Publish a course|publish a course]] to a hub<br />
*This capability is allowed for the default role of manager only<br />
<br />
==See also==<br />
<br />
* [[Community hubs]]<br />
* [[Capabilities/moodle/backup:backuptargethub|moodle/backup:backuptargethub]]<br />
<br />
[[Category:Capabilities|Course]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja:ケイパビリティ/moodle/course:publish]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Capabilities/moodle/restore:restoretargethub&diff=129500Capabilities/moodle/restore:restoretargethub2017-11-27T04:18:20Z<p>Marina.glancy: </p>
<hr />
<div>{{Capabilities}}<br />
*This allows a user to restore a backup downloaded from Moodle.net, see [[Community finder block]]<br />
*This capability is allowed for the default roles of manager and teacher<br />
<br />
[[Category:Capabilities|Backup]]<br />
[[Category:Backup]]<br />
[[Category:Moodle.net]]<br />
<br />
[[es:Capabilities/moodle/restore:restoretargethub]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Moodle.net&diff=129499Moodle.net2017-11-27T04:16:37Z<p>Marina.glancy: </p>
<hr />
<div>{{Moodle.net}}<br />
==What is Moodle.net?==<br />
[[File:moodle.net search.png|thumb|Moodle.net search for courses]]<br />
[http://moodle.net Moodle.net] (previously known as MOOCH) is the Moodle.org Open Community Hub - a directory of courses for download or to enrol in.<br />
<br />
==How do we get onto Moodle.net?==<br />
<br />
* EITHER go to [http://moodle.net moodle.net]<br />
* OR ensure your Moodle site is registered with Moodle.net in ''Administration > Site administration > Registration'' then add the [[Community finder block]] to courses on your site<br />
<br />
==How can I publish courses to Moodle.net?==<br />
<br />
Managers (and any other users with the capability [[Capabilities/moodle/course:publish| moodle/course:publish]]) can publish courses to Moodle.net as follows:<br />
<br />
# Go to ''Administration> Course administration > Publish''<br />
#Then choose whether you wish to your course to be available for people to enrol in or to download<br />
<br />
{|<br />
| [[File:moochpublish.png|thumb|1. Publish link]]<br />
| [[File:moochpublish2.png|thumb|2. Choosing the publish method]]<br />
|}<br />
<br />
See [[Publishing a course]] for more details.<br />
<br />
==How can a teacher publish courses to Moodle.net?==<br />
<br />
To enable teachers to publish courses to Moodle.net, an administrator needs to allow the capability moodle/course:publish for the teacher role. See [[Publishing a course]] for details.<br />
<br />
==Are there any criteria which courses must satisfy in order to be listed on Moodle.net?==<br />
<br />
Yes, just a few! See the [http://moodle.net/mod/page/view.php?id=2 Moodle.net Course approval criteria].<br />
<br />
==How long does it take for a course to be approved and visible on Moodle.net?==<br />
<br />
We aim to check and approve courses within 48 hours, though it can sometimes take a little longer, so please be patient. If you require your course to be approved urgently, please [http://moodle.net/mod/page/view.php?id=15 contact us].<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Moodle.net&diff=129498Moodle.net2017-11-27T04:16:21Z<p>Marina.glancy: </p>
<hr />
<div>{Moodle.net}<br />
==What is Moodle.net?==<br />
[[File:moodle.net search.png|thumb|Moodle.net search for courses]]<br />
[http://moodle.net Moodle.net] (previously known as MOOCH) is the Moodle.org Open Community Hub - a directory of courses for download or to enrol in.<br />
<br />
==How do we get onto Moodle.net?==<br />
<br />
* EITHER go to [http://moodle.net moodle.net]<br />
* OR ensure your Moodle site is registered with Moodle.net in ''Administration > Site administration > Registration'' then add the [[Community finder block]] to courses on your site<br />
<br />
==How can I publish courses to Moodle.net?==<br />
<br />
Managers (and any other users with the capability [[Capabilities/moodle/course:publish| moodle/course:publish]]) can publish courses to Moodle.net as follows:<br />
<br />
# Go to ''Administration> Course administration > Publish''<br />
#Then choose whether you wish to your course to be available for people to enrol in or to download<br />
<br />
{|<br />
| [[File:moochpublish.png|thumb|1. Publish link]]<br />
| [[File:moochpublish2.png|thumb|2. Choosing the publish method]]<br />
|}<br />
<br />
See [[Publishing a course]] for more details.<br />
<br />
==How can a teacher publish courses to Moodle.net?==<br />
<br />
To enable teachers to publish courses to Moodle.net, an administrator needs to allow the capability moodle/course:publish for the teacher role. See [[Publishing a course]] for details.<br />
<br />
==Are there any criteria which courses must satisfy in order to be listed on Moodle.net?==<br />
<br />
Yes, just a few! See the [http://moodle.net/mod/page/view.php?id=2 Moodle.net Course approval criteria].<br />
<br />
==How long does it take for a course to be approved and visible on Moodle.net?==<br />
<br />
We aim to check and approve courses within 48 hours, though it can sometimes take a little longer, so please be patient. If you require your course to be approved urgently, please [http://moodle.net/mod/page/view.php?id=15 contact us].<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Site_registration&diff=129497Site registration2017-11-27T04:14:50Z<p>Marina.glancy: /* 4 reasons to register */</p>
<hr />
<div>{{Moodle.net}}<br />
<div class="navtrail">[[Main page]] ► [[Managing a Moodle site]] ► [[{{PAGENAME}}]]</div><br />
__NOTOC__<br />
[[File:Boost-Moodle-Registrations.jpg]]<br />
==Why register my site?==<br />
Registering your site gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.<br />
<br />
==5 reasons to register==<br />
# Stay up to date by email whenever there are new releases of Moodle or security alerts. <br />
# Be part of the [https://moodle.net/stats/ statistics of the worldwide community]. <br />
# List your site on our [https://moodle.net/sites/ list of registered sites in your country]. (But if you want to keep it private, that’s fine too!)<br />
# [[Publishing a course|Share or advertise your courses]]<br />
# Make use of the messaging server https://messages.moodle.net/ for [[Mobile app notifications|Moodle mobile push notifications]].<br />
<br />
==How about security?==<br />
We don’t share your information with anyone. We don’t go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.<br />
<br />
==How do I register?==<br />
Register your site by logging in as an administrator and going to ''Administration > Site administration > Registration''. If you’re not the admin, ask them nicely to check!<br />
<br />
==I don’t want my details public==<br />
Your registration is private to us unless you choose to make it public.<br />
<br />
==Do I have to register? What happens if I don’t?==<br />
Registration is optional, but we wouldn’t want you to miss out on any important security issues or upgrades and put your site at risk. <br />
<br />
The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. <br />
<br />
So registering is a win-win for you as well as for us.<br />
<br />
==I can’t register my site!==<br />
Only sites which are online can be registered. If your site is online and you have problems registering or updating your registration, please email [mailto:support@moodle.org support@moodle.org].<br />
<br />
Note that it can take a while before your site is listed on https://moodle.net/sites/ so please be patient.<br />
<br />
[[Category:Site administration]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja: サイト登録]]<br />
[[de:Moodle-Site registrieren]]<br />
[[es:Registro del sitio]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Site_registration&diff=129496Site registration2017-11-27T04:13:02Z<p>Marina.glancy: </p>
<hr />
<div>{{Moodle.net}}<br />
<div class="navtrail">[[Main page]] ► [[Managing a Moodle site]] ► [[{{PAGENAME}}]]</div><br />
__NOTOC__<br />
[[File:Boost-Moodle-Registrations.jpg]]<br />
==Why register my site?==<br />
Registering your site gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.<br />
<br />
==4 reasons to register==<br />
# Stay up to date by email whenever there are new releases of Moodle or security alerts. <br />
# Be part of the [https://moodle.net/stats/ statistics of the worldwide community]. <br />
# List your site on our [https://moodle.net/sites/ list of registered sites in your country]. (But if you want to keep it private, that’s fine too!)<br />
# Make use of the messaging server https://messages.moodle.net/ for [[Mobile app notifications|Moodle mobile push notifications]].<br />
<br />
==How about security?==<br />
We don’t share your information with anyone. We don’t go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.<br />
<br />
==How do I register?==<br />
Register your site by logging in as an administrator and going to ''Administration > Site administration > Registration''. If you’re not the admin, ask them nicely to check!<br />
<br />
==I don’t want my details public==<br />
Your registration is private to us unless you choose to make it public.<br />
<br />
==Do I have to register? What happens if I don’t?==<br />
Registration is optional, but we wouldn’t want you to miss out on any important security issues or upgrades and put your site at risk. <br />
<br />
The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. <br />
<br />
So registering is a win-win for you as well as for us.<br />
<br />
==I can’t register my site!==<br />
Only sites which are online can be registered. If your site is online and you have problems registering or updating your registration, please email [mailto:support@moodle.org support@moodle.org].<br />
<br />
Note that it can take a while before your site is listed on https://moodle.net/sites/ so please be patient.<br />
<br />
[[Category:Site administration]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja: サイト登録]]<br />
[[de:Moodle-Site registrieren]]<br />
[[es:Registro del sitio]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Course_sharing&diff=129493Course sharing2017-11-27T04:10:37Z<p>Marina.glancy: </p>
<hr />
<div>{{Moodle.net}}<br />
Publishing a course is a method of sharing your course on Moodle.net.<br />
<br />
When you publish a course, you can choose whether to make it available <br />
* for download (as a course backup file) OR<br />
* to enrol in on your site<br />
<br />
==Connecting to Moodle.net==<br />
<br />
An administrator first needs to check in ''Administration > Site Administration > Registration'' that your Moodle site is [[Site_registration|registered]] with the community hub(s) that you wish to publish courses to.<br />
<br />
Note: Only sites which are publicly available on the Internet can register with Moodle.net.<br />
<br />
==Publishing a course for download==<br />
[[Image:Backup_publication.png|thumb|First page of the backup process]]<br />
<br />
# Go to ''Administration > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Share this course for people to download'<br />
# Enter information about the course<br />
# Click the 'Upload this course' button<br />
# Select the data to be included in the backup<br />
# Create the course backup<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
How to upload a Moodle course to Moodle.net video:<br />
<br />
{{MediaPlayer | url = http://www.youtube.com/watch?v=nz7_pHkaCoQ}}<br />
<br />
===Updating a course backup===<br />
<br />
If you improve the course and wish to update the course backup, firstly remove it from the hub, then re-share it. You may also share different versions of the same course.<br />
<br />
==Publishing a course for people to enrol in==<br />
<br />
You can display a link to your course on any hub your site is registered on. The hub will redirect users your course.<br />
<br />
# Go to ''Settings > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Advertise this course for people to join'<br />
# Enter information about the course<br />
# Click the 'Advertise this course' button<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
You can change the information about the course by clicking the 'Update' button in the actions column.<br />
<br />
''Note: You also need to make sure that users can actually enrol in the course you have just published.'' This normally means having [[Email-based self-registration|email-based self-registration]] enabled for the site and enabling [[Self enrolment|self-enrolment]] for the course.<br />
<br />
:Tip! When you advertise a course try to make the course easy to see for people not registered on your site (allow [https://docs.moodle.org/en/Course_settings#Guest_access guest access in your course settings] / allow [https://docs.moodle.org/en/User_policies#Auto-login_guest Auto-login guests] / allow people to register themself).<br />
<br />
== Moodle.net listing ==<br />
<br />
You can check whether your course has been approved by the hub administrator and is listed on Moodle.net as follows:<br />
<br />
# Go to ''Settings > Course administration > Publish''<br />
# Click the 'Check it now' link in the hub listing column<br />
<br />
Your Moodle site will contact Moodle.net and will then update the status of your course.<br />
<br />
[[File:published on list.png]]<br />
<br />
==Removing a course from Moodle.net==<br />
<br />
If you wish, you can remove your course from a hub at any time.<br />
<br />
# Go to ''Settings > Course administration > Share''<br />
# Click the 'Remove from Moodle.net' button in the actions column<br />
<br />
==Capabilities==<br />
<br />
Only users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]] (by default only users with the role of manager) can publish their course to a community hub. The capability [[Capabilities/moodle/backup:backuptargethub|moodle/backup:backuptargethub]] is also required for publishing courses for download.<br />
<br />
==Enabling teachers to publish their courses==<br />
<br />
An administrator can enable teachers to publish their courses on a hub by allowing the capability ''moodle/course:publish'' for the teacher role.<br />
<br />
# Go to ''Settings > Site administration > Users > Permissions > Define roles''<br />
# Click the edit icon opposite the teacher role<br />
# On the editing role page, paste ''moodle/course:publish'' into the filter box<br />
# Tick the checkbox opposite ''moodle/course:publish'' to allow the capability<br />
# Click the 'Save changes' button<br />
<br />
[[Category:Moodle.net]]<br />
<br />
[[fr:Publier un cours]]<br />
[[ja:コースを公開する]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Course_sharing&diff=129492Course sharing2017-11-27T04:10:13Z<p>Marina.glancy: </p>
<hr />
<div>Publishing a course is a method of sharing your course on Moodle.net.<br />
<br />
When you publish a course, you can choose whether to make it available <br />
* for download (as a course backup file) OR<br />
* to enrol in on your site<br />
<br />
==Connecting to Moodle.net==<br />
<br />
An administrator first needs to check in ''Administration > Site Administration > Registration'' that your Moodle site is [[Site_registration|registered]] with the community hub(s) that you wish to publish courses to.<br />
<br />
Note: Only sites which are publicly available on the Internet can register with Moodle.net.<br />
<br />
==Publishing a course for download==<br />
[[Image:Backup_publication.png|thumb|First page of the backup process]]<br />
<br />
# Go to ''Administration > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Share this course for people to download'<br />
# Enter information about the course<br />
# Click the 'Upload this course' button<br />
# Select the data to be included in the backup<br />
# Create the course backup<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
How to upload a Moodle course to Moodle.net video:<br />
<br />
{{MediaPlayer | url = http://www.youtube.com/watch?v=nz7_pHkaCoQ}}<br />
<br />
===Updating a course backup===<br />
<br />
If you improve the course and wish to update the course backup, firstly remove it from the hub, then re-share it. You may also share different versions of the same course.<br />
<br />
==Publishing a course for people to enrol in==<br />
<br />
You can display a link to your course on any hub your site is registered on. The hub will redirect users your course.<br />
<br />
# Go to ''Settings > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Advertise this course for people to join'<br />
# Enter information about the course<br />
# Click the 'Advertise this course' button<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
You can change the information about the course by clicking the 'Update' button in the actions column.<br />
<br />
''Note: You also need to make sure that users can actually enrol in the course you have just published.'' This normally means having [[Email-based self-registration|email-based self-registration]] enabled for the site and enabling [[Self enrolment|self-enrolment]] for the course.<br />
<br />
:Tip! When you advertise a course try to make the course easy to see for people not registered on your site (allow [https://docs.moodle.org/en/Course_settings#Guest_access guest access in your course settings] / allow [https://docs.moodle.org/en/User_policies#Auto-login_guest Auto-login guests] / allow people to register themself).<br />
<br />
== Moodle.net listing ==<br />
<br />
You can check whether your course has been approved by the hub administrator and is listed on Moodle.net as follows:<br />
<br />
# Go to ''Settings > Course administration > Publish''<br />
# Click the 'Check it now' link in the hub listing column<br />
<br />
Your Moodle site will contact Moodle.net and will then update the status of your course.<br />
<br />
[[File:published on list.png]]<br />
<br />
==Removing a course from Moodle.net==<br />
<br />
If you wish, you can remove your course from a hub at any time.<br />
<br />
# Go to ''Settings > Course administration > Share''<br />
# Click the 'Remove from Moodle.net' button in the actions column<br />
<br />
==Capabilities==<br />
<br />
Only users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]] (by default only users with the role of manager) can publish their course to a community hub. The capability [[Capabilities/moodle/backup:backuptargethub|moodle/backup:backuptargethub]] is also required for publishing courses for download.<br />
<br />
==Enabling teachers to publish their courses==<br />
<br />
An administrator can enable teachers to publish their courses on a hub by allowing the capability ''moodle/course:publish'' for the teacher role.<br />
<br />
# Go to ''Settings > Site administration > Users > Permissions > Define roles''<br />
# Click the edit icon opposite the teacher role<br />
# On the editing role page, paste ''moodle/course:publish'' into the filter box<br />
# Tick the checkbox opposite ''moodle/course:publish'' to allow the capability<br />
# Click the 'Save changes' button<br />
<br />
[[Category:Moodle.net]]<br />
<br />
[[fr:Publier un cours]]<br />
[[ja:コースを公開する]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Course_sharing&diff=129491Course sharing2017-11-27T04:09:49Z<p>Marina.glancy: Publishing only possible on Moodle.net</p>
<hr />
<div>{{Community hubs}}<br />
Publishing a course is a method of sharing your course on Moodle.net.<br />
<br />
When you publish a course, you can choose whether to make it available <br />
* for download (as a course backup file) OR<br />
* to enrol in on your site<br />
<br />
==Connecting to Moodle.net==<br />
<br />
An administrator first needs to check in ''Administration > Site Administration > Registration'' that your Moodle site is [[Site_registration|registered]] with the community hub(s) that you wish to publish courses to.<br />
<br />
Note: Only sites which are publicly available on the Internet can register with Moodle.net.<br />
<br />
==Publishing a course for download==<br />
[[Image:Backup_publication.png|thumb|First page of the backup process]]<br />
<br />
# Go to ''Administration > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Share this course for people to download'<br />
# Enter information about the course<br />
# Click the 'Upload this course' button<br />
# Select the data to be included in the backup<br />
# Create the course backup<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
How to upload a Moodle course to Moodle.net video:<br />
<br />
{{MediaPlayer | url = http://www.youtube.com/watch?v=nz7_pHkaCoQ}}<br />
<br />
===Updating a course backup===<br />
<br />
If you improve the course and wish to update the course backup, firstly remove it from the hub, then re-share it. You may also share different versions of the same course.<br />
<br />
==Publishing a course for people to enrol in==<br />
<br />
You can display a link to your course on any hub your site is registered on. The hub will redirect users your course.<br />
<br />
# Go to ''Settings > Course administration > Share'' (only available to users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]])<br />
# Click the button 'Advertise this course for people to join'<br />
# Enter information about the course<br />
# Click the 'Advertise this course' button<br />
<br />
The course will then need to be approved by the hub administrator before it appears in the course listing.<br />
<br />
You can change the information about the course by clicking the 'Update' button in the actions column.<br />
<br />
''Note: You also need to make sure that users can actually enrol in the course you have just published.'' This normally means having [[Email-based self-registration|email-based self-registration]] enabled for the site and enabling [[Self enrolment|self-enrolment]] for the course.<br />
<br />
:Tip! When you advertise a course try to make the course easy to see for people not registered on your site (allow [https://docs.moodle.org/en/Course_settings#Guest_access guest access in your course settings] / allow [https://docs.moodle.org/en/User_policies#Auto-login_guest Auto-login guests] / allow people to register themself).<br />
<br />
== Moodle.net listing ==<br />
<br />
You can check whether your course has been approved by the hub administrator and is listed on Moodle.net as follows:<br />
<br />
# Go to ''Settings > Course administration > Publish''<br />
# Click the 'Check it now' link in the hub listing column<br />
<br />
Your Moodle site will contact Moodle.net and will then update the status of your course.<br />
<br />
[[File:published on list.png]]<br />
<br />
==Removing a course from Moodle.net==<br />
<br />
If you wish, you can remove your course from a hub at any time.<br />
<br />
# Go to ''Settings > Course administration > Share''<br />
# Click the 'Remove from Moodle.net' button in the actions column<br />
<br />
==Capabilities==<br />
<br />
Only users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]] (by default only users with the role of manager) can publish their course to a community hub. The capability [[Capabilities/moodle/backup:backuptargethub|moodle/backup:backuptargethub]] is also required for publishing courses for download.<br />
<br />
==Enabling teachers to publish their courses==<br />
<br />
An administrator can enable teachers to publish their courses on a hub by allowing the capability ''moodle/course:publish'' for the teacher role.<br />
<br />
# Go to ''Settings > Site administration > Users > Permissions > Define roles''<br />
# Click the edit icon opposite the teacher role<br />
# On the editing role page, paste ''moodle/course:publish'' into the filter box<br />
# Tick the checkbox opposite ''moodle/course:publish'' to allow the capability<br />
# Click the 'Save changes' button<br />
<br />
[[fr:Publier un cours]]<br />
[[ja:コースを公開する]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Moodle.net&diff=129490Moodle.net2017-11-27T04:05:54Z<p>Marina.glancy: </p>
<hr />
<div>==What is Moodle.net?==<br />
[[File:moodle.net search.png|thumb|Moodle.net search for courses]]<br />
[http://moodle.net Moodle.net] (previously known as MOOCH) is the Moodle.org Open Community Hub - a directory of courses for download or to enrol in.<br />
<br />
==How do we get onto Moodle.net?==<br />
<br />
* EITHER go to [http://moodle.net moodle.net]<br />
* OR ensure your Moodle site is registered with Moodle.net in ''Administration > Site administration > Registration'' then add the [[Community finder block]] to courses on your site<br />
<br />
==How can I publish courses to Moodle.net?==<br />
<br />
Managers (and any other users with the capability [[Capabilities/moodle/course:publish| moodle/course:publish]]) can publish courses to Moodle.net as follows:<br />
<br />
# Go to ''Administration> Course administration > Publish''<br />
#Then choose whether you wish to your course to be available for people to enrol in or to download<br />
<br />
{|<br />
| [[File:moochpublish.png|thumb|1. Publish link]]<br />
| [[File:moochpublish2.png|thumb|2. Choosing the publish method]]<br />
|}<br />
<br />
See [[Publishing a course]] for more details.<br />
<br />
==How can a teacher publish courses to Moodle.net?==<br />
<br />
To enable teachers to publish courses to Moodle.net, an administrator needs to allow the capability moodle/course:publish for the teacher role. See [[Publishing a course]] for details.<br />
<br />
==Are there any criteria which courses must satisfy in order to be listed on Moodle.net?==<br />
<br />
Yes, just a few! See the [http://moodle.net/mod/page/view.php?id=2 Moodle.net Course approval criteria].<br />
<br />
==How long does it take for a course to be approved and visible on Moodle.net?==<br />
<br />
We aim to check and approve courses within 48 hours, though it can sometimes take a little longer, so please be patient. If you require your course to be approved urgently, please [http://moodle.net/mod/page/view.php?id=15 contact us].<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Moodle.net&diff=129489Moodle.net2017-11-27T04:05:13Z<p>Marina.glancy: </p>
<hr />
<div>{{Community hubs}}<br />
==What is Moodle.net?==<br />
[[File:moodle.net search.png|thumb|Moodle.net search for courses]]<br />
[http://moodle.net Moodle.net] (previously known as MOOCH) is the Moodle.org Open Community Hub - a directory of courses for download or to enrol in.<br />
<br />
==How do we get onto Moodle.net?==<br />
<br />
* EITHER go to [http://moodle.net moodle.net]<br />
* OR ensure your Moodle site is registered with Moodle.net in ''Administration > Site administration > Registration'' then add the [[Community finder block]] to courses on your site<br />
<br />
==How can I publish courses to Moodle.net?==<br />
<br />
Managers (and any other users with the capability [[Capabilities/moodle/course:publish| moodle/course:publish]]) can publish courses to Moodle.net as follows:<br />
<br />
# Go to ''Administration> Course administration > Publish''<br />
#Then choose whether you wish to your course to be available for people to enrol in or to download<br />
<br />
{|<br />
| [[File:moochpublish.png|thumb|1. Publish link]]<br />
| [[File:moochpublish2.png|thumb|2. Choosing the publish method]]<br />
|}<br />
<br />
See [[Publishing a course]] for more details.<br />
<br />
==How can a teacher publish courses to Moodle.net?==<br />
<br />
To enable teachers to publish courses to Moodle.net, an administrator needs to allow the capability moodle/course:publish for the teacher role. See [[Publishing a course]] for details.<br />
<br />
==Are there any criteria which courses must satisfy in order to be listed on Moodle.net?==<br />
<br />
Yes, just a few! See the [http://moodle.net/mod/page/view.php?id=2 Moodle.net Course approval criteria].<br />
<br />
==How long does it take for a course to be approved and visible on Moodle.net?==<br />
<br />
We aim to check and approve courses within 48 hours, though it can sometimes take a little longer, so please be patient. If you require your course to be approved urgently, please [http://moodle.net/mod/page/view.php?id=15 contact us].<br />
<br />
[[Category:FAQ]]<br />
[[Category:Moodle.net]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Site_registration&diff=129488Site registration2017-11-27T04:04:13Z<p>Marina.glancy: </p>
<hr />
<div><div class="navtrail">[[Main page]] ► [[Managing a Moodle site]] ► [[{{PAGENAME}}]]</div><br />
__NOTOC__<br />
[[File:Boost-Moodle-Registrations.jpg]]<br />
==Why register my site?==<br />
Registering your site gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.<br />
<br />
==4 reasons to register==<br />
# Stay up to date by email whenever there are new releases of Moodle or security alerts. <br />
# Be part of the [https://moodle.net/stats/ statistics of the worldwide community]. <br />
# List your site on our [https://moodle.net/sites/ list of registered sites in your country]. (But if you want to keep it private, that’s fine too!)<br />
# Make use of the messaging server https://messages.moodle.net/ for [[Mobile app notifications|Moodle mobile push notifications]].<br />
<br />
==How about security?==<br />
We don’t share your information with anyone. We don’t go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.<br />
<br />
==How do I register?==<br />
Register your site by logging in as an administrator and going to ''Administration > Site administration > Registration''. If you’re not the admin, ask them nicely to check!<br />
<br />
==I don’t want my details public==<br />
Your registration is private to us unless you choose to make it public.<br />
<br />
==Do I have to register? What happens if I don’t?==<br />
Registration is optional, but we wouldn’t want you to miss out on any important security issues or upgrades and put your site at risk. <br />
<br />
The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. <br />
<br />
So registering is a win-win for you as well as for us.<br />
<br />
==I can’t register my site!==<br />
Only sites which are online can be registered. If your site is online and you have problems registering or updating your registration, please email [mailto:support@moodle.org support@moodle.org].<br />
<br />
Note that it can take a while before your site is listed on https://moodle.net/sites/ so please be patient.<br />
<br />
[[Category:Site administration]]<br />
[[Category:Moodle.net]]<br />
<br />
[[ja: サイト登録]]<br />
[[de:Moodle-Site registrieren]]<br />
[[es:Registro del sitio]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Category:Moodle.net&diff=129487Category:Moodle.net2017-11-27T04:03:49Z<p>Marina.glancy: Created page with "Site registration, course sharing and searching on https://moodle.net"</p>
<hr />
<div>Site registration, course sharing and searching on https://moodle.net</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Community_finder_block&diff=129486Community finder block2017-11-27T04:02:58Z<p>Marina.glancy: </p>
<hr />
<div>{{Blocks}}The community finder block enables users to access [http://moodle.net Moodle.net], and search for courses to download or enrol in.<br />
<br />
* Downloadable courses may be immediately restored to your Moodle site<br />
* Links to enrollable courses are saved in the community finder block<br />
<br />
{|<br />
| [[File:community finder block.png|thumb|Community finder block]]<br />
| [[File:search for community course.png|thumb|Search for community courses]]<br />
|}<br />
<br />
==Downloading courses from a hub==<br />
<br />
# In the community finder block click Search<br />
# Select 'Courses I can download' and then click the Search button<br />
# For any courses of interest, click 'Visit demo' then if you're happy with the course, click 'Download'<br />
# The course backup will then be downloaded and saved in your private files. Click Yes to immediately restore the course<br />
<br />
==Finding courses to enrol in==<br />
<br />
# In the community finder block click Search<br />
# Select 'Courses I can enrol in' and then click the Search button<br />
# For any courses of interest, click 'Visit site' then if you're happy with the course, click 'Save a link to this course'<br />
<br />
The link to the course will then be displayed in the community finder block.<br />
<br />
If you wish to remove any saved links, click the X icon after the link.<br />
<br />
==Capabilities==<br />
<br />
By default, users with the role of manager or teacher can use the community finder block. <br />
<br />
The following capabilities control access to the block:<br />
* [[Capabilities/moodle/community:add|moodle/community:add]] - allows a user to use the Community block to search for courses on a hub<br />
* [[Capabilities/moodle/community:download|moodle/community:download]] - allows a user to use the Community block to download courses from a hub<br />
<br />
==See also==<br />
<br />
* [[Restoring file aliases]] for details of what happens when restoring a course which has been downloaded from a hub and which contains file aliases<br />
<br />
[[Category:Moodle.net]]<br />
<br />
[[de:Community-Suche]]<br />
[[fr:Bloc Recherche communauté]]<br />
[[es:Bloque de buscador de comunidad]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Community_finder_block&diff=129485Community finder block2017-11-27T04:00:22Z<p>Marina.glancy: /* Downloading courses from a hub */</p>
<hr />
<div>{{Blocks}}The community finder block enables users to access [http://moodle.net Moodle.net], and search for courses to download or enrol in.<br />
<br />
* Downloadable courses may be immediately restored to your Moodle site<br />
* Links to enrollable courses are saved in the community finder block<br />
<br />
{|<br />
| [[File:community finder block.png|thumb|Community finder block]]<br />
| [[File:search for community course.png|thumb|Search for community courses]]<br />
|}<br />
<br />
==Downloading courses from a hub==<br />
<br />
# In the community finder block click Search<br />
# Select 'Courses I can download' and then click the Search button<br />
# For any courses of interest, click 'Visit demo' then if you're happy with the course, click 'Download'<br />
# The course backup will then be downloaded and saved in your private files. Click Yes to immediately restore the course<br />
<br />
==Finding courses to enrol in==<br />
<br />
# In the community finder block click Search<br />
# Select [http://moodle.net Moodle.net]<br />
# Select 'Courses I can enrol in' and then click the Search button<br />
# For any courses of interest, click 'Visit site' then if you're happy with the course, click 'Save a link to this course'<br />
<br />
The link to the course will then be displayed in the community finder block.<br />
<br />
If you wish to remove any saved links, click the X icon after the link.<br />
<br />
==Capabilities==<br />
<br />
By default, users with the role of manager or teacher can use the community finder block. <br />
<br />
The following capabilities control access to the block:<br />
* [[Capabilities/moodle/community:add|moodle/community:add]] - allows a user to use the Community block to search for courses on a hub<br />
* [[Capabilities/moodle/community:download|moodle/community:download]] - allows a user to use the Community block to download courses from a hub<br />
<br />
==See also==<br />
<br />
* [[Community hub]]<br />
* [[Restoring file aliases]] for details of what happens when restoring a course which has been downloaded from a hub and which contains file aliases<br />
<br />
[[Category:Hub]]<br />
<br />
[[de:Community-Suche]]<br />
[[fr:Bloc Recherche communauté]]<br />
[[es:Bloque de buscador de comunidad]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_administration&diff=129484Hub administration2017-11-27T03:57:30Z<p>Marina.glancy: </p>
<hr />
<div>{{Community hubs}}<br />
'''Warning: from Moodle 3.4 onwards sites that want to register with custom hub will need to install [[Hub registration|additional plugins]].'''<br />
<br />
==Deciding to run a Hub==<br />
<br />
Running a hub server is not something you should undertake lightly. <br />
<br />
As the hub administrator you are responsible for the content in the hub, and you need to put in place processes to:<br />
* verify all the course content is clean (of porn or malicious javascript)<br />
* manage registered sites and their status <br />
* maintain the quality of the listings through editing<br />
<br />
=== Minimal Requirements ===<br />
<br />
Below is a list of Minimal requirements for running a Moodle Community Hub.<br />
<br />
* MySQL - minimum version 5.0.25<br />
* PHP 5.3.2<br />
* Apache<br />
* ensure that the site you will be registering does not use any upper case letters (even though those are perfectly valid). ''EG: moodle.org/2012-Spring will not work!''<br />
* ensure that the following php.ini variables are set to "On"<br />
** allow_url_fopen: This setting is required the hub to be able to register a site. If this option is not enabled, you will be given the [[error/local_hub/cannotregisternotavailablesite|cannotregisternotavailablesite]] error. Related tracker issue: https://tracker.moodle.org/browse/CONTRIB-3063<br />
* mod_security in Apache version 1 and mod_security2 in Apache version 2 will return a 403 forbidden error when a URL that is not the local domain is passed as a get variable. mod_security on either the hub or client servers will block the completion of the client/hub registration process, even to Moodle.net, as within the registration process URL's are passed as get variables a number of times. An exception can be added to mod_security in Apache version 1 via a local .htacess file. However, this ability was removed in mod_security2. In mod_security2 the exception must be added to mod_security.conf of /conf.d. Related forum discussion: http://moodle.org/mod/forum/discuss.php?d=188933<br />
<br />
==How the hub software works==<br />
<br />
The hub software is implemented as a separate "local" plugin designed to be added to a standard install of Moodle 2.x. In this way the hub gets to use on all the features in the Moodle core API and benefits from maintenance of the core code. This plugin is no longer supported by Moodle HQ and is not compatible with Moodle 3.4 or later.<br />
<br />
Once installed the whole site gets a new frontpage with a simple search box.<br />
<br />
Please don't add the hub capabilities to an existing Moodle site with real courses. Although it may work, there are some opportunities for GUI confusion and some unknowns when it comes to security, so please just avoid it. Moodle is free, so it's trivial to install another clean copy to build your hub with.<br />
<br />
==How to set up a Moodle Hub server==<br />
<br />
# Install Moodle 3.3 or earlier somewhere on a web server with a nice URL.<br />
# Download the latest hub plugin from https://github.com/moodlehq/moodle-local_hub (this plugin is no longer supported, you may need to modify it locally yourself)<br />
# Save the zip into the /local directory of Moodle and unzip, producing /local/hub <br />
# Visit the "Notifications" page in Moodle (/admin) to complete the upgrade and install the hub software.<br />
# Uncheck password policy (search 'passwordpolicy' in admin search)<br />
# Allow extended characters in usernames (search 'extendedusernamechars' in admin search)<br />
# Enable web services for the hub (''Administration > Site Administration > Advanced features'')<br />
# Enable the XML-RPC protocol (''Administration > Site Administration > Plugins > Web services > Manage protocols'')<br />
# Set up the SMTP (''Administration > Site Administration > Plugins > Message outputs > Email'')<br />
# Set up the recaptcha (''Administration > Site Administration > Plugins > Authentication > Manage authentication'') <br />
# Set up your hub (''Administration > Site Administration > Hub > Settings'') Supply a description, enable the hub, supply a hub password.<br />
# You will also need to set up mailing list using software that can be downloaded from https://sendy.co/<br />
<br />
Congratulations! You now have a working hub with no content!<br />
<br />
==Site registration==<br />
<br />
Only sites that are registered with the hub are allowed to publish content there.<br />
<br />
Sites register on the hub via ''Administration > Site administration > Server > Hubs''.<br />
<br />
For sites running Moodle 3.4 and above [[Hub registration|additional plugins are required]].<br />
<br />
==Managing sites==<br />
<br />
In ''Administration > Site administration > Hub > Manage sites'', you can:<br />
* Prioritise a site, so that it is listed higher than unprioritised sites on the hub. By default, sites are listed in alphabetical order. A prioritised site is always trusted.<br />
* Trust a site: when a site is trusted, any published course is immediately available<br />
* Delete a site: delete a site from the database. A message will be sent to the site administrator.<br />
* Settings: you can change some information as the name, the description, the language...<br />
* Make a site visible: only sites declared as visible appear on the the site list (currently the site list hasn't been implemented)<br />
<br />
==Managing courses==<br />
<br />
In ''Administration > Site administration > Hub > Manage courses'', you can:<br />
* Delete a course: delete a course from the database.<br />
* Settings: you can change some information as the name, the description, the language...<br />
* Make a course visible: decide if the course is displayed on search result<br />
<br />
== Important things about roles, users and web services ==<br />
<br />
A hub server uses [[Web services]] a lot. For this reason it is important to understand the web services administration, and what happens if you change some roles/users/services.<br />
<br />
=== Roles ===<br />
The hub server creates on the fly some roles that you should ''never delete/modify'':<br />
* one role for the hub directory<br />
* one role for registered sites<br />
* one role for public sites<br />
<br />
=== Users ===<br />
The hub server creates on the fly some users that you should ''never delete/modify'':<br />
* one user for the hub directory<br />
* one user for public access<br />
* as many users as registered sites<br />
<br />
=== Services ===<br />
The hub creates during installation some web services that you should ''never delete/modify'':<br />
* one service for Hub directory<br />
* one service for Registered sites<br />
* one service for Public sites<br />
<br />
It also creates tokens on the fly. These tokens are not displayed on the token management list, so you cannot accidentally delete them.<br />
<br />
==See also==<br />
<br />
*[[Site registration]]<br />
<br />
[[ja:ハブ管理]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_registration&diff=129483Hub registration2017-11-27T03:35:37Z<p>Marina.glancy: /* Registering with a hub */</p>
<hr />
<div>{{Community hubs}}<br />
==Registering with a custom hub==<br />
<br />
'''For registration with https://moodle.net please see [[Site registration]]'''<br />
<br />
Since Moodle 3.4 registration with custom hubs was removed from Moodle core. Custom hubs can still be created using local_hub plugin.<br />
<br />
There are plugins available for sites that run Moodle 3.4 (or later) and want to register with custom hubs, advertise, publish and search courses on them:<br />
<br />
* [https://github.com/moodlehq/moodle-tool_customhub tool_customhub for registration and course publishing]<br />
* [https://github.com/moodlehq/moodle-block_customhub block_customhub for searching courses published on custom hubs]<br />
<br />
==See also==<br />
<br />
* [[Site registration]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_registration&diff=129482Hub registration2017-11-27T03:33:05Z<p>Marina.glancy: /* Unregistering from a hub */</p>
<hr />
<div>{{Community hubs}}<br />
==Registering with a hub==<br />
<br />
Since Moodle 3.4 registration with custom hubs was removed from Moodle core. Custom hubs can still be created using local_hub plugin.<br />
<br />
Plugins are available for sites that run Moodle 3.4 (or later) and that want to register with custom hubs and/or advertise and publish courses on them:<br />
<br />
* [https://github.com/moodlehq/moodle-tool_customhub tool_customhub for registration and course publishing]<br />
* [https://github.com/moodlehq/moodle-block_customhub block_customhub for searching courses published on custom hubs]<br />
<br />
==See also==<br />
<br />
* [[Site registration]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Hub_registration&diff=129481Hub registration2017-11-27T03:32:55Z<p>Marina.glancy: /* Registering with a hub */</p>
<hr />
<div>{{Community hubs}}<br />
==Registering with a hub==<br />
<br />
Since Moodle 3.4 registration with custom hubs was removed from Moodle core. Custom hubs can still be created using local_hub plugin.<br />
<br />
Plugins are available for sites that run Moodle 3.4 (or later) and that want to register with custom hubs and/or advertise and publish courses on them:<br />
<br />
* [https://github.com/moodlehq/moodle-tool_customhub tool_customhub for registration and course publishing]<br />
* [https://github.com/moodlehq/moodle-block_customhub block_customhub for searching courses published on custom hubs]<br />
<br />
== Unregistering from a hub==<br />
<br />
You may unregister from a hub at any time by clicking the unregister button. You will then be given the option to remove all courses currently being advertised on the hub and remove all courses that were uploaded to the hub.<br />
<br />
==See also==<br />
<br />
* [[Site registration]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Upgrading&diff=129322Upgrading2017-11-13T03:11:28Z<p>Marina.glancy: /* Possible issues that may affect you in Moodle {{Version}} */</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for {{Version}} in ''Administration > Site administration > Server > [[Environment]]''. <br />
<br />
See the [{{Release notes}} release notes] in the dev docs for software requirements.<br />
<br />
Notes:<br />
<br />
* You can only upgrade to Moodle {{Version}} from Moodle 3.0 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/30/en/Upgrading_to_Moodle_3.0 upgrade to 3.0] as a first step.<br />
* The minimum PHP version has increased and is now 7.0.0.<br />
* The PHP extension '''intl''' is now required in Moodle 3.4 (previously it was only recommended).<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
Consider setting the [[Upgrade key|upgrade key]] for your site.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
== Check for plugin updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).<br />
<br />
The upgrade of the plugin will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.<br />
<br />
== Install the new Moodle software ==<br />
You can fetch the current version of the software through <br />
<br />
wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)<br />
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-{{Version}}.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version)<br />
chmod -R 755 moodle<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php') <br />
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle {{Version}} supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
If you put your site into Maintenance mode earlier; take it out now!<br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.<br />
<br />
===Cron===<br />
<br />
Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.<br />
<br />
The benefits of these changes are:<br />
* The schedule for every task can be configured by the admin<br />
* Tasks can run in parallel<br />
* Cron processes use locking to prevent the same task running at the same time by different processes<br />
* Clusters with multiple identical application nodes are supported, you can run cron on all of them<br />
<br />
A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.<br />
<br />
You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure. <br />
<br />
Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle {{Version}}==<br />
<br />
* Setting "Use HTTPS for logins" ('loginhttps') was completely removed since it provided false sense of security. If it was enabled before upgrade the whole site will be served via HTTPS protocol. [[HTTPS conversion tool]] is available for administrator to convert links to embedded contents from http to https.<br />
* Minimum supported PHP version was raised to 7.0. You cannot run your Moodle 3.4 site on PHP 5.6 or lower (please refer to [https://docs.moodle.org/dev/Moodle_3.4_release_notes#Server_requirements requirements section] for details).<br />
* Some authentication methods were removed from the standard distribution (fc, imap, nntp, pam, pop3). If you use them, you must provide them manually during the upgrade (MDL-50925).<br />
* The Messages block has been removed from the standard distribution. The new messages notification is displayed on the top of every page and this block is no longer needed. Block can be [https://github.com/moodlehq/moodle-block_messages manually downloaded] if needed<br />
* Support for custom registration hubs has been completely removed. Registration and course publishing is possible only with https://moodle.net<br />
* Course restore and import operations now will never change user dates and log dates. Only activity dates (due, open/close, etc.) will now change respective of the new course start date.<br />
<br />
See the [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]] for the full list of changes in Moodle {{Version}}.<br />
<br />
=== Moodle 3.1, 3.2 and 3.3 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]<br />
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]<br />
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]<br />
<br />
==See also==<br />
<br />
* [[Installation]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum] <br />
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Upgrading&diff=129321Upgrading2017-11-13T02:57:28Z<p>Marina.glancy: /* Possible issues that may affect you in Moodle {{Version}} */</p>
<hr />
<div>{{Installing Moodle}} <br />
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''<br />
<br />
==Check the requirements==<br />
<br />
Check that your server meets all requirements for {{Version}} in ''Administration > Site administration > Server > [[Environment]]''. <br />
<br />
See the [{{Release notes}} release notes] in the dev docs for software requirements.<br />
<br />
Notes:<br />
<br />
* You can only upgrade to Moodle {{Version}} from Moodle 3.0 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/30/en/Upgrading_to_Moodle_3.0 upgrade to 3.0] as a first step.<br />
* The minimum PHP version has increased and is now 7.0.0.<br />
* The PHP extension '''intl''' is now required in Moodle 3.4 (previously it was only recommended).<br />
<br />
==Before upgrading==<br />
<br />
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''<br />
<br />
Consider setting the [[Upgrade key|upgrade key]] for your site.<br />
<br />
== Backup important data ==<br />
<br />
There are three areas that should be backed up before any upgrade:<br />
#Moodle software (For example, everything in server/htdocs/moodle)<br />
#Moodle uploaded files (For example, server/moodledata)<br />
#Moodle database (For example, your Postgres or MySQL database dump)<br />
<br />
See [[Site backup]] for more specific information.<br />
<br />
== Check for plugin updates ==<br />
<br />
If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.<br />
<br />
If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).<br />
<br />
The upgrade of the plugin will then happen as part of the Moodle upgrade process.<br />
<br />
If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.<br />
<br />
==Put your site into maintenance mode==<br />
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in. Then you should wait for any currently running cron processes to complete before proceeding.<br />
<br />
== Install the new Moodle software ==<br />
You can fetch the current version of the software through <br />
<br />
wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz<br />
<br />
=== Standard install package ===<br />
<br />
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''<br />
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.<br />
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. <br />
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)<br />
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.<br />
<br />
====Linux====<br />
mv moodle moodle.backup<br />
tar xvzf moodle-{{Version}}.tgz<br />
<br />
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):<br />
<br />
cp moodle.backup/config.php moodle<br />
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme<br />
cp -pr moodle.backup/mod/mymod moodle/mod/mymod<br />
<br />
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.<br />
<br />
chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version)<br />
chmod -R 755 moodle<br />
<br />
If you use cron, take care that cron.php is executeable and uses the correct php command: <br />
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)<br />
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php') <br />
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.<br />
<br />
=== Using Git ===<br />
<br />
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.<br />
<br />
===Command line upgrade===<br />
<br />
On Linux servers, Moodle {{Version}} supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.<br />
<br />
== Finishing the upgrade ==<br />
<br />
The last step is to trigger the upgrade processes within Moodle. <br />
<br />
If you put your site into Maintenance mode earlier; take it out now!<br />
<br />
To do this just go to ''Administration > Site administration > Notifications''.<br />
<br />
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.<br />
<br />
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!<br />
<br />
Note: If you are running multiple servers then you should purge all caches manually (via ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.<br />
<br />
===Fatal error: Maximum execution time of 30 seconds exceeded...===<br />
<br />
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.<br />
<br />
==After upgrading==<br />
<br />
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 3.0 config-dist.php.<br />
<br />
===Cron===<br />
<br />
Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.<br />
<br />
The benefits of these changes are:<br />
* The schedule for every task can be configured by the admin<br />
* Tasks can run in parallel<br />
* Cron processes use locking to prevent the same task running at the same time by different processes<br />
* Clusters with multiple identical application nodes are supported, you can run cron on all of them<br />
<br />
A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.<br />
<br />
You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure. <br />
<br />
Before the upgrade, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade.<br />
<br />
===Assignments===<br />
<br />
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one. <br />
<br />
If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.<br />
<br />
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.<br />
<br />
==Possible issues that may affect you in Moodle {{Version}}==<br />
<br />
* Setting "Use HTTPS for logins" ('loginhttps') was completely removed since it provided false sense of security. If it was enabled before upgrade the whole site will be served via HTTPS protocol. The [HTTPS_conversion_tool|new tool] is available for administrator to convert links to embedded contents from http to https.<br />
* Minimum supported PHP version was raised to 7.0. You cannot run your Moodle 3.4 site on PHP 5.6 or lower (please refer to [Moodle_3.4_release_notes#Server_requirements|requirements section] for details).<br />
* Some authentication methods were removed from the standard distribution (fc, imap, nntp, pam, pop3). If you use them, you must provide them manually during the upgrade (MDL-50925).<br />
* The Messages block has been removed from the standard distribution. The new messages notification is displayed on the top of every page and this block is no longer needed. Block can be manually [https://github.com/moodlehq/moodle-block_messages downloaded] if needed<br />
* Support for custom registration hubs has been completely removed. Registration and course publishing is possible only with https://moodle.net<br />
* Course restore and import operations now will never change user dates and log dates. Only activity dates (due, open/close, etc.) will now change respective of the new course start date.<br />
<br />
See the [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]] for the full list of changes in Moodle {{Version}}.<br />
<br />
=== Moodle 3.1, 3.2 and 3.3 improvements ===<br />
<br />
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation<br />
<br />
* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]<br />
* [https://docs.moodle.org/32/en/Upgrading Upgrading to Moodle 3.2]<br />
* [https://docs.moodle.org/33/en/Upgrading Upgrading to Moodle 3.3]<br />
<br />
==See also==<br />
<br />
* [[Installation]]<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum] <br />
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]<br />
<br />
[[es:Actualización de moodle]]<br />
[[fr:Mise à jour]]<br />
[[ja:Moodleをアップグレードする]]<br />
[[de:Aktualisierung von Moodle]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=Media_FAQ&diff=128981Media FAQ2017-10-24T01:41:59Z<p>Marina.glancy: /* Why won't my FLV video play? */</p>
<hr />
<div>{{Working with media}}<br />
==Should I put my video into a label or a page?==<br />
While the embedding process is the same, adding a video to a label will mean it displays as soon as the user clicks on that course page. This can be beneficial if the video is, for example, an introduction to the course or an integral part of the whole course. However, if there are several videos in labels, they can slow the loading of the course down, especially if the videos are coming from an external site. Adding a video to a page in Moodle means that the user has to click a text link to reach the video, but it doesn't clutter up the main course page and it is a better choice if the course contains a large number of videos.<br />
<br />
==My embedded video is too big/small. How can I change its display size?==<br />
Changing the size of an embedded video depends on whether you're using Moodle's [[Multimedia plugins filter]] or if you're either embedding a video from another source using something like an iframe (for example, embedding a video from YouTube using the embed code they provide).<br />
<br />
====If you're using Moodle's Multimedia plugins filter:====<br />
*If you are not using it already, enable the [[Atto editor]] and click the Media icon.<br />
*Click the Video tab and then click Display options. You will be able to change its size there.<br />
<br />
====If you're using embed code====<br />
#Click the code/HTML source icon in your text editor<br />
#Locate the <iframe> tag or equivalent.<br />
#Inside that iframe should be "width" and "height" variables, which you can adjust as needed.<br>[[File:Youtuberesize.png]]<br />
#Click "update" in the HTML source editor screen, and save your changes. <br />
#Your video should now be the new size.<br />
<br />
==Why won't my swf video play?==<br />
The .swf format carries with it some security issues and so the filter that allows it to display is disabled by default. For you to be able to add .swf videos, your administrator needs to enable the filter in [[Multimedia_plugins|Multimedia plugins]], then to go to ''Site Administration>Security>Site policies'' and check the "enable trusted content" box. They then need to go to ''Site Administration>Users>Permissions>Define roles'' and allow Trust Submitted content ''moodle/site:trustcontent'' for your role. However; swf will still not display in all areas of Moodle, for example forum posts. See this discussion [http://moodle.org/mod/forum/discuss.php?d=183681#p800390| here]<br />
<br />
==Why won't my FLV video play?==<br />
<br />
FLV will only play if 'Use Flash fallback' is enabled in the 'VideoJS player' settings in the Site administration. It must also be supported by your browser and require plugins and permissions. Using Flash is not recommended for security reasons.<br />
<br />
==How can I convert my video file to an .FLV or other format?==<br />
*There are many sites online that allow you to upload a file which will then be converted and sent to you via a link or email. Zamzar [http://www.zamzar.com]or Youconvertit [http://www.youconvertit.com] are just two examples.<br />
*However, if it is a large video file or you want to do the conversion off line, then the free Any Video Converter [http://www.any-video-converter.com/products/for_video_free/] (a downloadable program) will convert most video formats to most others.<br />
*More and more full-featured MTS Video Converter [http://www.mtsconverterfree.com/]software free download a trial, to solve your problem more format conversions.<br />
*The free and open source video player, VLC has the ability to convert to and from many video formats. For more details and downloads [http://www.videolan.org/vlc/ visit their site].<br />
*If you are using Linux as your operating system either ffmpeg or avconv can both convert to FLV.<br />
<br />
== I have a .wma/wav file. How can I play it in Moodle's player?==<br />
*There are various free programs available that will convert one type of sound file to another. If you convert your file to an mp3 then you will be able to use Moodle's built-in mp3 player.<br />
*Jodix Free WMA to MP3 converter [http://www.wma-mp3.org/] is just one example<br />
<br />
==Videos don't embed even though the filters are enabled==<br />
You might need to change the order of your filters. See [[Filters]] and also the forum discussion [https://moodle.org/mod/forum/discuss.php?d=278993#p1198335 I can't embed YouTube videos]<br />
<br />
== How can I disable player embedding for one particular link? ==<br />
<br />
If you want to prevent the embedded player and keep just the link to the video, add "nomediaplugin" class to the HTML anchor tag producing the link. For example:<br />
<br />
<nowiki><a href="https://link.to/your/video" class="nomediaplugin">Link text</a></nowiki><br />
<br />
[[Category:FAQ]]<br />
[[Category:Audio]]<br />
[[Category:Video]]<br />
<br />
[[de:Multimedia FAQ]]<br />
[[es:Medios FAQ]]</div>Marina.glancyhttps://docs.moodle.org/34/en/index.php?title=PHP&diff=128297PHP2017-07-20T03:10:43Z<p>Marina.glancy: /* PHP Settings */</p>
<hr />
<div>{{Installing Moodle}}<br />
PHP is the scripting language in which Moodle is developed. It is integrated with your web server. The web server detects php pages (by their extension) and sends them to PHP for execution. PHP must be installed and configured properly for Moodle to work effectively (or at all). <br />
<br />
==PHP Settings==<br />
Check these settings in your php.ini or .htaccess file (if you're using Apache). For settings which use ON/OFF as their values, you can substitute 1 for ON and 0 for OFF if you prefer. If you change php.ini, don't forget to restart the server. <br />
* ''memory_limit'' needs to be at least 96M (although some functions may not work if this low). Moodle will refuse to install if lower. 128M is recommended. Large systems may need an even higher setting.<br />
* ''session.save_handler'' needs to be set to FILES.<br />
* ''magic_quotes_runtime'' needs to be OFF.<br />
* ''file_uploads'' needs to be ON.<br />
* ''session.auto_start'' needs to be OFF.<br />
* The temp folder must be defined and writeable by your webserver user<br />
* Check the error display/logging section. Make sure the settings are appropriate for your server use.<br />
* ''post_max_size'' and ''upload_max_filesize'' restrict the maximum file size that can be uploaded.<br />
* Check the ''[mail function]'' and database section (for your chosen database) to make sure they match your server configuration.<br />
<br />
==HTTP_RAW_POST_DATA errors==<br />
Some users are experiencing $HTTP_RAW_POST_DATA related errors, when establishing connection between MNET servers or making AJAX web services requests.<br />
<pre><br />
Request for server name returned empty response<br />
<br />
line 134 of /mnet/lib.php: call to debugging()<br />
line 115 of /admin/mnet/peers.php: call to mnet_get_public_key()<br />
</pre><br />
<br />
These errors are affecting users running moodle on PHP 5.6 version and it's a PHP bug on the '''always_populate_raw_post_data''' setting the default value to 0.<br />
<br />
To avoid the error messages above, please change the value following setting on your php.ini file:<br />
* '''always_populate_raw_post_data''' should be changed to '''-1'''.<br />
<br />
For more information about this bug, see: https://bugs.php.net/bug.php?id=66763<br />
<br />
==Finding the correct php.ini==<br />
Sometimes it is not obvious where the php.ini file is located or you may even find more than one. To be certain run 'phpinfo' - see below. The path of the php.ini file is a few lines down in the top section. <br />
<br />
Note that if you are using command-line (CLI) PHP for running cron (or anything else) it may be configured with a ''different'' php.ini file. To check, run the following command:<br />
<pre><br />
php -i | grep php.ini<br />
</pre><br />
<br />
==PHP Extensions and libraries==<br />
The following PHP extensions are required or recommended (some, e.g. iconv, ctype and tokenizer are now included in PHP by default). Others will need to be installed or selected.<br />
* The '''iconv''' extension is required.<br />
* The '''mbstring''' extension is recommended.<br />
* The '''curl''' extension is required (required for networking and web services).<br />
* The '''openssl''' extension is recommended (required for networking and web services).<br />
* The '''tokenizer''' extension is recommended.<br />
* The '''xmlrpc''' extension is recommended (required for networking and web services).<br />
* The '''soap''' extension is recommended (required for web services).<br />
* The '''ctype''' extension is required.<br />
* The '''zip''' extension is required.<br />
* The '''gd''' extension is recommended (required for manipulating images).<br />
* The '''simplexml''' extension is required.<br />
* The '''spl''' extension is required.<br />
* The '''pcre''' extension is required.<br />
* The '''dom''' extension is required.<br />
* The '''xml''' extension is required.<br />
* The '''intl''' extension is recommended.<br />
* The '''json''' extension is required.<br />
* '''The appropriate extension for your chosen database is also required.'''<br />
<br />
* Other PHP extensions may be required to support optional Moodle functionality, especially external authentication and/or enrolment (e.g. LDAP extension for LDAP authentication and the sockets extension for Chat server).<br />
<br />
==Installing (missing) extensions==<br />
<br />
This depends on how PHP was installed on your machine and what access you have. Here are some possibilities:<br />
* If this is a hosted server you are likely to have to ask the administrator or hosting company. <br />
* If PHP was compiled from source you will need to recompile, changing the 'configure' settings - see [[Compiling PHP from source]].<br />
* If it was installed using packages (typically Linux) you can install the required package (see your Linux distribution's documentation)<br />
* If you are using Windows you just need to uncomment the appropriate DLL files in php.ini<br />
<br />
After making any changes or additions, don't forget to re-start your web server.<br />
<br />
== .htaccess files ==<br />
<br />
If you don't have access to the php.ini file or there are conflicting requirements with other PHP applications on the same server you may be able to change PHP settings in an .htaccess file. This should be placed in the 'root' of your Moodle installation (i.e. the same place as the config.php file). <br />
<br />
'''The file isn't always called .htaccess and may not work at all. Contact your server administrator to be sure'''<br />
<br />
Settings are made by adding lines in one of two formats:<br />
* php_value ''name value''<br />
* php_flag ''name on/off''<br />
<br />
Examples:<br />
* '''php_value memory_limit 128M'''<br />
* '''php_flag register_globals off'''<br />
<br />
==PHP info==<br />
<br />
The phpinfo display contains information about the configuration of your PHP installation. This is useful for checking:<br />
* that your PHP installation meets Moodle's system requirements.<br />
* the values that are currently applied to your server's PHP install, e.g. File upload limits<br />
* that you have installed the required modules needed for Moodle to work, e.g. the LDAP module for LDAP authentication.<br />
<br />
=== Displaying phpinfo in Moodle===<br />
<br />
An administrator can find PHP info in ''Settings > Site administration > Server > PHP info''.<br />
<br />
=== Displaying phpinfo outside of Moodle ===<br />
<br />
To view the phpinfo information:<br />
* Create a file called info.php using your text editor, containing this single line:<br />
<br />
<code php><br />
<?php phpinfo(); ?><br />
</code><br />
<br />
* Save this file as info.php<br />
* Upload this file into the root web accessible folder on your server.<br />
* Now open this file in your browser. For example <nowiki>http://<server-name>/info.php</nowiki>.<br />
<br />
==See also==<br />
<br />
*[[Compiling PHP from source]]<br />
* [https://docs.moodle.org/dev/Moodle_and_PHP7 Moodle and PHP7] in the developers documentation<br />
*http://www.php.net/ - the PHP web site<br />
*http://php.iis.net/ - Microsoft PHP Installer for IIS<br />
* [[MoodleDocs:Style_guide#PHP_syntax_highlighting]] to highlight PHP syntax<br />
* [[Code syntax highlighting]] that uses the GeSHi (Generic Syntax Highlighter) filter. <br />
<br />
[[de:PHP-Versionen für Moodle]]<br />
[[es:PHP]]</div>Marina.glancy