Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.8
-
Fix Version/s: 1.8
-
Component/s: Installation
-
Labels:None
-
Environment:Any
-
Database:Any
-
Affected Branches:MOODLE_18_STABLE
-
Fixed Branches:MOODLE_18_STABLE
Description
Once the 1.7 branch has been performed we must start to require DB being exclusively UTF-8 under Moodle 1.8 upwards.
This include, IMO, some different actions:
1) Modify install.php to erase the option of continue the installation with the DB not being UTF-8
2) Re-check DB encoding in the admin.php script (before commencing with tables generation)
Note that we can check that with the setup_is_unicodedb() function everywhere (plus some special checks to add to MSSQL DBs, because they NEVER run under UTF-8).
Issue Links
| This issue blocks: | ||||
| MDL-6332 | Once 1.7 branch was generated, drop UTF-8 migration support from HEAD |
|
|
|
Removed dbencodingtests in install.php as they no longer make sense; encoding check is forced during environment check anyway. Added code in admin/index.php before generating main tables to prevent installation if db is not already in unicode.