media

Thanks... :)

my question is mod tables will stay there or the upgrade will wipe them off???

3.0 is on its way... I have few mods on my site, if i upgrade my board to 3.0 probably those mods are not going to be ready for 3.0 Can i keep the old mods on the system until i get the upgrade scripts for those mods??? or new 3.0 upgrade will wipe those mods off????? Thanks

Valtasar, I would like to thank you on this matter

in my config file i have this $INFO['sql_driver'] = 'mySQL'; Can someone help to place this code mysql_query( "SET NAMES utf8", $this->connection_id ); into this function, maybe i am doing something wrong on placing it into the function else { if ( IPS_MAIN_DB_CLASS_LEGACY ) { $this->connection_id = @mysql_connect( $this->obj['sql_host'] , $this->obj['sql_user'] , $this->obj['sql_pass'] ); } else { $this->connection_id = @mysql_connect( $this->obj['sql_host'] , $this->obj['sql_user'] , $this->obj['sql_pass'] , $this->obj['force_new_connection'] ); } } I will move this to pear section... :) thanks

No still broken charecters... I do not really get this why PHPMYADMIN is showing everything right and IPB is showin broken...

Hi bfarber, Just testing purposes, Would you please show me how i can edit this function with your recomendations Thanks

Oh that's excellent news... :) very happy to hear that.... Thanks

Thanks, This is the code that i have found, would you please show me how i can place that into this? if ( IPS_MAIN_DB_CLASS_LEGACY ) { $this->connection_id = @mysql_connect( $this->obj['sql_host'] , $this->obj['sql_user'] , $this->obj['sql_pass'] ); } else { $this->connection_id = @mysql_connect( $this->obj['sql_host'] , $this->obj['sql_user'] , $this->obj['sql_pass'] , $this->obj['force_new_connection'] ); } Thanks

Matt, Sorry to ask you but, is this explanation is for me? Are you saying that i do not have to convert my database to utf-8 for SEF links?

Thank you for your help, but i have no idea how to do those... I am on 2.3 and would you please tell me how i can do (in 2.3 you need to modify the database driver to do this.> this??? Thanks :)

Hello, I have finally got the database converted to UTF-8, but my problem is; In PhpMyAdmin I can read my string right with utf-8, but on the site in IPB view all the strings from database are broken (I have already set charset in CP to utf-8 - Yes i have recreated skins in CP) What would be the problem....???? (I see the browser is showing that site is using UTF-8 - Also I have cleared browser cache) Do i need to change anything else in the script or ????? any suggestion or idea.... Thanks

I have just tried this... It says it is completed but content of the database is still same.. Didn't convert anyything to UTF-8 (Content) But it converted table and field and database collation to UTF-8.... :)

