2010-10-09 05:00:13
Hi!
I am currently updating an existing version 1.5.3.3 installation to version 2.0 and I am at step 3: Conversion.
My screen shows some of the courses have been converted, but now nothing seems to be happening any more.
I do not see any final conclusion about the conversion (pass/fail).
How will I know the processing has ended?
Kind regards,
Evelien
2010-10-09 05:23:27
I refreshed the page in my browser, hoping to see more. But it would not come back.
Then I started the upgrade all over again. Now I see a page reporting that most of the courses are in Dutch (nl), for which no language pack has been installed.
A few courses are in Turkish, but were also created with a language setting of "nl".
Looks like some mistakes have been made in the past here, before my involvement in the project. :(
Is there any hope to repair a situation like this? The system tells me a language pack should (have) be(en) installed. Where should that be done? In the old installation, in the new one or in both?
I DO have a backup of the original database. The character set used was iso-8859-1...
Sorry I am such a nOOb...
2010-10-09 10:00:22
How many courses are there? Maybe start with a fresh install, and copy courses over one by one in course backups.
Have you confirmed that the system requirements are still met.
http://www.atutor.ca/atutor/docs/requirements.php
You might try upgrading to 1.5.5, then to 1.6 to do the utf-8 conversion, then to 2.0. While theoretically you should be able to upgrade from 1.5.3 to 2.0, 1.5.3 is very old, and a lot of things have changed since then both in ATutor and php/mysql.
You can find old language packs at:
http://www.atutor.ca/atutor/translate/index.old.php
2010-10-09 11:10:04
Thanks Greg!
by now I have managed to complete the upgrade. I did some of the upgrades for tables by hand and I forced the language of all the courses to 'en' temporarily. The Dutch character set is not very exotic, so I will likely get away with that for now. The Turkish ones may be damaged a little. I will check that when I get back in.
I have had to restart the upgrade again and again, so now my clumsy way of updating has re-encrypted the passwords at least 3 times :) But I know how to fix that after the one-hour blocking of the login screen. (I will reset the passwords in the database by using the SHA1-encryption of what I want them to be.)
Best regards,
Evelien