Moodle.org forum posts

Set list view as default on my courses

Tue, 15 Sep 2026 13:49:11 GMT

by hoang ka

Hi,

I'm using Moodle 5.2.2 with the Boost theme. On the My courses page, users can switch between Card, List and Summary views.

Is there a site setting to make List view the default for users who haven't selected a view yet? I found the Course overview settings where the available layouts can be enabled or disabled, but I couldn't find a setting for the default layout.

Thanks.

Bulk Deletion of Moodle Messages

Thu, 10 Sep 2026 12:40:26 GMT

by Ken Task

Don't think there is such a feature for users, but ... please see:

https://moodle.org/mod/forum/discuss.php?d=436157#p1755452

and how one user solved their similar issue.

'SoS', Ken

Let me say goodbye, and thanks!

Mon, 03 Aug 2026 10:29:04 GMT

by Eloy Lafuente (stronk7)

After 23+ years, saying goodbye is not easy.

What makes it even harder is that these have truly been the best years of my professional (and personal) life. It has been an absolute privilege (and a welcome responsibility) to share with you the birth and evolution of our beloved Moodle, and to witness with you, and because of you, how an idea grew into a global movement that has helped so many people learn and teach in better, more open, and more empowering ways.

When I look back, I do so with enormous pride, gratitude, and joy.

Together, you have built something extraordinary. Not just software, not just a platform, not just a project, but a community, a culture, and a shared purpose. Over all these years, Moodle has grown thanks to your talent, your generosity, your commitment, and your vision. Every contribution you made has mattered. Every conversation you had has mattered. Every challenge you helped face has made Moodle better.

And none of this happened in isolation. We have come this far by standing on the shoulders of giants: the early dreamers, the builders, the educators, the developers, the testers, the translators, the administrators, the advocates, and the countless people like you who gave your time, your energy, and your heart to make Moodle what it is today.

I feel deeply proud of all that you have achieved together, and deeply thankful that you let me be part of it.

[Video link: People Have the Power - Patti Smith]

As for what comes next, I do not want to make this too much about me. I simply hope to keep enjoying the things that have always inspired me: hacking as a hobbyist, exploring my own research ideas, and contributing to open source projects here and there. I also want to spend more time with music — keep playing guitar, and finally learn piano properly. And, of course, read more, travel more, and simply live life fully.

But before closing this chapter, I want to say the most important thing:

Thank you.

Thank you to all of you in Moodle-land. Thank you for your trust, your brilliance, your generosity, your passion, and your companionship through all these years. It has been a pleasure, an honour, and a constant source of learning to work with you, learn from you, and build with you. I will always carry that with me.

I leave with a full heart, with immense admiration for you, and with complete confidence that the best of Moodle’s story will continue to be written by you.

So let me say goodbye with a smile, with gratitude, and with hope.

[Video link: Eso que tú me das - Jarabe de Palo (Spanish)]

Stay Hungry, Stay Foolish.
Or, if you prefer: Stay Thirsty, Stay Crazy.

Thank you for everything. Final ciao from this shy hacker 🙂

P.S. For full transparency: Qwen 3.6 gave me a hand polishing the words for this farewell.

Re: Deleting a course takes so long time

Mon, 23 Sep 2024 09:20:42 GMT

by Immanuel Pasanec

One solution might be to use the cli script admin/cli/delete_course.php to delete the course via commandline.
sudo -u www-data /usr/bin/php admin/cli/delete_course.php --courseid=

Conditional access based on Quiz Question Categories/Grade Items instead of separate quizzes? (Moodle 5.0.7)

Tue, 15 Sep 2026 12:04:48 GMT

by Aurelie Soulier

Hi everyone,

I know it's been a few months but I just wanted to say a massive thank you to everyone who shared ideas, recommended plugins, or offered JavaScript workarounds on this thread and at the Moodle Leeds event earlier in the year.

Since I wasn't able to install new third-party plugins on the client's platform (or run scripts), I stuck strictly to native Moodle features. In the end, I split the diagnostics into targeted section tests. Based on the results, learners either pass (>=70%) and skip ahead access the specific module content (if they get <70%) and take the summative assessments

To build the diagnostic quizzes, I mapped them to questions pulled from eight different question banks. In each bank, questions are tagged by learning point. The quizzes are set up to fetch one or two random questions (depending on the learning point) from these specific tagged series within each bank, so learners are all tested on the same learning point but get different questions / question types.

