Posts made by Joseph Rézeau

Picture of Core developers Picture of Plugin developers Picture of Testers Picture of Translators

Hi Dan,

1.- That's right, the link to my plugins included mod_questionnaire, of which Mike is the current maintainer.

2.- And, in the list of my other plugins these two are already marked as Seeking new maintainer

  • block_glossary_export_to_quiz
  • block_lesson_essay_feedback

3.- Is there any further action I need to take? When/If someone decides to adopt one or some of my plugins I will of course transfer their github repo ownership to the new maintainer.

4.- At the recent MoodleMoot in Paris last July a number of participants expressed their concern about the current state of mod_questionnaire, which they are using. I'm afraid Mike is not longer maintaining it actively, there is a huge backlog of issues and PRs. IMHO Mike should be approached to find out whether he is willing to offer this extremely useful plugin for adoption. But it's not for me to say. 

Some explanations for my decision...

* I have been using Moodle for 20 years, but only 5 years with "real" students, as I've been retired from my University position since 2010. At the fairly advanced age of 80 years old, I am finding it more difficult to keep up with all the changes in Moodle, in the world of computing, with the arrival of AI, etc. I should now be reasonable and stick to cultivating my garden.

* The final blow was what I consider the unfortunate decision to make Moodle 5.1 almost impossible to run on a shared hosting, which is my case. Also I have found out that running Behat tests on my plugins on my Windows local site is getting extremely slow, about 4 times slower than in previous Moodle versions.

It's been great to be part of the Moodle community all those years, to meet both virtually and IRL a number of enthusiastic Moodlers, and I will leave that community with great memories but no regrets.

As Douglas Adams would have put it, "So long Moodle and thanks for all the fish!"🐟

Joseph

Average of ratings: Useful (12)
Picture of Core developers Picture of Plugin developers Picture of Testers Picture of Translators

On my Moodle site I have a number of courses, pages or sections which have been removed over the years. But links to those elements still exist on other site(s). 

I started to track some of those missing links and adding a general error message in a custom en_local/error.php (and fr_local/error.php) file. $string['invalidcoursemodule'] and $string['invalidrecordunknown'] etc.

But this will probably miss a number of unforeseen errors. 

Is there an admin general setting to catch all those "dead links" and issue a unique error message to visitors? Or a plugin that does the trick?

Joseph

Average of ratings: Useful (2)
Picture of Core developers Picture of Plugin developers Picture of Testers Picture of Translators

@Andrew,

Thanks for trying to help. Before I forward your answer to my hosting provider I have some questions/remarks.

1.- On Gandi shared hosting, the equivalent of public_html is typically located inside your hosting instance under a htdocs directory (not public_html as used by some other providers like cPanel).

When I connect via SFTP this is what I see:

 image.png

In my own case, I suppose your suggested hack would work by replacing public_html with htdocs?

2.- Very important, if I follow your procedure, what happens to all my other sub-directories/sites in the htdocs directory? Mainly my 5 WordPress sites... Will they remain accessible from the existing htdocs directory?

image%20%281%29.png

Picture of Core developers Picture of Plugin developers Picture of Testers Picture of Translators

Hi Andrew,

I'm on a shared hosting with GANDI and am struggling to upgrade my Moodle 5.0 site to version 5.1 because of the new file structure. A number of workarounds have been mentioned in this thread already, but I'm afraid I don't understand how to practically implement them, nor does my provider.

I would be delighted if you could provide simple, step-by-step instructions on how to implement what you call "a very common approach", but what I would rather call an inconsiderate decision from Moodle HQ. That is to say a decision that did not take into consideration us poor Moodlers who are on a shared hosting.

Is it really too late to re-consider that hasty decision and revert to the previous file structure which worked smoothly? If that is not possible, then I feel it's the duty of Moodle to provide working solutions that take into account all Moodle users, even small, unimportant hobbyists such as myself (and probably a number of others who will emerge as more people try to upgrade to 5.1 in the coming weeks or months)?

Looking forward to your answer,

Joseph 'papi Jo', a Moodle user for 20 years, on the verge of giving up.😵‍💫

Average of ratings: Useful (3)