TranslatePress – Translate Multilingual sites


Experience a better way to translate your WordPress site and go multilingual, directly from the front-end using a friendly user interface.

TranslatePress is a WordPress translation plugin that anyone can use.

The interface allows you to easily translate the entire page at once, including output from shortcodes, forms and page builders. It also works out of the box with WooCommerce.

Built the WordPress way, TranslatePress – Multilingual is a GPL and self hosted translation plugin, meaning you’ll own all your translations, forever. It’s the fastest way to create a bilingual or multilingual site.

Multilingual & Translation Features

  • Translate all your website content directly from the front-end, in a friendly user interface (translation displayed in real-time).
  • Fully compatible with all themes and plugins
  • Live preview of your translated pages, as you edit your translations.
  • Image translation support, allowing you to translate images, sliders and other media.
  • Support for both manual and automatic translation (via Google Translate)
  • Ability to translate dynamic strings (gettext) added by WordPress, plugins and themes.
  • Integrates with Google Translate, allowing you to set up Automatic Translation using your own Google API key.
  • Translate larger html blocks by merging strings into translation blocks.
  • Select specific html blocks for translation using the css class translation-block. <p class="translation-block">Translate <em>everything</em> inside</p>
  • Place language switchers anywhere using shortcode [language-switcher], WP menu item or as a floating dropdown.
  • Editorial control allowing you to publish your language only when all your translations are done
  • Conditional display content shortcode based on language [trp_language language=”en_US”] English content only [/trp_language]
  • Possibility to edit gettext strings from themes and plugins from english to english, without adding another language. Basically a string-replace functionality.
  • Translation Block feature in which you can translate multiple html elements together
  • Native Gutenberg support, so you can easily translate Gutenberg blocks
  • Out of the box WooCommerce compatibility

Note: this WordPress translation plugin uses the Google Translation API to translate the strings on your site. This feature can be enabled or disabled according to your preferences.

Users with administrator rights have access to the following translate settings:

  • select default language of the website and one translation language, for bilingual sites
  • choose whether language switcher should display languages in their native names or English name
  • force custom links to open in current language
  • enable or disable url subdirectory for the default language
  • enable automatic translation via Google Translate

Powerful Translation Add-ons

TranslatePress – Multilingual has a range of premium Add-ons that allow you to extend the power of the WordPress translation plugin:

Pro Add-ons (available in the premium versions only)

  • Extra Languages – allows you to add an unlimited number of translation languages, with the possibility to publish languages later after you complete the translation
  • SEO Pack – allows you to translate meta information (like page title, description, url slug, image alt tag, Twitter and Facebook Social Graph tags & more) for boosting your multilingual SEO and increase traffic
  • Translator Accounts – create or allow existing users to translate the site without admin rights
  • Browse as User Role – view and translate content that is visible only to a particular user role
  • Navigation Based on Language – configure and display different menu items for different languages
  • Automatic User Language Detection – redirect first time visitors to their preferred language based on their browser settings or IP address
  • DeepL Automatic Translation – The DeepL Automatic Translation add-on lets you automatically translate your website through the DeepL API

Free Add-ons

Keyboard Shortcuts

  • CTRL ( ⌘ ) + S – Save translation for the currently editing strings
  • CTRL ( ⌘ ) + ALT + Z – Discard all changes for the currently editing strings
  • CTRL ( ⌘ ) + ALT + → (Right Arrow) – Navigate to next string to translate
  • CTRL ( ⌘ ) + ALT + ← (Left Arrow) – Navigate to previous string to translate



Visit TranslatePress WordPress Translation plugin documentation page



Demo Site

