Supertext Translation and Proofreading

April 18, 2024

Supertext Translation and Proofreading Plugin

This plugin allows you to order human translations for your pages and posts using Supertexts professional translation services.

This plugin allows the user to send a WordPress post or page to Supertext for translation or proofreading.

Process for translation

Supertext can translate content, titles, excerpts, image captions, shortcode arguments and custom fields. Simply order a translation instead of creating a new page.
You will be presented with services, prices and deadlines. Select the right one for you.
Once completed, the translation will be automatically inserted into a new page or post in your WordPress installation.
You’ll be notified by email once your translated content has been uploaded to your website.
This works for every post type that is translatable by Polylang or WPML.

Process for proofreading

For proofreading your existing page or post, select the option “order proofread”. You will be presented with services, prices and deadlines.
Select the right one for you. Once completed, the proofread text will automatically be inserted into your post or page in your WordPress installation.

Please note

Translatable custom fields must be defined in the settings. Supported plugins at the moment are:

  • Advanced Custom Fields
  • Yoast SEO
  • All In One SEO pack

If the field is not available in one of the lists, you can define it by adding self defined custom fields.

The plugin supports following page builders:

  • Visual Composer
  • Beaver Builder
  • BE page builder
  • Divi page builder
  • SiteOrigin page builder
  • Elementor

We highly recommend to test the translation process for the page builders mentioned above and for any other that you may use.

Installation

How to install the plugin

  1. Upload polylang-supertext to the /wp-content/plugins/ directory.
  2. Activate the plugin through the “Plugins” menu in WordPress.
  3. Go to Settings > Supertext to provide API keys and language mappings. If relevant, define translatable custom fields and shortcode arguments.

Screenshots

  1. Just order your translation using the <em>Order translation</em> link instead of creating the new content yourself

    Just order your translation using the Order translation link instead of creating the new content yourself

  2. First order step for one post where you can select the content to be translated and the target language

    First order step for one post where you can select the content to be translated and the target language

  3. You need to order more than one post? Just use the bulk action <em>Order translation</em>

    You need to order more than one post? Just use the bulk action Order translation

  4. First order step for multiple posts where you can select the content to be translated and the target language

    First order step for multiple posts where you can select the content to be translated and the target language

  5. Second order step where you can select the service and deadline

    Second order step where you can select the service and deadline

  6. Order confirmation

    Order confirmation

FAQ

What do I require to use this plugin?

A valid Supertext customer account for every WordPress user and the corresponding API key.
You can create an account at Supertext if you don’t already have one.
Get the API key from the Settings page: Account Settings

How do I order a translation?

  1. Go to the post you would like to be translated by Supertext.
  2. Click on Order translation underneath the target language.
  3. Select the content you want to be translated.
  4. Select the service you want from the prices and deadlines presented. Supertext will translate your post and notify you once the translation has been uploaded to your website.

How do I order a proofreading?

  1. Go to the post you would like to be proofread by Supertext.
  2. Click on Order proofread underneath the section Proofreading.
  3. Select the content you want to be proofread.
  4. Select the service you want from the prices and deadlines presented. Supertext will proofread your post and notify you once the proofreading has been uploaded to your website.

How do I order multiple translation?

  1. Go to the post overview and select the posts you would like to be translated by Supertext.
  2. Select the Order translation bulk action and click on Apply.
  3. Select the content you want to be translated and the target language.
  4. Select the service you want from the prices and deadlines presented. Supertext will translate your post and notify you once the translation has been uploaded to your website.

How to translate the site title and tagline?

The site title and the tagline are part of the general settings of your WordPress. You can translate these texts using the String translations feature of Polylang/WPML:
Languages -> Strings translations

Did you translate the site title but it is still displayed in only one language? In this case you can check if the themes header is using the correct WordPress functions to get the title/tagline (wp_title() or get_bloginfo()).