Why i am getting stuck at this point???? Table inv_acp_help: fields to be converted: 4 primary keys: 1 inv_acp_help.page_key is assumed to contain iso-8859-9 characters inv_acp_help.help_title is assumed to contain iso-8859-9 characters inv_acp_help.help_body is assumed to contain iso-8859-9 characters inv_acp_help.help_mouseover is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 150 rows Converted: 190 rows Converted: inv_acp_help Table inv_admin_login_logs: fields to be converted: 3 primary keys: 1 inv_admin_login_logs.admin_ip_address is assumed to contain iso-8859-9 characters inv_admin_login_logs.admin_username is assumed to contain iso-8859-9 characters inv_admin_login_logs.admin_post_details is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 124 rows Converted: inv_admin_login_logs Table inv_admin_logs: fields to be converted: 4 primary keys: 1 inv_admin_logs.act is assumed to contain iso-8859-9 characters inv_admin_logs.code is assumed to contain iso-8859-9 characters inv_admin_logs.note is assumed to contain iso-8859-9 characters inv_admin_logs.ip_address is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 150 rows Converted: 200 rows Converted: 250 rows Converted: 300 rows Converted: 340 rows Converted: inv_admin_logs Table inv_admin_permission_keys: Skipping field perm_key since it is a primary key Table inv_admin_permission_keys: fields to be converted: 3 primary keys: 1 inv_admin_permission_keys.perm_main is assumed to contain iso-8859-9 characters inv_admin_permission_keys.perm_child is assumed to contain iso-8859-9 characters inv_admin_permission_keys.perm_bit is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 144 rows Converted: inv_admin_permission_keys Table inv_admin_permission_rows: fields to be converted: 1 primary keys: 1 Converted: inv_admin_permission_rows Table inv_admin_sessions: Skipping field session_id since it is a primary key Table inv_admin_sessions: fields to be converted: 4 primary keys: 1 inv_admin_sessions.session_ip_address is assumed to contain iso-8859-9 characters inv_admin_sessions.session_member_name is assumed to contain iso-8859-9 characters inv_admin_sessions.session_member_login_key is assumed to contain iso-8859-9 characters inv_admin_sessions.session_location is assumed to contain iso-8859-9 characters Converted: 1 rows Converted: inv_admin_sessions Table inv_announcements: fields to be converted: 3 primary keys: 1 inv_announcements.announce_title is assumed to contain iso-8859-9 characters inv_announcements.announce_post is assumed to contain iso-8859-9 characters inv_announcements.announce_forum is assumed to contain iso-8859-9 characters Converted: 4 rows Converted: inv_announcements Table inv_api_log: fields to be converted: 3 primary keys: 1 Converted: inv_api_log Table inv_api_users: fields to be converted: 4 primary keys: 1 Converted: inv_api_users Table inv_attachments: fields to be converted: 6 primary keys: 1 inv_attachments.attach_ext is assumed to contain iso-8859-9 characters inv_attachments.attach_file is assumed to contain iso-8859-9 characters inv_attachments.attach_location is assumed to contain iso-8859-9 characters inv_attachments.attach_thumb_location is assumed to contain iso-8859-9 characters inv_attachments.attach_post_key is assumed to contain iso-8859-9 characters inv_attachments.attach_rel_module is assumed to contain iso-8859-9 characters Converted: 4 rows Converted: inv_attachments Table inv_attachments_type: fields to be converted: 3 primary keys: 1 inv_attachments_type.atype_extension is assumed to contain iso-8859-9 characters inv_attachments_type.atype_mimetype is assumed to contain iso-8859-9 characters inv_attachments_type.atype_img is assumed to contain iso-8859-9 characters Any help?

The beauty of UTF-8 is you can post in any language without beaking their own charecters... SEF URL works with UTF-8 very well without getting any weird URL

Valtasar, I do not have any problem with time out... Script just display the code that i posted previous message and stop runing (1-2 minutes)... I tried to run again with mysql_query("SET max_allowed_packet=24M"); and same thing same code displayed on the scren.... :)

I did tried and i got as far as this Table inv_acp_help: fields to be converted: 4 primary keys: 1 inv_acp_help.page_key is assumed to contain iso-8859-9 characters inv_acp_help.help_title is assumed to contain iso-8859-9 characters inv_acp_help.help_body is assumed to contain iso-8859-9 characters inv_acp_help.help_mouseover is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 150 rows Converted: 190 rows Converted: inv_acp_help Table inv_admin_login_logs: fields to be converted: 3 primary keys: 1 inv_admin_login_logs.admin_ip_address is assumed to contain iso-8859-9 characters inv_admin_login_logs.admin_username is assumed to contain iso-8859-9 characters inv_admin_login_logs.admin_post_details is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 124 rows Converted: inv_admin_login_logs Table inv_admin_logs: fields to be converted: 4 primary keys: 1 inv_admin_logs.act is assumed to contain iso-8859-9 characters inv_admin_logs.code is assumed to contain iso-8859-9 characters inv_admin_logs.note is assumed to contain iso-8859-9 characters inv_admin_logs.ip_address is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 150 rows Converted: 200 rows Converted: 250 rows Converted: 300 rows Converted: 340 rows Converted: inv_admin_logs Table inv_admin_permission_keys: Skipping field perm_key since it is a primary key Table inv_admin_permission_keys: fields to be converted: 3 primary keys: 1 inv_admin_permission_keys.perm_main is assumed to contain iso-8859-9 characters inv_admin_permission_keys.perm_child is assumed to contain iso-8859-9 characters inv_admin_permission_keys.perm_bit is assumed to contain iso-8859-9 characters Converted: 50 rows Converted: 100 rows Converted: 144 rows Converted: inv_admin_permission_keys Table inv_admin_permission_rows: fields to be converted: 1 primary keys: 1 Converted: inv_admin_permission_rows Table inv_admin_sessions: Skipping field session_id since it is a primary key Table inv_admin_sessions: fields to be converted: 4 primary keys: 1 inv_admin_sessions.session_ip_address is assumed to contain iso-8859-9 characters inv_admin_sessions.session_member_name is assumed to contain iso-8859-9 characters inv_admin_sessions.session_member_login_key is assumed to contain iso-8859-9 characters inv_admin_sessions.session_location is assumed to contain iso-8859-9 characters Converted: 1 rows Converted: inv_admin_sessions Table inv_announcements: fields to be converted: 3 primary keys: 1 inv_announcements.announce_title is assumed to contain iso-8859-9 characters inv_announcements.announce_post is assumed to contain iso-8859-9 characters inv_announcements.announce_forum is assumed to contain iso-8859-9 characters Converted: 4 rows Converted: inv_announcements Table inv_api_log: fields to be converted: 3 primary keys: 1 Converted: inv_api_log Table inv_api_users: fields to be converted: 4 primary keys: 1 Converted: inv_api_users Table inv_attachments: fields to be converted: 6 primary keys: 1 inv_attachments.attach_ext is assumed to contain iso-8859-9 characters inv_attachments.attach_file is assumed to contain iso-8859-9 characters inv_attachments.attach_location is assumed to contain iso-8859-9 characters inv_attachments.attach_thumb_location is assumed to contain iso-8859-9 characters inv_attachments.attach_post_key is assumed to contain iso-8859-9 characters inv_attachments.attach_rel_module is assumed to contain iso-8859-9 characters Converted: 4 rows Converted: inv_attachments Table inv_attachments_type: fields to be converted: 3 primary keys: 1 inv_attachments_type.atype_extension is assumed to contain iso-8859-9 characters inv_attachments_type.atype_mimetype is assumed to contain iso-8859-9 characters inv_attachments_type.atype_img is assumed to contain iso-8859-9 characters It stopped 1 minute later and displayed this... :( Thank you Valtasar for batch addition... :)

