Hey Chris,
Unfortunately currently still not possible to support tag for multilingue yet.
I did discuss this with our team regarding this in previously, we still looking for the better way to solve these complexity and technical issue, one of the complexity issue is tag suggestion from the composer.
Imagine if I create following tag which assigned to specify language :
- tag1 - English
- tag2 - Germany
If the user logged in English site and compose a new blog post but user want to create a blog post under Germany language,
so this tag suggestion will fail, because it will always show those suggestion tag from English instead of Germany, it actually based on the current user viewing that language page.
But this will work if the blog post already published is because system already know this blog post already posted under this Germany language.
Another complexity stuff is save draft process :
Imagine if the userA create a blog post but userA just save as draft for this post first before publish.
These following is the current post options as what that userA set.
- post language selection - English langauge
- post tag (tag1, tag2) - all these tag will store in English language
These English tags (tag1, tag2) already stored in database.
Another day, userB create a new blog post and added the same tag, but he will realised these tags (tag1, tag2) someone already created before,
so it will show these tags suggestion on that composer tag field, then userB insert these tag and publish the blog post under English language.
After that, userA editing his draft post and decide to change that post language to Germany language and publish the blog post.
So these tags (tag1, tag2) will store it under this Germany language.
It will affected the one userB created that blog post which posted the same tag because these tags already stored in Germany language.
We actually need to cater for all these complexity stuff before we implement support tag multilingue, if not everything will become messy since Easyblog is not a small component, it involved a lot of features which can associated with the tag.
By the way, we'll see if we can find a better way to sort out all of these complexity stuff.