How can I order a translation for image texts only?

  1. Go to the media library (Media->Library).
  2. Select the images you want to order.
  3. Select Order translation from the Bulk Actions drop down.
  4. Click on Apply next to the drop down.
  5. And follow the order process steps.

Changelog

4.24

  • Remove unused sync feature

4.23

  • Add additional filters and actions to allow other plugins to hook into when the translation is written back (sttr_post_meta_translation for applying filter on translated post meta value, sttr_writeback_target_content for applying filter on target content, sttr_finish_target_post_writeback for running action after the target post write back)

4.22

  • Allow service type IDs greater than 5 in the settings

4.21

  • Extend shortcode settings with option to deactivate shortcode replacement

4.20

  • Enhance shortcode settings to allow inversion of encoding/decoding enclosed content

4.19

  • Exclude shortcode replacement in html comments

4.18

  • Check for Divi Builder using ET_CORE_VERSION so that it works for Divi from theme

4.17

  • Fix version issue

4.16

  • Fix issue that prevented the write back of media texts
  • Use staging environment for testing

4.15

  • Fix shortcode replacement bug when no shortcodes are present

4.14

  • Fix bug when ACF block attributes contained Shortcodes
  • Enhance content selection to make sure the post content is sent for translation when ACF blocks are selected for translation

4.13

  • Add support for ACF 6 (Blocks)

4.12

  • Enable bulk action for proofreading when no multilang plugin is installed or activated
  • Improved warning/error messages

4.11

  • Skip checking for translated post IDs for proofreading orders

4.10

  • Use WordPress standard functions to serialize Gutenberg blocks.

4.09

  • Add basic support for ACF Gutenberg blocks that contain text in the data object.

4.08

  • Suppress warnings generated by DOMDocument::loadHTML()
  • Fix ordering bug when blog name is longer than 50 characters

4.07

  • Fixed fallback copy logic of post meta data when WPML is used but the translation management plugin is not activated
  • Extended ACF support with possibility to copy ACF structural meta data like flexible content structure over to the translation post

4.06

  • Fix bug with Custom vs. Elementor settings that saved the entered custom fields as Elementor field

4.05

  • Expose startTranslationOrderProcess and startProofreadOrderProcess on Supertext.Interface to be able to start either of the two order processes

4.04

  • Expose startOrderProcess on Supertext.Interface so that it can be called outside the JS module with the post IDs (e.g. Supertext.Interface.startOrderProcess([1005, 1032]))

4.03

  • Extended Elementor extention to also support custom element settings and not only the ones from the free plugin version

4.02

  • Introduced blind copy feature for post meta data when WPML is used
  • Removed workaround for copying none translatable ACF fields since this is not needed with the WPML translation management feature and its meta data copying settings/feature

4.01

  • Fixed JavaScript bug in minified admin extension script

4.00

  • Enhanced proofreading feature
  • Added missing translations
  • Restructured folders and namespaces
  • Fixed saving of meta data to target post when writing back
  • Various code improvements

3.22

  • Fixed language mapping bug that prevented writing translations back

3.21

  • Added manual write back feature

3.20

  • Fixed bug that prevented ordering posts while WPML Translation Management plugin is active

3.19

  • Fixed ordering multiple posts with WPML
  • Fixed bug that prevented writing back the translation for WPML orders because an invalid reference key

3.18

  • Added support for WPML

3.17

  • Switched to new order API version 1.1

3.16

  • Added support for block attributes

3.15

  • Fixed Elementor page builder bugs

3.14

  • Added support for Elementor
  • Fixed enqueuing block editor script on block editor page only

3.13

  • Fixed order links for new Polylang block editor sidebar
  • Upgraded npm dependencies for gulp

3.12

  • Fixed ACF plugin bug when writing back

3.11

  • Fixed image alternative text bug
  • Fixed target post creation with latest Polylang
  • Various client assets improvements

3.10

  • Fixed comment issue
  • Enhanced sent order title and information

