Cum la spre Convertizor Character A ezat a aranja �i Collation de WordPress Baz� de date

DinWordPress 2.2, WordPress supports feature that allows art.hot. user la spre define both art.hot.WordPress baz� de date character a ezat a aranja �i collation cu DB_CHARSET �i DB_COLLATE values �n�untru wp-config.php dosar. Cu ace�tia values defined, WordPress voin�� a voi folos art.hot. designated baz� de date characterset ( acuza�ie) �i baz� de date collation (i.e. sort ordine de la scrisori, num�r, �i symbols de un character a ezat a aranja) c�nd unire un baz� de date mas�.

Totu�i, �n�untru existing WordPress instalare that e�ti upgraded de la mai devreme traducere de WordPress sau nu explicitly a ezat a aranja un Unicode UTF-8 acuza�ie collation, art.hot. lips� baz� de date character a ezat a aranja is normally a instaura as Latin1 ( lips� on aproape tot MySQL instalare) cu latin1_swedish_ci collation. Dac� tu a alerga un bilingv sau multilingual blog cu WordPress, tu po�i fa�� problem� on character encoding c�nd al t�u blog post e�ti part. trecut de la vb. write �n�untru alt codru limbaj, sau c�nd tu export �i spate art.hot. baz� de date �i mai t�rziu a �nso�i la spre re- import art.hot. baz� de date dump �n sear� de baz� de date failure sau a servi a migra �i film. Art.hot. symptom is obvious, al t�u WordPress post sau pagin� voin�� a voi contact garbled, weird �i funny characters, uneori chiar lots de????? (�ntrebare pia��), rendering art.hot. WordPress baz� de date cu al t�u tare work useless �i output unreadable. (Mai veninos de asemenea by gre�eal� acuza�ie collation)

Art.hot. cel mai bun solution la character encoding problem� �n�untru WordPress is la spre convertizor art.hot. acuza�ie sau baz� de date �i collation la spre UTF-8 sau Unicode. Totu�i, tu ABIL simplu a lega la spre MySQL via raft sau phpMyAdmin �i sper�nd pentru tot al t�u scripts voin�� a voi convertizor dr�gu�. As explain by WordPress baz� de date schimbare ghid, convertizor character sets a cere folosire art.hot. art.hot. MySQL ALTER MAS� virgul�. C�nd convertizor art.hot. character sets, tot TEXT ( �i similar) fields e�ti convertizor la spre UTF-8, numai that schimbare voin�� a voi GUSTARE DE DIMINEA�� existing TEXT fiindc� art.hot. schimbare a se a�tepta la art.hot. date la spre a fi �n�untru latin1, numai WordPress Mai have magazin unicode characters �n�untru un latin1 baz� de date, �i as un result, date a putut sf�r�it sus as garbage dup� un schimbare!

Art.hot. ghid provides un foarte ruj �i vague ghid as un solution on cum la spre actually convertizor WordPress MySQL baz� de date mas� de la unul character a ezat a aranja la spre alt, usually UTF-8. Totu�i, art.hot. ghid actually works, although art.hot. proces a putea a fi lengthy. La spre convertizor, art.hot. pas involved generally e�ti la spre alter each �i fiecare TEXT �i rela�ii fields interior fiecare WP mas� la spre BLOB, apoi atunci alter art.hot. character a ezat a aranja de baz� de date �i definitiv scimbare art.hot. BLOB fields spate la spre TEXT. Privire simplu, numai cum lung it trec.de la will a lua la spre convertizor so mul�i fields on so mul�i mas�? Mult mai �ndep�rtat, tu vei de asemenea nevoie la spre a-�i aminti art.hot. origine tip �i length sau values de tot fields.

