Problem: You are developing a site with a custom post type set as not translatable and are using the
wpml_active_languages
filter to input a custom language switch. However, on the singular page of the custom post type, this filter returns an empty array, preventing the display of the language switch, although the page displays in the correct language when linked from a normal page. Solution: The issue arises because the custom post type is set as not translatable, meaning it does not have any language information. WPML cannot retrieve language info or use second-language URLs for such content. To resolve this, you have two options: 1. Use the "fallback" mode (display as translated). 2. Set the post type to translatable. It's important to note that the availability of second-language URLs when the content is marked as not translatable is a known limitation/bug, planned to be fixed in a future release. If you're looking to translate elements like the footer or header, that depends on how they're implemented (via templates, widgets, PHP, etc.).
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
Problem: You have a custom plugin with a custom post type. When the site's current language is set to a non-default language, such as Dutch, and you create a custom post type, it is only associated with the current language. You tried using
'lang' => 'all'
in WP_Query parameters without success. The issue is that when performing a WP_Query for the custom post type, only records in the default language are shown, filtering out records in other languages. Solution: To include custom post types in all languages in your WP_Query, you need to use the
suppress_filters
argument in your query. Here's how you can modify your WP_Query: 1. Set
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at our support forum.