It took some basic tinkering with passing grade conditional access (but nothing exceptional), but it runs smoothly. Our first learner actually completed the whole track two days ago, got their certificate and is moving on to the face-to-face course as expected. (and custom report is automated to send weekly to summarised who completed so we don't have to always check completion reports)

Thanks again for all the brainpower and support from this amazing community! it really helped me get this across the finish line!

Best wishes,
Aurélie

Re: Moodle 4.5 error with embed object

Wed, 06 Nov 2024 01:00:07 GMT

by Brett Dalton

have you checked the HTML view of the content? are there any tags being stripped out after it is saved? Is possible that when the text is being sanatised something is being removed that shouldn't be. For reference TinyMCE is fully open source, the only paid parts are some premium plug ins. Atto was wholy written by Moodle and was taking considerable resources to maintain, streamlining this will mean we can concentrate on a better user experience across the board on core LMS functionality

Tiles format is no longer maintained - what replacement?

Tue, 15 Sep 2026 08:42:44 GMT

by Philipp Memmel

Hi David,

I believe a lot of people that are using format_tiles are having this issue. For now there are multiple forks that are being maintained, we as well are maintaining a fork (https://github.com/bycs-lp/moodle-format_tiles) that includes some bug fixes, some small features and - most importantly right now - compatibility with moodle 5.2. There are also other forks like this that just includes fixes to make it run under moodle 5.2: https://github.com/leonstr/moodle-format_tiles.

As long as we don't receive any information from the maintainer, we still need to wait or use these workarounds by (hopefully temporarily) maintain forks.

Regards,

Philipp

Course structure and Sections as Subjects

Thu, 27 Aug 2026 14:42:29 GMT

by Emma Richardson

You need to implement separate groups, restrict the section by group and then remove the permission to View All Groups from the teacher role..I would actually suggest duplicating the built in teacher role, renaming it to Section Teacher or something similar and then removing the permission from that role rather than the stock teacher role.

mdl-demo for Microsoft WSL containers

Mon, 07 Sep 2026 18:49:58 GMT

by Petr Skoda

A few months ago Microsoft announced support for containers in WSL, it is still in early access.

You create your own personal Moodle demo site by installing container support and configuring NOTHING — no public directory hassle, no misconfigured router, no composer headaches.

That is what my mdl-demo OCI image does. Moodle 5.3dev is already in it, and any of the 6000+ plugins from the CAMP registry is a few clicks away.

Using Mac? No problem, macOS has its own container support too, via Apple container.

It looks like Microsoft and Apple both think containers belong in everyday operating systems, so why not spend the evening playing with some new interesting Moodle plugins instead of installing Apache yourself, or asking somebody else to do it for you?

mdl-demo for Microsoft WSL containers

Tue, 08 Sep 2026 11:57:08 GMT

by Petr Skoda

I have upated the docs:

added a Linux section (just don't run it straight on your workstation)
noted you may have to reopen the terminal after wsl --update

Thanks everybody for the feedback!

Activity and Resource Icons Turn Black

Wed, 16 Sep 2026 03:11:38 GMT

by Simey Lameze

Hi everyone, thanks for reporting this.

This issue is going to be investigated and fixed on this MDL ticket: https://moodle.atlassian.net/browse/MDL-89814

Thank you

Detecting failed requests for files inside a SCORM package — what shows up in nginx / PHP-FPM logs?

Thu, 03 Sep 2026 14:20:29 GMT

by Eduardo Kraus

1. Since the cache is marked as private, CloudFront will not keep this content in a shared cache. The interruption can happen either between Apache and CloudFront or between CloudFront and the learner. Because of that, I would start with the CloudFront logs and analyze each file separately, especially the number of bytes delivered in each request. Using the timestamps you already have, you can check whether a particular file tends to stop around the same point or whether the interruptions are random.

2. In Apache, %X helps identify when a connection was closed before the response was completed. For the byte count, I would rather use mod_logio and log %O. It is more appropriate for determining how much data was actually transmitted. This is also useful with X-Sendfile, since Apache is the component actually delivering the file.

3. With gzip, I would not compare against the physical size of the file on disk. I would compare each URL against other normal transfers of that same URL, also taking the encoding into account.

You can even take the logs and give them to ChatGPT or Claude and ask it to separate the requests by file, determine the normal size for each one, and highlight transfers that were smaller than expected.

If the log volume is large, I would do something even simpler. Ask ChatGPT or Claude to generate a small Python or PHP script that you can run locally. The script can read the logs and generate a CSV containing only the relevant information, such as date, time, IP, file, HTTP status, bytes sent, user-agent, and any other useful fields available in the logs.

It is much easier to analyze that CSV than to work directly with thousands or millions of log lines.

You can also cross-reference the IP addresses with the lastip field in the mdl_user table and try to identify which learners were involved. The IP cannot be treated as an absolute identifier because an entire company may be behind the same NAT, and a learner can also change IP addresses, but combining IP, timestamp, and the other access information can usually narrow the investigation considerably.

Since you still have 16 incidents within the log retention period, I would start with those and generate a separate CSV containing only a few minutes before and after each incident.

4. When I mentioned caching JS and CSS files, I was referring to static files. Those files are not personalized by Moodle. If someone who is not logged in can download that JS or CSS file, that alone does not create a security issue.

The requests that really depend on the session, enrolment, permissions, or any other validation performed by Moodle are the ones that need to remain protected. Those cannot simply receive a shared public cache without taking authorization into account.

So it is not a matter of putting all mod_scorm content into cache. You need to separate what is genuinely static from what still needs to be protected by Moodle.

5. The learner also does not necessarily download the same file from Moodle every time they navigate inside that SCORM package. On the first access, the browser downloads it and keeps it in the local cache. During that learner's navigation, the file will normally be reused locally while the cache remains valid.

The problem is different learners.

Learner A accesses the course and fetches the file from Moodle. Learner B later accesses the same SCORM and fetches the same file from Moodle again. Learner C does the same thing.

In this scenario, CloudFront is basically acting as another game of telephone between the learner and Moodle. You added another connection in the path, but you are not taking advantage of one of the main benefits of a CDN, which is serving the same file to multiple learners without having to go back to Moodle.

And that additional connection also becomes another place where the transfer can be interrupted.

6. Regarding MP4, I have worked with video and CloudFront for many years. I was actually a co-founder of Videofront. The name came from combining Video with CloudFront. I have also worked with other CDNs such as Bunny and Cloudflare, and personally I consider Cloudflare very poor for this kind of video workload.

CloudFront can store the complete MP4 and then respond to visitors using the required byte ranges. The more delicate point is the first access, while that file is not yet present in that CloudFront cache.

If you make the origin ignore the Range request, that first learner may end up receiving the entire file. Once CloudFront has the complete object cached, subsequent requests can be served by the CDN using the required ranges.

So there is that side effect for the first uncached request.

For that reason, I would not remove Range support indiscriminately. I would test that behavior first, especially because Safari and video players rely heavily on byte-range support for playback and seeking.

Certificate not generated until student accesses it – Moodle 4.5.13

Tue, 15 Sep 2026 13:06:31 GMT

by Mark Nelson

Hi Bastián and anyone wondering why the behaviour changed, please see further discussion in https://github.com/mdjnelson/moodle-mod_customcert/issues/904.

Problem with deleting directories on NFS in FreeBSD: new idea

Tue, 15 Sep 2026 11:11:01 GMT

by Marcin K.

Hi,

The topic I've started five years ago was locked, so I'm starting the new one. The original one can be found here: https://moodle.org/mod/forum/discuss.php?d=426781

I returned to this topic after five years because the issue of deleting directories on an NFS-mounted resource kept bothering me when removing them from within Midnight Commander. The cause of the problem is the same: during the deletion of a directory’s contents, the handle changes, which causes readdir to stop returning results, and the items inside the directory are no longer removed. As a result, the directory cannot be deleted because “it is not empty”.

How did I deal with this in MC? I simply pressed F8 again and again until the directory was successfully removed. So I figured that such a mechanism could be implemented in PHP as well, and I modified the remove_dir() function in moodlelib.php into the following form (the additional code in bold):

/**
* Delete directory or only its content
*
* @param string $dir directory path
* @param bool $contentonly
* @return bool success, true also if dir does not exist
*/
function remove_dir($dir, $contentonly=false, $attempt=1) {
if (!is_dir($dir)) {
// Nothing to do.
return true;
}

if (!$contentonly) {
// Start by renaming the directory; this will guarantee that other processes don't write to it
// while it is in the process of being deleted.
$tempdir = rename_to_unused_name($dir);
if ($tempdir) {
// If the rename was successful then delete the $tempdir instead.
$dir = $tempdir;
}
// If the rename fails, we will continue through and attempt to delete the directory
// without renaming it since that is likely to at least delete most of the files.
}

if (!$handle = opendir($dir)) {
return false;
}
$result = true;
while (false!==($item = readdir($handle))) {
if ($item != '.' && $item != '..') {
if (is_dir($dir.'/'.$item)) {
$result = remove_dir($dir.'/'.$item) && $result;
} else {
$result = unlink($dir.'/'.$item) && $result;
}
}
}
closedir($handle);
if ($contentonly) {
clearstatcache(); // Make sure file stat cache is properly invalidated.
return $result;
}
$result = rmdir($dir); // If anything left the result will be false, no need for && $result.
clearstatcache(); // Make sure file stat cache is properly invalidated.

if (!$result && is_dir($dir) && $attempt < 10) {
// The directory still exists despite the rmdir() attempt – most likely
// readdir() did not return a complete list (see: known issue with the
// NFS client on FreeBSD). Try again from scratch.
return remove_dir($dir, false, $attempt + 1);
}

return $result;
}

So if the $result of rmdir($dir) is false, another attempt to remove the directory is made. The $attempt parameter limits the number of recursive iterations so that the function doesn’t keep trying indefinitely. A value of 10 is probably too high, but if rmdir() succeeds, no further attempts will be made anyway. One could also check the reason why rmdir() failed, but that would only slow the function down.

To the best of my knowledge, the function in this form does not cause any issues, apart from increasing execution time in the specific situation it was modified for — that is, when deleting a directory fails. When everything goes according to plan, no additional attempts are made.

I’m not a specialist, so I’d appreciate any comments regarding the modified function. Is there a chance it could appear in this form, or in a similar form following the same idea, in the official Moodle code?

With Regards,
Marcin

PS. I've tested the modified function in Moodle, but I also wrote some scripts to test it outside the Moodle environment.

Script 1 [creates a directory structure that triggers errors when deleting it using the original function or in MC]:

#!/bin/sh
set -eu

BASE_DIR="/mnt/nfs/nas_delete/katalog_testowy"

# Generowanie 48 | 96 alfanumerycznych znaków bezpieczne pod FreeBSD
gen_name() {
LC_ALL=C tr -dc 'a-zA-Z0-9' < /dev/urandom | dd bs=96 count=1 2>/dev/null
}

populate_dir() {
target_dir="$1"
create_subdirs="$2"

mkdir -p "$target_dir"

# Tworzenie 24 plików po 4kB / 1MB / 32MB / 4MB / ...
i=1
while [ "$i" -le 24 ]; do
fname=$(gen_name)
if [ -n "$fname" ]; then
dd if=/dev/urandom of="$target_dir/$fname" bs=1m count=4 status=none
fi
i=$((i + 1))
done

# Tworzenie 8 podkatalogów (jeśli parametr wynosi 1)
if [ "$create_subdirs" -eq 1 ]; then
j=1
while [ "$j" -le 8 ]; do
dname=$(gen_name)
if [ -n "$dname" ]; then
subdir="$target_dir/$dname"
mkdir -p "$subdir"
echo "$subdir"
fi
j=$((j + 1))
done
fi
}

mkdir -p "$BASE_DIR"

# Poziom 1
level1_dirs=$(populate_dir "$BASE_DIR" 1)

# Poziom 2
level2_dirs=""
for d1 in $level1_dirs; do
sub_dirs=$(populate_dir "$d1" 1)
level2_dirs="$level2_dirs $sub_dirs"
done

# Poziom 3
for d2 in $level2_dirs; do
populate_dir "$d2" 0
done

echo "Struktura została pomyślnie utworzona w $BASE_DIR."

Script 2 [functions copied from moodlelib.php to test the deletion procedure outside the Moodle codebase]:

#!/usr/local/bin/php

<?php

$BASE_DIR="/mnt/nfs/nas_delete/katalog_testowy";

/**
* Renames a file or directory to a unique name within the same directory.
*
* This function is designed to avoid any potential race conditions, and select an unused name.
*
* @param string $filepath Original filepath
* @param string $prefix Prefix to use for the temporary name
* @return string|bool New file path or false if failed
* @since Moodle 3.10
*/
function rename_to_unused_name(string $filepath, string $prefix = '_temp_') {
$dir = dirname($filepath);
$basename = $dir . '/' . $prefix;
$limit = 0;
while ($limit < 100) {
// Select a new name based on a random number.
$newfilepath = $basename . md5(mt_rand());

// Attempt a rename to that new name.
if (@rename($filepath, $newfilepath)) {
return $newfilepath;
}

// The first time, do some sanity checks, maybe it is failing for a good reason and there
// is no point trying 100 times if so.
if ($limit === 0 && (!file_exists($filepath) || !is_writable($dir))) {
return false;
}
$limit++;
}
return false;
}

if (!$contentonly) {
// Start by renaming the directory; this will guarantee that other processes don't write to it
// while it is in the process of being deleted.
$tempdir = rename_to_unused_name($dir);
if ($tempdir) {
// If the rename was successful then delete the $tempdir instead.
$dir = $tempdir;
}
echo "tmp dir: $dir","\n";
// If the rename fails, we will continue through and attempt to delete the directory
// without renaming it since that is likely to at least delete most of the files.
}

if (!$result && is_dir($dir) && $attempt < 10) {
// The directory still exists despite the rmdir() attempt – most likely
// readdir() did not return a complete list (see: known issue with the
// NFS client on FreeBSD). Try again from scratch.
return remove_dir($dir, false, $attempt + 1);
}

return $result;
}

remove_dir($BASE_DIR);

?>

Output of script 2:

tmp dir: /mnt/nfs/nas_delete/_temp_b53102476e9d8c4492fae934cfa2cd9f
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_b53102476e9d8c4492fae934cfa2cd9f): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_cd58fd232cc2f011e28bbf217fd48c43
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_cd58fd232cc2f011e28bbf217fd48c43): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_683bc9582a298da27ced5210d11b70c2
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_266eb34c11423b4676907ee57277413c
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_66b559d4b39cf57e86697d4d17a1264a
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_eb42429d8c4313c5b36d52ba80cb7477
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_2a0ac1f68841a9d557dd59fbbc40a67b
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_7f194022f3eceae169c7c04a17df1d2a
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_4b5cef3764fd95cb5df68013ab40a934
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_bad3c94f6dfbc576138dd69f4855fabb/_temp_37a35888cc8b602e10d32f8134910e1b
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_cc03cbb818b797531c7f85f98cf4303e
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_cc03cbb818b797531c7f85f98cf4303e): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_d74430a0f913965ad0c11015743951c9
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_89b821797ee93390b4e253d8b030f80a
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_c9eb6b24eddfa29ec2fa6c33428ea4f3
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_031194de4dfe57a242c184bf6b9b1cad
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_01689fff44bacd051ab2281e41d06408
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_9f14d007b3e9f805bfee27f1414c8b05
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_48f2d58e09dbc41d444d457589d71bfe
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_b46a31acc1f8bcd5b3f7b37227dd27f2/_temp_88b9328f69ebadaafa48e3695abcea40
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_9552ceb0fe8690c2018d044b8a5aee56
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_9552ceb0fe8690c2018d044b8a5aee56): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_e97edb20ff96a5fce08d21686d813fa1
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_6817f74c5c3fd628c6320caee516b51a
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_b0648f5e58bc561ae20ae144efffa712
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_9e613bbbc70203469fecab8fe155615c
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_15f4e2b90153a68a2206f2a162f91c19
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_b8eddb39bef2e557403792b7595ad674
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_69dcde8c9069a71205a3ffdd159c2de9
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_450445c36bf881cc1cbd93e986841efa/_temp_df909c93ee09909f730e42722466dfeb
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_5d4a914c887e5792280518418ea70778
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_5d4a914c887e5792280518418ea70778): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_32f7700e1b50865788e5744f01e8ce22
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_74142fe642d7722fa293d0980ee131f8
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_de6c4911fea6f0997bdba72863f0ba4d
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_d7f68df844a6ae5b2ec209aa64aa68b8
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_4daecb876f8c8e3670376fb87e64a7d3
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_a541f92b27daabfdbd7ebdf62af6db08
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_00ec27566d49b21305015089457490f5
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_64d8919edd5b5a10e11d2e0f1a4d8bd1/_temp_2d1d6ebcaac974d51223e854f803fac3
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_e6870cedb8b8c10a249c4976bd1619d5
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_e6870cedb8b8c10a249c4976bd1619d5): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_79b598fa8256b1fec5a1181aca297421
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_d1e083318347181aec8c15790c8f97f6
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_54cdadc5c69aca631f2d93bd59047622
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_02c21c7545873ad47e792b8bf17c2e29
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_38e5c2a54701518212383d37caa67cdc
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_ab8c9c3f2d580e46cf9f3433a68a4ac9
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_0577482fb41003056615fea22a9c48be
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_6e3995d9fb92318a03922ea95789e9aa/_temp_5a66f8fae1fb29a57286413e3ebfbae3
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_37ace85886108b66bfa735dd44fdea00
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_37ace85886108b66bfa735dd44fdea00): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_81fb655982b5d8db091ac56f4e62e45d
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_af566c30092516fb75a55d534c072898
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_72a8dc4f741e3d00b64ca4b681a656d0
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_bae8d51fa1f829de6462638303ce868c
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_35af330a38fe88b29397b24e074a2d20
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_8aaebf50c53224576e9e40c0ffa85356
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_c99884c7d2087f58c3350b856ea678db
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_462d50fd24ebf429566485043cecb3cb/_temp_4c8d68eb7f7ee2351615ef91f64fd0e6
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_70f07bc7fac7b29d97d65d4c2f97741e
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_70f07bc7fac7b29d97d65d4c2f97741e): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_d4cf55c55be7265441ea9220e794314a
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_a5ef57215e744d3382d5ca0e733961db
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_2de94b9aa50c2e3390f98cd6726ad7b1
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_320c00741d6c8d25af84989f380d36f0
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_3fb97a0d9322b063a770b205c05dd654
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_8d3a7d4a0a0ae6a86fdc1d4afa01e3cf
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_4c5d7e39ab6ffa2322828c7f0eb4bbc0
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_3face4f9b8830c537e5644abfdb8361f/_temp_ea62f2c2c69b2bde012f5941955cb50b
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_739654658fec35f2c18641cb140cd7c7
PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_739654658fec35f2c18641cb140cd7c7): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_cfe134e86c41ee6b2ee10cc4594f3c10
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_a02cdeb9906da0d76b07e5c6df09f515
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_19d1b6ef67e97152db1f13ea4355ff40
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_63d8d6bf2ba39ec9464726e28651688f
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_cba43efe16ca473be722682e469bc2c2
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_8725a76b22fdd59baaff596b7935a58f
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_d1022fbd207631032e366f9568e8488e
tmp dir: /mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_48500998037fa01958a9b72abf6f8605/_temp_a1e5a0835826e97b409b9750af1988fb

