> Windows File Name.doc is not friendly to Linux.
Absurd! May be to Linux, but Moodle can handle _any_ unicode character in file names. Read "(Moodle 2.1.2) Problem with Unziping zip files that contain special characters" https://moodle.org/mod/forum/discuss.php?d=190958. (Well, I am quoting others. So testing never hurts, or hurts less than without. ;)
Visvanath Ratnaweera
Poster lagt til av Visvanath Ratnaweera
Hi
You are lucky since you has MySQL also on the Windows side. So the "Moodle migration" should proceed as prescribed: https://docs.moodle.org/29/en/Moodle_migration.
P.S. Unless you plan to burn the Windows server immediately, the back-up is not urgent. You can take your own time testing the new Moodle instance!
You are lucky since you has MySQL also on the Windows side. So the "Moodle migration" should proceed as prescribed: https://docs.moodle.org/29/en/Moodle_migration.
P.S. Unless you plan to burn the Windows server immediately, the back-up is not urgent. You can take your own time testing the new Moodle instance!
In that case your migration path is:
A. 1.9.x > 1.9.final https://docs.moodle.org/19/en/Upgrading
B. 1.9.final > 2.2.final https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2
this is the trickiest one. People have given up site upgrades have done the workaround through https://docs.moodle.org/19/en/Course_backup and then https://docs.moodle.org/22/en/Course_restore. Yet others have rebuilt the courses from scratch, in Moodle 2 style!
C. 2.2.final > 2.7.latest https://docs.moodle.org/27/en/Upgrading
D. 2.7.latest > 3.1.latest https://docs.moodle.org/31/en/Upgrading
In any case plan a lot of time. You are going to jump across 12 full version of a software! The final updates to 1.9 came out over four years ago. And if you were happily using 1.9 so long, I don't see an urgent reason (other than forced by the Moodle developers) to long jump to 3.1.
A. 1.9.x > 1.9.final https://docs.moodle.org/19/en/Upgrading
B. 1.9.final > 2.2.final https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2
this is the trickiest one. People have given up site upgrades have done the workaround through https://docs.moodle.org/19/en/Course_backup and then https://docs.moodle.org/22/en/Course_restore. Yet others have rebuilt the courses from scratch, in Moodle 2 style!
C. 2.2.final > 2.7.latest https://docs.moodle.org/27/en/Upgrading
D. 2.7.latest > 3.1.latest https://docs.moodle.org/31/en/Upgrading
In any case plan a lot of time. You are going to jump across 12 full version of a software! The final updates to 1.9 came out over four years ago. And if you were happily using 1.9 so long, I don't see an urgent reason (other than forced by the Moodle developers) to long jump to 3.1.
See https://docs.moodle.org/21/en/Upgrading.
Wait: Is there a specific reason why you need 2.1? The usual upgrade path is 1.9.x > 1.9.latest > 2.2.latest > so on.
And, don't skip the first step, back up every thing and test the backup!
Wait: Is there a specific reason why you need 2.1? The usual upgrade path is 1.9.x > 1.9.latest > 2.2.latest > so on.
And, don't skip the first step, back up every thing and test the backup!
Hi
You said:
> Now I'm no longer able to install new Moodle - instance (i.e Releases I downloaded from Moodle) e.g. for test purposes.
How did you proceed? Where you had to stop? Why?
> What is more , there are plugins in other Moodle-Instances that are not working properly.
So you installed this and "other Moodle instances" after all?
> I think is due to php7 which is shipped with Ubuntu 16.04.
Did you think or do you have proof?
Here is a start before touching Moodle: Create a file named phpinfo.php with the single liner:
You said:
> Now I'm no longer able to install new Moodle - instance (i.e Releases I downloaded from Moodle) e.g. for test purposes.
How did you proceed? Where you had to stop? Why?
> What is more , there are plugins in other Moodle-Instances that are not working properly.
So you installed this and "other Moodle instances" after all?
> I think is due to php7 which is shipped with Ubuntu 16.04.
Did you think or do you have proof?
Here is a start before touching Moodle: Create a file named phpinfo.php with the single liner:
<?php phpinfo(): ?> in the same directory as the Moodle's config.php and visit http://yoursite/phpinfo.php in a web browser. Post the result here. You'll find more details in the docs under https://docs.moodle.org/29/en/PHP#PHP_info.