13 Responses

  1. Krzysztof
    Krzysztof February 4, 2015 at 16:06 | | Reply

    There’s actually one more alternative to WPML worth considering – Polylang (https://wordpress.org/plugins/polylang/). It’s actively developped and in my personal view you should definitely add it to the list. At almost 0.5 milion downloads it’s exclusion here makes the list incomplete.

    I am an owner of WPML full licence but I’ve also had experience with Polylang and I need to say that on smaller projects (where compatibility with other plugins isn’t a must) Polylang… wins hands down. It feels much faster, makes fewer calls to the database and has never let me down (comparing to WPML with which I’ve had a few problems). It’s incredible how much more polished this FREE plugin feels. Unfortunately it suffers from the fact that it’s still comparatively young and not all plugin devs have noticed its existence and so haven’t made their soft compatible.

    You should definitely test it and complete your article.

    1. Senff
      Senff February 25, 2015 at 20:15 | | Reply

      I’m not sure why Polylang didn’t show up in my research prior to writing the article, but from the looks of it you’re right — it definitely should have been included. I’ll give it a look and see if we can update the article or if we’ll save it for a future one. Thanks Krzysztof!

  2. Ryan Hellyer
    Ryan Hellyer February 4, 2015 at 16:46 | | Reply

    In my experience, the only viable ways to handle multlingual sites are Babble and MultilingualPress.

    1. Jean Galea
      Jean Galea February 5, 2015 at 15:48 | | Reply

      Why is that Ryan?

  3. Anastis Sourgoutsidis
    Anastis Sourgoutsidis February 5, 2015 at 15:49 | | Reply

    +1 for Polylang. Combine it with Codestyling Localization for translating static texts, and you get pretty much all you ever wanted.

  4. tomatillodesign
    tomatillodesign February 5, 2015 at 16:31 | | Reply

    +1 for Polylang. Incredible free plugin.

  5. tudoutou
    tudoutou February 6, 2015 at 18:02 | | Reply

    How about Bogo?

    1. Senff
      Senff February 25, 2015 at 20:22 | | Reply

      Bogo didn’t show up in the top 5 of alternatives in my research prior to writing the article, which is why it wasn’t addressed initially. We’ll probably give it a go in a future article.

  6. Brian
    Brian February 12, 2015 at 10:13 | | Reply

    gtanslate hasn’t worked for a year. It has been disowned by its author and is not compatible with wordpress 3.9 and above. That isn’t in the ‘cons’ section.

    1. Senff
      Senff February 25, 2015 at 20:19 | | Reply

      Please note we reviewed qTranslate PLUS, not the original, abandoned qTranslate plugin (qTranslate Plus is a fork of the original one and is still maintained). Maybe I should have made that a little more clear.

  7. entwickler99
    entwickler99 April 21, 2016 at 06:43 | | Reply

    PRO: inititial translation is done automatically

    That is actually a CON, because automatic translations are useless crap.
    I guess the only reason there are people using them is that they only know one language (mostly english) and don´t realize the translations are totally worthless

  8. Kenneth Horn
    Kenneth Horn July 20, 2017 at 10:52 | | Reply

    I’ve had so many problems with WPML over the past year and half that I’ve now begun a search for an alternative. (1) The Website and documentation are all convoluted. Horribly organized. Lousy technology. Just go look at the website and see how confusing it is. (2) What I consider ODD functionality. When it translates a taxonomy you can’t see that the translation is done back-end. The mysterious translation only appears front -end. Most importantly (3) Despite saying it is compatible with Divi, it is NOT. It disables the GLOBAL MODULE functionality when activated with Divi. Whether there is anything better, I don’t know. But I’m going to find out!

  9. Kenneth Horn
    Kenneth Horn July 20, 2017 at 11:23 | | Reply

    Clarification: The way I see it, multilingual plugins do three things. (1) They make the back-end (Admin) available in a language other than English. This will not be important to most developers creating multilingual websites as they are going to have to have access to translators that speak, read and write in both the primary and secondary language. So having the Admin available in the secondary language is not really necessary. We purposely retain English (our primary language) on the Spanish side of the site. (2) It translates strings and taxonomy. String means thing the viewer will see front end like (Home Page, Continue, etc) As far as the few visible strings that are not technically content, I would assume that all plugins handle these about the same. As far as the taxonomy goes, I think implementation is clunky. You can’t see a translated custom-field string back-end. You have to preview the page front end and check it. I find that incredibly awkward. (The taxonomies, such as categories, are handled very well and are visible back end just as you would see them in the primary language in the right column Admin panel) But custom field translation is awkward. If you use Advanced Custom Fields? Forget it! Horrible implementation of translation. Toolsets (created by the same authors as WPML) work smoothly. That’s a PRO because Toolsets is immensely better than ACF in my opinion. (3) Translation management. If you think that any of these plugins will actually translate your content, forget it. I have in-house translators working on relatively small sites in just 2 languages. I’ve never even looked at the translation management features other than to say the whole management system looks a bit confusing. But the straw that broke the camel’s back is how WPML broker the global module functionality of Divi (even after I deactivated and uninstalled WPML). Hope these details help.

Leave a Reply