| 开发者 | |
|---|---|
| 更新时间 | 2026年4月16日 05:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
_trp_title_fr_CA)wpai-translatepress-sync folder to /wp-content/plugins/For posts/products:
_trp_title_[lang] - Translated title_trp_content_[lang] - Translated content/description_trp_excerpt_[lang] - Translated excerpt (optional)
For WooCommerce categories:
_trp_cat_[lang] - Translated category names (pipe-separated)
_trp_cat_slug_[lang] - Translated category slugs (requires SEO Pack)
For WooCommerce variation descriptions:
_variation_description - Default language variation description (standard WooCommerce field)
_trp_variation_desc_[lang] - Translated variation description
For WooCommerce attributes:
_trp_attr_[attribute-slug]_[lang] - Translated attribute values (pipe-separated)
Replace [lang] with your language code (e.g., fr_CA, es_ES, de_DE).
They are updated/overwritten with the new translations from your import.
No! Imported translations are saved with status 2 (Human Reviewed), which protects them from being overwritten by automatic translation.
Use pipe-separated values. Example: _trp_cat_fr_CA = "Chaises|Tables|Bureaux"
Yes, TranslatePress SEO Pack addon is required for slug translations. Category name translations work without it.
pmxi_after_post_import hook (runs after all WooCommerce processing)_trp_convert_linebreaks check)<p>, </p>, <div>, </div> tags and replaces with <br><br><!-- wp:paragraph -->)<br> variants (<br>, <br/>, <br />)<br> tags and spacers<p> tags + newlines + <br> + <div> in any combination<br> tags_trp_convert_linebreaks custom field is no longer required (normalization always happens)_trp_variation_desc_[lang] meta so themes can access it directly_trp_variation_desc_[lang])pa_ prefix in attribute meta keys_trp_cat_[lang])_trp_cat_slug_[lang]) - requires SEO Pack_trp_attr_[slug]_[lang])_trp_convert_linebreaks = 1 (deprecated in 3.7.0 - now automatic)