As you can see, PHP reports the problem several times:

PHP Warning: rmdir(/mnt/nfs/nas_delete/_temp_384cfbf87014b5dbeb5f09bff88e2f2b/_temp_739654658fec35f2c18641cb140cd7c7): Directory not empty in /home/marcinkk/skrypt_testowy_nfs_delete.sh on line 84

but in the end the directory, along with its contents, is successfully removed from disk.

Critical The default user role "Authenticated user" is incorrectly defined!

Mon, 14 Sep 2026 20:43:06 GMT

by Daniel Thies

To clarify why this is reported this way. It is not necessarily wrong to not have green checks on the security report. The report is showing potential risks that are associated with the standard user role. Whether those risks are real depends what privileges your users need and your data policy. The capability dataprivacy:requestdelete gives the user the ability to request the deletion of their data which is ok if that is the site policy (is required potentially by GDPR a for commercial site). However, if there is a reason not to allow a user to delete records (most school systems), then it risks deleting data that violates the policy. You should review capabilities to see if they are appropriate, but do not have to change them to make the report happy.

Generico Two (G2) - the next generation widget system for Moodle

Thu, 10 Sep 2026 10:30:06 GMT

by Séverin TERRIER

Hi Justin,

Thank you for this new plugin, that seems very nice

A question (to speed translations) : do you know if some strings are the same (identifier and content) between Generico and Generico Two, and could be directly reused (and imported in AMOS) ?

