Developed by: qTranslate Team based on original code by Qian Qin Contributors: johnclause, chineseleper, Vavooon, grafcom Tags: multilingual, language, multi-language, multilanguage, bilingual, Polyglot, admin, tinymce, widget, switcher, i18n, l10n, professional, human, translation, service, WPML, WPGlobus, Polylang, Ceceppa Multilingua, qTranslate, zTranslate, mqTranslate, qTranslate Plus Requires at least: 3.9 Tested up to: 4.5 Stable tag: 3.4.6.5 License: GPLv3 or later Donate link: https://qtranslatexteam.wordpress.com/donations/ License URI: http://www.gnu.org/licenses/gpl-3.0.html

Adds a user-friendly multilingual dynamic content management.

The plugin offers a way to maintain dynamic multilingual content on a WordPress site. While static localization is already excellently implemented and offered by WordPress framework through po/mo file framework, it is still impossible to maintain dynamic multilingual content without an additional specialized plugin, a kind of which qTranslate-X belongs to. For example, what if you need to make title, content and excerpt of a page to be multilingual? In theory, it could be handled by po/mo files, but in an insanely inconvenient way.

To deal with dynamic content, qTranslate-X provides language switching buttons on applicable admin editing pages, which, once pressed, make all the text of multilingual fields to be filled with the language chosen. The instant language change happens locally in your browser without sending an additional request to the server, which makes it most convenient for bi-lingual or few-lingual sites, for example, owners of which perform the translation of content on their own. qTranslate-X does not provide a way to translate static strings, assuming that this part is already implemented and handled by the WordPress localization framework.

The plugin provides a way to designate which fields on a page or post are to be multilingual. Once a field is declared multilingual, it will be distinguishably highlighted (in a customizable way) on admin side. Pressing one of the Language Switching Buttons (LSB) will change the value of mutlilingual fields allowing to input and edit edit different values for each language. Note, that only the fields configured to be multilingual respond to LSB, while regular fields are not affected and keep the same value for each language. At frontend, the value of active language, as defined by a page viewer, is extracted from multilingual field to be displayed within HTML context. Thus, a concept of multilingual field is in use here, as opposite to a concept of whole separate page or separate site for each language, as it is done in a number of other multilingual content management plugins, see for example, free Polylang or paid WPML. Each plugin has its own pros and cons, please, choose carefully the one which suits your needs the best.

Plugin qTranslate-X provides a convenient way to describe which fields need to be multilingual through a JSON-encoded configuration file as described in Integration Guide. It makes it easy to integrate your theme or other plugins with qTranslate-X. A JSON-encoded file, named i18n-config.json, such as the one used by qTranslate-X itself, may be provided by themes and plugins within their distribution. Plugin qTranslate-X picks up and load those configuration files on activation of a plugin or on the switch of a theme. Such a configuration file can potentially be employed by any other multilingual plugin. The developers are encouraged to contact us to discuss a common standard for the i18n-config.json configuration file.

The plugin does not currently offer any kind of translation services. The team has conducted an online survey to find out how people translate their content. You are welcome to make your entry too. It appears so far, that translation service is not an immediate need. Administrators normally have their ways to translate the content, but they need a convenient way to enter translated content into an appropriate place, which this plugin is designed to help for. Translation services might still be provided in the future releases as a paid feature.

Plugin qTranslate-X makes creation of multilingual content as easy as working with a single language. Here are some features:

• One-click local switching between the languages - Changing the language as easy as switching between Visual and HTML.
• Comes with a number of languages already built-in - English, German, Simplified Chinese, for example, and many more.
• Language customizations without changing the .po/mo files - It stores all the translations in the same post fields, while shows it to user for editing one by one depending on the language to edit chosen.
• In-line syntax '[:en]English Text[:de]Deutsch[:]' or '<!--:en-->English Text<!--:--><!--:de-->Deutsch<!--:-->' for theme-custom fields gets them translated - See FAQ for more information.
• Language tag encoding allows strings like this '[:en]English Text[:]<html-language-neutral-code>[:de]Deutsch[:]<another-html-language-neutral-code>', with language-neutral text embedded.
• Multilingual dates out of the box - translates dates and time for you.
• Theme custom fields can be configured to be translatable too.
• Choose one of a few modes to make your URLs look pretty and SEO-friendly, for example, the simple and beautiful /en/foo/, or nice and neat en.yoursite.com, or everywhere compatible ?lang=en.
• One language for each URL - Users and SEO will thank you for not mixing multilingual content.
• qTranslate-X supports unlimited number of languages, which can be easily added/modified/deleted via a comfortable Configuration Page at Settings->Languages.
• Custom CSS for "qTranslate Language Chooser" widget configurable via its properties.
• Menu item "Language Switcher" to enable language choosing from a menu.
• To generate language-specific sitemaps for better SEO support, use Google XML Sitemaps or 'XML Sitemaps' under Yoast SEO. Please, report a successful use of other sitemap plugins.

The website qTranslate-X explained provides and keeps updated a few useful listings:

