View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006427||OXID eShop (all versions)||2.3. Extensions (modules, themes)||public||2016-07-07 09:46||2017-03-08 15:59|
|Product Version||4.10.0 / 5.3.0|
|Target Version||Fixed in Version|
|Summary||0006427: visual cms installation causes collation warnings in sysrequirements check|
|Description||after installation of new visual cms module, the sys-req check will throw dozens of warnings for not matching collations.|
this is due to the fact, that the new visual cms tables have fields of collation 'latin1_swedish_ci' and the table "ddmedia" is the first table that is checked in the function checkCollation.
Every other table is then compared to the first tables collation type. (order by table_name)
If those tables are not also latin1_swedish_ci, the warnings are thrown.
|Tags||No tags attached.|
|PHP Version||Not defined|
|MySQL Version||Not defined|
It depends on the collation of the database itself.
If the database has the collation latin1_general_ci, the new table ddmedia has latin1_general_ci. If the database collation is for example greek_somewhat, then the table would have the collation greek_somewhat.
Please note: To reproduce this the table ddmedia must be dropped by yourself, as the deactivation of the module VisualCMS doesn't delete it (for good reasons).
you are right - my development database was indeed set to latin1_swedish_ci.
I wasnt aware of that... all tables and columns are set to latin1_general_ci.
so, the bug is more like:
collate check checks against ddmedia instead of against database collate setting.