Converts Cyrillic characters in post, page, and term slugs to Latin characters. Useful for creating human-readable URLs.<\/p>\n\n
<\/p>\n\n
Based on the original Rus-To-Lat plugin by Anton Skorobogatov.<\/p>\n\n
Sponsored by Blackfire<\/a>.<\/p>\n\n <\/p>\n\n Version 7.0 is an architecture-focused release. It keeps the existing transliteration table, locale filters, post and term conversion tools, and WP-CLI command stable while moving slug handling to explicit services.<\/p>\n\n Existing posts, pages, terms, filenames, and WooCommerce product data are not destructively rewritten during the plugin upgrade. Use the Converter page or WooCommerce attributes created before 7.0 are not automatically migrated. Existing global Cyr-To-Lat 7.0.1 keeps legacy WooCommerce local variation attributes, including Add this code to your theme's For instance, if your non-standard locale is uk_UA, you can redefine it to Add similar code to your theme's Version 7.0 uses explicit slug handlers for posts, terms, WooCommerce attributes, and other known save paths. A legacy You can disable the broad fallback with this code:<\/p>\n\n The filter receives the current default value, For debugging unknown bridge calls, define Add similar code to your theme's Add the following code to your plugin's (or mu-plugin's) main file. This code won't work being added to a theme's functions.php file.<\/p>\n\n Add similar code to your theme's Use the following command in the console:<\/p>\n\n Where\n -post_type is a list of post types,\n -post_status is a list of post statuses.<\/p><\/dd>\n Cyr-To-Lat 7.0 explicitly handles new and updated WooCommerce product slugs, product category and tag slugs, global attribute slugs, global attribute term slugs, local product attribute keys, variation attribute keys, frontend add-to-cart requests, cart session loading, REST\/API saves, and admin save flows.<\/p>\n\n Existing WooCommerce attributes are not automatically migrated during plugin upgrade. This means existing global Regeneration of thumbnails with the command To avoid it, deactivate the cyr2lat plugin during regeneration:<\/p>\n\n Yes, you can!<\/p>\n\n Please report security vulnerabilities by email to:<\/p>\n\n security@kagg.eu<\/strong><\/p>\n\n When reporting a vulnerability, please include as much information as possible to help us reproduce and investigate the issue, such as:<\/p>\n\n We will review your report and respond as quickly as possible.<\/p><\/dd>\n\n<\/dl>\n\n\nPlugin Support<\/h3>\n\n
\n
\n
cyr2lat<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\nUpgrade notes for 7.0<\/h4>\n\n
wp cyr2lat regenerate<\/code> when you intentionally want to regenerate existing post and term slugs.<\/p>\n\npa_*<\/code> taxonomies and existing local or variation attribute keys should be reviewed separately; any future migration must use a dedicated dry-run-first workflow.<\/p>\n\nAny<\/code> variations, aligned between the product form, add-to-cart request, and cart session.<\/p>\n\n\n\n
How can I define my own substitutions?<\/h3><\/dt>\n
functions.php<\/code> file:<\/p>\n\n\/**\n * Modify conversion table.\n *\n * @param array $table Conversion table.\n *\n * @return array\n *\/\nfunction my_ctl_table( $table ) {\n $table['\u042a'] = 'U';\n $table['\u044a'] = 'u';\n\n return $table;\n}\nadd_filter( 'ctl_table', 'my_ctl_table' );\n<\/code><\/pre><\/dd>\nHow can I redefine non-standard locale?<\/h3><\/dt>\n
uk<\/code> by adding the following code to your theme's function.php<\/code> file:<\/p>\n\n\/**\n * Use non-standard locale.\n *\n * @param string $locale Current locale.\n *\n * @return string\n *\/\nfunction my_ctl_locale( $locale ) {\n if ( 'uk_UA' === $locale ) {\n return 'uk';\n }\n\n return $locale;\n}\nadd_filter( 'ctl_locale', 'my_ctl_locale' );\n<\/code><\/pre><\/dd>\nHow can I define my own transliteration of titles?<\/h3><\/dt>\n
functions.php<\/code> file:<\/p>\n\n\/**\n * Filter title before sanitizing.\n *\n * @param string|false $result Sanitized title.\n * @param string $title Title.\n *\n * @return string|false\n *\/\nfunction my_ctl_pre_sanitize_title( $result, $title ) {\n if ( '\u043f\u0438\u0432\u043e' === $title ) {\n return 'beer';\n }\n\n return $result;\n}\nadd_filter( 'ctl_pre_sanitize_title', 10, 2 );\n<\/code><\/pre><\/dd>\nHow can I control the legacy sanitize_title bridge?<\/h3><\/dt>\n
sanitize_title<\/code> bridge remains as a compatibility fallback for broad calls that older integrations may still rely on.<\/p>\n\nadd_filter( 'ctl_enable_legacy_sanitize_title_bridge', '__return_false' );\n<\/code><\/pre>\n\n$title<\/code>, $raw_title<\/code>, and $context<\/code>. Explicit known contexts, such as WordPress save handling, continue to use the dedicated 7.0 slug paths.<\/p>\n\nCYR_TO_LAT_DEBUG_LEGACY_SANITIZE_TITLE_BRIDGE<\/code> as true<\/code>. This diagnostic log is disabled by default and is not enabled by WP_DEBUG<\/code>.<\/p><\/dd>\nHow can I define my own transliteration of filenames?<\/h3><\/dt>\n
functions.php<\/code> file:<\/p>\n\n\/**\n * Filter filename before sanitizing.\n *\n * @param string|false $result Sanitized filename.\n * @param string $filename Title.\n *\n * @return string|false\n *\/\nfunction my_ctl_pre_sanitize_filename( $result, $filename ) {\n if ( '\u043f\u0438\u0432\u043e' === $filename ) {\n return 'beer';\n }\n\n return $result;\n}\nadd_filter( 'ctl_pre_sanitize_filename', 10, 2 );\n<\/code><\/pre><\/dd>\nHow can I allow the plugin to work on the frontend?<\/h3><\/dt>\n
\/**\n * Filter status allowed Cyr To Lat plugin to work.\n *\n * @param bool $allowed\n *\n * @return bool\n *\/\nfunction my_ctl_allow( bool $allowed ): bool {\n $uri = isset( $_SERVER['REQUEST_URI'] ) ?\n sanitize_url( wp_unslash( $_SERVER['REQUEST_URI'] ) ) :\n '';\n\n if ( 0 === strpos( $uri, '\/divi-comments' ) ) {\n return true;\n }\n\n return $allowed;\n}\n\nadd_filter( 'ctl_allow', 'my_ctl_allow' );\n<\/code><\/pre><\/dd>\nHow can I limit post types for background conversion?<\/h3><\/dt>\n
functions.php<\/code> file:<\/p>\n\n\/**\n * Filter post types allowed for background conversion.\n *\n * @param array $post_types Allowed post types.\n *\n * @return array\n *\/\nfunction my_ctl_post_types( $post_types ) {\n return [\n 'post' => 'post',\n 'page' => 'page',\n 'attachment' => 'attachment',\n 'product' => 'product',\n 'nav_menu_item' => 'nav_menu_item',\n ];\n}\nadd_filter( 'ctl_post_types', 'my_ctl_post_types' );\n<\/code><\/pre><\/dd>\nHow can I convert many posts\/terms using wp-cli?<\/h3><\/dt>\n
wp cyr2lat regenerate [--post_type=<post_type>] [--post_status=<post_status>]\n<\/code><\/pre>\n\nWhat WooCommerce attribute behavior is supported in 7.0?<\/h3><\/dt>\n
pa_*<\/code> taxonomies, local product attribute keys, and variation attribute keys keep their current stored values until you intentionally change them. A future migration tool should be separate and dry-run-first so store owners can review the impact before any rewrite.<\/p><\/dd>\nHow can I regenerate thumbnails safely?<\/h3><\/dt>\n
wp media regenerate<\/code> can break links in old posts as file names become transliterated.<\/p>\n\nwp media regenerate --skip-plugins=cyr2lat\n<\/code><\/pre><\/dd>\nCan I contribute?<\/h3><\/dt>\n
\n
Where do I report security bugs found in this plugin?<\/h3><\/dt>\n
\n
7.0.1 (20.05.2026)<\/h4>\n\n
\n
Any<\/code> variations, after upgrading from versions before 7.0.<\/li>\n7.0.0 (18.05.2026)<\/h4>\n\n
\n
ctl_enable_legacy_sanitize_title_bridge<\/code> compatibility filter for broad legacy sanitize_title<\/code> behavior.<\/li>\n6.8.0 (10.05.2026)<\/h4>\n\n
\n
6.7.0 (01.04.2026)<\/h4>\n\n
\n
6.6.0 (30.11.2025)<\/h4>\n\n
\n
6.5.0 (24.10.2025)<\/h4>\n\n
\n
6.4.1 (03.05.2025)<\/h4>\n\n
\n
6.3.0 (22.12.2024)<\/h4>\n\n
\n
6.2.3 (24.11.2024)<\/h4>\n\n
\n
6.2.2 (15.11.2024)<\/h4>\n\n
\n
6.2.1 (13.11.2024)<\/h4>\n\n
\n
6.2.0 (13.11.2024)<\/h4>\n\n
\n
6.1.0 (09.03.2024)<\/h4>\n\n
\n
6.0.8 (14.02.2024)<\/h4>\n\n
\n
6.0.7 (11.02.2024)<\/h4>\n\n
\n
6.0.6 (14.01.2024)<\/h4>\n\n
\n
6.0.5 (09.10.2023)<\/h4>\n\n
\n
6.0.4 (23.09.2023)<\/h4>\n\n
\n
6.0.3 (29.07.2023)<\/h4>\n\n
\n
6.0.2 (26.07.2023)<\/h4>\n\n
\n
6.0.1 (26.07.2023)<\/h4>\n\n
\n
6.0.0 (26.07.2023)<\/h4>\n\n
\n