Slash arguments
This is a technical page for server administrators and hosting providers.
Quest uses Moodle's slash arguments to determine which view to display to the user. If the web server is not properly configured, the following error may appear: Coding error: Controller for route not found.
Nginx​
Please ensure that Nginx was set-up according to the Moodle documentation on Nginx. The plugin has been confirmed to work in this configuration.
If you still do not have success with this, you might have the following rewrite rule in your site definition:
rewrite ^/(.*.php)(/)(.*)$ /$1?file=/$3 last;
The latter rule assumes that the path should be passed to the file argument, and thus creates a conflict with the way Quest handles the routes. If Nginx is configured according to the Moodle documentation, that rewrite should not be needed, and thus you may try to remove it and see if it works.
Alternatively, and note that this is discouraged, you can add the follow rewrite rule before the previous rewrite rule. Your Nginx site definition should therefore read this:
rewrite ^/(blocks/gearup/.*.php)(/)(.*)$ /$1?_r=/$3 last;
rewrite ^/(.*.php)(/)(.*)$ /$1?file=/$3 last;
If at this point you're not having any success, consider disabling the Moodle admin setting slasharguments.
IIS​
Please ensure that IIS was set-up according to the Moodle documentation on IIS.
You will need to add a second rewrite rule for Quest itself, please configure as follows:
- Requested URL: Matches the pattern
- Using: Regular expressions
- Pattern:
^(blocks\/gearup\/[^\?]+?\.php)(\/.+)$ - Action: Rewrite
- Rewrite URL:
{R:1}?_r={R:2} - Append query string: Checked
- Stop processing of subsequent rule: Checked
Make sure that this rule takes precedence over the other rule required by Moodle.
If at this point you're not having any success, consider disabling the Moodle admin setting slasharguments.