Please make sure to update to WPML 4.3.4 before reporting any issue
Hi, Amit here, I am the WPML Support Manager, our current ticket queue is high, update your WPML plugins and make sure you meet the minimal requirements for running WPML before reporting an issue please - many tickets are resolved doing that
Please look at our updated list of Known Issues and you can also use our support search to find helpful information and of course review our documentation before opening a ticket.
If you do need to open a ticket please make sure to provide us with all the needed information as described in this page
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This thread is resolved. Here is a description of the problem and solution.
Problem: How can I display all content for all languages using Fallback?
Solution: The fallback option only works for posts created in the default language. So, if you don't translate a post that is created in the default language, the secondary language will fallback to the default language. It does not work in the opposite direction, however. So you can't fallback to a secondary language if the post is not translated to the default language. So as far as your example goes, $fallback_language = default language. Fallback language cannot equal anything other than the default language. I hope this makes sense.
You can use this setting on any custom post types by going to WPML -> Translation Management -> Multilingual Content Setup.