Hello there, Moving to a new dedicated host today. My old one had mysl 4.0.20 New host has mysql 4.1.13 I get "unsupported database type" when i check the results of my whm/cpanel migration... odd thing is this is for my civicspace .8.3 rc6 install only. but my standard drupal 4.6.3 sites come up clean and working...
I was also recieving the elusive collation errors before in my civicspace sites if i enabled civicrm.. it is disabled still as a result.
My question is this... Is civicspace compatible with mysql 4.1.13? And for the future.. will i be able to get i18n working with civicspace/civicrm? What is the current status of the i18n bug? It is making me nervous that the only solution to the collation bug at this point is a hack which fundamentally disables i18n ability....
eager to see a multilingual civicspace, ryan grace.
database error was unrelated.... ..but.. i am still interested to see if anyone has tried i18n with civicspace and civicrm yet.
thanks ryan grace.
Ryan Grace wrote:
Hello there, Moving to a new dedicated host today. My old one had mysl 4.0.20 New host has mysql 4.1.13 I get "unsupported database type" when i check the results of my whm/cpanel migration... odd thing is this is for my civicspace .8.3 rc6 install only. but my standard drupal 4.6.3 sites come up clean and working...
I was also recieving the elusive collation errors before in my civicspace sites if i enabled civicrm.. it is disabled still as a result.
My question is this... Is civicspace compatible with mysql 4.1.13? And for the future.. will i be able to get i18n working with civicspace/civicrm? What is the current status of the i18n bug? It is making me nervous that the only solution to the collation bug at this point is a hack which fundamentally disables i18n ability....
eager to see a multilingual civicspace, ryan grace.
-
Ryan Grace