Visvanath Ratnaweera

Found the original discussion: 🚀 Exciting Improvements Coming to Moodle. I saw it earlier, but then set aside "for future" and forgot. I usually stay with the LTS, having upgraded to 4.5 LTS only this summer. Thought of making an exception this time, moving to 5.1 next summer, mainly because of the new question sharing behaviour since 5.0. 

 

No, I am not qualified to comment on whether the /public will enhance security, nor streamline deployment and modernize the codebase.

 

To my original question, I believe, I can get 5.1 going with the help of MDL-83424 on a new FQDN. My test sites are on my own domain. So, I can get unlimited sub-domains - and avoid the mydomain/subdir/ kind of URLs. The production domains are different. They belong to institutions and I won't get sub-domains. But I have plenty of time till then to understand the new Apache rules. (Or earlier, when we'll have exciting times in the Installing and upgrading help forum, starting 6 October. )

 

I'd be glad if there's better documentation than that zip file. The content look like they are for Windows or Mac, not Linux, ideally Debian. And what about Nginx?

We use the term "bug" to mean something more specific: The program behaves in a way you don't expect, others can reproduce it, you find others who agree and somebody has submitted a tracker issue on it,.. You don't see a button is far from that.

 

The theme is responsible for rendering. Moodle still have the function but the theme could have tried to put the GUI element somewhere else or differently and fail. Sometimes it is simply a conflict in CSS.

Please re-read my previous post, the bug discussion belongs to the _original_ thread. Also close it properly, as explained in the Code of conduct: "If your problem is solved, reply to the thread, adding [Solved] to the subject line of your post. Share links to documentation, discussions or tracker issues that helped you." This is what happens, when you ask anew when you are not making progress in the original discussion.

I saw https://moodle.org/mod/forum/discuss.php?d=469573. How do you conclude from that there is a bug (in the code)? If so, what about the "corrupted files"? Has both happened? Where is the evidence?

I see that you are getting help in the original thread. Please try to solve it there, or somehow come to a conclusion. It could be something as simple as an unmaintained theme. Main thing, wait till you know the cause of the problem before taking action. Just an ides, since you have this second Moodle, you can easily Course backup and Course upgrade in the new one and see whether the problem is gone. Please respond in the first thread.

Well, what do you mean by buggy? I notice that you are talking of Moodle 4.0.6. Indeed many bugs have been fixed since then and the version 4.0 itself is now outdated. If you are not talking of bugs introduced by you, changing the code on your own, then going to a new 4.0.6 won't solve your problems. You need to _Upgrade_, to at least Moodle 4.1 LTS. See https://moodledev.io/general/releases.

Here's your route planer: http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.

 

Edit: I see now, you are talking of "corrupted files" in the code tree. How did that happen? Well then drop the database and delete the whole moodledata/ of the new Moodle, and continue with the remaining part of  Moodle migration, i.e. take only moodledata/filedir/ directory and the database (as a database dump) with you.

 

P.S. There is an alternative way. Course-by-course Course backup in the original and Course restore in the target. But there are differences between the two.

 

P.P.S. I think this is more an Installing and upgrading help topic. Hint to the moderator.

Moodle_migration? Notice that in a true migration you don't _install_ a new Moodle. You take the code too with you. Otherwise it is usually an Upgrade.