New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Convert Non-Latin characters in post, page and term slugs to Latin characters. | You have to log in to add a translation. | Details |
Original untranslated
Convert Non-Latin characters in post, page and term slugs to Latin characters.
You have to log in to edit this translation. |
|||
| ↑ | Cyr-To-Lat | You have to log in to add a translation. | Details |
Original untranslated |
|||
| For debugging unknown bridge calls, define <code>CYR_TO_LAT_DEBUG_LEGACY_SANITIZE_TITLE_BRIDGE</code> as <code>true</code>. This diagnostic log is disabled by default and is not enabled by <code>WP_DEBUG</code>. | You have to log in to add a translation. | Details | |
Original untranslated
For debugging unknown bridge calls, define <code>CYR_TO_LAT_DEBUG_LEGACY_SANITIZE_TITLE_BRIDGE</code> as <code>true</code>. This diagnostic log is disabled by default and is not enabled by <code>WP_DEBUG</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Cyr-To-Lat 7.0.1 keeps legacy WooCommerce local variation attributes, including <code>Any</code> variations, aligned between the product form, add-to-cart request, and cart session. | You have to log in to add a translation. | Details | |
Original untranslated
Cyr-To-Lat 7.0.1 keeps legacy WooCommerce local variation attributes, including <code>Any</code> variations, aligned between the product form, add-to-cart request, and cart session.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| Existing WooCommerce attributes are not automatically migrated during plugin upgrade. This means existing global <code>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. | You have to log in to add a translation. | Details | |
Original untranslated
Existing WooCommerce attributes are not automatically migrated during plugin upgrade. This means existing global <code>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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The filter receives the current default value, <code>$title</code>, <code>$raw_title</code>, and <code>$context</code>. Explicit known contexts, such as WordPress save handling, continue to use the dedicated 7.0 slug paths. | You have to log in to add a translation. | Details | |
Original untranslated
The filter receives the current default value, <code>$title</code>, <code>$raw_title</code>, and <code>$context</code>. Explicit known contexts, such as WordPress save handling, continue to use the dedicated 7.0 slug paths.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You can disable the broad fallback with this code: | You have to log in to add a translation. | Details | |
Original untranslated
You can disable the broad fallback with this code:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Version 7.0 uses explicit slug handlers for posts, terms, WooCommerce attributes, and other known save paths. A legacy <code>sanitize_title</code> bridge remains as a compatibility fallback for broad calls that older integrations may still rely on. | You have to log in to add a translation. | Details | |
Original untranslated
Version 7.0 uses explicit slug handlers for posts, terms, WooCommerce attributes, and other known save paths. A legacy <code>sanitize_title</code> bridge remains as a compatibility fallback for broad calls that older integrations may still rely on.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| What WooCommerce attribute behavior is supported in 7.0? | You have to log in to add a translation. | Details | |
Original untranslated
What WooCommerce attribute behavior is supported in 7.0?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| How can I control the legacy sanitize_title bridge? | You have to log in to add a translation. | Details | |
Original untranslated
How can I control the legacy sanitize_title bridge?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| WooCommerce attributes created before 7.0 are not automatically migrated. Existing global <code>pa_*</code> taxonomies and existing local or variation attribute keys should be reviewed separately; any future migration must use a dedicated dry-run-first workflow. | You have to log in to add a translation. | Details | |
Original untranslated
WooCommerce attributes created before 7.0 are not automatically migrated. Existing global <code>pa_*</code> taxonomies and existing local or variation attribute keys should be reviewed separately; any future migration must use a dedicated dry-run-first workflow.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| Existing posts, pages, terms, filenames, and WooCommerce product data are not destructively rewritten during the plugin upgrade. Use the Converter page or <code>wp cyr2lat regenerate</code> when you intentionally want to regenerate existing post and term slugs. | You have to log in to add a translation. | Details | |
Original untranslated
Existing posts, pages, terms, filenames, and WooCommerce product data are not destructively rewritten during the plugin upgrade. Use the Converter page or <code>wp cyr2lat regenerate</code> when you intentionally want to regenerate existing post and term slugs.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in installation paragraph. You have to log in to edit this translation. |
|||
| Upgrade notes for 7.0 | You have to log in to add a translation. | Details | |
Original untranslated
Upgrade notes for 7.0
CommentFound in installation header. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.