Each of these plugins have their own way to organize datas and translations. Some creates tables, another use general options table and another only uses mo files to contain translation completing root language taxonomy for post.
As demonstrated in thousand of websites, xili-language trilogy is able to support
– switching of page (or any custom post type) according language.
– switching categories (translation of name and description)
– dynamic content navigation menus according language and or cloning of navigation menus (one content per language).
– tags clouds grouped by language.
– and more (if using plugin hooks and using features available in source)…
All is done without creating tables in the WP database since WP 2.3 and now WP 3.5. It is reversible.
Xili-language is free but with a little work it becomes a powerful tool for web masters even with complex content strategy or profit/commercial theme.
http://2012.wpmu.xilione.com
M.
Hi,
I din’t know how you did your testing, but I did also test a lot of multi-language plugins and the only one that worked properly is XILI-language. It supports all of the mentioned items you listed. So you are not right with your sentence that Polylang IS THE only one that supports these.
I did not only had a look to the obvious things while testing, I practice all the plugins for several weeks. The only practical to use was XILI-language for me. All others disqualified their self, also in respect of beeing SEO compliance.
Anyhow I don’t know PolyLang – but I just wanted to point out that your statement is not true.
Cheers
Yogie