• The list of plugins, which provide integration of qTranslate-X with other popular plugins.
• The list of some plugins reported to be compatible with qTranslate-X without an additional integrating plugin.
• The list of some plugins reported not to be currently compatible with qTranslate-X.
• The list of Know Issues.

If you encounter a conflicting plugin, please let us know, and meanwhile try to use other plugin of similar functionality, if possible.

This plugin has started as a descendant of qTranslate, which has apparently been abandoned by the original author, Qian Qin. At this point, qTranslate-X has many new features and hardly resembles its ancestor. Neither it is a straightforward compatible with older plugin. One will need to carefully read Migration Guide in order to switch a site from old qTranslate to qTranslate-X.

You may still find some useful information through reading qTranslate's original documentation, which is not duplicated here in full. There are also other plugins, which offer multilingual support, but it seems that Qian Qin has a very good original back-end design, and many people have been pleasantly using his plugin ever since. It stores all translations in the same single post, which makes it easy to maintain and to use it with other plugins. However, the user interface of former qTranslate got out of sync with the recent versions of Wordpress, especially after WP went to TinyMCE 4. There has been a number of forks of qTranslate, for example, mqTranslate, qTranslate Plus and zTranslate. Most of them are now retired. They all tried to fix qTranslate's user interface preserving its original back-end, which is what this plugin does too. This plugin is a hybrid of all of them and fixes a few bugs in each of them. It also has many new features too, like theme custom translatable fields, for instance. We hope that this plugin is the most complete working version which combines the best features of the original qTranslate as well as all its forks.

We organized an impersonal entity qTranslate Team to maintain a joint authority of all qTranslate-ish plugins. Anyone is welcome to join with a contribution. Participating plugin authors should share the support efforts for each other.

GitHub repository is available: https://github.com/qTranslate-Team/qtranslate-x.git.

We thank our sponsors for persistent help and support:

• Citizens Law Group
• Gunu (Marius Siroen)
• Lightbulb Web Agency
• OptimWise
• Pedro Mendonça
• pictibe Werbeagentur

Important: Read migration instructions, if you previously used other multilingual plugin, otherwise initial installation of this plugin is no different from any other standard plugin. It may help to review Startup Guide in order to get an idea on what to expect.

Very Important: Whenever you update the plugin, make sure to deactivate the previous version and then activate the new one. Normal WordPress update does that, and should be sufficient, but if you overwrite plugin files manually, be sure to execute deactivation/activation cycle, otherwise you will miss the execution of activation hooks and some options may become misconfigured. For the sake of performance, plugin is not programmed to run all the necessary checks every time it is loaded, since activation hook is an expensive operation. That is why it is important to execute deactivation/activation cycle.

Otherwise the installation is similar to any other WordPress plugin:

1. Download the plugin from WordPress or take the latest development version from GitHub.
2. Use WordPress /wp-admin/plugin-install.php page to install a plugin or extract all the files and upload everything (keeping the directory structure) to the /wp-content/plugins/ directory.
3. Deactivate plugin qTranslate, mqTranslate, qTranslate Plus, zTranslate or any other multilingual plugin, if you are running any.
4. Activate qTranslate-X through the 'Plugins' (/wp-admin/plugins.php) configuration page in WordPress.
5. Open Settings->Languages configuration page and add/delete/disable any languages you need.
6. Add the "qTranslate Language Chooser" widget or "Language Switcher" menu item to let your visitors switch the language.
7. For the new installers, it may be useful to read Startup Guide.
8. Configure theme or other plugins custom fields to be translatable if needed (Settings -> Languages: "Integration").
9. If your theme shows multilingual fields at front end in raw format, then read Integration Guide.

• For the new installers, it may be useful to read Startup Guide.
• It is important to read migration instructions, if you previously used other multilingual plugin.
• Read Integration Guide when you need to make theme or other plugin custom fields to be multilingual.

A general FAQ list is available at "qTranslate-X explained" website: https://qtranslatexteam.wordpress.com/faq/, where it is easier to maintain it in between releases.

Developers: please drop new topics here, the text will be moved to qTranslate-X explained at the time of the next release.

1. Editing screen showing the Language Switching Buttons (LSB). Pressing a button does not make a call to the server, the editing happens locally in browser, until "Update" button is pressed, the same way as it is for one language. Multilingual Fields (MLF) are decorated with a color bar on the left to make it easier to distinct them. The way MLF is marked is customizable. Note, that only the fields configured to be multilingual respond to LSB, while regular fields are not affected and keep the same value for each language.
2. Language Management Console - tab "General". Read Startup Guide for more information.
3. Language Management Console - tab "Advanced". Read Startup Guide and FAQ for more information.
4. Language Management Console - tab "Integration". These are the options to configure custom Multilingual Fields (MLF). Read Integration Guide for more information.
5. Language Management Console - tab "Import/Export". Read Migration Guide for more information.
6. Language Management Console - tab "Languages". Read Startup Guide for more information.
7. Language Management Console - page "Configuration Inspector". This page allows to review the combined resulting JSON-encoded configuration of qTranslate-X. Read Integration Guide for more information.

