I'm working on a directory site that will be available in multiple languages (using WPML). All users should see taxonomy terms (e.g. category of directory entries) in their language. The entries on the other hand are language independent, so all users share the same objects, no matter what language the creator speaks.
So I've created:
- custom post type "location" --> set to "not translatable" in WPML
- custom taxonomy "location-category" --> set to "translatable"
All location category terms are nicely translated. But I run into tons of problems:
- Shortcodes like [wpv-post-taxonomy type="location-category" format="name"] or [wpv-post-taxonomy type="location-category" format="slug"] don't seem to output the other languages version (location created in EN, displayed in DE --> location-category name or slug are empty)
- Filters for views show only the translated versions of location-category (based on user language), as expected. BUT when actually applying a filter, only those locations are picked up that have been created in the users language. Those locations created in another language, having a translated version of location-category assigned to them, are missing (but will show when switching to that language).
Any ideas about that?
Another option would be to NOT make location-category translatable, but use string translation instead to translate the term names and descriptions. Unfortunately they don't show up in string translation module. Is there a way to achieve that just using Toolset and WPML capabilities?
