Installing and upgrading help

Read this... Using_slash_arguments

On a 19 site that works ... yikes, still in use! :\
Links to an image example in a course of a 1.9.19+ site:

<img complete="true" src="http://site/file.php/3/funnycompic1.jpg" alt="Funny" style="width: 402px; height: 202px;" title="Funny" vspace="0" border="0" hspace="0" />

Note after file.php/ a number.   That's the course ID number ... remaining of
the src link /funnycompic1.jpg is the file in humanly recognizable format that
was located in moodledata/3/ somewhere.

No longer true in version 2/3 in Moodle.
All files moved to filedir, are renamed for the contenthash of the resource,
(no longer found in filedir by a course ID number subdirectory nor by humanly recognizable names).

So in 2.2 you must leave legacy files turned on - site wide and in every
course until files have been moved from 'legacy'.

Historically .. there was a user that had discovered a 'work-around-way' to
rid a course of legacy, but one had to have no higher than version 2.3.2 ... after that version, the work-around no longer worked.  eg could not upgrade to 2.3.highest and expect the work-around to work. :\

There was a plugin for Moodle called poof.
Discussion:
https://moodle.org/mod/forum/discuss.php?d=276501
But I can't see to find it anymore via:
https://moodle.org/plugins/
to see if there was a version for 2.2.x .. think it came along later.

Once installed that allowed one to edit each individual resource to a file
that was broken and correct it.   Note the each individual resource.

So now comes the questions for they kinda determine where you go from here.

How many courses are we talking about?

Think the strategy now is to spin up a new/fresh 3.x and rebuild courses rather
than attempt migration from 1.9.anything up through versions of 2.x.
BTW, truely the only way to do that efficiently is via git but it means
the first step would be to move the 1.9.x site under git so one can upgrade
it to the highest 1.9.19+.  Then 'march' the site through stages.
Been there.  Done that.  It does work.   But, one still has legacy at the
end. :\

In anticipation of a logical question to ask .... can I restore a 1.9 backup
to a 2.x or 3.x?
Answer: possibly ... but ... here it comes ... you end up with legacy still.
And loose users/roles, etc..

Are you on Linux?

Are you averse to using command lien?

Are you desparate enough to try something I'm calling 'clipoof' on one course?

and last ... you might be restricted from doing this ... but have a server where we could test the 'clipoof' on one course backup ... and then restore it to one 3.0,3.1,3.2 - if you are game.

'spirit of sharing', Ken