Introducing new date/time handling method based on the latest WordPress implementation of date/time translation.

More of compatibility issues with WP 4.5

Compatibility issues with WP 4.5

Fix: A fix for Internal Server Error 500 under some circumstances.

This version recovers translation of parent of a category on category edit page.

• Enhancement: New date/time handling (QTX_DATE_WP) based on WordPress implementation. Related options are moved to a new tab "Dates" on language management page. The default is changed to the new method.
• Enhancement: Improved language choosing and handling for the first-time installation.
• Enhancement: Improved new language handling with more pre-filled attributes.
• Enhancement: Table of languages is now sortable.
• Enhancement: Table of languages now shows language names in admin language.
• Enhancement: Column "Edit" has been removed from the table of languages as redundant. Click now name of language or its flag to edit a language.
• Enhancement: Improved performace and error handling of function qtranxf_updateGettextDatabasesEx.
• Enhancement: Handling of slugs in qTranslate-X native way, instead of semi-integrated plugin "Qtranslate Slug" - removed later, it needs more work.

• Imrovement: translation of taxonomies on page /wp-admin/edit.php.
• Fix: proper tag editing on page post.php Issue #366.

• Fix: for /wp-login/ and /login/. Thanks to extremecarver.
• Fix: unexpected menu behaviour for empty menu label when option "Hide Content which is not available for the selected language" is on: WP Topic.

• Fix: WP45, '/wp-admin/nav-menus.php': title of newly added menu item kept one language only.
• Fix: WP45, '/wp-admin/nav-menus.php': double quotation mark in menu label.

• Improvement: Option 'Show language names in "Camel Case"' has been added on Settings/Languages page /wp-admin/options-general.php?page=qtranslate-x#general in order to handle absence of function mb_convert_case, as PHP module mbstring may not be installed by default: WP Topic.
• Enhancement: added preset for Welsh (Cymraeg, 'cy') language.
• Fix: regular expression to detect lang=xx in line preg_match('/(^|&|&|&|\?)lang=([a-z]{2})/i',$url_info['query'],$match) of file qtranslate_core.php: Issue #288.
• Fix: smooth run of wp-cron.php from command line: WP Topic.
• Fix: consistency of option "Hide Content ..." to show single post without 404 error, like it is with single page: Issue #297.
• Fix: Predefined locales are changed to match WordPress locales:
  Estonian (Eesti) 'et_EE' renamed to 'et',
  Basque (Euskera, in native alphabet, Euskara, in WordPress, both correct) eu_ES renamed to 'eu',
  Greek (Ελληνικά) 'el_GR' renamed to 'el',
  Finnish (Suomi) 'fi_FI' renamed to 'fi',
  Croatian (Hrvatski) 'hr_HR' renamed to 'hr'.
  Old .mo files are kept in order not to break the sites that may be currently using them, but they should now switch the locale appropriately. The following /lang/qtranslate-* files have been renamed to match changes in locale:
  qtranslate-el_GR. renamed to qtranslate-el.
  qtranslate-es_CA. renamed to qtranslate-ca.
  qtranslate-hr_HR. renamed to qtranslate-hr.*
  This emerged from Topic #27.
• Languages: Slovak (sk_SK) language preset has been added. Thanks to Andrej Leitner.
• Fix: WP45, LSB on term adit page '/wp-admin/term.php': Issue #342
• Fix: WP45, menu update problem '/wp-admin/nav-menus.php': Issue #347.
• Fix: PHP7, Warning 'Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP': Issue #.

• Enhancement: The list of avalable languages in "Not Available Message" and alternative language shown now follow the order of languges defined on configuration page, ignoring the default language. For example, if the first language in the order is English, the second is your native and the default, then English translation will be preferably shown as alternative language. Most sites are expected to be unaffected, since the first language in the order is normally the default langauge. However, it may make sense to first try to show most common language (like English in this example), instead of the default language. Now this is possible with putting the most common language to be the first in the order of languages. The order affects language menu, widget and language shown when translation is not available, as well as any other place where languages need to be listed in an order.
• Fix: home_url() on admin side is now only filtered on /wp-admin/customize.php page, otherwise it created a few problems, for example, wrong overwriting of .htaccess file in some cases, causing Internal Server Error 500 with infinite redirection loop: WP Topic.
• Fix: consistency and caching of meta data translations. Known affected theme: Sahifa. WP Issue.

• Fix: recovered translation of parent of a category on category edit page.

• Fix: Call of qtranxf_get_admin_page_config is moved after all integrating plugins loaded their *-admin.php, otherwise i18n configuration is loaded only partially, which broke "Woocommerce & qTranslate-X". Issue #277.

• All issues after version 3.4.4

• Feature: Type 'custom' with arbitrary format of items for widget "qTranslate Language Chooser". Arguments of function qtranxf_generateLanguageSelectCode are chenge to comply with WordPress standards. Compatibility with old arguments is preserved.
• Enhancement: Translation of language names to other languages: Issue #264. Thanks to benique.
• Enhancement: Moved meta tag "generator" to a separate action: Issue #244.
• Enhancement: PNG files have been further compressed with advanced algorightms: PR #279. Thanks to benique.
• Enhancement: Translation of colon ':' to satisfy French language and may be some other.
• Fix: enabled back translation of posts in qtranxf_postsFilter with filter 'raw'.