Thank you... I will run it from command line next time but someone needs to modify the script with batch system... I hope someone willing to do that.. Thanks guys...

I set php_value max_execution_time 0 in .htaccess and try to run again.... But for the big databases we need batch system like to run 500 records at a time... Finally Timed out... :) Thanks

After I change those new setting... It is working i see chars in UTF-8... But still problem exist, if the database or table is big the script stops working.... Is there a way to setup the memory thing in php? to prevent that...

Ok i got this as output: Table inv_acp_help: fields to be converted: 4 primary keys: 1 Converted: page_key Converted: help_title Converted: help_body Converted: help_mouseover Table inv_admin_login_logs: fields to be converted: 3 primary keys: 1 Converted: admin_ip_address Converted: admin_username Converted: admin_post_details Table inv_admin_logs: fields to be converted: 4 primary keys: 1 Converted: act Converted: code Converted: note Converted: ip_address Table inv_admin_permission_keys: Skipping field perm_key since it is a primary key Table inv_admin_permission_keys: fields to be converted: 3 primary keys: 1 Converted: perm_main Converted: perm_child Converted: perm_bit Table inv_admin_permission_rows: fields to be converted: 1 primary keys: 1 Converted: row_perm_cache Table inv_admin_sessions: Skipping field session_id since it is a primary key Table inv_admin_sessions: fields to be converted: 4 primary keys: 1 Converted: session_ip_address Converted: session_member_name Converted: session_member_login_key Converted: session_location Table inv_announcements: fields to be converted: 3 primary keys: 1 Converted: announce_title Converted: announce_post No did not do the job... I guess memory limit or something is effecting the script what should i do to prevent that.... or something else

Thank you I am ready to give it a try right now.... will see what happens... At least it is a copy of my database we can play with it... Thanks Valtasar....

Ok let me rewrite what I do again and let's see if you see anything i am missing.... :) 1. Make a copy of my database with phpmyadmin 2. On new database, I run this little script to convert collums and fields to new charset // Database info $dbhost = "localhost"; $dbuser = "username"; $dbpass = "password"; $dbname = "db_name"; //ALTER TABLE $table DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci, CONVERT TO CHARACTER SET utf8 //ALTER TABLE $table DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci // <?php

Guys don't get me wrong I have to understand before i do anything please follow my steps and tell if anything wrong with these steps... Do i need to do anything other than above steps? Valtasar, I have to give the GOLD MEDAL man.... Thank you :cool: [*]A new copy of my database on the server [*]Upload script to the root of IPB [*]Edit new database information (copy) in the script (Database and charset) [*]Run the script

Valtasar, Thank you for this, but your post is too technical for us.... What do you mean by "LOCAL COPY ONLY"???? If i make a back up from my database with PHPMYADMIN and run this script on my backup on the server, CAN I DO THIS?