3.9

  • Added support for media translation
  • Fixed ACF tab support

3.8

  • Optimized tab initialisation (and with this change fixed issue when adding a new field to flexible content layout, ACF bug)
  • Changed acf settings structure

3.7

  • Added support for ACF flexible content
  • Removed deprecated code
  • Changed content selection layout (first order step)

3.6

  • Fixed taxonomy text accessor bug
  • Added service type setting

3.5

  • Added support for WooCommerce product categories and tags

3.4

  • Fixed post creation bug
  • Various code improvements

3.3

  • Added support for WooCommerce
  • Fixed write back bug
  • Various code improvements

3.2

  • Added support for PHP 7.1
  • Various code improvements

3.1

  • Fixed ACF content accessor to support accordions
  • Various code improvements

3.0

  • Extended settings page to add default settings
  • Allow the use of the plugin even though not all languages are supported
  • Enhanced write back errors
  • Various code improvements

2.9

  • Fixed migration issue
  • Added new/missing texts

2.8

  • Added new feature to send translation changes back to Supertext
  • Added support for multisite
  • Added new default shortcode and custom fields settings
  • Various code improvements and fixes

2.7

  • Extended shortcode replacement
  • Added support for Divi page builder

2.6

  • Fixed GitHub issue 2 – replaced callback url used for writing translations back with ajax admin url
  • Clean database options on uninstall
  • Added support for Beaver Builder standard version

2.5

  • Corrected language mapping with Supertext API
  • Extended content step
  • Various code improvements and fixes

2.4

  • Added shortcode replacement support for PHP with object context bug
  • Extended order creation request with additional plugin information
  • Added german formal language file
  • Added content accessors (for translation of categories and tags)

2.3

  • Added new translations
  • Added support for Polylang Pro
  • Extended order item list
  • Extended plugin activation with adding defaults settings depending on installed plugins

2.2

  • Fixed plugin defined content accessor

2.1

  • Added support for BE page builder
  • Made API url configurable
  • Added support for Salient Visual Composer
  • Various code improvements and fixes

2.0

  • Extended plugin to be able to order multiple posts/pages
  • Changed order process
  • Introduced Gulp for minification of JavaScript and SASS files
  • Various code improvements

1.9

  • Added support for Visual Composer
  • Extended Beaver Builder support with shortcode replacement
  • Extended post creation for translation post
  • Various code improvements

1.8

  • Added support for Beaver Builder
  • Extended custom field settings page (with possibility to add own defined custom fields)
  • Various code improvements

1.7

  • Changed layout of translation status column in posts tables
  • Fixed minor ACF bug

1.6

  • Added ability to define shortcode attribute encodings
  • Enhanced callback error handling
  • Extended callback to return appropriate http response codes
  • Enhanced token generation and validation
  • Added new setting to automatically publish translations and allow Supertext to override published content

1.5

  • Added new translation
  • Enhanced error messages and handling
  • Extended Shortcode replacement

1.4

  • Settings and support for Custom Fields
  • Added support for re-translation
  • Post creation without redirect to page-new.php
  • Added translation status column on manage posts tables
  • Fixed encoding when replacing Shortcodes
  • Various code improvements

1.3

  • Settings and support for Shortcodes
  • Text and UI changes
  • Various code improvements

1.2

  • Better user information when the translation is created
  • Logging all communication with Supertext and display it in the article sidebar
  • Always show a translation status and order number in “to be translated” articles
  • Detailed and translated language information on offer page
  • Removed order confirm question

1.1

  • Switched to english, changed german translation
  • Minor text and UI fixes
  • Various small UI improvements

1.0

  • Initial, german only version of the plugin

Details

  • Version: 4.24
  • Active installations: 60
  • WordPress Version: 4.0
  • Tested up to: 6.4.5

Ratings


5 Stars
4 Stars
3 Stars
2 Stars
1 Stars