Hello,
i am curious why CB 1.8.1 (tools) wants to change a lot of fields ?!?!
for example 1 date and some checkbox fields to varchar(255)...
also a default setting should be set to NULL ? Why is all this happening. CB 1.8 did not have any issues or complaints about my fields.
...
DATE:
Table #__comprofiler Column cb_geburtsdatum type is date instead of varchar(255)
CHECKBOX:
Table #__comprofiler Column cb_allowausweisdruck type is tinyint(3) unsigned instead of varchar(255)
Table #__comprofiler Column cb_eaccess type is tinyint(3) unsigned instead of varchar(255)
Table #__comprofiler Column cb_versicherung type is tinyint(3) unsigned instead of varchar(255)
DEFAULT:
Table #__comprofiler Column cb_magazin DEFAULT is 'drums & percussion (6 Ausgaben)' instead of NULL
CHECKBOXES:
Table #__comprofiler Column cb_magazin3 type is tinyint(3) unsigned instead of varchar(255)
Table #__comprofiler Column cb_magazin4 type is tinyint(3) unsigned instead of varchar(255)
Table #__comprofiler Column cb_mitgliedschaftok type is tinyint(3) unsigned instead of varchar(255)
...
Is this correct? I don´t trust this info. Can it harm my installation and data storage?
Additionally, i see RED field types in field manager, and the roolover tooltip says "the field might not be visible, because CB core field AJAX is not published...". But i don´t use it on any field, yet!
Please, help.
EDIT:
I removed CB Core Field AJAX plugin, and the red marks disappear. CB Tools field check turns back to normal, there are no messages at all.
Questions:
Does CB Core Field AJAX have to modify the fields to varchar?! If yes, why? Does my previous posted messages make any sense? Is it a feature or bug?
krileon
