What's going on in 1.6development

What's going on in 1.6development

by Howard Miller -
Number of replies: 5
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
All of a sudden this morning all my strings are ..... after I did a CVS update.

I gather that all the language files have been removed leaving only en_utf8 but even selecting eb_utf8 doesn't fix the problem.
Average of ratings: -
In reply to Howard Miller

Re: What's going on in 1.6development

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
This *might* be a bug actually... With the new 'regime' you have only have utf8 so you have to run the migrate script utfdbmigrate.php, yes? But you can no longer see the message on the admin screen telling you to that - all you get is unicodeupgradenotice. If you see what I mean mixed
In reply to Howard Miller

Re: What's going on in 1.6development

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
It's sort of mid-way at the moment, we're just sorting it all out.
In reply to Martin Dougiamas

Re: What's going on in 1.6development

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
ahhhhh..... I'll shut up then smile

Have fun!
In reply to Howard Miller

Re: What's going on in 1.6development

by Julian Ridden -
rename your en language folder to en_utf8

That did it for me.
In reply to Julian Ridden

Re: What's going on in 1.6development

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
Be careful next time you upgrade, because there is an en_utf8 in there now.