https://docs.moodle.org/32/en/api.php?action=feedcontributions&feedformat=atom&user=Simoncoggins 2026-05-16T05:42:49Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/32/en/index.php?title=Course_creator_role&diff=115231 2014-10-13T23:24:21Z

<p>Simoncoggins: Undo revision 114044 by Nabuccocenter (talk)</p> <hr /> <div>{{Standard roles}}<br /> A user assigned the role of course creator can (as the name suggests!) create a course. If the setting &quot;Creators' role in new courses&quot; is left as default (teacher), then the course creator is enrolled as a teacher in the course they have just created and can then edit the course settings and enrol other users.<br /> <br /> A course creator can also view hidden courses.<br /> <br /> The role of course creator could typically be assigned to a master teacher, department head or program coordinator. <br /> <br /> ==Creating a course==<br /> <br /> The &quot;Add a new course&quot; button can be found at the bottom of the page listing all courses.<br /> <br /> When a course creator creates a course, they are automatically enrolled in the course as a teacher, or whatever role is set in ''Administration &gt; Site administration &gt; Users &gt; Permissions &gt; User policies''.<br /> <br /> '''Note (1):''' If a user is assigned the role of course creator in the course category context, the &quot;Add a new course&quot; button only appears when the course category contains at least one course.<br /> <br /> '''Note (2):''' Course creators are not automatically assigned the role of teacher in a course they have not created, even if it is in a category where they have course creator rights.<br /> <br /> ==Deleting a course==<br /> <br /> There is no user interface for course creators to delete courses they have created, however they can do so by editing the URL of the course from &lt;nowiki&gt;http://yourmoodlesite.net/course/view.php?id=N&lt;/nowiki&gt; to &lt;nowiki&gt;http://yourmoodlesite.net/course/delete.php?id=N&lt;/nowiki&gt; (replacing 'view' with 'delete').<br /> <br /> ==Role assignment==<br /> <br /> A user may be assigned the role of course creator as a system role (in ''Administration &gt; Site administration &gt; Users &gt; Permissions &gt; Assign system roles'') or in the course category context. <br /> <br /> ==Role permissions==<br /> <br /> If you require a course creator to have additional permissions, it is recommended that the [[Manager role]] is used, rather than changing the course creator role permissions. Otherwise, allowing additional capabilities for the course creator role may result in course creators having access to courses which they have not created.<br /> <br /> The role of course creator is ONLY intended for enabling users to create courses; it is not intended for enabling users to edit existing courses! <br /> <br /> [[fr:Créateur de cours]]<br /> [[ja:コース作成者]]<br /> [[de:Kursersteller-Rolle]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Capability_explorer&diff=112731 2014-05-19T20:53:25Z

<p>Simoncoggins: /* Installation */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Download the plugin code from:<br /> <br /> https://github.com/simoncoggins/moodle-tool_capexplorer<br /> <br /> Install this plugin into the 'admin/tool' folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ===Requirements===<br /> <br /> At present this plugin requires Moodle 2.7 or greater.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then find the tool in the Site Administration menu:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the contexts in your site. If you aren't sure just select 'System context'.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Capability_explorer&diff=112730 2014-05-19T20:44:09Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ===Requirements===<br /> <br /> At present this plugin requires Moodle 2.7 or greater.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then find the tool in the Site Administration menu:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the contexts in your site. If you aren't sure just select 'System context'.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Capability_explorer&diff=112729 2014-05-19T20:39:52Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ===Requirements===<br /> <br /> At present this plugin requires Moodle 2.7 or greater.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then find the tool in the Site Administration menu:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112728 2014-05-19T20:38:43Z

<p>Simoncoggins: Redirected page to Capability explorer</p> <hr /> <div>#redirect [[Capability_explorer]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Capability_explorer&diff=112727 2014-05-19T20:38:13Z

<p>Simoncoggins: Help documentation for the Capability explorer plugin</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ===Requirements===<br /> <br /> At present this plugin requires Moodle 2.7 or greater.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112714 2014-05-19T10:50:59Z

<p>Simoncoggins: /* Installation */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ===Requirements===<br /> <br /> At present this plugin requires Moodle 2.7 or greater.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112713 2014-05-19T10:50:15Z

<p>Simoncoggins: /* Installation */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called 'capexplorer', then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112712 2014-05-19T10:45:14Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112711 2014-05-19T10:44:51Z

<p>Simoncoggins: </p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]<br /> <br /> ==External Links==<br /> <br /> * [https://github.com/simoncoggins/moodle-tool_capexplorer Source code repository]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112710 2014-05-19T10:43:30Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form|600px]]<br /> <br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page|600px]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112709 2014-05-19T10:41:34Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form]]<br /> <br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> <br /> [[Image:capexplorer-results-full.png|thumb|center|Capability explorer results page]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=File:capexplorer-results-full.png&diff=112708 2014-05-19T10:41:21Z

<p>Simoncoggins: Screenshot of the full Capability explorer results page.</p> <hr /> <div>Screenshot of the full Capability explorer results page.</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112707 2014-05-19T10:40:22Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> [[Image:capexplorer-form.png|thumb|center|Capability explorer form]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results.png|thumb|center|Capability explorer results page]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112706 2014-05-19T10:39:17Z

<p>Simoncoggins: /* Usage */</p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> [[Image:capexplorer-form.png|frame|center|Capability explorer form]]<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.<br /> <br /> [[Image:capexplorer-results.png|frame|center|Capability explorer results page]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=File:capexplorer-results.png&diff=112705 2014-05-19T10:38:09Z

<p>Simoncoggins: Screenshot of the Capability explorer results page.</p> <hr /> <div>Screenshot of the Capability explorer results page.</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=File:capexplorer-form.png&diff=112704 2014-05-19T10:37:24Z

<p>Simoncoggins: Screenshot of the Capability explorer form</p> <hr /> <div>Screenshot of the Capability explorer form</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112699 2014-05-19T10:17:51Z

<p>Simoncoggins: </p> <hr /> <div>Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].<br /> <br /> ==Installation==<br /> <br /> Install this plugin into the admin/tool folder, in a subfolder called capexplorer, then visit the Site Administration &gt; Notifications page to install.<br /> <br /> ==Usage==<br /> <br /> Login as a user with access to the tool (by default a &quot;Manager&quot; or Site Administrator).<br /> <br /> You can then access the tool via:<br /> <br /> Site Administration &gt; Users &gt; Permissions &gt; Capability Explorer<br /> <br /> Submit the form by providing:<br /> <br /> * '''Username.''' The username of a user. The tool will check if this user has permission to do something. The field uses autocomplete so start typing a user's name, username or email address and select one of the options that appears.<br /> * '''Capability.''' The name of one of Moodle's capabilities. A full list of capabilities can be accessed via Site Administration &gt; Users &gt; Permissions &gt; Define system roles &gt; Manager. This field uses autocomplete so start typing a capability string and select one of the options that appears.<br /> * '''Context.''' A specific context in which to check the capability. You can select a context from the tree by clicking the name, or expand part of the tree using the arrows. The icons represent the type of item (e.g. course, category, block, module). The tree represents the hierarchical structure of the context tree of your site.<br /> <br /> The results page will give a summary of whether the user is granted the capability in the context you chose. Also shown is a step-by-step guide explaining how the capability was calculated. Click the help icons for more detailed information. If you have permission you can follow the change links to modify some of your existing permission settings.</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112698 2014-05-19T10:08:55Z

<p>Simoncoggins: </p> <hr /> <div>==Capability explorer==<br /> <br /> Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112697 2014-05-19T10:08:00Z

<p>Simoncoggins: /* Capability explorer */</p> <hr /> <div>=Capability explorer=<br /> <br /> Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report|Capability Overview Report]].</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112696 2014-05-19T10:07:35Z

<p>Simoncoggins: </p> <hr /> <div>=Capability explorer=<br /> <br /> Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[admin/roles/check#Checking_permissions|Check system permissions]] or the [[admin/tool/capability/index#Capability_overview_report Capability Overview Report]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=admin/tool/capexplorer/index&diff=112695 2014-05-19T10:06:23Z

<p>Simoncoggins: Created page with &quot;=Capability explorer= Capability explorer is a small admin tool designed to help explain exactly how Moodle&#039;s capability system works. Given a user, capability and context th...&quot;</p> <hr /> <div>=Capability explorer=<br /> <br /> Capability explorer is a small admin tool designed to help explain exactly how Moodle's capability system works. Given a user, capability and context the tool will provide a detailed breakdown of the process used to calculate if the capability would be granted to the user in the context specified.<br /> <br /> The tool uses the existing system data so you can use it to figure out why a particular user does or doesn't have a capability. It is designed to be complementary to Moodle's other permission tools such as [[https://docs.moodle.org/32/en/admin/roles/check#Checking_permissions|Check system permissions]] or the [https://docs.moodle.org/32/en/admin/tool/capability/index#Capability_overview_report Capability Overview Report]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=107871 2013-11-19T02:03:00Z

<p>Simoncoggins: /* Sites running PHP version below 5.3.7 */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse.<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onwards Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new scheme, but it may take a long time before all your users have logged in. Alternatively, if you would like to force all your users to use the new scheme you could force reset all passwords using [[Bulk_user_actions|Bulk user actions]].<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism relies on bcrypt support from PHP which is only normally available in PHP version is 5.3.7 or greater (see note below). If you are using a version of PHP which doesn't properly support bcrypt, Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt until you are able to upgrade PHP.<br /> <br /> Note: While an important fix to PHP's hashing algorithm was added in 5.3.7, some distributions of Linux have backported the fix to bcrypt to earlier versions of PHP. This means that some earlier versions of PHP may still work. To confirm if your PHP supports the new hashing scheme you can use [https://github.com/ircmaxell/password_compat/blob/master/version-test.php this test].<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105008 2013-05-13T20:32:28Z

<p>Simoncoggins: /* Sites running PHP version below 5.3.7 */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse.<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new scheme, but it may take a long time before all your users have logged in. Alternatively, if you would like to force all your users to use the new scheme you could force reset all passwords using [[Bulk_user_actions|Bulk user actions]].<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism is only supported if your PHP version is 5.3.7 or greater. If you are using a lower version of PHP Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt until you are able to upgrade PHP.<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105007 2013-05-13T20:30:26Z

<p>Simoncoggins: /* Backwards compatibility for site upgrades */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse.<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new scheme, but it may take a long time before all your users have logged in. Alternatively, if you would like to force all your users to use the new scheme you could force reset all passwords using [[Bulk_user_actions|Bulk user actions]].<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism is only supported if your PHP version is 5.3.7 or greater. If you are using a lower version of PHP Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt even for new 2.5 installations until you are able to upgrade PHP.<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105006 2013-05-13T20:29:45Z

<p>Simoncoggins: /* Backwards compatibility for site upgrades */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse.<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new scheme, but it may take a long time before all your users have logged in. Alternatively, if you would like to force all your users to use the new scheme you could force reset all passwords using [[Bulk_user_actions Bulk user actions]].<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism is only supported if your PHP version is 5.3.7 or greater. If you are using a lower version of PHP Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt even for new 2.5 installations until you are able to upgrade PHP.<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105005 2013-05-13T20:26:15Z

<p>Simoncoggins: </p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse.<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new scheme, but it may take a long time before all your users have logged in.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism is only supported if your PHP version is 5.3.7 or greater. If you are using a lower version of PHP Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt even for new 2.5 installations until you are able to upgrade PHP.<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105004 2013-05-13T20:25:17Z

<p>Simoncoggins: </p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new system, but it may take a long time before all your users have logged in.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> ==Sites running PHP version below 5.3.7==<br /> <br /> The new password hashing mechanism is only supported if your PHP version is 5.3.7 or greater. If you are using a lower version of PHP Moodle will fall back to the old password hashing scheme, so we recommend that you continue to use a site-wide salt even for new 2.5 installations until you are able to upgrade PHP.<br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105003 2013-05-13T20:23:22Z

<p>Simoncoggins: /* Backwards compatibility */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility for site upgrades==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new system, but it may take a long time before all your users have logged in.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> <br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105002 2013-05-13T20:22:49Z

<p>Simoncoggins: /* How does Moodle use password salting? */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for '''new''' installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new system, but it may take a long time before all your users have logged in.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> <br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105001 2013-05-13T20:22:38Z

<p>Simoncoggins: /* Backwards compatibility */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for new installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility==<br /> <br /> '''Important!''' If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> Each time a user logs in their password hash will be converted to the new system, but it may take a long time before all your users have logged in.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> <br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=105000 2013-05-13T20:21:12Z

<p>Simoncoggins: /* How does Moodle use password salting? */</p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 there was a single site-wide salt which was used when hashing every user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for new installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility==<br /> <br /> If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> <br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Password_salting&diff=104999 2013-05-13T20:20:16Z

<p>Simoncoggins: </p> <hr /> <div>{{Security}}<br /> ==What is password salting?==<br /> <br /> [http://en.wikipedia.org/wiki/Salt_%28cryptography%29 Password salting] is a way of making password hashing more secure by adding a random string of characters to passwords before their hash is calculated, which makes them harder to reverse (the longer the random string, the harder you make it).<br /> <br /> ==How does Moodle use password salting?==<br /> <br /> Prior to Moodle 2.5 Moodle used a single site-wide salt which was used when hashing each user's password. From Moodle 2.5 onward Moodle automatically generates and adds a different salt for each individual user. This is more secure and means that a site-wide configuration variable for the salt is no longer required for new installations of 2.5 or greater.<br /> <br /> ==Backwards compatibility==<br /> <br /> If you are upgrading a site from 2.4 or below and you are already using a site-wide salt in your configuration file, '''you need to keep using it to ensure your existing users can still log in'''.<br /> <br /> For more details about the old site-wide salt configuration, see the [https://docs.moodle.org/24/en/Password_salting Moodle 2.4 Password Salt documentation].<br /> <br /> <br /> <br /> [[cs:Solení hesel]]<br /> [[de:Kennwortverschlüsselung (Salt)]]<br /> [[es:report/security/report_security_check_passwordsaltmain]]<br /> [[fr:Salage de mot de passe]]<br /> [[it:report/security/report_security_check_passwordsaltmain]]<br /> [[nl:report/security/report_security_check_passwordsaltmain]]<br /> [[ja:パスワードSALT]]<br /> [[ru:Зашумление паролей]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Upgrading&diff=104750 2013-05-05T20:11:09Z

<p>Simoncoggins: /* Possible issues that may affect you in Moodle 2.5 */</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 2.5 in ''Settings &gt; Site administration &gt; Server &gt; [[Environment]]''.<br /> <br /> Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br /> <br /> ==Check for plugin updates==<br /> <br /> Check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.5 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and 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 /> Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.<br /> <br /> ==Before you upgrade your site for real==<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 /> == 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 /> ==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.<br /> <br /> == Install the new Moodle software ==<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 custom plugins on your site you should add them to the new code. 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. <br /> <br /> ====Linux====<br /> mv moodle moodle.backup<br /> tar xvzf moodle-2.5.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 /> 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 '&lt;?php')<br /> <br /> if necessary.<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 2.5 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 /> To do this just go to ''Settings &gt; Site administration &gt; 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 ''Settings &gt; Site administration &gt; Development &gt; Purge all caches'') after completing the upgrade on all servers.<br /> <br /> ==After upgrading==<br /> <br /> The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 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 2.5 config-dist.php.<br /> <br /> ==Possible issues that may affect you in Moodle 2.5==<br /> <br /> ===Multi-server architectures with different PHP versions ===<br /> <br /> Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).<br /> <br /> ===Restoring Moodle 2.5 backups to sites with old PHP versions===<br /> <br /> Because bcrypt is not supported in PHP versions below 5.3.7, course backups made using the $CFG-&gt;includeuserpasswordsinbackup setting on a site using PHP version 5.3.7+ that are subsequently restored to a site with PHP version &lt; 5.3.7 will require a password reset.<br /> <br /> The same issue would occur if you downgraded the PHP version on the server running your site from 5.3.7+ to less than 5.3.7 (MDL-35332).<br /> <br /> ===Course listing improvements===<br /> <br /> Course listings are now displayed consistently throughout the site. See [[:dev:Courses lists upgrade to 2.5]] for details of admin setting changes and possible custom theme changes required.<br /> <br /> <br /> ''Please add further items...''<br /> <br /> === Moodle 2.3 and 2.4 improvements ===<br /> <br /> If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3] and [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4].<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br /> * [[dev:Moodle 2.5 release notes|Moodle 2.5 release notes]]<br /> * [[dev:Upgrade API|Upgrade API]]<br /> <br /> [[es:Actualización de moodle]]<br /> [[fr:Mise à jour]]<br /> [[ja:Moodleをアップグレードする]]<br /> [[de:Aktualisierung von Moodle]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Upgrading&diff=104749 2013-05-05T20:09:50Z

<p>Simoncoggins: /* Possible issues that may affect you in Moodle 2.5 */</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 2.5 in ''Settings &gt; Site administration &gt; Server &gt; [[Environment]]''.<br /> <br /> Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br /> <br /> ==Check for plugin updates==<br /> <br /> Check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.5 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and 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 /> Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.<br /> <br /> ==Before you upgrade your site for real==<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 /> == 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 /> ==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.<br /> <br /> == Install the new Moodle software ==<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 custom plugins on your site you should add them to the new code. 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. <br /> <br /> ====Linux====<br /> mv moodle moodle.backup<br /> tar xvzf moodle-2.5.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 /> 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 '&lt;?php')<br /> <br /> if necessary.<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 2.5 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 /> To do this just go to ''Settings &gt; Site administration &gt; 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 ''Settings &gt; Site administration &gt; Development &gt; Purge all caches'') after completing the upgrade on all servers.<br /> <br /> ==After upgrading==<br /> <br /> The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 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 2.5 config-dist.php.<br /> <br /> ==Possible issues that may affect you in Moodle 2.5==<br /> <br /> ===Multi-server architectures with different PHP versions ===<br /> <br /> Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).<br /> <br /> ===Restoring Moodle 2.5 backups to sites with old PHP versions===<br /> <br /> Because bcrypt is not supported in PHP versions below 5.3.7, course backups made using the $CFG-&gt;includeuserpasswordsinbackup setting on a site using PHP version 5.3.7+ that are subsequently restored to a site with PHP version &lt; 5.3.7 will require a password reset.<br /> <br /> The same issue would occur if you downgraded the PHP version on the server running your site from 5.3.7+ to less than 5.3.7.<br /> <br /> ===Course listing improvements===<br /> <br /> Course listings are now displayed consistently throughout the site. See [[:dev:Courses lists upgrade to 2.5]] for details of admin setting changes and possible custom theme changes required.<br /> <br /> <br /> ''Please add further items...''<br /> <br /> === Moodle 2.3 and 2.4 improvements ===<br /> <br /> If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3] and [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4].<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br /> * [[dev:Moodle 2.5 release notes|Moodle 2.5 release notes]]<br /> * [[dev:Upgrade API|Upgrade API]]<br /> <br /> [[es:Actualización de moodle]]<br /> [[fr:Mise à jour]]<br /> [[ja:Moodleをアップグレードする]]<br /> [[de:Aktualisierung von Moodle]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Upgrading&diff=104748 2013-05-05T19:57:05Z

<p>Simoncoggins: /* Multi-server architectures with difference php versions */</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 2.5 in ''Settings &gt; Site administration &gt; Server &gt; [[Environment]]''.<br /> <br /> Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br /> <br /> ==Check for plugin updates==<br /> <br /> Check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.5 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and 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 /> Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.<br /> <br /> ==Before you upgrade your site for real==<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 /> == 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 /> ==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.<br /> <br /> == Install the new Moodle software ==<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 custom plugins on your site you should add them to the new code. 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. <br /> <br /> ====Linux====<br /> mv moodle moodle.backup<br /> tar xvzf moodle-2.5.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 /> 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 '&lt;?php')<br /> <br /> if necessary.<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 2.5 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 /> To do this just go to ''Settings &gt; Site administration &gt; 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 ''Settings &gt; Site administration &gt; Development &gt; Purge all caches'') after completing the upgrade on all servers.<br /> <br /> ==After upgrading==<br /> <br /> The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 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 2.5 config-dist.php.<br /> <br /> ==Possible issues that may affect you in Moodle 2.5==<br /> <br /> ===Multi-server architectures with different PHP versions ===<br /> <br /> Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).<br /> <br /> ===Course listing improvements===<br /> <br /> Course listings are now displayed consistently throughout the site. See [[:dev:Courses lists upgrade to 2.5]] for details of admin setting changes and possible custom theme changes required.<br /> <br /> <br /> ''Please add further items...''<br /> <br /> === Moodle 2.3 and 2.4 improvements ===<br /> <br /> If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3] and [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4].<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br /> * [[dev:Moodle 2.5 release notes|Moodle 2.5 release notes]]<br /> * [[dev:Upgrade API|Upgrade API]]<br /> <br /> [[es:Actualización de moodle]]<br /> [[fr:Mise à jour]]<br /> [[ja:Moodleをアップグレードする]]<br /> [[de:Aktualisierung von Moodle]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Upgrading&diff=104747 2013-05-05T19:56:52Z

<p>Simoncoggins: /* Multi-server architectures with difference php versions */</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 2.5 in ''Settings &gt; Site administration &gt; Server &gt; [[Environment]]''.<br /> <br /> Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.<br /> <br /> ==Check for plugin updates==<br /> <br /> Check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.5 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and 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 /> Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.<br /> <br /> ==Before you upgrade your site for real==<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 /> == 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 /> ==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.<br /> <br /> == Install the new Moodle software ==<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 custom plugins on your site you should add them to the new code. 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. <br /> <br /> ====Linux====<br /> mv moodle moodle.backup<br /> tar xvzf moodle-2.5.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 /> 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 '&lt;?php')<br /> <br /> if necessary.<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 2.5 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 /> To do this just go to ''Settings &gt; Site administration &gt; 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 ''Settings &gt; Site administration &gt; Development &gt; Purge all caches'') after completing the upgrade on all servers.<br /> <br /> ==After upgrading==<br /> <br /> The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 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 2.5 config-dist.php.<br /> <br /> ==Possible issues that may affect you in Moodle 2.5==<br /> <br /> ===Multi-server architectures with difference php versions ===<br /> <br /> Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).<br /> <br /> ===Course listing improvements===<br /> <br /> Course listings are now displayed consistently throughout the site. See [[:dev:Courses lists upgrade to 2.5]] for details of admin setting changes and possible custom theme changes required.<br /> <br /> <br /> ''Please add further items...''<br /> <br /> === Moodle 2.3 and 2.4 improvements ===<br /> <br /> If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3] and [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4].<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] <br /> * [[dev:Moodle 2.5 release notes|Moodle 2.5 release notes]]<br /> * [[dev:Upgrade API|Upgrade API]]<br /> <br /> [[es:Actualización de moodle]]<br /> [[fr:Mise à jour]]<br /> [[ja:Moodleをアップグレードする]]<br /> [[de:Aktualisierung von Moodle]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Configuration_file&diff=102947 2013-01-31T08:11:24Z

<p>Simoncoggins: /* Including passwords in backups */</p> <hr /> <div>{{Installing Moodle}}<br /> The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).<br /> <br /> <br /> ==config-dist.php==<br /> Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. A sample config file, called config-dist.php, is shipped with Moodle.<br /> <br /> To get started simply copy config-dist.php to config.php, then edit config.php with you favourite editor. The file is very well commented. The important options (which you must supply) are all nearer the top. Other less common options are further down.<br /> <br /> ==Setting $CFG-&gt;wwwroot correctly==<br /> This setting must be a fixed URL (a string constant) that points to your site. Do not try to set this with any PHP code that can generate a variable URL. This is not supported, can cause strange problems and will stop command line scripts working completely. If your site is accessed from different IP addresses this should be done with a split DNS, see [[Masquerading]]<br /> <br /> ==Enabling password salting==<br /> <br /> See [[Password salting]].<br /> <br /> ==Including passwords in backups==<br /> <br /> Hashed user passwords are no longer saved in backup files containing user data in Moodle 1.8.11 and 1.9.7 onwards.<br /> <br /> If you really need passwords to be saved (in the rare case of restoring a backup with user data to a different site), the following line may be added to config.php:<br /> <br /> $CFG-&gt;includeuserpasswordsinbackup<br /> <br /> ==Changing default block layout for new courses==<br /> <br /> See [[Block layout]].<br /> <br /> ==Changing default theme directory location==<br /> The location of theme directories may be altered, using the variables ''$CFG-&gt;themewww'' and ''$CFG-&gt;themedir''. Themes placed in the directory specified by these variables will then be available for selection using the theme selector.<br /> <br /> For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:<br /> &lt;pre&gt;<br /> $CFG-&gt;wwwroot = 'http://my.moodle.site.edu';<br /> $CFG-&gt;dirroot = '/var/www/my.moodle.site.edu/public_html';<br /> $CFG-&gt;themewww = $CFG-&gt;wwwroot . '/my_moodle_themes';<br /> $CFG-&gt;themedir = $CFG-&gt;dirroot . '/my_moodle_themes';<br /> &lt;/pre&gt;<br /> <br /> ==Disabling update notifications==<br /> <br /> See [[Notifications]].<br /> <br /> ==Enabling debugging==<br /> <br /> See [[Debugging]].<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion<br /> <br /> [[de:Konfigurationsdatei]]<br /> [[fr:Fichier de configuration]]<br /> [[ja:設定ファイル]]</div>

Simoncoggins https://docs.moodle.org/32/en/index.php?title=Development:Profiling_PHP&diff=77674 2010-11-10T22:51:36Z

<p>Simoncoggins: /* See also */</p> <hr /> <div>PHP has two significant profilers...<br /> <br /> One is [http://www.xdebug.org/docs/profiler XDebug] - this is well known and understood and it's trace output is supported by tools like [http://kcachegrind.sourceforge.net/html/Home.html KCachegrind].<br /> <br /> The other is [http://pecl.php.net/package/xhprof xhprof], a profiler released by facebook's engineering team, designed for capturing profile traces on live servers. Compared to XDebug, xhprof aims to have the minimum impact on execution times and require relatively little space to store a trace, so you can run it live without a noticeable impact on users and without filling disks. The trade off with xhprof is in ''slightly'' less detail and a trace format that needs it's own GUI to visualize (which ships with xhprof). The reason you'd want to profile in a live environments (vs. on development) is certain categories of problem may only been seen live, e.g. (data related) what happens when the user table grows 100 times, the impact on &quot;login.php&quot; or (service related) server to server HTTP requests. Did a presentation once [https://docs.google.com/present/view?id=dcbkgbgf_45fbg3rnmk XHProf - facebooks PHP profiler] which explains in more detail - Penny saw the talk which is how I ended up writing this.<br /> <br /> ==See also==<br /> <br /> * [http://moodle.org/mod/forum/discuss.php?d=162045 Forum thread about profiling Moodle 2.0]<br /> * [https://docs.google.com/present/view?id=dcbkgbgf_45fbg3rnmk&amp; presentation about xhprof]<br /> * http://techportal.ibuildings.com/2009/12/01/profiling-with-xhprof/<br /> * http://devzone.zend.com/article/2803-Introducing-xdebug<br /> <br /> {{CategoryDeveloper}}</div>

Simoncoggins