UTF-8

  • Resolved mcyzyk

    (@mcyzyk)


    3 years, 2 months ago

    (I’ve been using the paid version of this plugin for years. Love it!)

    I have a site that I’m transferring to another server. This site has MANY Greek characters on it.

    I transfer it into my (UTF-8-configured) WP Multisite server and all Greek characters become: ????????

    BUT I then go in to edit a page on this new server, put the Greek word Σωφροσ?νη in it, save, and no problem.

    So somehow, I’m thinking this plugin is not saving as UTF-8 when it takes its snapshot???

    I really need this to work. It’s for a University and the topic is largely about ancient Greece!

    Thanks,

    Mark

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter mcyzyk

    (@mcyzyk)

    Is there some way for me to unzip the packet and actually SEE whether properly-encoded Greek characters are in its text files?

    Plugin Author Yani

    (@yaniiliev)

    For premium products please reach over to our support team.
    Premium products are not supported on these forums.

    To extract wpress files, you can use Traktor.

    The plugin preserves data – you need to make sure that the encoding has been configured properly on the site that you are importing on.

    Thread Starter mcyzyk

    (@mcyzyk)

    Thanks so much!

    I used Traktor to open my .wpress file, opened up the .sql file in a text editor, and searched for: Σωφροσ?νη

    FOUND!

    For all those reading: My issue is not with this plugin.

    (And, in fact, I think I’ve determined that my issue is that any new tables in my WP Multisite are NOT being created with UTF-8 encoding. Will investigate, fix….)

    Mark

    Thread Starter mcyzyk

    (@mcyzyk)

    Hold the bus!

    While I could SEE, e.g., Σωφροσ?νη in the SQL file, there’s this:

    `[root@wphost02 my.cnf.d] [DEV] $ strings /opt/wordpress/wp-content/ai1wm-backups/wphost-dev.mse.jhu.edu-symondsproject2-20211216-152123-ld7aj3.wpress | egrep latin1
    ) ENGINE=InnoDB AUTO_INCREMENT=177 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=282 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=86 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=5433 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=2993 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=2080 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB AUTO_INCREMENT=66838076 DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;`

    So this backup file IS restoring everything into my new location as “latin1”. It’s baked right into the backup file.

    Any way to override this behavior?

    Plugin Author Borislav Angelov

    (@bangelov)

    I think this issue is because of the different charset configuration on both servers.

    Could you please make sure that import site (new site) has the same DB_CHARSET and DB_COLLATE in wp-config.php as in your export site? If not, please adjust them and re-import the website.

    Thread Starter mcyzyk

    (@mcyzyk)

    It definitely looks like the issue here is NOT with this plugin. Rather, the SQL statement coming off the host is setting creation of new tables to DEFAULT CHARSET=latin1

    Not good.

    Is there any way for me to reach into the SQL dump inside the .wpress file and replace all instances of “DEFAULT CHARSET=latin1” with “DEFAULT CHARSET=utf8mb4”???

    Thread Starter mcyzyk

    (@mcyzyk)

    Is there any way for me to reach into the SQL dump inside the .wpress file and replace all instances of “DEFAULT CHARSET=latin1” with “DEFAULT CHARSET=utf8mb4”???

    I.e., some way to open up the .wpress file, edit the SQL dump with a search and replace, then close back up the .wpress file?

    Mark

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘UTF-8’ is closed to new replies.