• Enhancement: integration with plugin bbPress started, file ./i18n-config/plugins/bbpress/i18n-config.json.
• Enhancement: integration with theme WPEX Elegant started, file ./i18n-config/themes/wpex-elegant/i18n-config.json.
• Enhancement: integration of WP Widget "Text" is enabled: WP Issue.
• Fix: position of flags in admin menu: Issue #269.

• Improvement: admin configuration loading is moved to filter 'plugins_loaded', search for function qtranxf_admin_load to see the change.
• Fix: removed meta box "Languages" in any Editor Mode, except "Single Language".

• Enhancement: argument $found for qtranxf_split_blocks.
• Enhancement: removed limit of 5 characters in language form for locale: Issue #262;

• Fix: Crash on customize.php screen. No Language Switching Buttons on customize screen yet, some values are not translated, but raw multilingual values work. Issue #223.
• Fix: Remove children of parent menu item deleted: Issue #255.
• Fix: Obsolete widget constructor Issue #250
• Fix: Enable a language when gettext database fails to update on a private server: Issue #236.
• Fix: use table of list of languages for WP 4.3.
• Fix: disabled translation of posts in qtranxf_postsFilter with filter 'raw'.
• Enhancement: home_url on admin side now returns url of current front end language - this helps on customize screen.
• Enhancement: choice 'css_only' for $style argument in qtranxf_generateLanguageSelectCode: Issue #259.
• Enhancement: Handle the CSRF vulnerability.

• Fix: link 'View Page': WP Topic.
• Fix: security exploit found by WordPress for vulnerable parameters json_config_files and json_custom_i18n_config: report.

• Fix: qtranxf_trim_words defined at front and admin side: Issue #201.
• Fix: BugTraq issue 139 reported for old qTranslate was assumed to be applicable to qTranlstae-X too, causing WP to ban the plugin temporarily.
• Improvement: WP_CLI compatibility.
• Translation: a lot of thanks to all translators contributed.

• Fix: i18n configuration loading on the first installation, WP Topic.
• Fix for qtranxf_updateGettextDatabases.

• Fix: i18n configuration loading for integrated plugins.

• Includes all changes after version 3.3. Please, review Release Notes.
• Major new feature: Integration Framework is finalized in its first edition.
• Translation: a lot of thanks to all translators contributed.

• Fix: warning message on the first update from 3.3 due to new options creation.

• Enhancement: deep translation of options (qtranxf_translate_option) including embedded serialized values.
• Enhancement: allow absolute paths in 'src' attribute in configuration: Issue #186.
• Enhancement: Dealing with '&' in term name, filter 'get_terms_args'.

• Enhancement: option 'Locale at front-end' added. WP Topic.
• Feature: custom language switching menu with #?lang=xx.
• Enhancement: in function qtranxf_collect_translations_posted, parse variables collected as a query string in an option.
• Enhancement: update option 'Configuration Files' on theme switch.
• Enhancement: search for i18n-config.json files under active theme, plugins and qtranslate-x/i18n-config folder.
• Enhancement: more on error handling.
• Enhancement: translation of admin menu.
• Enhancement: display translation of h2 titles on post.php (for custom types).

• Feature: finalizing Integration Framework.
• Feature: swirly-bracket(brace) language encoding added to be used in places where square-bracket and comment encoding do not work. '[:]' sometimes conflict with shortcodes. '' does not survive tag clean up. '{:}'(swirly-bracket) seems to survive all.
• Enhancement: 'plugins' vs 'mu-plugins', links of sub-folders, etc. Issue #168.
• Enhancement: gettext filters in raw and single language modes.
• Enhancement: turn on 'Compatibility Functions' on first activation, if a file of one of the former forks is detected.
• Enhancement: translation of user metadata at front end WP Topic.
• Fix: handling non-standard language code: Issue #171.
• Fix: 'Head inline CSS' update on language list changes.
• Fix: pagination of posts under Query Mode of URL Modification (filter 'qtranxf_convertBlogInfoURL'): Issue #155. Filters 'home_url' and 'bloginfo_url' are disabled in Query mode.
• Fix: updated qtranxf_get_option_config_files to check for misconfigurations.
• Fix: prev/next_post_link WP Topic.

• Feature: Integration Framework finalizing JSON file format.
• Enhancement: function qtranxf_error_log to show crucial error messages as admin notices on all admin pages and to update 'error_log' file.

• Fix: function qtrans_join: WP Topic.
• Feature: Meta-box 'Language' with Language Switching Buttons is now ready for functionality testing.
• Feature: Integration Framework for PHP code.

• Fix: skip filter 'pre_get_posts' for post_type 'nav_menu_item': WP Topic.
• Fix: hreflang in <link> is now locale instead of language code: WP Topic.

