Visvanath Ratnaweera

aapanel, https://www.aapanel.com/ ?

That is the problem with those packaged solutions: Great, if it worked. If not, you need intimate knowledge of the "panel". I don't. I doubt whether anybody here has - never seen that product. If you don't too, I hope you have Unix command (shell) access and "speak the language".

Hi Ken

You said:
> I did git (branches) and the entire install was done via command line (symlink/subdirectory) before any change to config for the subdomain was even considered. That went without a hitch .... no errors.

Congrats!

 

I can confirm that it would even work without symlinks. But that is a detail. The main thing is, 5.2 is not more troublesome than the 5.1.

 

What was the problem? Or better, the solution, which is what Rudraksh is asking?

> The GUI check environment is now all green with no 'check' notices - router or composer.

 

Even better!

 

> The command line checks.php -v is what is reporting the router config error.

 

That is not nice. GUI check is green, the CLI checks.php red!

> And, to top it off, the site appears to run fine with what I tested ... even setup Google Oath2 ... that functions ...

 

Yeah, the immediate interest is to get the site going as, say 5.0 did, not worrying about composer and router.

 

> Anyhoo ... discussing/cussing issues is normally frowned upon in these forums so the offer to poster for direct email.

 

Possible, in general. But the current vice-OP was not rebuffed in any way, AFAICS.

> And like I said before, I consider any .0 release

 

True. 5.2 is still 5.2(.0).

 

> as 'not ready for production' - declared stable or not! But that's my 'moodle madness'!

 

Just to say, according to HQ 5.2 is stable, thought the others should not misunderstand.

 

> Tis Sunday where I am ... taking day off! 

 

True, we should follow the rules in the outback, make no noise during weekends and public holidays.

Hi Ken

'course I checked the Vice-OP's Moodle CV - the info is a just a few clicks away!

HI all (Rudraksh, Ken and Rick)

So the problem common to you all is that you made it up to Moodle 5.1 but hitting an obstacle in Moodle 5.2? Are you convinced that you all three have the _same_ problem irrespective of differing platforms and the differing installation methods?

Or, do you speculate that the new router is blocking your (all three) path? I would say, No. I installed a 5.2 exactly as I did 5.1 - no composer and router, that is. Went without a hitch. FYI: Andrew confirmed earlier that configuring the router is not compulsory for Moodle 5.2.

 

Rick, I understand your urge to throw your not functioning Moodle 5.2 to the mixture hoping a (common) solution will come out. Unfortunately, it muddles the running discussion instead. I'm sorry.

The Canvas Hack Is discussed here: https://moodle.org/mod/forum/discuss.php?d=474179.

My thoughts were in another direction, not about the relative "hardness" of the two products: I don't have the background to compare them. Even if I had, this hardness (hackability) is something vague. No, I was thinking of the fact that Canvas is mostly SaaS whereas Moodle mostly DIY - except for the Moodle Cloud.

 

Apparently a nasty team of hackers have compromised the Canvas SaaS. To my great surprise some major universities are among the victims. So one hack, a large number of institutions compromised. If Moodle had such a hole, the hackers need to exploit one Moodle instance per institution. So the damage in Canvas is huge.