Séverin

Tenth Moodle Community Meeting on Collaborative Development in the France and Japan Moodle Communities

Mon, 14 Sep 2026 07:30:19 GMT

by Harald Schnurbusch

Dear Community,

On 29 September, 2026, the 10th Moodle Community Meeting will take place on moodle.org. Don Hinkelman and Nicolas Martignoni will talk about Collaborative Development in the France and Japan Moodle Communities. Here is all the information:

Date: Tuesday, 29 September 2026
Time: 1-2p.m. UTC
Meeting room: BigBlueButton on moodle.org
Guests: Don Hinkelman (Moodle Association of Japan), Nicolas Martignoni (MoodleBox)
Note: The meeting wil be recorded and is available through the BBB activity linked above.

Topic: Collaborative Development in the France and Japan Moodle Communities

One of the largest MoodleMoots this year, was held this July in Tours, France, and featured two projects that educators in the Japanese and French communities will collaborate on. Developers of the Video Assessment Module from Sapporo Gakuin University in Japan were invited to Tours to present their innovations in performance-based rubric assessment. From this, funding by both the Japanese and French educational ministries will push video assessment into the AI era. In addition, the President of MoodleMoot France and key developer of MoodleBox, Nicholas Martignoni, will highlight a key needed feature: MoodleBox-to-MoodleBox course synchronization that both the Moodle Association of Japan and the Moodle Association Francophone will build together.