• Feature: Meta-box 'LSB' for Language Switching Buttons, which can be placed anywhere on a page (not finished, just to test an idea on how it will look and work).
• Feature: integration framework is finished in its first version as it is described in Integration Guide. The configuration is now loadable from JSON files, which 3rd-party themes or plugins may generate.
• Enhancement: pre-sets for option 'Highlight Style' are changed to use CSS property 'border' instead of 'box-shadow' and 'outline', otherwise the highlighting was not always visible, specifically when class 'widefat' is also in use.
• Fix: visual mode misbehaviour in field 'Details' for events managed by plugin Events Made Easy Issue #152.

• Enhancement: added class attributes qtranxs-available-language* to the message about available languages to make it CSS-customizable: WP Topic.
• Enhancement: qtrans_getAvailableLanguages added to "Compatibility Functions".
• Enhancement: tabs on configuration page, thanks to Pedro Mendonça for the idea and initial coding: Issue #135 & #153.
• Fix: pagination of posts under Query Mode of URL Modification (filter 'get_pagenum_link'): Issue #155, WP Topic and WP Topic.
• Fix: locale 'ja_JP' changed back to 'ja' as this is what WordPress uses. Files lang/qtranslate-ja_JP.mo/po renamed to qtranslate-ja.mo/po.

• Includes all changes after version 3.2.9. Please, review Release Notes.
• Translation: a lot of thanks to all translators contributed.

• Enhancement: admin message with a link to Startup Guide on the first install.
• Fix: sub-domains should be external hosts Issue #148.

• Fix: one more problem is discovered in function qtranxf_filter_postmeta for the case of empty $meta_key, reported in Issue #138.

• Enhancement: override admin language from $_POST['WPLANG'] in case user tries to change language using field 'Site Language' on page /wp-admin/options-general.php.
• Fix: action 'updated_postmeta' added to clear post meta data cache: Issue #138.

• Feature: query argument qtranslate-mode=raw to retrieve a page without translation as suggested in issue #133.
• Fix: use of post meta cache after its update, Issue #138.
• Translation: German (de_DE) po/mo files updated. Thanks to Robert Skiba.
• Translation: Dutch (nl_NL) po/mo files updated. Thanks to Marius Siroen.

• Feature replaced: Visual Composer compatibility moved to a separate plugin: WPBakery Visual Composer & qTranslate-X
• Enhancement: filters 'gettext' and 'gettext_with_context' are moved to qtranslate_frontend.php, as they are not needed on admin side.
• Enhancement: js scripts in the 3rd-party integration framework.
• Fix: the list of available languages in the column 'Languages' of post listing.

• Enhancement: support for flags of type svg.
• Enhancement: improved report messages for action 'markdefault'.
• Enhancement: improved messages in column "Language" of post listing pages.
• Translation: German (de_DE) po/mo files updated. Thanks to Robert Skiba.
• Enhancement: another attempt to check REDIRECT_STATUS in function qtranxf_can_redirect to prevent unnecessary redirection if mod_rewrite is already doing redirection. In particular, this should help to troubleshoot internal server error as it was observed in Issue #96.

• Fix: troublesome use of deprecated function mysql_real_escape_string is removed: WP Topic.

• Fix: alt attribute for flag icons in widget 'qTranslate Language Chooser': WP Topic.
• Fix: title attribute for language menu items: WP Topic.
• Feature: take language menu title from field 'Navigation Label' of menu editor: WP Topic.
• Feature: options 'names' and 'colon' in Language Menu configuration.
• Translation: .pot, .po and .mo files updated.

• Design: Java script interface for 3rd-party integration, functions: getLanguages, getFlagLocation, isLanguageEnabled, addLanguageSwitchBeforeListener, addLanguageSwitchAfterListener, enableLanguageSwitchingButtons.
• Translation: pot and po files updated.

• Feature: option 'Post Types' to exclude some post types from translation: WP Topic and WP Topic.
• Feature: Visual Composer compatibility (experimental).
• Enhancement (cancelled previously changed at 3.2.9.8.8, it breaks some other places, needs more investigation): added check isset($_SERVER['REDIRECT_STATUS']) in function qtranxf_can_redirect to prevent another redirection if mod_rewrite is already doing redirection. In particular, this should help to troubleshoot internal server error 500 as it was observed in Issue #96.

• Translation: Greek ('el_GR') predefined language added, thanks to Marios Bekatoros.
• Translation: Arabic (ar) po/mo files updated. Thanks to Nedal Elghamry.
• Enhancement: added check isset($_SERVER['REDIRECT_STATUS']) in function qtranxf_can_redirect to prevent another redirection if mod_rewrite is already doing redirection. In particular, this should help to troubleshoot internal server error 500 as it was observed in Issue #96.
• Feature: js functions addLanguageSwitchBeforeListener and addLanguageSwitchAfterListener is designed for other plugin integration, read Integration for more information. Thanks to Dmitry for the useful design discussion Issue #128.
• Fix: more special cases for arrays in POST, Issue #127.

• Fix: special cases for arrays in POST, Issue #127 and WP Topic.
• Translation: thanks to all translators contributed. po files updated with correct version number.

