Title: release 3.1 notes
Last modified: August 22, 2016

---

# release 3.1 notes

 *  ResolvedPlugin Author [John Clause](https://wordpress.org/support/users/johnclause/)
 * (@johnclause)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/)
 * The major feature of the release 3.1 is that it introduces new encoding for multilingual
   text which is referred to as ‘square bracket only’ style. It enables closing 
   tag `[:]` in the former `[:]`-encoding mode. This makes it possible to use `[:]`-
   mode in any text possibly embedded into language neutral text (like HTML code,
   for example). This change enables compatibility with a number of other plugins.
 * The new database format is no longer straightforwardly compatible with other 
   forks of former qTranslate, but we have implemented “Convert Database” options
   to automate the process of conversion. However, even with this additional conversion
   step, the 3rd-party plugins custom-stored data will not be auto-converted, but
   manual editing will still work.
 * Plugin [description](https://wordpress.org/plugins/qtranslate-x/) and [FAQ](https://wordpress.org/plugins/qtranslate-x/faq/)
   have more information.

Viewing 9 replies - 1 through 9 (of 9 total)

 *  [pirexfamily](https://wordpress.org/support/users/pirexfamily/)
 * (@pirexfamily)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5822996)
 * Dear Charles hello,
 * Thanks for the great work!
    I changed from mqtranslate with success,but I have
   a major issue with this 3.1 update (I had to downgrade to 3.0). With this 3.1
   only on the default language – no metter which language – brakes the theme layout,
   but works fine for the translation. With the exact same html text. Any ideas?
 * Best Regards
    Pedro
 *  Plugin Author [John Clause](https://wordpress.org/support/users/johnclause/)
 * (@johnclause)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823095)
 * I cannot think of any change that could possibly cause it and I cannot reproduce
   it either. Would it be possible for you find out the reason and let us know? 
   Otherwise I do not see how we can troubleshoot it unless you give us access to
   a test-copy of your site. There are a few WP plugins, which help to copy site
   easily enough.
 *  [jjbte](https://wordpress.org/support/users/jjbte/)
 * (@jjbte)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823106)
 * Ahh, this is where I saw the post about someone’s theme layout being broken after
   upgrading to 3.1.
 * pirexfamily, is there any chance you have photos with multilingual Alt tags on
   some/all of your pages?
 * Please see my discussion of my issue and resolution here: [https://wordpress.org/support/topic/issue-with-translated-alt-tag-breaking-page-layout?replies=1](https://wordpress.org/support/topic/issue-with-translated-alt-tag-breaking-page-layout?replies=1).
 *  [extremecarver](https://wordpress.org/support/users/extremecarver/)
 * (@extremecarver)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823168)
 * Quick question – will the automatic conversion convert all
    <:> to [:] or will
   it simply set the closing [:] after the last langauge?
 *  [jjbte](https://wordpress.org/support/users/jjbte/)
 * (@jjbte)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823170)
 * Hi extremecarver… Here is what I experienced on my test site while trying to 
   edit an existing photo in my Media Library:
 * The Title, Caption, and Description fields had the <!–:en–> language tags, and
   the Alt field had the [:en] language tags (no closing [:] tags, since these did
   not exist prior to 3.1).
 * First, I tried to simply open the photo in the full-page Media Editor and hit
   the Update button without making any changes. This left all fields exactly as
   they had been–no changes at all to the language tags–and page layout still broken
   due to the Alt closing quotes issue.
 * Next, I loaded the photo back in the full-page Media Editor and “pretended” to
   edit the Alt field for each language. What I actually did was place my cursor
   at the end of the Alt field text, hit backspace once, and then retype whatever
   character I had just eliminated using the backspace key. I did this for each 
   language, hit Update, and my Alt field now had the [:] closing tag at the end
   of its string, which fixed my layout problem. You could accomplish the same result
   by opening the “popup” photo editor and simply typing [:] at the end of your 
   Alt field string.
 * Since I made no changes to Title, Caption, and Description, they stayed just 
   as they were with the <!–:en–> language tags, but they didn’t appear to cause
   any issues with my site so it would seem it’s OK to leave those fields alone.
 * If you do make changes to these fields using the full-page Media Editor (not 
   the popup), then yes, the <!–:en–> language tags for the edited field will be
   replaced by the [:en] language tags and a [:] will be placed at the end to close.
   This is only true for fields you edit. So, for instance, if you change your Title,
   its tags will be converted, but Caption and Description tags will remain the 
   same unless and until you edit them in the full-page editor.
 * Note: I only tested scenarios where ALL photo fields had values. There are times
   where WordPress substitutes Title and/or Description for the Alt attribute if
   the actual Alt field has been left empty. I wouldn’t anticipate any issues in
   such situations, but I did not have time to specifically test this scenario.
 *  [extremecarver](https://wordpress.org/support/users/extremecarver/)
 * (@extremecarver)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823172)
 * My question was aimed at plain posts and plain pages content – not media content…
 *  [jjbte](https://wordpress.org/support/users/jjbte/)
 * (@jjbte)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823173)
 * The “conversion upon editing” behavior most likely works the same for existing
   posts and pages as it does for media files. The full-page Media Editor in WordPress
   works much the same as the pages and posts editor (with language-switching buttons,
   etc.).
 * There is also the option of automated conversion of your database. After updating
   to 3.1, there are new options under Settings > Languages > Import/Export > Convert
   Database. The first one is “Convert database to the ‘square bracket only’ style,”
   which does specifically state “All string options and standard post and page 
   fields will be uniformly encoded like ‘[:en]English[:de]Deutsch[:]’.”
 *  [Daniel](https://wordpress.org/support/users/ddumondgmailcom/)
 * (@ddumondgmailcom)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823176)
 * This last update appears to have broken something!
 * The default language of my website is English, and when I click to fire it in
   french, it works great, but then I’m stuck viewing it in french!!
 * When I mouse over the language switcher it points to the english url, but when
   I click on it, it loads the french page again.
 * Even if I manually type in a url like [http://www.website.com/contact/](http://www.website.com/contact/)
   it redirects me to [http://www.website.com/fr/contact/](http://www.website.com/fr/contact/)
 * My system browser language is English and I shut-off the auto direct just to 
   be sure that’s not the problem.
 * Would any one know what might cause this? I don’t recall this issue with the 
   last update,
 * Thanks in advance!!
 * ——————————————–
 * **EDIT:**
    Found the fix [here](https://wordpress.org/support/topic/default-language-cant-be-chosen?replies=41)—
   Hopefully this fix is included in the next update!
 * Cheers!
 * ——————————————–
 *  Plugin Author [John Clause](https://wordpress.org/support/users/johnclause/)
 * (@johnclause)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823194)
 * [@extremecarver](https://wordpress.org/support/users/extremecarver/)
 * > Quick question – will the automatic conversion convert all
   >  <:> to [:] or will
   > it simply set the closing [:] after the last language?
 * It sets `[:]` after last language only. [FAQ](https://wordpress.org/plugins/qtranslate-x/faq/)
   explains that in combination like this `[:][:de]`, `[:]` is redundant, but does
   not hurt if present.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘release 3.1 notes’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/qtranslate-x_f9f9f9.svg)
 * [qTranslate X](https://wordpress.org/plugins/qtranslate-x/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/qtranslate-x/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/qtranslate-x/)
 * [Active Topics](https://wordpress.org/support/plugin/qtranslate-x/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/qtranslate-x/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/qtranslate-x/reviews/)

 * 9 replies
 * 5 participants
 * Last reply from: [John Clause](https://wordpress.org/support/users/johnclause/)
 * Last activity: [11 years, 3 months ago](https://wordpress.org/support/topic/release-31-notes/#post-5823194)
 * Status: resolved