This thread is resolved. Here is a description of the problem and solution.
Problem: You are using WPML with ACF Multilingual and have encountered an issue where the custom post type's permalink works as expected in the primary language (English), but the permalink structure is broken in a secondary language. Solution: This behavior might be expected due to the design of ACF's custom post types (CPT) functionality, which may not fully support multilingual permalink structures. We recommend setting up a staging environment to conduct further tests and identify a possible solution. If this issue persists, check if the post is published as a Draft.
100% of people find this useful.
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.
Background of the issue:
We are using WPML + ACF Multilingual and we found a problem. ACF now supports the creation and management of custom post types and taxonomies. We would like to use its custom permalink function for some post types. Link to a page where the issue can be seen: hidden link
Symptoms:
The custom post in English (the primary language) can be referred to with the customized URL as we expected. However, the permalink structure for the custom post in a secondary language is completely broken. You can see the broken URL in the language switcher.
Questions:
Who is responsible for this issue, WP Engine or onTheGoSystems?
The articles you cited are regarding the custom archive slug.
But the issue I reported is regarding the custom permalink of single custom posts.
Besides, when we use another plugin, Custom Post Type UI, it works perfect.
Sorry that the translated post was private.
The permalink of the Chinese custom post looks like: hidden link
We hope this issue can be fixed.
Thank you for your support any way.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
This is likely expected behavior when using ACF’s CPT functionality, as some components aren’t supported due to how ACF CPTs are designed. Do you have a staging environment where we could run some tests?
Oops! It was our mistake. The Chinese post is not even a private post but is a draft.
Sorry for making an inappropriate report.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
