Posts made by Visvanath Ratnaweera

Picture of Particularly helpful Moodlers Picture of Translators
Not to downplay its importance, but the developers can always argue that only 4.1 LTS, 4.3, 4.4 and 4.5 LTS are supported as of today.

With this we delve in to the old topic whether there should be a versioning recommendation for plug-ins. That gave non-ending discussions, which I don't want to repeat here. Here is one: Re: Versioning and Deprecation changes. In the light of the new incidents one may revisit those threads. As we all know, unsolved problems keep on coming back. Luckily that thread is still open.
Picture of Particularly helpful Moodlers Picture of Translators
You are talking of upgrades (major) like going from 4.1 LTS to 4.3. Doing that on a copy first is usual practice.

But the two incidents reported in this discussion happened going from 4.1.13 to 4.1.14, during an update (minor) and updating a plug-in which was tagged deprecated as a result - which are unusual.
 
That is why I was asking, "I don't know whether we should change the common opinion here that updates (minor) are harmless. Instead advise to test even updates (minor) and (resulting) plug-in updates first in a staging server." in my previous post.
Picture of Particularly helpful Moodlers Picture of Translators

Isn't swapping the language filter because one update broke somewhat drastic? I see, you are repeating the same questions that were recurring in the forums pre-2013. Exactly so solve the problem(s) you are reporting the "second" Multi-lingual Content filter was introduced in November 2013. See New filter is waiting for approval. There was a transition a couple of years later to the current Multi-Language Content (v2) which is still (well) maintained. All my encounters with them were simply exceptional, including yours: multilang2 upgrade failed and now I can't access the system. Look at the time line (first reported Wed 14:24 GMT, debugged and new release announced Friday 19:25 GMT. In the interim one could removed the filter (as I did) or replaced it with the previous one. You don't have to compare that to the rolling (and breaking) Windows 11, version 24H2 update, it is at lease in par with the Open Source standards. (We are spoiled.)

The irony of it is, "Functionality wise, there are no differences whatsoever between that and 2.0.3. 2.0.3 is just about Moodle 4.5 compatibility." Ref. https://moodle.org/mod/forum/discuss.php?d=462953#p1859006. The code was touched just to comply with this API change: https://moodledev.io/docs/4.5/devupdate#filter-plugins.

I am not going to hold you back, but before repeating pre-2013 questions please find them with an advanced forum search like this one.

Picture of Particularly helpful Moodlers Picture of Translators
allowing it to continue using MySQL 5.7. If you need to do this until your shared server gets the latest MySQL 8.0 updateHi

Thanks for the information. The "environment.xml hack" is known in these forums. But it remains a "hack", nobody wants to take responsibility in whether there is a piece of code somewhere which was not kicked during the upgrade but will show its teeth later. That is what Ken was reminding us here - there is a commercial one-click upgrade "panel" which violently ignores the environment.xml and then sends the patients here.

Therefore if you can take "It seems" part out from "It seems Moodle isn't taking advantage of any of the new features of MySQL 8.0, but is requiring it because MySQL 5.7 has reached its official end of life." and make a more committing statement, that will be valuable.
 
It is clear to me that all upgrades are temporary. So, "allowing it to continue using MySQL 5.7. If you need to do this until your shared server gets the latest MySQL 8.0 update" part is perfectly OK. wink
Picture of Particularly helpful Moodlers Picture of Translators
Hi all

In case the video is missing, please go to the Moodle Academy webinar. It is a significantly extended version of this talk.
 
In a sense, one can call this thread CLOSED. ;)
Average of ratings: Useful (1)