Background of the issue:
I am trying to display the translated content of our custom post types using a custom template within our custom block theme. However, the translated content is being displayed using the default single post template instead. We have explained the issue in detail in the video linked here: hidden link. The issue can be seen on this page: hidden link.
Symptoms:
The translated version of custom post types is displayed using the default single post template instead of the intended custom template.
Questions:
Why is the translated content using the default single post template instead of the custom template?
How can we ensure the custom template is used for translated content?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
The Site Templates and Templates Parts of your Block Theme are available for translation at WPML > Translation Management > Dashboard.
Have you already translated those templates?
Note:
You might run into display condition issues with templates if you try to edit templates inside the Site Editor in a second language. In such case, you need to apply the workaround found in the following errata:
We haven’t yet translated the templates or template parts associated with our custom post types, and we’re seeking clarification on the correct process.
Do we need to translate the custom post type templates before translating the custom post type content?
We reviewed the documentation you provided, but it’s still unclear whether template translation is a required step. To test this, we translated the template for our resource custom post type into German and then checked the translated content. However, the German content is still displaying using the default single post template instead of the custom single-resource template. As a result, we’ve removed the translated template for now.
A few key points for context:
1) We have custom templates for each custom post type.
2) The template for resource works fine in the default language (English).
3) We’re unsure whether enabling slug translations for custom post types is necessary to resolve this issue.
Could you please guide us through the correct steps to ensure that translated content for custom post types loads with the correct custom template on the frontend?
