Book Image

Moodle 4 Administration - Fourth Edition

By : Alex Büchner
5 (1)
Book Image

Moodle 4 Administration - Fourth Edition

5 (1)
By: Alex Büchner

Overview of this book

This updated fourth edition of the classic Moodle Administration guide has been written from the ground up and covers all the new Moodle features in great breadth and depth. The topics have also been augmented with professional diagrams, illustrations, and checklists. The book starts by covering basic tasks such as how to set up and configure Moodle and perform day-to-day administration activities. You’ll then progress to more advanced topics that show you how to customize and extend Moodle, manage authentication and enrolments, and work with roles and capabilities. Next, you'll learn how to configure pedagogical and technical Moodle plugins and ensure your LMS complies with data protection regulations. Then, you will learn how to tighten Moodle’s security, improve its performance, and configure backup and restore procedures. Finally, you'll gain insights on how to compile custom reports, configure learning analytics, enable mobile learning, integrate Moodle via web services, and support different types of multi-tenancy. By the end of this book, you’ll be able to set up an efficient, fully fledged, and secure Moodle system.
Table of Contents (24 chapters)

Optimizing Moodle system performance

In this section, we have grouped settings that potentially impact performance without compromising any Moodle features. The topics covered are session handling, cron management and scheduled tasks, global search, and system paths.

Handling sessions

A session is initiated for each user that authenticates against Moodle, which also applies to guests. There are several well-explained settings relevant in a performance optimization context, which can be found by going to Site administration | Server | Session handling:

Figure 15.13 – Session handling

Moodle manages sessions and cookies very well. However, when problems occur, it is sometimes necessary to intervene manually. This should be done locally in the web browser if a specific user experiences issues (clear cache and cookies) or on the server if the problem affects multiple users. The latter is done by clearing the mdl_sessions table if sessions are stored...