See you on the 29th!

Best
Harald
(Moodle Community Meetings orga team)

I can't download the adaptable theme from the marketplace (403 message)

Mon, 17 Aug 2026 12:14:02 GMT

by Gareth Barnard

Dear Mimi,

I've not listed the Adaptable theme on Moodle Marketplace (please see https://moodle.atlassian.net/wiki/external/ZTZjOTcwNmFmZmE3NDJjNmE3NzM4NWY1ZjU0YmJiNGY), however it is still available from GitHub, https://github.com/gjbarnard/moodle-theme_adaptable and listed on https://camp-registry.org/plugin/theme_adaptable.html.

Kind regards,

Gareth

Unenrol inactive after" - Moodle Brasil

Mon, 14 Sep 2026 12:43:04 GMT

by Eduardo Kraus

https://moodle.org/user/index.php?id=5 I checked pages 7, 8, and 9, and all users have a last login from a looong time ago... So the last site access is also the last course access.

Moodle 4.5.14 Shadow Release

Mon, 14 Sep 2026 12:08:42 GMT

by Ken Task

There was an announcement in Developers forum about an unscheduled minor release
coming 14 September.

"General developer forum -> HEADS UP: Unscheduled minor release coming 14 September
I am writing to inform you that an unscheduled release will be taking place on Monday, 14 September, which will include Moodle LMS versions 5.2.3, 5.1.7, 5.0.10 and 4.5.13."

Just did a git pull on a 4.5 code directory.

