MoodleDocs - Wkład użytkownika [pl]

Upgrading

2012-11-29T08:58:35Z

Markn86: /* Possible issues that may affect you in Moodle 2.4 */

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Check that your server meets all requirements for 2.4 in ''Settings > Site administration > Server > [[Environment]]''.

Note: You can only upgrade to Moodle 2.4 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.

==Checking database schema - old sites==

If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.4 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]. You should also run the database integrity checks in the XMLDB editor.

==Contributed plugins==

Any contributed/custom plugins (including themes) that you have previously installed on your site will also need to be replaced with a version suitable for Moodle 2.4 ''before'' upgrading your Moodle installation.
* Check in the [http://moodle.org/plugins Moodle Plugins directory] for a Moodle 2.4 version of the plugin and copy it to the appropriate location in your Moodle code.
* The upgrade of the plugin will happen as part of the Moodle upgrade process.
* If there is not a Moodle 2.4 version of the plugin available, you will need to [[Installing plugins|uninstall the plugin]] before upgrading, otherwise the Moodle upgrade will fail.

==Before you upgrade your site for real==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

== Backup important data ==

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, the SQL or Postgres database)

See [[Site backup]] for more specific information.

==Put your Site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.

== Install the new Moodle software ==

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# 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.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# 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.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-2.4.tgz

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'''):

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

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.

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')

if necessary.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle 2.4 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.

== Finishing the upgrade ==

The last step is to trigger the upgrade processes within Moodle.

To do this just go to ''Settings > Site administration > Notifications''.

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.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

==After upgrading==

The config.php file from your 2.2 or 2.3 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.4 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.4 config-dist.php.

==Possible issues that may affect you in Moodle 2.4==

=== Block capabilities undefined. ===

You may get a debugging message warning you that a capability has not been defined for a custom block. For example:

<pre>
The block <blockname> does not define the standard capability block/<blockname>:myaddinstance

line 597 of /blocks/moodleblock.class.php: call to debugging()
line 570 of /blocks/moodleblock.class.php: call to block_base->has_add_block_capability()
line 236 of /lib/blocklib.php: call to block_base->user_can_addto()
line 1834 of /lib/blocklib.php: call to block_manager->get_addable_blocks()
line 1007 of /lib/blocklib.php: call to block_add_block_ui()
line 353 of /lib/blocklib.php: call to block_manager->ensure_content_created()
line 6 of /theme/base/layout/general.php: call to block_manager->region_has_content()
line 804 of /lib/outputrenderers.php: call to include()
line 734 of /lib/outputrenderers.php: call to core_renderer->render_page_layout()
line 74 of /user/files.php: call to core_renderer->header()
</pre>

Moodle 2.4 onwards introduced the capabilities addinstance and myaddinstance for core blocks. They were introduced so that it was possible to control the use of individual blocks. Please see [[Blocks#Ready.2C_Set.2C_Go.21]] for more information.

=== Two assignment modules ===

A new assignment module was added in Moodle 2.3. The old assignment module is still available (renamed 'Assignments 2.2') and sites which have upgraded from previous versions will have both versions available.

It is recommended that admins upgrade all existing assignments to use the new assignment module as soon as possible, as described in [[Upgrade tool|Assignment upgrade tool]], then disable the old assignment module, to avoid the confusion of having two assignment modules.

===Google registration required for Google Docs and Picasa plugins===

Due to a change in Google's service, Moodle 2.3 onwards has switched to a more secure and more user-friendly system for communicating with Google called 'OAuth 2.0'. As a result, any Google Docs and Picasa plugins (the Google Docs and Picasa repositories and the Google Docs and Picasa portfolios) used previously on the site will be disabled when the site is upgraded.

To re-enable these plugins, an administrator must register their site with Google, as described in [[Google OAuth 2.0 setup]], and obtain a client ID and secret. The client ID and secret can then be used to configure all Google Docs and Picasa plugins.

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[dev:Moodle 2.4 release notes|Moodle 2.4 release notes]]
* [[dev:Upgrade API|Upgrade API]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Conditional activities settings

2012-11-23T03:12:33Z

Markn86: /* Restricting access by user profile fields */

{{Conditional activities}}
==Enabling the use of conditional activities==

To use conditional activities, the feature must be enabled by an administrator by checking the enable availability box in ''Settings > Site administration > Advanced features''. A restrict access section will then appear for teachers on the edit activity page.

==Restricting access==
[[File:newrestrictaccess.png]]

The restrict access section asks for the conditions when the activity (or resource) should be visible. This can be based upon dates, and/or score ranges of other activities and/or if other activities are considered completed (see [[Activity completion]]). Note that ALL access restrictions (date, grade condition, activity completion condition) have to be met in order for the activity to be made available.

Note that it is possible to restrict access based on an actual time and not just a date.

===Restricting access to course sections===

It is possible to restrict access to activities within a whole course section by specifying the conditions in the settings for that particular section.

[[File:sectioncompletion1.png]]

Watch the [http://youtu.be/5Z0pYuOiZ5E "Restrict access to course sections" screencast] for a demonstration.

===Restricting access by user profile fields===

{{New features}}

It is possible to restrict access to activities based on a custom user profile field. You can select a field type, condition and name. For more information please see [[Conditional_user_fields]]. You can also watch the [http://www.youtube.com/watch?v=Y3LNq82gD9k&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg "Conditional profile fields" screencast] to see this feature in action.

{|
|[[File:userfield1.png|thumb|Restricting access by user profile field]]
|[[File:userfield2.png|thumb|An example of restricting access to members of one department only]]
|}

===Grade condition===

You can specify a condition on any grade in the course: the full course grade, the grade for any activity, or a custom grade that you create manually. You can enter either a minimum value (at least percentage), a maximum value (less than percentage), both, or neither. The activity will only appear if the student has a value for the specified grade, and if it falls within any specified number range. You can add more than one grade condition. All conditions must be met in order for the activity to appear.

* The range numbers can be fractional (with up to five decimal places) if necessary.
* Be careful with the maximum value; if the maximum is 7, a student who scores exactly 7 will not see the activity. You could set it to 7.01 if you really wanted to include 7.
* If creating several different activities that appear according to grade ranges, use the same number for the maximum of one activity, and the minimum of the next. For example, you might create one activity with a maximum of 7 and another with a minimum of 7. The first would appear to everyone scoring between 0 and 6.99999, and the second would appear to everyone scoring 7.00000 to 10. This guarantees that everyone with a grade will see one or other.

[[de:Einstellungen zur bedingten Verfügbarkeit]]

Conditional activities settings

2012-11-23T03:10:50Z

Markn86: /* Restricting access by user profile fields */

{{Conditional activities}}
==Enabling the use of conditional activities==

To use conditional activities, the feature must be enabled by an administrator by checking the enable availability box in ''Settings > Site administration > Advanced features''. A restrict access section will then appear for teachers on the edit activity page.

==Restricting access==
[[File:newrestrictaccess.png]]

The restrict access section asks for the conditions when the activity (or resource) should be visible. This can be based upon dates, and/or score ranges of other activities and/or if other activities are considered completed (see [[Activity completion]]). Note that ALL access restrictions (date, grade condition, activity completion condition) have to be met in order for the activity to be made available.

Note that it is possible to restrict access based on an actual time and not just a date.

===Restricting access to course sections===

It is possible to restrict access to activities within a whole course section by specifying the conditions in the settings for that particular section.

[[File:sectioncompletion1.png]]

Watch the [http://youtu.be/5Z0pYuOiZ5E "Restrict access to course sections" screencast] for a demonstration.

===Restricting access by user profile fields===

{{New features}}

It is possible to restrict access to activities based on a custom user profile field. You can select a field type, condition and name. For more information please see [[Conditional_user_fields]]. You can also watch the [http://www.youtube.com/watch?v=Y3LNq82gD9k&feature=share&list=UUCRg_EbhU9tdpLdiGGN1Mgg "Conditional profile fields" screencast] to see this feature in action.

===Grade condition===

You can specify a condition on any grade in the course: the full course grade, the grade for any activity, or a custom grade that you create manually. You can enter either a minimum value (at least percentage), a maximum value (less than percentage), both, or neither. The activity will only appear if the student has a value for the specified grade, and if it falls within any specified number range. You can add more than one grade condition. All conditions must be met in order for the activity to appear.

* The range numbers can be fractional (with up to five decimal places) if necessary.
* Be careful with the maximum value; if the maximum is 7, a student who scores exactly 7 will not see the activity. You could set it to 7.01 if you really wanted to include 7.
* If creating several different activities that appear according to grade ranges, use the same number for the maximum of one activity, and the minimum of the next. For example, you might create one activity with a maximum of 7 and another with a minimum of 7. The first would appear to everyone scoring between 0 and 6.99999, and the second would appear to everyone scoring 7.00000 to 10. This guarantees that everyone with a grade will see one or other.

[[de:Einstellungen zur bedingten Verfügbarkeit]]

Conditional user fields

2012-11-23T03:07:21Z

Markn86: Created page with "This page explains how to restrict an activity, resource or course section via user fields and/or custom profile fields. ==Instructions== 1. Conditional access must be enabled...."

This page explains how to restrict an activity, resource or course section via user fields and/or custom profile fields.

==Instructions==

1. Conditional access must be enabled. (see [[Conditional_activities]] for instructions on how to enable this for your site).<br />
2. When adding or editing an activity, resource or course section scroll to the user fields in the 'Restrict Access' section.<br />
3. Choose which fields you want to restrict by (adding more if needed), select the restriction you want to put in place and then enter a value.<br />
4. Save the settings.

==Example==

This is an example of the interface in Moodle when adding an activity to a course with the conditional functionality enabled

[[File:conditional_user_setup.jpg]]

This is how it will appear to users who fail to meet the restrictions set in place.

[[File:conditional_user_courseview.jpg]]

==User Fields==

You can restrict by using one of the user fields that are located in the Moodle user table. Not all the user fields are included, as not all of them would make sense in this context. The ones included are listed below.

===AIM ID===

This is the value in the 'aim' column.

===Address===

This is the value in the 'address' column.

===City/town===

This is the value in the 'city' column.

===Country===

This is the value in the 'country' column.

===Department===

This is the value in the 'department' column.

===Email Address===

This is the value in the 'email' column.

===First name===

This is the value in the 'firstname' column.

===ICQ number===

This is the value in the 'icq' column.

===ID number===

This is the value in the 'idnumber' column.

===Institution===

This is the value in the 'institution' column.

===Interests===

This is the value in the 'interests' column.

===MSN ID===

This is the value in the 'msn' column.

===Mobile phone===

This is the value in the 'phone2' column.

===Phone===

This is the value in the 'phone1' column.

===Skype ID===

This is the value in the 'skype' column.

===Surname===

This is the value in the 'lastname' column.

===Web page===

This is the value in the 'url' column.

===Yahoo ID===

This is the value in the 'yahoo' column.

==Custom Profile Fields==

These are all the custom profile fields that have been created on the Moodle site. See [[User_profile_fields]]

==Operators==

The operators define the relationship between the field chosen and the value entered. For example, when the user's email must contain @school.com, the field chosen is 'Email address', the operater is 'contains' and the value is '@school.com'.

===Contains===

This operator restricts access to those whos chosen field contains the value provided.

===Does not contain===

This operator restricts access to those whos chosen field does not contain the value provided.

===Is Equal To===

This operator restricts access to those whos chosen field equals the value provided.

===Starts With===

This operator restricts access to the activity to those whos chosen field starts with the value provided.

===Ends With===

This operator restricts access to the activity to those whos chosen field ends with the value provided.

===Is Empty===

This operator restricts access to the activity to those whos chosen field is empty. Note, if any value is provided in this case, it is ignored.

error/moodle/nopermissions

2012-10-08T10:24:34Z

Markn86:

This is a general error that indicates the current user account does not have permission to do what you were attempting.

One of the most likely causes is that you are trying to do something as a guest user (somebody who has not yet logged in to Moodle).

This feature is part of the [[Roles]] framework introduced in Moodle 1.7. If you believe that your roles for that user DO allow that action you were attempting, then you may have found a bug. Congratulations! Please help us by creating a new issue at http://tracker.moodle.org/browse/MDL and describing what you did in detail.

[[Category:Roles|Error]]
[[Category:Error|Nopermissions]]

[[eu:error/moodle/nopermissions]]
[[fr:error/moodle/nopermissions]]
[[zh:error/moodle/nopermissions]]

Plik:conditional user courseview.jpg

2012-05-17T09:33:42Z

Markn86:

Plik:conditional user setup.jpg

2012-05-17T09:05:26Z

Markn86:

Certificate module

2011-10-26T04:03:37Z

Markn86:

{{Update}}
The '''Certificate module''' creates PDF certificates/diplomas for students of the course and is completely customizable. You can add borders, watermarks, seals and even show grade information.

Certificate 2.x should be tested on your site or a place that will be similar to your production site. The PukunuiAustralia version is the best one to download for 2.x production servers. See bugs comments below.

==Certificate examples==
Here are 3 examples. A certificate that uses the standard features found in the install package. Then 2 others with slightly more customization.
<gallery caption="Certificate examples - click on any to enlarge" widths="200px" heights="100px" perrow="6">
Image:Certificate 1.gif|Standard features showing: Fancy border, signature line, seal, code
Image:Certificate199 example lines.png|Standard lines, signature, seal, watermark, code, grade, outcomes, with custom text
Image:Certificate199 example creative.png|Custom border, custom signature, custom seal, custom watermark, code, outcome
</gallery>

==Installing==
#Download and Unpack the Certificate zip file in a temporary area,
#Copy the "certificate" folder to your moodle mod folder located for example at yourhost\moodle\mod . This will include folders backup, db, lang, pix (including subfolders for borders, seals, signatures and watermarks), and type (with sub folders for each of 4 default types).
#Go to your Moodle, and click on the Notifications link in the Site administration. Moodle knows something has been added and it will proceed to install the certificate module.
:Note: It is not necessary to move the lang file into the Moodle lang folder, the certificate lang folder can stay in the mod/certificate folder.
:Note: If the download zip/tar file does not create a certificate folder, rename the top folder certificate. There needs to be a folder in /mod called certificate.
See also: [[Installing_contributed_modules_or_plugins]] in MoodleDocs.

==Settings==
This is a short list of settings listed by their group. Please see [[Add/edit_certificate_module]] for more detailed information.

*General - Certificate name and introduction. The certificate will use the course name, this is the link name.
*Issue options -Here you can set email options, determine if you want to save and or reissue certificates.
*Print text options - determine date, security code, grade outcomes, credit hours, teachers names, custom text.
*Design (and image) options - select Type, then determine orientation, and select images for border, lines, watermark, signature, seal or say no to any or all of them.
*Common module settings -These are standard Moodle module settings. See [[Common module settings]]
*Locking options - if conditional dependencies has been turned on by the site administrator, teacher can set standards that must be met before certificate can be issued.

==Customizing certificate==
There are several ways to create a custom certificate. Please see [[Certificate customizing]] for many examples.

The easiest way is to add your images to the appropriate /mod/certificate/pix folder. This will make them available under settings. For example, add your logo to the "seals" folder. Another way is to edit the text strings in the /mod/certificate/lang folder files.

However, it is possible to reposition and format text and images by editing a single file located in the /mod/certificate/type folder. You may create as many "types" of certificates as you wish. This is more complicated and requires some knowledge of PHP and TCPDF (which is the open source software used by Moodle to generate the Certificate files.

==Certificate companions==
{{Update}}
Not all these may work with Moodle 2.x.

===Certificate Site-wide Report===
As of February 2008, there is a '''Certificate Site-wide Report''' which can be added in Moodle 1.9, as a supplement. This is an add-on to the certificate module--if installed, you will have an option when creating a certificate to send that certificate's info to the report. An optional block is included that provides a link to the report. Students will see a list of all received certificates. Administrators (or those who have the capability of viewing site reports) will see a link on the Certificate Report page to view/download a report of all students' received certificates. To install: Place the certificates folder in your root (main) moodle folder and upload to your server. Place the my_certificates block folder under your moodle/blocks folder, upload to your server and click on the Administration>>Notifications link to install.

===Certificate Verification Block===
A companion to the Certificate module for Moodle 1.9. This is a block with a form for entering a given certificate code for verification. The verification page shows the student name, course name, date received and grade (if a grade is printed on the certificate). The certificate code can be printed on a certificate.

This feature is useful when a Registrar, supervisor or administrator wishes to verify that the printed certificate is valid for that student. To install: Place the verify_certificate block folder under your moodle/blocks folder, upload to your server and click on the Administration>>Notifications link to install.

==See also==
* [[Add/edit certificate module]]
* [[mod/certificate/view|Viewing a Certificate]]
* [[Certificate customizing]] - many tips and how tos

The links below will lead to the current download areas
{{Update}}

*[https://github.com/PukunuiAustralia/moodle-mod_certificate PukunuiAustralia / moodle-mod_certificate] Version 2.0 but will work with 2.1 as well.

* Moodle.org link? Certificate Sitewide Reports plugin
* Moodle.org link? Certificate Validation Block plugin

* Using Moodle [http://moodle.org/mod/forum/view.php?id=7163 Certificate module] forum
* [[Activity_Locking]] - a conditional dependency add-in
* [[Development:Certificate Module|Development of the certificate module]]
* [http://tracker.moodle.org/browse/CONTRIB-334 Patch to enable linking] to [[Face-to-face module|Face-to-Face]] contributed module.

[[Category:Certificate]]
[[Category:Contributed code]]

[[es:Certificate]]