You can test out TranslatePress – Multilingual plugin by visiting our demo site


  • TranslatePress front-end visual translation editor in action
  • Front-end translation editor used to translate the entire page content
  • How to translate a Dynamic String (gettext) using TranslatePress - Multilingual
  • Translate WooCommerce Products using TranslatePress - Multilingual
  • Translate Images and Image Sliders
  • Settings Page for TranslatePress - Multilingual
  • Floating Language Switcher added by TranslatePress - Multilingual
  • Menu Language Switcher


  1. Upload the translatepress folder to the ‘/wp-content/plugins/’ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to Settings -> TranslatePress and choose a translation language.
  4. Open the front-end translation editor from the admin bar to translate your site.


Where are my translations stored?

All the translation are stored locally in your server’s database.

What types of content can I translate?

TranslatePress – Multilingual plugin works out of the box with WooCommerce, custom post types, complex themes and site builders, so you’ll be able to translate any type of content.

How is it different from other multilingual & translation plugins like WPML or Polylang?

TranslatePress is easier to use and more intuitive altogether. No more switching between the editor, string translation interfaces or badly translated plugins. You can now translate the full page content directly from the front-end. This makes TranslatePress a great alternative to plugins like Polylang and WPML.

How do I start to translate my WordPress site?

After installing the plugin, select your secondary language and click “Translate Site” to start translating your entire site exactly as it looks in the front-end.

Will it slow down my website?

TranslatePress will have little impact on your site speed. For more details see Top WordPress Translation Plugins Compared Based on Page Load Time

Does it work with WooCommerce?

Yes, TranslatePress works out of the box with WooCommerce. You can use it to translate WooCommerce products and build a multilingual store.

Where can I find out more information?

For more information please check out TranslatePress – Multilingual plugin documentation.


October 10, 2019
I reported an issue with my theme covernews that stops working when translatepress is activated (it was working before). the developper marked my issue as solved but it was not solved, and stopped ansering my messages also in other sites i have it is not possible to translate some strings. or the admin panel overlays some parts of the site making it impossible to translate some strings
October 4, 2019
Hello! I noticed that my product size name have change since I added your plugin. earlier the product name was for example: HUNDHALSBAND ORANGE REFLEX - XS But now it changes to: HUNDHALSBAND ORANGE REFLEX <span> - </span>XS It adds the span html code. This doesn´t show in the product view, but it shows when I try to add barcodes and when the invoice is sent with Svea Checkout and also on the order print. Would like the plugin not to mess up that, it would be great. Thanks!
October 3, 2019
Tried all popular translaters and found TranslatePress to be the best for my customer enabling him to make front-end translations in an intuitive and user friendly way. Adding my own translations on the fly from a 30,000 article catalog by adding them to the TranslatePress tables in php scripts. An unforeseen error in the customer data led to an inexplicable disturbance in some translations, but TranslatePress support were able to track this down allowing me to tighten my scripts. My compliments! P.S. base language is Dutch, translations in English and French.
October 2, 2019
I was trying to make my listingpro theme multi lingual with WPML but some option parts would just not work. I spend almost 2 nights figuring it out, reading dozens of forum threads, spend hours fixing it and finally got too frustrated and gave up. Also tried 2 other translate plugins but they were also very frustrating Now TBH I've been playing around with translatepress for just 60min but I already achieved so much more. I have no clue how the hell they are doing it because with WPML you have to edit and add so many things and with translatepress I literally spend 10 min on the front page and already got it working without issues in 2 languages.. dafuq man?! Gonna test it out a little bit more and although their premium packages is a bit on the expensive side if it keeps working as good as this I will definitely purchase the plugin.
October 1, 2019
Haven't come across another plugin that is so convenient to use, we have our site in 2 languages. Technical support was a bit slow in the beginning, but seems that they have now improved.
September 23, 2019
En Fundación Recover hemos instalado este plugin porque necesitábamos traducir nuestra web sin que fuera de forma automática y el resultado es fantástico. El precio no es muy alto y para su gran calidad. Además, el soporte técnico es rápido y totalmente personalizado. 100% recomendable!!
Read all 126 reviews

Contributors & Developers