Did acquire quite a few things:
Fast-forward
.upgradenotes/MDL-88833-2026052708560431.yml | 9 -
MDL-89384-2026080511520494.yml | 8 +
MDL-89384-2026080511591999.yml | 8 +
UPGRADING.md | 38 +++-
admin/environment.xml | 205 +++++++++++++++++++++
.../tests/behat/apply_presets.feature | 6 +-
.../tests/behat/revert_changes.feature | 2 +-
.../dataprivacy/templates/request_details.mustache | 4 +-
.../tests/behat/manage_data_requests.feature | 15 ++
admin/tool/usertours/templates/tourstep.mustache | 2 +-
.../editor/classes/external/generate_image.php | 7 +-
.../condition/profile/classes/condition.php | 4 +
.../condition/profile/tests/condition_test.php | 5 +
...block_recentlyaccessedcourses_dashboard.feature | 40 +++-
comment/comment.js | 51 ++---
comment/lib.php | 8 +-
comment/tests/behat/accessibility.feature | 41 +++++
course/classes/management_renderer.php | 5 +-
course/format/UPGRADING.md | 16 ++
.../amd/build/local/courseeditor/mutations.min.js | Bin 15416 -> 16472 bytes
.../build/local/courseeditor/mutations.min.js.map | Bin 45951 -> 49657 bytes
.../amd/build/local/courseindex/section.min.js | Bin 4764 -> 5715 bytes
.../amd/build/local/courseindex/section.min.js.map | Bin 11544 -> 14170 bytes
.../format/amd/src/local/courseeditor/mutations.js | 52 ++++++
course/format/amd/src/local/courseindex/section.js | 41 +++++
.../format/templates/local/courseindex/cm.mustache | 8 +-
.../templates/local/courseindex/section.mustache | 10 +-
course/renderer.php | 10 +-
.../templates/local/activitychooser/error.mustache | 4 +-
.../templates/local/activitychooser/help.mustache | 4 +-
course/tests/behat/activity_chooser.feature | 14 ++
customfield/amd/build/form.min.js | Bin 8220 -> 8340 bytes
customfield/amd/build/form.min.js.map | Bin 17419 -> 17611 bytes
customfield/amd/src/form.js | 2 +
customfield/externallib.php | 2 +
customfield/templates/list.mustache | 2 +-
customfield/tests/behat/edit_categories.feature | 19 ++
enrol/manual/manage.php | 2 +
grade/classes/external/get_gradable_users.php | 2 +-
.../tests/behat/incomplete_marking_guide.feature | 57 ++++++
grade/import/xml/import.php | 47 +----
grade/import/xml/index.php | 12 +-
grade/import/xml/lib.php | 41 +++++
grade/import/xml/tests/lib_test.php | 72 ++++++++
grade/tests/external/get_gradable_users_test.php | 49 +++++
install/lang/es_mx/install.php | 2 +-
install/lang/gd/install.php | 2 +-
install/lang/he/install.php | 4 +
install/lang/sq/admin.php | 44 +++++
install/lang/sq/error.php | 52 ++++++
install/lang/sq/install.php | 78 ++++++++
install/lang/sq/moodle.php | 6 +-
lang/en/course.php | 1 +
lang/en/courseformat.php | 8 +
lang/en/customfield.php | 1 +
lang/en/reportbuilder.php | 1 +
lib/UPGRADING.md | 20 +-
lib/amd/build/sortable_list.min.js | Bin 14357 -> 14396 bytes
lib/amd/build/sortable_list.min.js.map | Bin 42729 -> 43320 bytes
lib/amd/src/sortable_list.js | 6 +
lib/authlib.php | 8 +-
lib/behat/classes/partial_named_selector.php | 4 +-
lib/classes/output/core_renderer.php | 4 +-
lib/classes/task/scheduled_task.php | 2 +-
lib/editor/tiny/amd/build/editor.min.js | Bin 10423 -> 11437 bytes
lib/editor/tiny/amd/build/editor.min.js.map | Bin 32576 -> 36214 bytes
lib/editor/tiny/amd/src/editor.js | 98 +++++++---
.../tests/behat/modal_help_dialogue_focus.feature | 77 ++++++++
lib/form/tests/behat/collapsible_sections.feature | 66 +++++++
lib/form/tests/behat/dates.feature | 20 ++
.../moodle-form-dateselector-debug.js | Bin 15467 -> 19605 bytes
.../moodle-form-dateselector-min.js | Bin 7502 -> 8238 bytes
.../moodle-form-dateselector.js | Bin 15467 -> 19605 bytes
.../moodle-form-shortforms-debug.js | Bin 4053 -> 5978 bytes
.../moodle-form-shortforms-min.js | Bin 1174 -> 1329 bytes
.../moodle-form-shortforms.js | Bin 3787 -> 5715 bytes
lib/form/yui/src/dateselector/js/calendar.js | 12 +-
lib/form/yui/src/dateselector/js/dateselector.js | 83 +++++++++
lib/form/yui/src/shortforms/js/shortforms.js | 117 +++++++-----
lib/form/yui/src/shortforms/meta/shortforms.json | 3 +-
lib/moodlelib.php | 30 ++-
lib/table/classes/flexible_table.php | 30 ++-
lib/templates/activity_header.mustache | 2 +-
lib/templates/block.mustache | 2 +-
lib/templates/modal.mustache | 2 +-
lib/tests/authlib_test.php | 48 +++++
lib/tests/behat/behat_general.php | 16 ++
.../fakeplugins/auth/passwordpolicyprobe/lib.php | 44 +++++
.../auth/passwordpolicyprobe/version.php | 29 +++
lib/tests/moodlelib_test.php | 14 +-
lib/tests/task/scheduled_task_test.php | 42 ++++-
lib/tests/task/send_login_notifications_test.php | 19 +-
login/lib.php | 2 +-
mod/assign/tests/behat/submission_comments.feature | 2 +-
mod/book/tests/behat/toc_skiplink_keyboard.feature | 35 ++++
mod/forum/classes/local/exporters/post.php | 4 +
.../forum_discussion_nested_v2_first_post.mustache | 2 +-
mod/forum/templates/forum_discussion_post.mustache | 4 +-
.../templates/local/grades/view_grade.mustache | 10 +-
mod/forum/tests/behat/grade_forum.feature | 16 ++
mod/forum/tests/exporters_post_test.php | 3 +
mod/forum/tests/externallib_test.php | 26 ++-
mod/lesson/tests/behat/lesson_course_reset.feature | 12 +-
.../tests/behat/lesson_group_override.feature | 24 +--
mod/lesson/tests/behat/lesson_practice.feature | 23 ++-
mod/lesson/tests/behat/lesson_retake.feature | 21 +--
.../tests/generator/behat_mod_lesson_generator.php | 42 +++++
mod/lesson/tests/generator/lib.php | 112 +++++++++++
mod/lesson/tests/generator_test.php | 52 ++++++
.../statistics/tests/quiz_attempt_deleted_test.php | 1 +
.../tests/quiz_attempt_submitted_test.php | 1 +
.../tests/behat/subsection_courseindex.feature | 88 +++++++++
.../tests/behat/subsection_coursepage.feature | 13 +-
.../bank/history/classes/question_history_view.php | 8 +-
question/type/multichoice/renderer.php | 9 +-
.../type/multichoice/tests/walkthrough_test.php | 27 +++
reportbuilder/classes/form/audience.php | 8 +-
reportbuilder/classes/local/audiences/base.php | 2 +-
.../classes/local/helpers/user_profile_fields.php | 8 +-
reportbuilder/classes/local/report/column.php | 35 +++-
.../local/systemreports/report_schedules.php | 3 +-
.../classes/table/custom_report_table.php | 8 +-
.../classes/table/system_report_table.php | 8 +-
reportbuilder/lib.php | 8 +-
reportbuilder/tests/behat/columneditor.feature | 13 ++
reportbuilder/tests/behat/schedules.feature | 2 +
.../googledocs/templates/upload_dialogue.mustache | 4 +-
theme/boost/scss/moodle/blocks.scss | 4 +
theme/boost/scss/moodle/courseindex.scss | 15 ++
theme/boost/scss/moodle/modules.scss | 10 +
theme/boost/style/moodle.css | 23 +++
theme/classic/style/moodle.css | 23 +++
theme/classic/tests/behat/blacklist.json | 3 +-
user/tests/behat/edit_user_enrolment.feature | 87 +++++++++
version.php | 4 +-
135 files changed, 2398 insertions(+), 328 deletions(-)
delete mode 100644 .upgradenotes/MDL-88833-2026052708560431.yml
create mode 100644 MDL-89384-2026080511520494.yml
create mode 100644 MDL-89384-2026080511591999.yml
create mode 100644 comment/tests/behat/accessibility.feature
create mode 100644 grade/grading/form/guide/tests/behat/incomplete_marking_guide.feature
create mode 100644 grade/import/xml/tests/lib_test.php
create mode 100644 install/lang/sq/admin.php
create mode 100644 install/lang/sq/error.php
create mode 100644 install/lang/sq/install.php
create mode 100644 lib/editor/tiny/tests/behat/modal_help_dialogue_focus.feature
create mode 100644 lib/form/tests/behat/collapsible_sections.feature
create mode 100644 lib/tests/fixtures/fakeplugins/auth/passwordpolicyprobe/lib.php
create mode 100644 lib/tests/fixtures/fakeplugins/auth/passwordpolicyprobe/version.php
create mode 100644 mod/book/tests/behat/toc_skiplink_keyboard.feature
create mode 100644 mod/subsection/tests/behat/subsection_courseindex.feature

