"Restore" means going back to a state which was working. It will never (try to) create new tables! You seem to have made a mess. Sorry, I know, that news is not very helpful. You should cautiously restore the site first.
What caught my eye, was the bump I had a two days ago: "Upgrade 2.7.19 > 3.1.5+ : qtype_ddimageortext " ddlexecuteerror" https://moodle.org/mod/forum/discuss.php?d=350361. No idea, whether they are related.
Visvanath Ratnaweera
Posts made by Visvanath Ratnaweera
Moodle in English -> Workshop -> Assesment phase: Can not enter the values, "Undefined variable: type in moodle/lib/pear/HTML/QuickForm/group.php on line 277" -> Re: Assesment phase: Can not enter the values, "Undefined variable: type in moodle/lib/pear/HTML/QuickForm/group.php on line 277"
by Visvanath Ratnaweera -
Even after upgrading to 3.1 [3.1.5+ (Build: 20170331) from 2.7.19 (Build: 20170313)] the problem persists. The system is Debian Jessie: PHP Version 5.6.30-0+deb8u1, MySQL 5.5.54.
The upgrade was bumpy https://moodle.org/mod/forum/discuss.php?d=350380, therefore can't say that the problem is in 3.1.5. One needs to reproduce this in a clean 3.1. (Not high priority for me right now.)
The upgrade was bumpy https://moodle.org/mod/forum/discuss.php?d=350380, therefore can't say that the problem is in 3.1.5. One needs to reproduce this in a clean 3.1. (Not high priority for me right now.)
Ken
Our posts crossed.
In short: As you pointed out, "side loading" clean code was the solution.
Longer version: I can't explain how Git lost track of my code. This being an "old" site, I was careful. Did a trial upgrade, sent a whole team to test. All was well. Today was the upgrade of the production Moodle, with an agreed dead line. The two hiccups meant a delay of two hours, 'course prohibitive in Swiss standards!
;-(
Can confirm:
That said, I am not so sure, whether my trial upgrade was on a fresh set of code. I have no other explanation for the missing files. Git didn't complain and all the key files I know, where there are version information, are correct.
Well, don't expect a serious post-mortem, now this 3.1 is in production. (I have a bad feeling though, and in the Murphy country, those bad feelings do get materialzed!)
Whatever, will write you a PM on the OT, once the dust settle. Not that we are going to change history, you know...!
Our posts crossed.
In short: As you pointed out, "side loading" clean code was the solution.
Longer version: I can't explain how Git lost track of my code. This being an "old" site, I was careful. Did a trial upgrade, sent a whole team to test. All was well. Today was the upgrade of the production Moodle, with an agreed dead line. The two hiccups meant a delay of two hours, 'course prohibitive in Swiss standards!
;-(
Can confirm:
git branch --track MOODLE_31_STABLE origin/MOODLE_31_STABLE
git checkout MOODLE_31_STABLE
That said, I am not so sure, whether my trial upgrade was on a fresh set of code. I have no other explanation for the missing files. Git didn't complain and all the key files I know, where there are version information, are correct.
Well, don't expect a serious post-mortem, now this 3.1 is in production. (I have a bad feeling though, and in the Murphy country, those bad feelings do get materialzed!)
Whatever, will write you a PM on the OT, once the dust settle. Not that we are going to change history, you know...!
For whatever the reason, ./mod/assignment directory was incomplete! I cloned a new 3.1 and replaced the ./mod/assignment directory completely. The upgrade finished after that.
Still testing for everything (touch wood ;) !
Still testing for everything (touch wood ;) !
Looks like a confusion between mod/assign and mod/assignment.
The upgrade script is looking for mod/assignment/db/install.xml, which is not there. But there is a mod/assign/db/install.xml. Does it give a hint?
The upgrade script is looking for mod/assignment/db/install.xml, which is not there. But there is a mod/assign/db/install.xml. Does it give a hint?