Support » Plugin: WP Multilang » It did put an end to the translation nightmare

  • jaldunate

    (@jaldunate)


    I spent so long trying to find a solution for translation. I had to make a list after several failed iterations because it was hard to keep track of what was tested. These is what I wrote:

    translatepress

    * Works well
    * only two languages in free version, paid version is very expensive, plus paid periodically

    wpml

    * paid version with ok price does not support woocommerce
    * paid version with woocommerce support too expensive

    Making a multisite

    * Works well, but you get two parallel woocommerce settings
    * Woocommerce settings might get bugs on multisite (in my case it was unusable)
    * you need to install plugins for
    – shared woocommerce settings
    – shared media

    Polylang

    * works ok, but woocommerce works badly
    * paid version is expensive

    Transposh

    * works well like translatepress
    * some links throws the user back to default language
    * you have to translate span by span, which can get extremely tedious

    Weglot

    * free version limits amt of words and only one more language

    wpglobus

    * it either doesn’t work or it’s very badly designed

    Multilanguage

    * there is no way to add translation to posts

    Translate by Supsystic

    * seems ok but does not work with gutenberg, which would mean re-doing all the content

    falang

    * Works perfect; I did not like the translation interface.

    Bogo

    * works well
    * a bit annoying that EVERY page needs to be translated or the ux breaks

    sublanguage

    * works well
    * some woocommerce buttons take the user back to initial language
    * Woocommerce products not supported?? it seems it was, but new version f*d up

    wp multilang

    * seems to work
    * translates wp and does not break the “language link string”
    * something weird happened with permalinks after install, it got solved after resetting that setting
    * correctly activates native language support strings
    * It can bug out if a page does not have a translation version; thankfully it is in my power to solve that.

    • This topic was modified 2 months, 2 weeks ago by jaldunate.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi,
    I’m Stéphane from Falang , i have write you an email to have more infos on what you don’t like in the interface.
    You Don’t have to translate everything, by default the current language is displayed and you translate only the items you want to be showed in another language.

    Stéphane

    hey! I saw it and I replied.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this review.