Difference between revisions of "Upgrading to Moodle 1.8"

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Upgrading to Moodle 1.8.

(Documenting steps to allow authenticated users to view site news.)
Line 19: Line 19:
  
 
It is recommended to reset all legacy roles to defaults because some of the default permissions were changed. You can do that via ''Administration > Users > Permissions > Define Roles'', click on each legacy role and review recommended permissions (dark background) or reset with Reset to defaults button.
 
It is recommended to reset all legacy roles to defaults because some of the default permissions were changed. You can do that via ''Administration > Users > Permissions > Define Roles'', click on each legacy role and review recommended permissions (dark background) or reset with Reset to defaults button.
 +
 +
In addition, in order to let your logged in users read the site news once logged in, you will need to follow these steps:
 +
#As an administrator, navigate to: Site Administration->Front Page->Front Page roles
 +
#Click on the "Override roles" link
 +
#Click on "Authenticated User"
 +
#Find the Forum heading, then "View Discussions" (mod/forum:viewdiscussion capability) and tick the second radio input (Allow)
 +
#At the bottom, press "Save changes"
  
 
==Multi Authentication==
 
==Multi Authentication==

Revision as of 08:28, 13 April 2007

Moodle1.8


  • Before upgrading, check that your site meets all system requirements for 1.8 in Administration > Server > Environment.
  • Always do a full database backup before upgrading!
  • Remember to purge PHP cache if using any PHP accelerator.

UTF-8 database encoding

For understanding upgrading to 1.8 and the UTF-8 encoding requirement, a small Moodle history lesson is required: Prior to 1.6, Moodle did not support UTF-8 across all languages and the encoding in which the data was stored in the database depended upon the language used in a particular course. From Moodle 1.6 onwards, all language packs are converted to UTF-8 and different languages may be used on the same page. Moodle 1.6 and 1.7 include a utility to migrate your database from any encoding to UTF-8.

From Moodle 1.8 onwards, the database migration utility is no longer included, as it is assumed that you upgrade from a UTF-8 encoded database.

Thus, if you wish to upgrade from 1.5 or an earlier version, you must first upgrade to 1.6 or 1.7, migrate your database to UTF-8, and then upgrade to 1.8. Similarly, if you are using Moodle 1.6 or 1.7 and have not yet migrated your database, you need to do so before upgrading to 1.8. Please refer to Upgrading to Moodle 1.6 for additional information.

Roles and capabilities

In addition to many Roles fixes and refinements (see the list of Roles improvements in the Tracker), in Moodle 1.8 the system context is separated from the site context.

The site context in Moodle 1.8 is the "front page course" and its activities. Roles may be assigned in the site context via Administration > Front Page > Front Page roles.

It is recommended to reset all legacy roles to defaults because some of the default permissions were changed. You can do that via Administration > Users > Permissions > Define Roles, click on each legacy role and review recommended permissions (dark background) or reset with Reset to defaults button.

In addition, in order to let your logged in users read the site news once logged in, you will need to follow these steps:

  1. As an administrator, navigate to: Site Administration->Front Page->Front Page roles
  2. Click on the "Override roles" link
  3. Click on "Authenticated User"
  4. Find the Forum heading, then "View Discussions" (mod/forum:viewdiscussion capability) and tick the second radio input (Allow)
  5. At the bottom, press "Save changes"

Multi Authentication

Originally all existing accounts were enabled, now only accounts with enabled authentication plugins can log in. If you selected Manual accounts users created with email sign-up will be disabled now. Solution is go to Administration > Users > Authentication and enable Email-based self registration, but leave Self registration disabled under "common settings" lower on the page.

Themes

Due to major changes needed for accessibility and XHTML strict compliance most 3rd party themes must be updated to work correctly. Before reporting any error, please switch to Standard theme and try to replicate the problem.

See also