• Fix: taxonomy names with apostrophe and other special characters: Issue #122.
• Fix: locale 'ja' changed to 'ja_JP'. Thanks to Yusuke Noguchi.
• Translation: thanks to all translators contributed.

• Feature: choice 'Single Language Mode' for option 'Editor Mode'.
• Enhancement: New release handling framework.
• Fix: function qtranxf_sanitize_url, thanks to HAYASHI Ryo: Issue #117.

• Feature: js function addLanguageSwitchListener is designed for other plugin integration, read Integration for more information.
• Fix: handling of cookie qtrans_edit_language.

• Fix: function qtranxf_join_b, test for qtranxf_allthesame.
• PHP version compatibility: syntax changed in 'qtranxf_collect_translations*'.

• Improvement: TinyMCE handling is re-designed once again. [WP Topic] [Issue #115]
• Feature: new type of hook, displayHookAttrs, in admin/js/common.js to translate submit button texts (used in Woocommerce, for example).

• Translation: German (de_DE) po/mo files updated, thanks to Maurizio Omissoni.
• Translation: Italian (it_IT) po/mo files updated, thanks to Maurizio Omissoni.
• Feature: new front-end option 'Show content in an alternative language': Issue #21.
• Improvement: error handling for gettext updates #105 and #113, and other minor code clean up.

• Translation: Dutch (nl_NL) po/mo files updated. Thanks to Marius Siroen.
• Translation: Portuguese (pt_PT) po/mo files updated. Thanks to Pedro Mendonça.
• Feature: framework for handling admin notices on new releases.
• Improvement: design of option handling: optimization and simplification in the code.
• Fix: replaced pre-defined language code 'pt-br' with 'pb': Issue #104.
• Fix: hidden multilingual input fields moved right before their single-lingual originals: WP Topic.

• Improvement: 'Code' column in the list of languages. Thanks to Pedro Mendonça for the discussion.
• Fix: date/time formats containing backslashes: Issue #99.

• Translation: po files updated. Thanks to Pedro Mendonça for a discussion.
• Fix: languages management problems: Issue #102.

• Feature: qtrans_join added to option 'Compatibility Functions'. [Issue #106]
• Translation: Portuguese (pt_PT) po/mo files updated. Thanks to Pedro Mendonça.
• Fix: various problems with new option save/load methods.
• Fix: CSS syntax. Thanks to Michel Weimerskirch: Issue.

• Feature: option "LSB Style" to customize Language Switching Buttons style.
• Feature: after the first activation, the current WordPress active language becomes the default one for qTranslate-X, instead of English. No other languages are added anymore.
• Improvement: option load and save algorithm re-designed.
• Fix: special cases for function convertURL.

• Feature: Option "Highlight Style". Thanks to Michel Weimerskirch.
• Fix: handling of relative urls in qtranxf_convertURL.
• Fix: default locale for Estonian is 'et_EE'.
• Improvement: more on 'URL Modification Mode' option Per-Domain.
• Translation: Arabic (ar) po/mo files updated. Thanks to Nedal Elghamry.
• Translation: Dutch (nl_NL) po/mo files updated. Thanks to Marius Siroen.

• Improvement: function convertURL has been re-designed to take into account scheme, user, password and fragment correctly.
• Improvement: added "x-default" link <link hreflang="x-default" rel="alternate" /> as suggested by Google.
• Feature: added exclusions to qtranxf_convertFormat for language-neutral date formats 'Z', 'c' and 'r' in addition to 'U' [Issue #76]
• Feature: variable $url_info['set_cookie'] can be overridden via qtranslate_detect_language filter. [WP Topic]
• Feature: admin notices for integrating plugins 'ACF qTranslate', 'All in One SEO Pack & qTranslate‑X', 'Events Made Easy & qTranslate‑X', 'qTranslate support for GravityForms', 'WooCommerce & qTranslate‑X' and 'Yoast SEO & qTranslate‑X'.
• Feature: added URL folder /oauth/ to the list of language-neutral URLs. [Issue #81]
• Maintenance: GitHub repository information in the header of qtranslate.php
• Performance: function convertURL now uses cached values of previously converted urls.
• Performance: a few other little performance improvements.
• Translation: Dutch (nl_NL) po/mo files updated. Thanks to Marius Siroen.
• Translation: French (fr_FR) po/mo files updated. Thanks to Sophie.
• Translation: Portuguese (pt_PT) po/mo files updated. Thanks to Pedro Mendonça.
• Fix: Query in qtranxf_excludePages. [WP Topic]
• Fix: Warning 'Undefined index: doing_front_end' reported in WP Topic.
• Fix: time functions adjusted. [WP Topic]
• Fix: custom menu item query 'setlang=no': [Issue #80]

• Includes all changes after version 3.2.2.
• Improvement: added removeContentHook in admin/js/common.js. Thanks to Tim Robertson: [GitHub Issue #69]
• Improvement: use of nodeValue instead of innerHTML in addDisplayHook of admin/js/common.js.
• Translation: Dutch (nl_NL) po/mo updated, thanks to Marius Siroen.
• Translation: pot/po files updated

• Feature: replaced option 'Remove plugin CSS' with 'Head inline CSS'.
• Fix: problem with url like site.com/en without slash.

• Feature: options of similar functionality of mqTranslate: 'Remove plugin CSS', 'Cookie Settings' and 'Translation of options'. Thanks to Christophe) for the initial pull.
• Improvement: qtrans_getLanguageName added to option 'Compatibility Functions'.
• Fix: url like site.com/en?arg=123 without slash before question mark now works correctly.

• Feature: multiple sets of Language Switching Buttons per page. Enabled by default above metabox 'Excerpt'. Will be customizable later.

• Improvement: auto-translation of metadata at front-end, filter qtranxf_filter_postmeta. [Ticket]

• Translation: Dutch (nl_NL) po/mo updated, thanks to Marius Siroen.
• Improvement: common.js modifications needed for plugin All in One SEO Pack & qTranslate-X.
• Fix: non-standard host port handling. Thanks to Christophe. [Ticket]

• Feature: added option "Hide Title Colon" for widget "qTanslate Language Chooser". [Ticket]
• Improvement: disabled browser redirection for WP_CLI. [Ticket]
• Fix: wp-admin/nav-menus.php: new menu items for pages get added with title already translated.

• Includes all changes after version 3.1.
• Translation: Dutch (nl_NL) po/mo updated, thanks to Marius Siroen.
• Improvement: add_filter('term_description') at front-end. Thanks to josk79.

• Feature: class qtranxs-translatable is introduced to distinct all translatable fields. Thanks to Michel Weimerskirch.
• Improvement: QTRANS_INIT constant is now defined when "Compatibility Functions" is on. [WP issue.]
• Improvement: various code improvements, search for '3.2-b3' tag to look them them up.

• Translation: Hungarian (hu_HU) po/mo updated, thanks to Németh Balázs.
• Translation: German (de_DE) po/mo updated, thanks to Maurizio Omissoni.
• Improvement: Basque language added to the pre-set list of languages, thanks to Xabier Arrabal.
• Improvement: 'Convert Database' options now also convert postmeta.meta_value database field.
• Fix: 'Convert Database' options would not work correctly for some options.
• Fix: qtranxf_http_negotiate_language used to return en_US when PHP supports function http_negotiate_language.

• Translation: Dutch (nl_NL) po/mo updated, thanks to Marius Siroen.
• Improvement: updated activation/migration messages with a link to Migration from other multilingual plugins publication.
• Improvement: updated "Compatibility Functions" option with qtrans_split.
• Fix: dealing with https and port 443.

• Includes all changes after version 3.0.
• Maintenance: 'Translate Service' feature has been disabled, as the vast majority of people surveyed declined it. Thanks to Gunu (Marius Siroen) who made this survey possible.

• Improvement: up to date code for updateGettextDatabases and cleaning up of a lot of code. Thanks to Michel Weimerskirch.
• Translations: Croatian po/mo - thanks to Sheldon Miles.
• Translations: po/mo adjusted for a typo fixed. Thanks to Michel Weimerskirch.
• Translations: default time format for Sweden changed - thanks to Tor-Björn.
• Fix: import/export from other qTranslate-ish forks.
• Fix: problem with menu editor under some configurations.

• Fix: 'Hide Title' in the widget. WP topic
• Fix: corrected redirection in some peculiar cases.

• Fix: query to implement option 'Hide Content which is not available for the selected language'

• Feature: more on framework for integration with other plugins and themes.

• Feature: closing tag [:] for square bracket language encoding mode is introduced.
• Feature: options to convert database to/from square bracket only mode.
• Feature: new language encoding mode 'byline', particularly needed for Woocommerce integration.
• Improvement: altered the response of filter 'esc_html' to return a translation to current language instead of the default language.
• Feature: more on framework for integration with other plugins and themes.
• Fix: import from mqTranslate (thanks to Christophe).

• Includes all changes after version 2.9.6.
• Please, do not forget to respond to survey on 'Translate Service' feature by courtesy of Gunu (Marius Siroen), whose continuous help is much appreciated.
• Feature: framework for integration with other plugins and themes.
• Maintenance: po/mo files updated.

• Feature: editing of menu item description on page /wp-admin/nav-menus.php.
• Feature: hooks for integration with other plugins
• Improvement: safer comment query with cache support when 'Hide Untranslated Content' is on. issue #17
• Compatibility: PS Disable Auto Formatting. WP issue
• Maintenance: .pot and .po files updated with new untranslated strings.

• request for survey on 'Translate Service' feature

• the version can be downloaded here: 2.9.8.7 alpha.
• more on proper detection of front-end vs back-end on AJAX calls.
• 'attr_title' is now translated in menu display

• more on option "Hide Content which is not available for the selected language"
• thanks to Marius Siroen for Dutch translation

• .pot/.po files in order. Thanks to Pedro Mendonça for an extensive discussion on the best way to proceed with translations.
• added 500ms delay before page refresh after new tag insertion on wp-admin/edit-tags.php.

• Translations of captions and attributes in standard WP galleries, which is, in fact, much bigger change affecting many places. Need to re-test all carefully.
• improved run-time performance.
• some improvements on plugin translation as suggested by Gunu.

• updated "Compatibility Functions" option with qtrans_generateLanguageSelectCode and qtrans_useCurrentLanguageIfNotFoundShowAvailable.
• more on TinyMCE compatibility
• taxonomy editor pages improved to switch languages for additional display fields.

• URL of a custom menu item gets converted to active language, unless query argument 'setlang=no' is added.
• filter 'get_search_form' is no longer need, since we adjusted home_url() issue #8

• plugin integration design
• po/mo files are updated. Translators needed.

• more fixes for issue #5.

• fix for wrong language on AJAX requests

• menu items with empty text for the current language are not shown any more (WP issue).
• enable Language Switching Buttons on menu editor page. Fields "Navigation Label", "Title Attribute" and "Description" now respond to Language Switching Buttons.
• option "Custom Pages" to enable Language Switching Buttons on custom-defined pages.
• [per-domain URL modification mode]https://wordpress.org/support/topic/qtranslate-tld-url-change-mode).
• split the qtranslate.js script into a few scripts in admin/js/ folder to be loaded depending on the page which needs them.
• updated qtranslate.pot and fixed proper translation of various strings in the code (thanks to Pedro Mendonça).
• fix for when cookie 'qtrans_edit_language' contains unavailable language.
• various performance improvements.
• option "Editor Raw Mode" to be able to edit database text entries as they are, with language tag separators, without Language Switching Buttons.
• fix for random <p> in TinyMCE editors.
• fix for login problem when siteurl option is different from 'home'.
• compatibility with Qtranslate Slug.
• fix for blank translations.
• fix for & in url problem.
• fix for option Hide Untranslated Content.
• compatibility with plugin Groups, issue

• more fixes for <!--more--> and <!--nextpage--> tags and parsing multilingual texts.

• more fixes for <!--more--> and <!--nextpage--> tags.

• fix for https://wordpress.org/support/topic/comment-shows-404-error

• "Language Switcher" menu options, read FAQ for more information.
• fix for too early call to current_user_can, which caused a debug notice from within some other plugins.
• fix for https://wordpress.org/support/topic/editor-adds-characters-before-text

• Option "Compatibility Functions" to enable former qTranslate function names: qtrans_getLanguage, qtrans_convertURL, qtrans_use, qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage, qtranxf_useTermLib and qtrans_getSortedLanguages
• "Language Switcher" menu options: flags=[yes|no], type=[LM|AL]. They can be used in a query string in URL field of Language Menu.

• JS bug fixed, which would not show any field value if no languages are yet configured for that field.

• ability to enable "Custom Fields" by either "id" or "class" attribute.
• ability to specify filters, which other theme or plugins define, to pass relevant data through the translation.
• support for <!--more--> and <!--nextpage--> tags.
• language cookie are renamed to minimize possible interference with other sites.

• added option "Show displayed language prefix when content is not available for the selected language".
• compatibility with "BuddyPress" plugin and various improvements.
• custom CSS for "qTranslate Language Chooser" widget configurable via its properties.
• now always redirects to a canonical URL, as defined by options, before displaying a page.
• use of cookies to carry the language chosen from session to session.

• [this does not work yet] created wrappers to make former qTranslate function names available: qtrans_getLanguage, qtrans_convertURL, qtrans_use, qtrans_useCurrentLanguageIfNotFoundUseDefaultLanguage.

• user-friendly activation hook to deactivate/import/export other qTranslate forks.
• import/export settings from other forks

• improved automatic downloading of gettext databases from WP repository.
• translation of "Site Title" and "Tagline" in Settings->General (/wp-admin/options-general.php).

• Option "Custom Field": theme custom fields can be translatable.

• handling multiple tinyMCE editors, as some themes have it. It will now make all fields in page and post editors of class "wp-editor-area" translatable.

• fix permalink on edit pages
• disabled autosave script in editors, since it saves the active language only and sometimes hardly messes it up later.

• fixes for flag path, when WP is not in /. Permalink on edit pages is still broken, apparently has always been for this case.
• various minor improvements

• bug fixer

• enabled translation of image 'alt' attribute.
• corrected behaviour of category and tag editing pages when admin language is not the default one.
• hid 'Quick Edit' in category and tag editing pages since it does not work as user would expect. One has to use "Edit" link to edit category or tag name.

• enabled translations of image captions, titles and descriptions (but not 'alt').

• improved Description, FAQ and other documentation.

• added "Language Switcher" menu item to WP menu editing screen
• currently editing language is memorized in cookies and preserved from one post to another
• on the first page load, the default language is now activated instead of the last language
• full screen mode for tinyMCE integrated properly
• more translation on tag and category editor pages
• added 'post_title' filter to translate all titles fetched for display purpose
• fixed problem with comment date display in some themes

It is important to review the list of Known Issues before starting using the plugin.

Please, review the credentials page at qTranslate-X explained website.

A list of desirable features is maintained at qTranslate-X explained website.