Moodle in English

Don't despair! I see the new Git recommendations as a cavalier act, just like the composer and the router. Correspondingly, to be gallop with them, you have to perform some stunts. If you fall, hard luck!

In the news:

by WiseCat, today 21 May 2026 (11 min 49 sec)

 

Ha, ha, ha!

If you would provide us the information described in Before you post.. Read this, people here can give you more pointed answers.

>> - Web server: Apache or Nginx?

 

You didn't specifically say, but from the syntax of the config file and the command '/sbin/httpd -S' I assume it is Apache.

>> - Domain: a FQDN (https://example.com/) or a path (https://example.com/foobar/)?

 

> The following URL did not return the expected status code: https://mg.sosoftexas.org/m52/lib/exampleshimroute2.php. 

 

So, on a path, https://sub.example.com/m52/

>> - PHP: PHP-FPM or PHP-FastCGI?

 

 > PHP 8.4.21
> All extensions for Moodle loading
> running php-fpm - as socket

>> - Linux distribution: Debian or derivatives (incl. Ubuntu Linux) or RedHat/Fedora (AlmaLinux)?

 

> Rocky 9

>> I assume, you want an "all green" result, incl. composer and router, and Moodle 5.2 as the subject line says?

 

> 

    ERROR | Router configuration (core_router)                          
          |     A standard page controller could not be loaded correctly.
          |     The router may not be configured properly.
          |     The following URL did not return the expected status code: https://mg.sosoftexas.org/m52/core/check/controller/test. Expected 200 ("OK") and received 404 ("Not Found")

So Moodle 5.2 says, No!

I got it going on Debian, Nginx and PHP-FPM. See  https://moodle.org/mod/forum/discuss.php?d=473950#p1899833. I don't know how much it helps you to find out the weak point. In my case it was the way the web server handles/translates pathinfo and handing it over to the executable (PHP).

I am not too keen to try out Apache, I have no test server around running Apache, all are Nginx. What about the others? Any volunteers (to try out 5.2 on Apache and PHP-FPM)?

I don't think the developers willingly sacrifice the 'pathinfo' part of the URL, which has been there since the beginning of the world wide web. See:

 

I think the problem is that the new "routing" concept, which is a glorified address rewriting scheme - my feeling, can not handle the (added) path, or at least make the 'pathinfo' handover to the PHP layer too complicated for the normal server administrator.