Multisite Translation Relations
| 开发者 | mudosdigital |
|---|---|
| 更新时间 | 2026年5月23日 18:25 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Multisite Translation Relations helps WordPress Multisite networks connect posts and pages that represent the same content in different languages.
The plugin stores relation metadata on each content item, provides admin columns and row actions for editors, outputs frontend language switcher markup, and adds SEO-friendly hreflang tags for published related content.
This is not an automatic translation plugin. It manages relationships between translated content that editors create or link across subsites.
Documentation: https://mudosdigital.com/multisite-translation-relations/
Features
- Link translated posts and pages across WordPress Multisite subsites.
- Create translation drafts on target language sites.
- Link existing translated content without duplicating posts.
- Prevent duplicate translations for the same language.
- Site locale mapping.
- Language and relation admin columns for supported post types.
- Translation relation metabox.
- Frontend language switcher shortcode:
[mstr_language_switcher]. - Hreflang alternate output for published singular content.
- Translation Health audit screen.
- Safe repair tools for missing language metadata.
- Editorial multisite networks where each language is a subsite.
- Teams that translate selected pages manually and need relation management.
- SEO workflows that need consistent hreflang output from relation data.
- Site owners who need to audit legacy multilingual relation metadata.
安装:
- Upload the
multisite-translation-relationsfolder to/wp-content/plugins/. - Network activate the plugin from Network Admin > Plugins.
- Open Network Admin > Settings > Multilingual Relations.
- Confirm enabled post types and site locale mapping.
- Open Network Admin > Settings > Translation Health.
- Run the audit and review relation health before making bulk edits.
屏幕截图:
常见问题:
Does uninstalling the plugin remove translation metadata?
No. The uninstall routine intentionally preserves mstr_post_language, mstr_translation_group, and mstr_translation_source metadata to avoid data loss.
Does every post or page need a translation group?
No. Content without translations can remain outside a group. Translation Health reports these as informational items, not critical errors.
Are draft translations shown to visitors or search engines?
No. Draft, private, trash, and unsupported post type relations are excluded from frontend switchers and hreflang output.
Can the repair tool overwrite existing language metadata?
No. The safe repair tool only fills empty mstr_post_language values from site locale mapping. Existing language metadata is not overwritten.
更新日志:
1.0.4
- Added dynamic multisite locale discovery from site paths and language subdomains when explicit locale mapping is not saved.
- Keeps manual Network Admin locale mapping as the first priority while allowing /tr/ style subsites to work out of the box.
- Moved admin column CSS into the registered admin stylesheet and enqueue flow.
- Replaced the short
mmrcode prefix with the longermstrprefix for plugin-owned code identifiers, hooks, options, metadata, AJAX actions, CSS classes, and shortcode names. - Prefixed the translation group sequence option and relation metadata keys.
- Added plugin homepage and author homepage metadata.
- Added a documentation link to the readme.
- Added explicit nonce validation for Translation Health filter parameters.
- Prepared the first public submission release.