Visvanath Ratnaweera

Relieved to know that you are trying on a test server first!

 

Anything red in the "Environment" is not good. Check the release notes linked from the chart.

About the target Moodle version: Under the system software you have, my favorite would be 3.11 LTS, since it was LTS.

Even without that, the transition to Moodle 4 was a "generation change" with lot of visible (look-and-feel) changes. Some ware more happy than the others. ;) My personal choice would be to spend some time in 3.11 LTS and aim for 4.3 as the next target. 3.11 > 4.3 long jump is supported. (See the chart) Some ups-and-downs of the initial 4 versions were ironed out by then.

 

P.S. I should have added about the themes that the following line will force Moodle to its default (and must have) theme Boost, possibly allowing you to uninstall the other themes from the admin GUI:

$CFG->theme='boost';

 

Themes are less involved plug-ins. You can just remove their directories from the Moodle code. The plugins page will mark them "Missing in disk" but they cause no damage. You can later delete the records from the database.

Now, before diving in, what are the versions of you system software? See Before you post.. read this... Also https://docs.moodle.org/405/en/Upgrading and make sure that Site administration > Server > Environment is green. Watch the drop-down there to check whether the platform is 3.10 ready.

Is there a specific reason why you go for 3.10, not 3.11 LTS, which was supported much longer?

This chart helps to keep an overview on various versions: http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.

It is a setting in the web server (Apache or Nginx or Litespeed or ..) not a setting in Moodle. If you are in a shared hosting, you have to ask your hosting provider. They don't change settings for a single customer but maybe show you a way of getting it with .htaccess files or putting your moodledata/ in a place they specify. If both fail you have to look for a different hosting provider.

 

Pl. read https://moodle.org/mod/forum/discuss.php?d=458243#p1840304. There is also the forum search for more: https://moodle.org/mod/forum/search.php?id=5.

Rereading, although only the RedHat faction was speaking, I don't think it is a RedHat-only problem. Even then hopping distro is a drastic measure.

It is (was) apparently an old PHP problem, 7.4.x. https://bugs.php.net/bug.php?id=74129 Can't believe it is not fixed in 8.x.

Quote: The problem is that the rawurldecode() is being skipped because this line is never reached. The reason is that this condition is false. That's happening because this PHP issue got fixed in PHP 8.1.18, 8.2.5 and 8.3+. Therefore $_SERVER['SCRIPT_NAME'] now no longer contains $_SERVER['PATH_INFO'] as a substring. But $_SERVER['PATH_INFO'] is still urlencoded and needs to be urldecoded in setuplib.php. Since the urldecode is currently not being done, the wrong pathnamehash gets computed in e.g. the function resource_pluginfile() and the file is not found and you get to here and then here.

It is a mean bug. Apparently only the "RedHat line" is hit - not the Debian line. Since both have the same upstream for Apache and PHP-fpm, it must be a compilation parameter. Just speculating, does anybody know?

 

Odd, is it only the space in file names that breaks, not other special characters, # , ! @ ... ä ö ü Ä Ö Ü ...?