fgrep '$release' version.php
$release = '4.5.14 (Build: 20260914)'; // Human-friendly version name

'SoS', Ken

Unenrol inactive after" - Moodle Brasil

Mon, 14 Sep 2026 07:55:32 GMT

by Séverin TERRIER

I suppose that some people could be enrolled to some courses, subscribed to some forums, receive email of messages without connecting, and it was ok for them.

Of course, one can argue that having send two mails explaining they needed to connect before having they account suspended (and deleted ?) is enough. And it's perhaps true for most people.

HEADS UP: Unscheduled minor release coming 14 September

Fri, 11 Sep 2026 07:51:49 GMT

by Matt Porritt

Hi everyone,

I am writing to inform you that an unscheduled release will be taking place on Monday, 14 September, which will include Moodle LMS versions 5.2.3, 5.1.7, 5.0.10 and 4.5.13.

The most recent 5.2.2 and 5.1.6 releases contained an issue where a grade penalty calculation fix was carried out, but did not freeze affected grades to prevent them changing to the corrected values if a re-calculation was triggered (please see this post for more details). Since then, we have prioritised fixing this issue, so that affected assignment grades can be successfully frozen and the grades can be repaired. We have now completed the fix, as well as thorough testing to ensure the solution is sound and does not introduce any further side effects.

Given the importance of grades, we are undertaking this unscheduled release to ensure the fix is available as soon as possible. This is to minimise the impact on sites either waiting for the fix before upgrading, or for those directly affected (having already upgraded).

Due to the nature of our release process, all bug and security fixes that have been completed since the last minor release must also be included in the release. This is why all security supported versions are included in this release and not just the two versions affected by the original issue, as two security issues have been fixed during this period and will also be included.

Thank you to all of our community members that contributed to these releases.

Matt Porritt
Product Director, Platform Solutions

Version	Release status	Initial release	General support ends	Security support ends
4.5 (LTS)	Current security	7 Oct 2024	6 Oct 2025	4 Oct 2027
5.0	Current security	14 Apr 2025	20 Apr 2026	5 Oct 2026
5.1	Current stable	6 Oct 2025	5 Oct 2026	19 Apr 2027
5.2	Current stable	20 Apr 2026	19 Apr 2027	4 Oct 2027
5.3 (LTS)	Future stable	5 Oct 2026	4 Oct 2027	1 Oct 2029

Download Whole Forum

Fri, 05 Sep 2025 03:28:15 GMT

by Al Charl

Students have created their own post in a forum with text and files. I’m trying to download everything from the forum, both the text of posts and the files students uploaded. I'm not sure if is possible. I’ve seen the “Export” option, which gives me all the text, but I can’t find a “Download all submissions” or “Download all attachments” option.

Is there a way to get all files at once, or do I need to do it manually for each post and file? Any tips, plugins, or workarounds would be appreciated.

Seven Major Challenges with Moodle Assignments

Tue, 09 Dec 2025 19:07:42 GMT

by Richard van Iwaarden

After administrating Moodle for two decades, I present this overview as a Christmas gift to Moodle.org. This compilation distills twenty years of experience viewed through a strictly educational lens. It is my firm belief that if Moodle succeeds in resolving these issues, it will elevate the platform from its current standing into a truly superior product.

The following points outline the most significant friction points encountered when utilizing the Moodle assignment interface within a university setting.

1. The Invisibility of Grades in Previous Attempts (MDL-87214, MDL-87211)

Tracking a student's academic trajectory is notoriously difficult when utilizing rubrics across multiple attempts. The interface obscures the grade of a specific prior attempt, rendering it invisible to the instructor. Furthermore, the user interface terminology is misleading; it claims an instructor is "editing" a previous attempt when they are merely viewing it, and displays "Not Graded" even when a grade has, in fact, been assigned.

2. Inability to Configure Deadlines per Attempt

Moodle lacks the functionality to pre-configure distinct deadlines for separate attempts within a single assignment structure.

The Dilemma: If an instructor wishes to set a deadline of April 1st for the first attempt and April 7th for the second, the system offers no native solution.
The Workarounds: Instructors must either clutter their gradebook by creating two separate assignments or manually edit the assignment settings between dates.
The Consequence: Editing the deadline retroactively extends the time for the first attempt, forcing teachers to manually close that attempt for all students, resulting in significant administrative overhead.

3. Irreversibility of Accidental Attempt Creation

There is currently no mechanism to delete an attempt once it has been opened, regardless of whether it was created in error. Even system administrators are unable to undo this action. This is particularly problematic in academic environments where students are strictly limited to a specific number of attempts per year; an accidental click by a teacher effectively consumes a student's valid opportunity without their request.

4. Disregard for Marking Workflow Protocols (MDL-87064)

The system fails to respect the status of the marking workflow when a new attempt is initiated.

The Scenario: In collaborative grading environments, an instructor may determine a student has failed and decide to grant a new attempt immediately, even if they are not yet ready to finalize the grade release.
The Failure: Granting the new attempt inadvertently releases the partial grade to the student immediately, overriding the marking workflow setting that indicates the grade should not yet be released.

5. Absence of Rich Text Formatting in Rubrics (MDL-77404)

