Documentation: Autolanguage plugin
YOOtheme Pro Builder Support
Unlock this and other features by upgrading to Joomill Autolanguage PRO
Go PRO
How YOOtheme Pro Builder translation works
If you build your Joomla articles or pages with YOOtheme Pro's Builder, your content isn't stored as plain HTML, it's stored as JSON data embedded inside the article. A standard translation plugin would copy that JSON across as-is, leaving your text untranslated.
Autolanguage PRO handles this automatically. When translating a YOOtheme Pro page, the plugin reads the JSON structure, identifies all translatable text fields inside it, sends only those texts to your chosen translation engine, and writes the translated content back into a perfectly intact JSON structure. Your layout, styling, images and element settings stay completely unchanged, only the text is translated.
Important: YOOtheme Pro translation requires the Batch translation method. The Upon saving (Alert banner) method does not support YOOtheme Pro Builder content. Make sure Batch is selected in the plugin settings before translating YOOtheme Pro pages.
How to translate a YOOtheme Pro page
- Go to Content > Articles in your Joomla backend.
- Select one or more articles built with YOOtheme Pro.
- Click Actions > Translate in the toolbar.
- Autolanguage PRO detects the YOOtheme content and translates all supported fields automatically.
Supported YOOtheme Pro fields
The following built-in YOOtheme Pro element fields, and ZOOLanders Essential Addons fields, are currently supported for translation:
title, meta, content, image_alt, link_aria_label, link_text, tags, message, author, footer, label, home_text, scale_x_title_text, scale_y_title_text, subtitle_text, title_text, dataset_label, metadata, email_subject, email_body, shared_text, shared_url, control_name, control_error_message, text.
Need support for a third-party element?
Using a third-party YOOtheme Pro add-on or a custom element whose fields aren't being translated? Every add-on can define its own custom field names, so this is expected for anything we haven't seen yet.
Contact us with the name of the add-on and, if possible, an example of the JSON output it produces, and we'll add support for those fields in an upcoming update.