andersapt has post un schimbare script numitconvert_to_utf8_sql_generator.txt care automatically generates un list� de SQL declara�ie �i virgul� nevoie la spre plin convertizor al t�u WordPress baz� de date la spre UTF8 baz� pe ghid. Totu�i, acolo seems la spre a fi un minor bug cu art.hot. script, although art.hot. autor claimed it worked, unde �n�untru meu caz, it simplu wont’ generate art.hot. list� de SQL virgul� la spre a alerga datorie la error “PHP Fatal error: Chemare la spre un member func�ie get_results() on un nu-object �n�untru convert.php on linie 37″. O dat� fixat, cu this script �n�untru m�n� noi a putea easily �i iute convertizor art.hot. baz� de date, mas� �i fields la spre folos utf8_general_ci collation.

not � Eu am tried afar�UTF-8 Baz� de date Convertizor dop, numai s�u’ un failure. It seemed asem�n�tor art.hot. autor scimbare la spre character a ezat a aranja direct.

Ghid la spre Convertizor WordPress Baz� de date Character A ezat a aranja la spre UTF8 (Unicode)

1. A lua art.hot. WordPress blog offline by placing un afar�- de- serviciu sau maintenance notice.
2. Spate baz� de date acesta este foarte import, nothing is guaranteed la spre work. Dac� al t�u’ folosire cPanel sau alt contract panel, s�u’ cel mai bun la spre parfum un baz� de date spate de la contract panel se, unde tu po�i pauz� art.hot. baz� de date �n�untru unul piece �n schimbul by SQL declara�ie, �n caz de normal dump.
3. art.hot. fixatconvert_to_utf8_sql_generator.txt script �i a salva it cu un PHP prelungire.
4. Modify art.hot. script la spre input art.hot. baz� de date nume al t�u WordPress blog is folosire. A localiza art.hot. a urma text:

   Tables_in_DATABASENAME

   Art.hot. DATABASENAME �n�untru ro�u is art.hot. unic thing that tu nevoie la spre scimbare la spre meciuri al t�u WordPress baz� de date nume. It voi arat� ca this dup� scimbare, pentru a instala,

   Tables_in_wp_mydigitallife

5. �nc�rcat art.hot. convert_to_utf8_sql_generator.php ( sau tu po�i rename la spre un �ort nume such as convert.php) la baz� root WordPress instalare sincer, unde wp-config.php is de asemenea situat.
6. Acum, chemare �i maro art.hot. script de la orice web maro. La spre a face this, simplu a aduna convert_to_utf8_sql_generator.php ( sau orice nume tu a da la script) la sf�r�it de al t�u blog URL (i.e http:/www.mywebsite.com/convert_to_utf8_sql_generator.php) �i pres Enter. UN lung list� de SQL declara�ie voin�� a voi a fi generated pe web pagin�.
7. A asigura that al t�u post_content �i post titlu fields on wp_posts mas� DOES NU sub la spre orice a cresta sau FULLTEXT a cresta. Else art.hot. tip de la fields Mai nu a fi convertizor la spre BLOB cu unul de la errors list� sub. Ni�te dop, such as rela�ii post tend la spre a aduna a cresta la spre ace�tia fields. �n�untru this caz, temporarily drop art.hot. a cresta.

   ERROR 1170 (42000): BLOB/TEXT Columbia ‘post_content’ folosit �n�untru cheie specification f�r� un cheie length

   ERROR 1283 (HY000): Columbia ‘post_content’ abil a fi part de FULLTEXT a cresta

8. Login la spre al t�u a servi raft by Telnet sau SSH. Tu po�i skip this part de folosire Unix raft dac� tu intend la spre folos phpMyAdmin la spre a face art.hot. murd�rie work, numai Eu am nu tried it. So dac� tu a face, a face feedback on dac� it a putea a fi done.
9. A lega la spre MySQL a servi de la raft.
10. Publicare art.hot. a urma virgul� primul �n�untru MySQL prompt:

    folos DATABASENAME;

    Iar, replace DATABASENAME �n�untru ro�u la actual WordPress baz� de date nume.

