Context Navigation

Changeset 363928

Timestamp:

03/23/2011 08:19:38 PM (15 years ago)

Author:

stevevls

Message:

add character set to the CREATE TABLE invocations and add FAQ entry and SQL to help with encoding issues.

Location:

gts-translation

Files:

-                      r305620
+                      r363928
             modified_time timestamp not null default now(),
             UNIQUE KEY (local_id, language)
         )",
+        ) CHARACTER SET 'utf8'",
 …
             UNIQUE KEY (local_id, language),
             UNIQUE KEY (post_slug(255), language)
         )",
+        ) CHARACTER SET 'utf8'",
 …
             UNIQUE KEY (local_name, language),
             UNIQUE KEY (slug, language)
         )"
+        ) CHARACTER SET 'utf8'"
     );

-                      r363906
+                      r363928
 Once the translated content is approved by a moderator, it is stored on your own server in your WordPress database.
 We'll also keep a copy in our database in case the moderators or editors decide to make more changes.
+= When I switch my blog to Russian, all I see are question marks...what gives?
+This happens when the data is stored in MySQL with the wrong character encoding.  Execute the following (being sure to
+replace 'wp_' with the prefix specified in wp-config.php if you've changed that value):
+ALTER TABLE wp_gts_translated_options CONVERT TO CHARACTER SET 'utf8';
+ALTER TABLE wp_gts_translated_posts CONVERT TO CHARACTER SET 'utf8';
+ALTER TABLE wp_gts_translated_terms CONVERT TO CHARACTER SET 'utf8';
+Then get in touch with us so that we can help you reload your content.

-                      r305620
+                      r363928
             modified_time timestamp not null default now(),
             UNIQUE KEY (local_id, language)
         )",
+        ) CHARACTER SET 'utf8'",
 …
             UNIQUE KEY (local_id, language),
             UNIQUE KEY (post_slug(255), language)
         )",
+        ) CHARACTER SET 'utf8'",
 …
             UNIQUE KEY (local_name, language),
             UNIQUE KEY (slug, language)
         )"
+        ) CHARACTER SET 'utf8'"
     );

-                      r363907
+                      r363928
 Once the translated content is approved by a moderator, it is stored on your own server in your WordPress database.
 We'll also keep a copy in our database in case the moderators or editors decide to make more changes.
+= When I switch my blog to Russian, all I see are question marks...what gives?
+This happens when the data is stored in MySQL with the wrong character encoding.  Execute the following (being sure to
+replace 'wp_' with the prefix specified in wp-config.php if you've changed that value):
+ALTER TABLE wp_gts_translated_options CONVERT TO CHARACTER SET 'utf8';
+ALTER TABLE wp_gts_translated_posts CONVERT TO CHARACTER SET 'utf8';
+ALTER TABLE wp_gts_translated_terms CONVERT TO CHARACTER SET 'utf8';
+Then get in touch with us so that we can help you reload your content.

Note: See TracChangeset for help on using the changeset viewer.