qTranslate X vs. polylangCASE STUDY: A BATTLE OF TWO PLUGINS

By Miriam GoldmanWordCamp Ottawa 2016

Who is Miriam?

Front-end web developer at Fuel Industries Involved with WordPress for 5+ years Latin ballroom dancer 3rd degree black belt in karate

qTranslate X

Over 100,000+ installs Evolution of qtranslate Supported by a team of developers Hybrid of multiple qtranslate forks

https://en-ca.wordpress.org/plugins/qtranslate-x/

Pros

Easy language configuration Simple buttons to flip between languages in WP Editor Tied to a single page/post, rather than separate entries Works well with ACF (advanced custom fields) Free, no freemium

Cons

Need multiple plugins to support additional infrastructure Examples: qtranslate slug, qtranslate support for Gravity

Forms/woocommerce Easy to get confused as to which language you are on

polylang

100,000+ installs Offers addons Supported by sole developer

https://wordpress.org/plugins/polylang/

Pros

More default languages installed You can set the order in the language switcher String translations can be set separately

Cons

Certain settings need the Pro upgrade Separate pages are created, not as clean as a switch Additional configuration needed to support items such as ACF

So…which is better?

Depends Easy of use: qtranslate X Ability to separate languages: polylang

FULL DISCLOSURE: Other plugins also available (WPML, for example)

Who wins? It’s a tie, really

Connect with Miri

Twitter: @mirigoldman Web: http://www.miriamgoldman.com Email: sensei.Miriam@gmail.com

THANK YOU!