“TranslatePress – Translate Multilingual sites” is open source software. The following people have contributed to this plugin.


“TranslatePress – Translate Multilingual sites” has been translated into 8 locales. Thank you to the translators for their contributions.

Translate “TranslatePress – Translate Multilingual sites” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Change log


  • Add an option to block crawlers from triggering automatic translations
  • Added support for excluding words from automatic translation
  • Compatibility with WooCommerce Checkout Add-Ons plugin
  • Improved integration with WooCommerce PDF Invoices & Packing Slips by translating product name and options in invoices
  • Removed possible trp-wrap tags ending up in front-end content
  • Improved display of license error messages
  • Corrected and added missing flags for 7 languages
  • Eliminate need for jQuery in language switcher shortcode
  • Fixed issue with translating admin ajax JSON strings
  • Fixed issue with html tags breaking HTML
  • Fixed warning in when saving advanced settings
  • Fixed trpst characters in WooCommerce shipping calculator
  • Fixed getting translations on fallback admin-ajax
  • New integration with Deepl API Automatic translation in PRO versions


  • Added machine translation limit
  • Added setting for translation memory limit
  • Fixed encoding for the “Fix broken html feature”
  • Fixed CSS for translate button in TP Editor
  • Fixed disabling dynamic translation in translation editor when it is disabled from Advanced option


  • Modified an autoloader to prevent errors when manually updating the plugin


  • Improved speed on Gettext exclusion
  • Make Gettext exclusion work without a domain in Advanced Settings
  • Allow po/mo localization files to translate excluded Gettext strings
  • Added Advanced setting to Exclude selectors from translation
  • Added option to change floating language switcher position
  • Added compatibility with CartFlows plugin
  • Added compatibility with NextGen plugin
  • Added compatibility with Ninja Popups plugin mails
  • Added compatibility with Woo Tours plugin
  • Fixed issue with trp-gettext wrappings in WooCommerce REST API
  • Fixed issue with translating images run through JetPack CDN
  • Fixed edge case where gettext inside script tag attributes was breaking html
  • Translated title of product in WooCommerce “Product has been added to cart” message
  • Better handling of string overdetection in dynamic string translation
  • Better handling of sql errors and machine translation
  • Fixed WooCommerce Product Translation on Cart Page for products with hyphen in their names


  • Fixed warnings regarding settings that appeared on fresh installs


  • Added Translation Memory feature
  • Beaver Builder compatibility
  • Fixed isseu with gettext special characters inside attributes breaking html sometimes
  • Fixed an issue with urls slugs not being translated in site-map for secondary languages if “Use subdirectory on default language” was on
  • Added support for display attribute for language-switcher shortcode


  • Fixed blank page when opening Translation Editor in some localized languages


  • Added -Advanced- tab with various custom settings
  • Added compatibility to allow translating SeedProd plugin Coming Soon page


  • Added maximum possible size to srcset for translated images
  • Added compatibility with Query Monitor plugin
  • Better handling of licenses when pro addons are active
  • Improved descriptions in settings page and other places
  • Added filter to allow translation of href as an exception
  • Fixed translation blocks not working on live in some edge cases
  • Fixed translation block created in secondary language not working when strings were already translated
  • Fixed JS error when dynamic translation is disabled by filter
  • Fixed translating dynamic strings in Editor when viewing as Logged out
  • Fixed page titles containing special characters not being translated
  • Fixed title attribute not being translated
  • Fixed certain custom WooCommerce permalinks not working on translated products
  • Fixed pencil icon not showing for WooCommerce product images in Shop page on certain themes
  • Fixed modifying wp_mail headers when we didn’t have to


  • Fixed some dynamic images not showing up in translated pages.


  • Fixed incompatibility with custom code for changing flags
  • Fixed some pages not being translated due to incorrectly encoded character
  • Fixed some images missing when automatic translation is on


  • Added support for translating images
  • Added support for translating title attribute
  • Added support for translating href pointing to internal files and href pointing to any external links
  • Added support for translating attributes modified dynamically through JS
  • Added support for translating multiple attributes on the same node
  • Added support for translating nodes containing mixt of gettext and user-inputted strings
  • Added notification and disabled TP for servers not running minimum PHP version 5.6.20
  • Refactored and improved Translation Editor user interface
  • Added Keyboard shortcuts: CTRL + S (save), CTRL + ALT + Z (discard all changes), CTRL + ALT + LEFT (previous string), CTRL + ALT + RIGHT (next string)
  • Fixed issues with translation blocks not working on some instances
  • Security improvements


  • Fixed a php error in previous commit


  • Fixed a js compatibility error with mootools.js
  • Modified how the license page works and added plugin notifications
  • Allow compatibility fix for Translation Editor on certain environments
  • Fixed Safari bug with links when WooCommerce active


  • Performance improvements
  • Fixed an issue that was causing empty strings to get inserted in the database
  • Improvements to detecting dynamic js strings earlier
  • Fixes some urls for sitemap
  • We now check if str_get_html is successful to avoid fatal error
  • Fixed regular string loaded by ajax not detected in translation editor
  • We now allow translating WooCommerce product base name separately from selected variations
  • Fixed WooCommerce cart details not being translated when changing language
  • Fixed Automatic Google Translation on languages not published yet
  • Fixed Translation Editor not working in default language when no translation language is published yet
  • Fixed gettext wrapping characters showing up in WooCommerce Shipping taxes metabox on Order pages


  • Added more filters
  • Make sure we do not insert empty strings in the gettext translation table
  • Added support for Affiliate tracking


  • Fixed an issue with the Language by Get Parameter add-on
  • Added compatibility with WooCommerce PDF invoice and WooCommerce’s order notes.
  • Added stop_translating_page and before_running_hooks hooks.
  • Refactored hooks-loader to easily remove hook


  • Fixes the issue with not being able to publish pages when Use subdirectory for default language is set to yes and Gutenberg is installed
  • Fixed an issue with Elementor and Use subdirectory for default language set to yes
  • Fixed an issue with Yoast Premium and Use subdirectory for default language set to yes
  • Fixed missing spaces in translations for original gettext strings with untrimmed spaces


  • Added PHP 7.3 support
  • Performance improvements


  • Added Enfold compatibility by increasing the template_include hook priority
  • Add the costa rica flag
  • Speed improvements by optimizing the full_trim function
  • Added compatibility for WooCommerce Invoices plugins
  • Fixed querying for dynamic strings in Translation Editor not bringing up translations for all languages
  • Fixed notice when gettext table is empty
  • Added function to display strings with bad encoding in Translation Editor


  • Fixed some issues with url translations
  • Speed improvements
  • Add Javanese flag
  • Fixed issue with trimming dynamic strings in our own ajax calls


  • Speed improvements
  • Remove notices from Editor when we don’t have translation languages
  • Fixed notices with referrer in translator machine
  • Fixed issues with urls in other languages
  • Fix issue of nested gettext resulting in unwanted characters
  • Strip gettext tags from urls run through sanitize_title and esc_url
  • Set caching calls non-persistent. Doesn’t work with object caching otherwise
  • Set lang attribute in html tag all the time including when on default language
  • Refactored the way we translate json
  • Fixed issue with Woocommerce ajax calls


  • Fixed an issue with Woocommerce and redirects when the default language is not English
  • Speed improvements
  • Fix relative url without a trailingslash not getting a proper link back
  • Add ?trp=edit-translation=preview to ajax loaded content. Also add it to all dynamic content.
  • Added language code column in settings
  • Removed async false from JS translate-dom-changes


  • Refactored the get_url_for_language() function which should fix a lot of problems with links
  • Speed improvements
  • Fixed translation block icon when creating a new block
  • Fixed issues with trp tags leftovers in html
  • Fixed issues with gettext strings that weren’t detected correctly
  • Add support for relative url’s
  • Added warning in settings about controlling costs of Google API
  • Changed API key field description. Added feature to show/hide API key field based on Google Translate Active Yes/No
  • Fixed Translated-dom-changes string not translated through trp-ajax.
  • Fixed 400 errors in google translate API


  • Fixed translation problems introduced in the last two versions
  • Added a console message when trp-ajax request uses fall back to admin ajax for debugging purposes.


  • Fixed issue with options in select tag that couldn’t be translated
  • Fixed force language in custom links
  • Fixed Woocommerce links fpr products or categories that were added by the user manually in a page
  • Added Settings link to the list of links displayed on Plugins page
  • Fixed issue with Kazakhstan flag


  • Fixed issue with Woocommerce ajax strings that were broken in editor on default language in some cases
  • Speed improvements


  • Speed improvements
  • Add support for the Ginger – EU Cookie Law plugin
  • Add support for data-no-dynamic-translation attribute that skips dynamic strings from being translated by dom changes detector
  • Fixed Edit Pencil icon css in Translation Editor for some sites
  • Refactored the way we add trp-gettext tag. This should have a lot of benefits in compatibility with other plugins
  • Optimized block translation detection
  • Added caching to trp_x function when reading external .mo files
  • Fixed issue with translatepress icon css that was broken on wpforms forms
  • Added secret page for removing duplicate rows from database: wp-admin/admin.php?page=trp_remove_duplicate_rows


  • Fixed Woocommerce translation of permalinks
  • Added support for remove_accents to be based on default language when called from the sanitize_title function
  • Added support for translating JSON found in custom ajax request
  • Added better REST compatibility
  • Added compatibility for Peepso plugin
  • Fixed TranslatePress roken link to google translate set up api key on settings page
  • Corrected flags for Arabic and Bengali languages
  • Fixed issue with multiple slashes being added when the URL had extra get parameters


  • Added support for word trim when the default language is japanese, chinese or thai.
  • Exluded wp_trim_words funtion from our gettext filter to prevent som issues
  • Fixed an issue with gettext inside attributes that passed through the wp_kses function.
  • Fixed issues with the Customizer
  • Added padding to the language switcher image so we don’t conflict with themes that add extra padding to images inside links
  • We no longer remove \r \n \t from the translation
  • Fixed issue with title attribute that contained html
  • Added a filter to all href attributes detected on our translation page
  • Added a notice to inform admins of the missing mbstring php library
  • We now send all error logs to debug.log
  • Added cite and blockquote as top_parents for merge rule on Translation blocks
  • Fixed nonce accidentally being passed through internationalized function


  • Rearranged and renamed some languages in the options dropdown
  • Fixed flag of Khmer language
  • Added Automatic Language Detection notice and included it on add-ons page
  • Fixed an issue with WooCommerce checkout and Stripe Gateway
  • Fixed issues with some improper responses from the WP Remote API functions
  • Fixed minor issues with ajax


  • Added a lot of hooks in the translation manager interface so other people can insert new content there.
  • We now take into account the presence of www or lack of it in custom links that might be local
  • We now make sure we’re not changing the locale in the backend if the language order is different.
  • Fixed issue with incorrect language adding in the backend that caused notices in the front-end
  • Removed obsolete function add_cookie
  • Fixed trailingslashit over get_permalink in url-converter
  • Removed adding cookie from php. Fixed enqueue_styles on license and add-ons tabs. Removed deprecated function.


  • Added a warning when changing the default language that it will invalidate their existing translations
  • Fixed incorrect detection of the form action language parameter
  • Improved compatibility with themes and plugins that use object buffering
  • Fixed some issues with image urls


  • Refactored determining language, redirecting and cookie adding
  • Removed leftover trp-gettext tags when WooCommerce is active on some pages
  • Fixed get_url_for_language function that was having problems in some cases.


  • Fixed DOM changes script not being enqueued anymore


  • Refactor the shortcode language switcher so it’s now HTML similar to the floater
  • Added link to Appearance -> menus in TranslatePress settings page
  • Fixed language redirect with permalinks so custom parameters are passed correctly back to the url
  • Do not load dynamic string translation for IE11 and older


  • Fixed back-end css style not being targeted only for TranslatePress Settings page
  • Add filter to not remove detected dynamic strings until the ajax is finished
  • Fixed data-no-translation not taken into account in some cases of Dynamic strings
  • Fixed translated slug not being included in url sometimes
  • Fixed issue with gettext string on non visible html attr that prevented other attr from being translated
  • Fixed bug with translating dom changes not working for complex HTML hierarchy
  • Corrected flag for Afrikaans.
  • Fixed compatibility issues with older jQuery versions


  • Added Translation Block feature in which you can translate multiple html elements together
  • Improvement: make it possible for the SEO Addon to automatically translate page slugs using Google Translate
  • Fix: using the shortcode language switcher added #trpprocessurl to the end of the url
  • Fix: changing languages from a secondary language gave 404 page when the page slug was translated
  • Fix: submitting a form from one page to another directed the user to the default language. Now if Force Custom Language Links is enabled the user gets directed to the correct url


  • Extra css for the floater images so they don’t brake the line in certain themes
  • Fixed compatibility issue with Woocommerce cart widget
  • Fix: use the siteurl when the homeurl is empty to detect the language


  • Fix wptexturize changing characters in secondary languages
  • Mini refactoring of the url_is_file() function
  • Refactor get_url_for_language() to not use the global var
  • We no longer add the language path to links to actual files on the server


  • Fix widget language switcher to take into account the new hreflang


  • Fixed bug with Strings List appearing also in Dynamic Strings List. Also fixed bug with duplicate dynamic strings not having a pencil icon because of missing jquery_object.
  • Fixed Woocommerce session storage compatibility
  • Fixed language floater not opening on iPhone.
  • Fixed issue with normal text nodes that were inside an element that had an atribute with gettext and did not get translated
  • Replaced _ with – in hreflang and filter it
  • Make force language to custom links set to yes as a default
  • Remove intensive functions from inside two loops so they only happen once we detect something in js
  • Decode html characters in mutation observed strings and removed stripslashes from trp-ajax.php to fix some strings added with js not being translated


  • Compatibility fix with Elementor Page Builder
  • Added translation .pot file
  • Add proper encoding for mysqli connection in our trp-ajax.php file so we fixed some translation
  • Fixed infinite loop related to mutation observer on javascript strings by not re-adding detected strings again if they are similar to existing ones
  • Aligned text from add-ons tab.


  • Added support for translating Contact Form 7 alert messages
  • Fixed issue with some strings containing special characters not being translated (i.e. “¿¡”)
  • Fixed bug with switching languages in Editor when viewing as Logged out
  • Fixed issue with broken homepage links in some themes
  • Added support for RTL languages in translation editor


  • Added support for translation blocks using the css class .translation-block.
  • Added possibility to choose a different language as default language seen by website visitors.
  • Updated add-ons settings page with the missing add-ons, added Language by GET parameter addon
  • Fixed issue with the [language-switcher] in a post or page that broke saving the page when Yoast SEO plugin is active
  • Added a plugin notification class and a notification for pretty permalinks
  • Added WooCommerce compatibility tag
  • Small css improvements


  • Filter to allow adding new language: ‘trp_wp_languages’
  • Fixed issue with get_permalink() in ajax calls that was not returning the propper language
  • Adapted code to allow language based on a GET parameter
  • Fix some issues with language switcher and custom queries as well as take into account if subdirectory for default language is on
  • Fixed issue with js translation that was trimming numbers and other characters from strings when it shouldn’t


  • Fix issue where the language switcher didn’t work for BuddyPress pages
  • Fixed issue with CDATA in post content that was breaking the translation
  • Added a filter that can be activated and that tries to fix invalid html: trp_try_fixing_invalid_html


  • We now make sure that all forms when submitted redirect to the correct language
  • Fixed an issue with missing slash from language switcher
  • Fixed an issue where we were not redirecting to the correct url slug when switching languages
  • Fixed a possible notice inside the get_language_names function
  • Fixed html breaking because of unescaped quotes in translated meta content
  • Removed a special character from the full_trim function that was causing some strings to not be selectable for translation


  • Fixed js error with startsWith method not being supported in IE
  • Removed unnecessary files from select2 lib
  • Improved the way we rewrite urls to remove certain bugs


  • Implemented View As “Logged out user” functionality so you can translate strings that show only for logged out users
  • Allow slug edit for default language
  • Fixed an issue with the dropdown of translation strings when there were unsaved changes and the dropdown disconected from the textarea
  • Prevent translate editor icon pencil to exit the translation iframe
  • Fixed translating via the next/prev buttons that reset the position in the translation string list
  • Refactor the way we are generating the language url for the language switcher when we don’t have a variable available


  • We now flush permalinks when saving the settings page to avoid getting 404 and 500 errors
  • Added the current language as a class on the body tag. Ex: translatepress-en_US
  • Small readme changes


  • We now allow HTML in normal strings translations.
  • Changed the way we get the default language permalinks in Woocommerce rewrites
  • Fixed issues with date_i18n function
  • Fixed a warning generated when there are no rewrite rules
  • Fixed dynamic strings not updating the translation dropdown list.
  • Fixed issues with hidden space characters that were breaking some translations
  • Make sure we don’t loose the trp-edit-translation=preview from url after a WordPress redirect


  • Fixed a small bug in js regarding the translation editor sidebar with
  • Fixed Language Switcher for Woocommerce product categories and product tags going to 404 pages
  • Fixed issues with Woocommerce and permalinks when the default language was not english
  • Excluded more functions from getting gettext wraps


  • Added filter on capabilities to allow other roles to edit translations:’trp_translating_capability’
  • Don’t show php errors and notices when we are storing strings in the database
  • Fixed issues with attributes that contain json content, for instance in woocommerce variations
  • We no longer wrap gettext inside the wptexturize function
  • We no longer wrap gettexts that appear in the bloginfo function


  • Added possibility to edit gettext strings from themes and plugins from english to english, without adding another language. Basically, string-replace functionality.
  • We now can translate text input placeholders
  • We have a way of translating emails using the conditional language shortcode [trp_language language=”en_US”] English only content [/trp_language]
  • Fixed issues with some elements that contained new lines and \u00a0 at the start of the strings


  • Fixed issues with the pencil select icon in the translation editor not showing up in certain cases on the button element
  • Fixed issues with the pencil select icon in the translation editor not showing up in certain cases because of overflow hidden
  • Fixed a issue that was sometimes causing javascript errors with certain plugins


  • Added a conditional language shortcode: [trp_language language=”en_US”] English only content [/trp_language]
  • Create link to test out Google API key.
  • Improvements to Woocommerce compatibility
  • Fixed json_encode error that was causing js errors
  • Changed ‘template_include’ hook priority to improve compatibility with some themes


  • Translation interface improvements
  • Fixed issues with strings loaded with ajax
  • Added an addon page
  • Fixed bug with gettext node accidentally wrapping another string too.


  • Fixed incorrect blog prefix name for Multisite subsites on admin_bar gettext hook.
  • Fixed Translate Page admin bar button sometimes not having the correct url for entering TP Editor Mode
  • Skipped dynamic strings that have only numbers and special characters.
  • Fixed order of categories in Editor dropdown. (Meta Information, String List..)
  • Fixed JS error Uncaught Error: Syntax error, unrecognized expression


  • Initial release.