Howard Miller

Your config.php file now needs to go in the 'public' folder inside the Moodle installation, not in the root of the Moodle install.

You need (and this might be the tricky bit) to point your web server's root to Moodle's public folder. I don't know if that's possible on cPanel. There is another thread (can't be far away) about running Moodle on shared hosting.

When you say "nothing happens", I don't buy it. *Something* happens, even if it's a blank screen.

Convert submission is a bit like that. I assume that those conversions have failed. It might be something you want to investigate but conversions do fail. I clearly don't know how you have the conversions configured.

The downside is that these are taking up three "runners" for adhoc tasks that could be doing something else. Whether this presents a problem depends on what you have set the number of concurrent adhoc tasks to (See site admin > Server > Task processing). As the default is only 3, this could represent an issue. My concern would be that *all* your convert_submission tasks are failing. You'll need to look at the task logs for that.

Moodle will grab back the lock on a task after 24 hours if it's not complete. But if you're only running 3 adhoc tasks in each 24 hour period then you do need to investigate further.

Yeh - I found that (by accident) some days later. It's documented here...

https://docs.moodle.org/dev/Page_API

...fine when you know it's there

Im terrified of submodules. It's never ended well

Again... IF you've used Git in that way. It comes down to there being no particularly elegant way to handle optional plugins.

I'm sure I read that one of the objectives (for a future release) is to have a single plugins folder (like Wordpress). That would make all this so much simpler.