We use ACF Pro to setup some CPTs like this one here (some ACF php code to demonstrate the case/code from ACF)
------
'has_archive' => 'dp-comments-branchendaten',
'rewrite' => array(
'slug' => 'dp-item-branchendaten',
'feeds' => false,
),
etc
------
The CPT archive page is correctly shown at domain.com/dp-comments-branchendaten and posts at domain.com/dp-item-branchendaten/item-1
We have another language setup with WPML, and we only see an option in WPML settings to translate "dp-item-branchendaten" to other languages, but not the slug for "dp-comments-branchendaten" itself, that is used as the post type archive page slug.
I understand the issue you're having and will try my best to assist you in this matter.
Since you're using the ACF PRO plugin, it's important to also install the "Advanced Custom Fields Multilingual" plugin on your site to ensure ACF functions correctly with the WPML plugin. Please check the documentation below for more information.
You can install and activate the plugin from Plugins > Add New > Commercial tab.
To enable the translation of the Slug for the Custom Post Type (CPT) that's registered programmatically, the 'has_archive' value needs to be set to 'true'. By defining a specific string as a value, you're defining the same slug for default and secondary language.
Please refer to the documentation provided below for guidance on how to make the slug of a programmatically created CPT translatable.
Do you agree, that your extra Plugin ACFML is not doing anything regarding the new features Custom Post Types in ACF? To me, it looks like this plugin handles only field groups.
Anyway, is it correct, that if a CPT is setup with
---
has_archive = true
---
WPML can translate this on the Settings page (tested an works well). But not if we use a custom slug like this example
---
has_archive = 'slug-to-archive-page'
---
Is this statement correct?
Thanks.
Best Regards
Andi
The ACFML plugin is essential for managing the translation of fields within a field group. This is indeed not required if the custom post type is created using ACF, as WPML itself can handle post-type translation.
The statement is totally correct! Setting the 'has_archive' value to 'true' makes the slug translatable. Conversely, if you define it as a string, it becomes the fixed slug for both the default and translated post type, which cannot be translated.
Since setting 'has_archive' to 'true' was successful for you, please proceed with this method to translate the slug.
I hope you can understand. Please let me know if you need further assistance or clarification in this matter. I will be happy to help.
