描述
MobiDevices Slug Translate creates clean English slugs for post, page, and media URLs in multilingual WordPress sites. It can translate non-ASCII text, including Cyrillic, and supported Latin-language content into English before WordPress saves the slug.
Developed by the team behind MobiDevices.com.
To use automatic translation, install and activate the plugin, sign up for Langbly, create or copy an API key in your Langbly account, and save the key in Settings => MobiDevices Slug Translate. If no key is saved or the translation service is unavailable, the plugin falls back to local transliteration.
Key features:
- Translates post and page slugs when WordPress saves them.
- Translates media file names on upload when translation is needed.
- Keeps clean ASCII slugs and file names unchanged.
- The admin interface is localized for English, Russian, Ukrainian, Spanish, French, German, Italian, Portuguese, and Polish.
External Services
This plugin connects to the Langbly translation service to translate post slugs and media file names. An account and API key are required for automatic translation.
This service is used only when:
- WordPress saves a post or page slug that needs translation;
- WordPress requests a Classic Editor sample permalink for a slug that needs translation;
- a media file name needs translation during upload;
- you use the key test button in the plugin settings.
The plugin sends:
- the text to translate, such as a post title, slug text, or media file name;
- the target language code, and the source language when the site locale is used for supported plain-Latin text;
- the saved API key in the request headers.
安装
- In WordPress, go to Plugins => Add New, install MobiDevices Slug Translate, and activate it. For manual installation, upload or copy the plugin folder to /wp-content/plugins/, then activate it from the Plugins screen.
- Sign up for Langbly.
- In your account dashboard, create or copy an API key from the API keys or credentials section.
- In WordPress, go to Settings => MobiDevices Slug Translate.
- Paste the API key into the settings field.
- Use the key test button if needed, then save the settings.
- Create or update content, or upload media files. The plugin will translate slugs and file names when needed.
常见问题
-
When does translation run?
-
Translation runs when WordPress saves a post or page slug, when the Classic Editor requests a sample permalink, or when a media file is uploaded. Clean ASCII slugs and file names are left unchanged.
-
Where can I get an API key?
-
Sign up at https://langbly.com/signup. After registration, open your account dashboard, find the API keys or credentials section, and create or copy an API key. Save that key in the plugin settings to enable automatic translation.
-
Where are the plugin settings?
-
The plugin settings are available in the WordPress admin area under Settings => MobiDevices Slug Translate.
-
Will already-English slugs be translated?
-
No. If the slug or file name is already a clean ASCII value such as hello-world, the plugin keeps it as-is.
-
Can the plugin translate Latin-based languages too?
-
Yes. For text with language-specific characters, the translation service auto-detects the source language. For plain Latin text, the plugin uses the site locale for Spanish, French, German, Italian, Portuguese, and Polish.
-
Translation is not working
-
Make sure the plugin is installed, activated, and has a saved API key. If the key test fails, check that the key is correct and that your account can still use the translation service. Other transliteration plugins can also change slugs, so disable them if results are unexpected.
评价
贡献者及开发者
更新日志
1.0.1
Fixed media file names with underscores being changed during upload and clarified setup instructions.
1.0.0
Renamed the plugin to MobiDevices Slug Translate.
5.4
Migrated to the Langbly API and added localized admin interface strings.
5.3
Performance improvements.
5.2
Added a separate settings page for the API key.
5.1
Documentation fixes.
5.0
Optimized the codebase and fixed block editor behavior.
4.1
Code optimization.
4.0
Reworked the translation algorithm and improved performance.
3.5
Algorithm changes.
3.2.5
Performance improvements.
3.1.5
Added WordPress 4.1 support and reduced server load.
3.1.3
Minor fixes.
3.1.1
General performance improvements.
3.1
Added URL translation support for XML-RPC publishing.
3.0
Added support for translating slugs from any language.
2.8
Removed URL prepositions that do not help SEO.
2.5
Added media filename translation and improved performance.
2.1.1
Minor fixes.
2.1
Added media filename transliteration support.
2.0
Optimized the codebase and improved performance by 150%.
1.0
Initial release.