After a couple of months, the research and development around the xili-language trilogy is gradually resuming. The offer of plugins to create multilingual WordPress sites is plethoric but only two use the taxonomic approach. On this site based on 2014-xili, multilingual child theme of Twenty Fourteen, remain the main documents concerning the trilogy. Following the WordCamp Europe Paris in June 2017, Twenty Seventeen’s site based on 2017-xili , will contain the Latest news and updates.
The plugin Xili-language (heart of his trilogy) continues its development …
Widget “language list” or “language selector”
After the period devoted to the management of menus and their style with image (flag), this is the appropriate time to review widget “language list” or language selector (switcher).
Adding pictures is based on an integrated style sheet in the header if and only if this widget is active. (thanks to the is_widget_active function). As with nav menus, the theme must support (add_theme_support) the “custom_xili_flag” introduced since Xili-language version 2.15.
Three possible styles: single text (as before), image + text and image / flag alone (in compact horizontal list).
Images/pictures can have three origins:
– Those provided by the developer of the theme (so in a theme subfolder and reported at the theme setup)
– Those introduced as nav menu image in the catalog media associated with a language,
– And in case of absence, for some images contained in the plugin.
Importing multilingual datas of a website previously controlled by Polylang plugin
A few years after the birth of Xili-language, Polylang also chosen the way of taxonomy “language” to organize posts according to their language. The slightly different implementation of this taxonomy is discussed here. This approach retains the posts (article, page) to their initial state. In a decidedly simple approach with an effective ergonomics, its success demonstrates that it meets expectations in a very competitive multilingual context. But as for music, cars, the webmaster / developer may want different or complementary qualities, that is why, apart from other reasons, the trilogy Xili-language continuing its development. If, during the life of a website, the need appears, Xili-language 2.1+ version is able to detect the presence of previous Polylang and recover data to continue the multilingual architecture with the trilogy (Xili-tidy- tags, xili-dictionary). Caution, in the list of extensions, just disable Polylang without removing it because otherwise, for lack of option provided for this purpose by the author, all specific data Polylang will be deleted. Once, Xili-language active, a semi-automatic multi-step process is fired … a specially dedicated post is published…
Widgets visibility option under the current language
If the option is activated (5th tab), the webmaster will see in the interface of each widget, a group of 2 dropdown menus to decide whether this widget should appear or not.
improved code and algorithms
Add filters to customize the implementation style images / flags in the language selector.
Added new theme twenty sixteen in the list of bundled themes that came with WordPress.
Intermediate versions before publication on the WP repository are available on GitHub
First: Xili-language compatibility is verified with WordPress 4.3 “Billie”.
Well known by donors, contributors, the functions related to the themes present in permalinks 201x-Xili child bundled themes are now included in the plugin itself.
It is therefore possible for all situations respecting the rules kernel (core) of WP to have permalinks integration with current language at the beginning of the URI instead ?lang = fr_fr at end of URI for example.
Note also that the language slug can be a shortcut to its ISO code but also an alias at your convenience associated with the activity of the website or its geography.
Possible to do tests with newest theme twenty sixteen (and his multilingual child theme).
Other fixes and code improvements continued to grow especially for parties of sometimes more than 5 years old. 😉
Thanks for your returns
The release of WordPress 4.3 Billie is shipped imminent (version RC2 today). Xili-language (version 2.19.3+), based from the outset on taxonomy “language” and language of file selection (.mo) continues to be consistent to manage a multilingual site.
This compatibility is confirmed after bbPress for extensions like famous WooCommerce : with some settings and a few small kit of filters, creating a multilingual shop is possible and the buyer will the shop, his cart and his checkout in the chosen language…
The 2.19.3 release adds enhancements for managing less common languages such as those with three (arq) or six characters (haw_US) of ISO name.
The child theme twentyfifteen-Xili contains sample additional text field (copyright) adjustable in the customizer (theme_mod function). To be continued with 2.20…
WordPress 4.2-beta2 is shipped since few days. The three plugins of the xili-language trilogy must be tested. Some improvements are added. More details in each repository (“Changelog” tab).
xili-language : version 2.16.4
– custom_xili_flag for admin side (admin side flag are uploadable – no need to take attention to name or type (.png, .jpg, gif)
– custom_xili_flag (frontend): if not ready or declared in customised theme, search in subfolder theme/images/flags (only .png)
– better selection of active widgets (new Categories widget with good counting if language selection must be enabled in 5th tab)
xili-dictionary : version 2.10.3 (Updated datatables js css – used in interactive table of tools)
– can import msgid of get_the_archive_title (introduced in WP 4.1)
– improves adding context only after draft state
– now able to use flags available in Medias Library (if xili-language is active)
Notes: images set as flag can be png et jpg and also gif – not necessary to also format the name of the file !
As usual, contributors are welcome to improve documentations and more…
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.