How to get utf-8 collation in database? with no screwups?

[jonkanon]

Hello and welcome to myself

Joomlafan and now concidering cms made simple, because its seems simple and slick

However, I am installing a test and I have xampplite for windows to manage it locally at home.

The thing is that the collation in the database is latin1, and I don't know why? Or how I can adjust to get it to be utf-8. I have installed smf and there there is a checkbox for utf-8 and the collation in the database is utf as well.

I have just abandoned vBulletin because of just this problem and no easy sollution. And now when I have found cms made simple I want it to be perfect from the beginning

I don't trust latin at all, it has really f***** things up and I don't want it near me! As soon as latin is involved there is always some sort of conversion somewhere and things get messed up. It looks good and works fair, but if I fore example want to combine users from a latin1 database and a utf-8 database, and if it gets the way as it did with vbull the utf-8 got converted to utf-8 in a latindatabase and that nothing could make readable for another software.

So please don't say it is ok, instead please help humble me how to get it right from the start.

Thank you thank you and thanks

/jon

[jonkanon]

Hmm, I guess this command as a SQL query in phpmyadmin did it, but is it right????

It looks like the page still works fine,

How will future updates manage??

If it's a green light to this, then just copy and paste and the original install av cms made easy alters the collation. Experts, what is your verdict???

ALTER TABLE cms_additional_htmlblob_users COLLATE utf8_general_ci;;;
ALTER TABLE cms_additional_htmlblob_users_seq COLLATE utf8_general_ci;;
ALTER TABLE cms_additional_users COLLATE utf8_general_ci;;
ALTER TABLE cms_additional_users_seq COLLATE utf8_general_ci;;
ALTER TABLE cms_adminlog COLLATE utf8_general_ci;
ALTER TABLE cms_admin_bookmarks COLLATE utf8_general_ci;
ALTER TABLE cms_admin_bookmarks_seq COLLATE utf8_general_ci;
ALTER TABLE cms_admin_recent_pages COLLATE utf8_general_ci;
ALTER TABLE cms_admin_recent_pages_seq COLLATE utf8_general_ci;
ALTER TABLE cms_content COLLATE utf8_general_ci;
ALTER TABLE cms_content_props COLLATE utf8_general_ci;
ALTER TABLE cms_content_props_seq COLLATE utf8_general_ci;
ALTER TABLE cms_content_seq COLLATE utf8_general_ci;
ALTER TABLE cms_crossref COLLATE utf8_general_ci;
ALTER TABLE cms_css COLLATE utf8_general_ci;
ALTER TABLE cms_css_assoc COLLATE utf8_general_ci;
ALTER TABLE cms_css_seq COLLATE utf8_general_ci;
ALTER TABLE cms_events COLLATE utf8_general_ci;
ALTER TABLE cms_events_seq COLLATE utf8_general_ci;
ALTER TABLE cms_event_handlers COLLATE utf8_general_ci;
ALTER TABLE cms_event_handler_seq COLLATE utf8_general_ci;
ALTER TABLE cms_groups COLLATE utf8_general_ci;
ALTER TABLE cms_groups_seq COLLATE utf8_general_ci;
ALTER TABLE cms_group_perms COLLATE utf8_general_ci;
ALTER TABLE cms_group_perms_seq COLLATE utf8_general_ci;
ALTER TABLE cms_htmlblobs COLLATE utf8_general_ci;
ALTER TABLE cms_htmlblobs_seq COLLATE utf8_general_ci;
ALTER TABLE cms_modules COLLATE utf8_general_ci;
ALTER TABLE cms_module_deps COLLATE utf8_general_ci;
ALTER TABLE cms_module_news COLLATE utf8_general_ci;
ALTER TABLE cms_module_news_categories COLLATE utf8_general_ci;
ALTER TABLE cms_module_news_categories_seq COLLATE utf8_general_ci;
ALTER TABLE cms_module_news_seq COLLATE utf8_general_ci;
ALTER TABLE cms_module_search_index COLLATE utf8_general_ci;
ALTER TABLE cms_module_search_items COLLATE utf8_general_ci;
ALTER TABLE cms_module_search_items_seq COLLATE utf8_general_ci;
ALTER TABLE cms_module_templates COLLATE utf8_general_ci;
ALTER TABLE cms_permissions COLLATE utf8_general_ci;
ALTER TABLE cms_permissions_seq COLLATE utf8_general_ci;
ALTER TABLE cms_siteprefs COLLATE utf8_general_ci;
ALTER TABLE cms_templates COLLATE utf8_general_ci;
ALTER TABLE cms_templates_seq COLLATE utf8_general_ci;
ALTER TABLE cms_userplugins COLLATE utf8_general_ci;
ALTER TABLE cms_userplugins_seq COLLATE utf8_general_ci;
ALTER TABLE cms_userprefs COLLATE utf8_general_ci;
ALTER TABLE cms_users COLLATE utf8_general_ci;
ALTER TABLE cms_users_seq COLLATE utf8_general_ci;
ALTER TABLE cms_user_groups COLLATE utf8_general_ci;
ALTER TABLE cms_version COLLATE utf8_general_ci

Thanks,

jon

[jonkanon]

Hmmm, now things starts to get hard for me.

I did an install and tried to name the admin Åke Örn. That name wasn't able to log in at all since the characters went wierd. But in the table users, the name Åke Örn stood with no problem at all.

So new install and then converted the database to utf-8 with the sql query in the post above. After the conversion I added the user Åke Örn and made him admin, he could log in with no problem. But in the table users Åke Örn looks like "Ã…ke Örn".

This is the double conversion utf stuff I was mentioning from the beginning. So the trouble is users with å ä ö names if I don't make the conversion, or faulty names when I do the conversion.

So please help me, how will I get this to work?

/jon

[jonkanon]

I have to take a wild guess, and it is only a guess...

But I have learned that phpmyadmin can be the one thing that corrupts data. I don't know how or why but that seems to be the problem. So now I am off to learn how to modify mysql through some other sort of interface

/jon