Skildring

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.

Use cases

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.

Skjermbilete

Network settings with enabled post types and site locale mapping.
Posts and pages list with Language and Relations data.
Translation Health audit summary and issue filters.
Repair Tools preview and apply flow.
Frontend language switcher and hreflang output.

Installasjon

Upload the multisite-translation-relations folder 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.

The plugin requires WordPress Multisite. On single-site installs it shows an admin notice and does not boot relation features.

Vanlege spm.

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.

Omtalar

There are no reviews for this plugin.

Bidragsytarar og utviklarar

“Multisite Translation Relations” is open source software. The following people have contributed to this plugin.

mudosdigital

Omset “Multisite Translation Relations” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.

Endringslogg

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.

1.0.3

Moved admin column CSS into the registered admin stylesheet and enqueue flow.
Replaced the short mmr code prefix with the longer mstr prefix 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.

1.0.2

Added plugin homepage and author homepage metadata.
Added a documentation link to the readme.

1.0.1

Added explicit nonce validation for Translation Health filter parameters.

1.0.0

Prepared the first public submission release.

Skildring

Features

Use cases

Skjermbilete

Installasjon

Vanlege spm.

Does uninstalling the plugin remove translation metadata?

Does every post or page need a translation group?

Are draft translations shown to visitors or search engines?

Can the repair tool overwrite existing language metadata?