This plugin Events Made Easy don’t use custom post type but add eleven (11) tables in the WP DB. xili-language is not made to manage customised added tables but custom post type and custom taxonomy as used – for example – by bbPress or WooCommerce…
If a plugin uses core WP rules, xili-language can be easily improved… but here definitively not possible…
M.
Plugin Author
Franky
(@liedekef)
In my defense: the plugin exists for a very long time, from before wordpress had custom post types. Changing it all will be a huge undertaking.
But if you add ‘?lang’, it should work when I include the xili API for translating strings.
Hi Franky you are great, think this might be helpfuel.
I am not a pro in this thins, maybe Michel from xiligroup want say something about this.
I’d like to spend money for both plugins when I go productif onlyn.
Thank you so much….Theo
@franky,
You are right, all terms displayed by a plugin using gettext functions like __(, or _e(, or… can be shown translated ‘live according current language’ if available in plugin or local .mo file with mechanism introduced by plugin as xili-language since 2009. For the others coming from specific tables of db, it depends from data architecture.
As you know internationalisation is not exactly live multilingual translation…
M.
Hi Franky,
thank you for the update 1.5.26 of the plugin.
A short question, is the language support for xili part of this update to?
All the best Theo
Plugin Author
Franky
(@liedekef)
I’ll try xili later on, I still need to completely integrate qtranslate-x first.
Hi Franky,
sorry that I reopen this Post.
I saw you integrated almost successful qtranslate-x, thank you for this major step.
How it looks now for xili support.
I will very delighted when this can follow now and would also spend something to push this.
Think xili is somewhat forgotten.
All the best Theo