While comprehensive feedback is paramount for student learning, the rubric grading method lacks basic text formatting capabilities. The interface prevents the insertion of line breaks or paragraphs within criteria fields or feedback text. Consequently, extensive feedback is compressed into a single, dense sentence. This lack of visual structure makes the feedback difficult to digest and diminishes its ability to motivate student improvement.

6. Lack of Knock-Out Criteria Functionality (MDL-87065)

The rubric system does not support "knock-out criteria"—mandatory requirements that a student must pass to succeed in the assignment.

The Issue: It is impossible to configure the system so that failure in specific criteria results in an overall failure; instead, high scores in other areas automatically compensate for these deficits.
The Workaround: While instructors can attempt to manipulate scores using negative points, this is merely a makeshift patch for a fundamental structural flaw.

7. Loss of Student Access to Submissions Post-Course (MDL-86530, MDL-86642)

In a typical four-year academic trajectory, students engage with numerous courses sequentially. While a course is in session, students maintain an active enrolment. However, once a course concludes, maintaining this active status is undesirable; it results in obsolete deadlines cluttering the calendar and subjects the student to irrelevant notifications regarding group enrolments or questionnaires.

To maintain hygiene in the system, students are typically transitioned out of the active state—either by being unenrolled entirely or by having their enrolment status changed to suspended or not current.

The Issue: Regardless of the method chosen to deactivate the student, the result is the same: the student loses the ability to access their own submitted work.

Role-Structure Failure: We have attempted to solve this by configuring guest access and explicitly enabling the capability within the role-structure for users to view their own submissions. Despite the setting existing within the Moodle architecture, the functionality is non-operational.
Status Limitations: Similarly, students who remain in the course with a suspended or not current status are inexplicably blocked from viewing their past assignment submissions.

Thanks for everything and merry Christmas to you all!

Richard.

Seven Major Challenges with Moodle Assignments

Mon, 15 Dec 2025 18:54:26 GMT

by Richard van Iwaarden

That is quite a list of questions, Rick

To provide some context, I spent 12.5 years as a Moodle administrator in secondary education (ages 12–18). I won't digress into the complexities of the Dutch educational system, but suffice it to say, it is intricate.

I have now been working in a university setting for nearly a decade. In my experience, the higher the level of education, the stricter the regulations become. While I may not always agree with them from a pedagogical standpoint, these rules are mandatory and must be adhered to.

As I mentioned in my initial post, we are dealing with specific constraints regarding due dates and attempts—for example, a deadline of April 1st for the first attempt and April 7th for the resit. By national law, students must know exactly when assignments are due and are entitled to two separate attempts. Furthermore, lecturers have a ten-day grading window, with the strict stipulation that students must receive their grades at least five days before their second attempt. Students also have a legal right to review their graded work to learn from previous errors. In some universities, students are even required to pay a fee for a second attempt.

This combination of national legislation and institutional rights necessitates a strictly tailored process. This is why I maintain that using multiple assignment instances for different attempts is untenable; it isn't just about cluttering the gradebook.

Consider a scenario where a student gains access to a video only after passing a specific assignment. With a single assignment instance, you simply set the restricted access to 'available if a passing grade is received for Assignment X.' However, if you copy this assignment four times to cover four attempts over two years, you have to reconfigure the conditional access into a labyrinth of logic. It would look something like: 'Access if Assignment 1 passed OR Assignment 2 passed (Year 1) OR Assignment 3 passed...' and so on.

The same issue applies to course progress. With four unique assignments, progress is easily tracked in 25% increments. If you set up 16 instances (4 assignments × 4 attempts), accurate tracking becomes a massive administrative burden. If one assignment changes, you must edit four instances and repair complex AND/OR statements for resource access.

Moodle’s built-in 'multiple attempts' feature exists for a reason. I often feel Moodle focuses too heavily on smaller schools or lower education levels where regulations are looser, and duplicating assignments is a viable workaround. In my environment, however, the regulations are far too strict for that approach.

Documentation of new features - Please create french screenshots each 6 months

Tue, 08 Sep 2026 14:29:44 GMT

by Séverin TERRIER

Hi,

On each new Moodle version, a new documentation is created, with pages documenting new features, with screenshosts.
To help french speaking / reading people understand the new features, translation of theses pages are made in french.

Since years, Mary Cooch (and Helen Foster) made french screenshots juste after making screenshots in english (just switching language), and put them in the french version of the documentation. It helps a lots, and ensure same information is captured, with same dimensions… I could then create the rest of the documentation pages.

Now that they don’t work on this anymore, could this be included in the work done when creating new documentation, each 6 months, by the person doing these screenshots ?

It would be really helpful for french community.

I've created MDLSITE-8500 for that.

Thanks a lot,
Séverin

PS : for french people, the same message is here

Critical The default user role "Authenticated user" is incorrectly defined!

Fri, 11 Sep 2026 13:46:44 GMT

by Richard van Iwaarden

Hi Daniel,

Can you post a screenshot? I can't find anything that looks like what you are describing.

Or if you mean this:

That link just sends you to a general page describing risks: https://docs.moodle.org/502/en/Risks

Re: How to delete messages?

Thu, 22 Jun 2023 07:04:17 GMT

by Helen Foster

Thanks Esdras for sharing your plugin tool for deleting messaging conversations.

For anyone having problems with lots of old messages, you may wish to vote for adding a feature to delete messages older than a specified date, MDL-18749, or a feature enabling users to delete all messages in one action, MDL-66998.

Re: How to delete messages?

Wed, 28 Jun 2023 00:10:35 GMT

by Esdras Caleb Oliveira Silva

In the next time you can use this
https://moodle.org/plugins/tool_deletemessage

Re: How to delete messages?

Sun, 10 Jul 2022 15:03:57 GMT

by Ian L

For anyone else who has the message problem. I finally got the message drawer to open up by deleting bulk user messages in phpmyadmin. I went from 3454 in the private messages to 1784. And it now works. I can see the messages I've sent from my profile and I can message users by clicking on their profile.

I did something like:

SELECT * FROM `mdl_messages` WHERE useridfrom = 2 ORDER BY `mdl_messages`.`fullmessagehtml` DESC

And then scrolled down and deleted 100-250 at a time. I was thinking of deleting older personal messages too but it's working now.