11. Apoi atunci copie �i trecut art.hot. �ntreg list� de SQL declara�ie auto generated by art.hot. schimbare script, �i trecut pe ei into art.hot. MySQL prompt. Each �i fiecare SQL virgul� voi acum a fi proces �i executed by MySQL unul by unul. Tu po�i nevoie la spre pres Enter cheie la spre terminat off art.hot. ultimul unul.
12. �n timpul art.hot. proces, art.hot. similar error mesaj rela�ii la spre cheie length as mentioned Mai apendice. �n�untru meu caz, art.hot. schimbare la spre BLOB failed cu such mesaj �n a urma fields:

    wp_categories.category_nicename
    wp_comments.comment_approved
    wp_links.link_visible
    wp_options.option_name
    wp_postmeta.meta_key
    wp_posts.post_status
    wp_posts.post_name
    wp_posts.post_type
    wp_usermeta.meta_key
    wp_users.user_login

    Tot ace�tia fields e�ti unlikely la spre contact nu-ASCII characters. �i fields such as category_nicename (category slug) �i post_name ( post slug) have been URL encoded ( unde al t�u URL cu unsafe nu-alphanumeric characters voin�� a voi a fi replaced cu un la sut� (%) semn a urma by doi hex cifr� �i perioad� encoded as plus (+) semn). Initial encoding de byte codes �i character assignments pentru UTF-8 is consistent cu ASCII, so sincer schimbare de ace�tia fields la spre UTF8 nu vom bring foarte mult problem�.

13. A redacta art.hot. wp-config.php dosar la spre a aduna �n�untru DB_CHARSET �i DB_COLLATE definitions. A aduna art.hot. a urma doi linii, preferably jos art.hot. section de MySQL Aranjare:

    defineDB_CHARSET(’’, ‘utf8′);
    defineDB_COLLATE(’’, ”);

    As explained �n�untruWordPress Codex, DB_COLLATE is left gol (null) so that art.hot. baz� de date collation voin�� a voi a fi automatically assigned by MySQL baz� pe baz� de date character a ezat a aranja.

14. Recreate art.hot. a cresta �i/ sau FULLTEXT a cresta been dropped, dac� orice.
15. Activate art.hot. blog spate into produc�ie model.
16. A verifica al t�u blog la spre a vedea dac� tot �i fiecare characters is foarte bine.
17. A �terge art.hot. PHP script.

import: Aceasta este o machine a traduce pagin� care is provided "as is" f�r� warranty. Machine traducere Mai a fi difficult la spre understand. A face pe plac la refer la spreorigine Englez anghinar� oric�nd posibil.

Share �i contribute sau a lua technical cin� �i ajutor laMeu Digital Via�� Forums.

Rela�ii Anghinar�

• WordPress Acuza�ie Encoding Problem� Dup� Upgrading la spre Traducere 2.2
• Cum la spre Spate �i Pauz� ( export �i Import) MySQL Baz� de date Tutorial
• IMP-00016 A cere Character A ezat a aranja Schimbare Nu Supported Error c�nd Import la spre Oracle Baz� de date
• WordPress 2.2 Released pentru Drum liber Drum liber
• Oracle EXP-00091 Error C�nd Export Baz� de date
• A nu fi de acord �i Nap Off Post Revizuire Tracking �n�untru WordPress 2.6 sau Above
• A verifica �i Optimize MySQL Baz� de date Automatically cu Crontab/Cron
• Cum la spre Obicei, Modify sau Scimbare WordPress Baz� de date Unire Error Pagin�
• WordPress 2.3 Release Candidate 1 (RC1) cu Tags Cin�
• Cum la spre A mi�ca WordPress Blog la spre Nou Domain sau A localiza

This intrare was post on S�mb�t�, Iunie 23rd, 2007 la 259: s�nt �i is dosar josInternet Serviciu. Tu po�i a urma orice r�spuns la spre this intrare g�t art.hot.RSS 2.0 feed. Tu po�iplecare un r�spuns,sau trackback de la al t�u own site.