Background of the issue:
Hi,
I'm new with both ACF and WPML and I'm building a site that is available in two languages: Dutch (NL) and French (FR)
I'm going to build a site where the client is using the Custom field (ACF) "Producten", which allows hom to add "products" to the site. My custom post type "products" consists of a few fields such as: "Title", "Description", "Dimensions", "Price",...
Some of those fields are the same in all languages (for example: price, dimensions, pictures,..). Other fields are different per language (For example: Title, Description,...). I thought it might be useful to build my custom post type in such a way that all fields are processed within 1 post. This means that I would make fields in my custom post type as "Title NL, Title FR, Description NL, Description FR, Price, Dimensions). With this approuch, my client would be able to simply fill in the form once, and immediately has the products in all the needed languages. HE really is slow with computers and this would be user friendly for him. This would save him time because he only has to enter things like dimensions, price, etc. once and immediately has the product in both languages.
I already have the basics for my website in Dutch, and now I'm adding the WMPL functions and the multilanguage part. However, I cannot see if this is a good Idea, and how to proceed in this.
My theme is Divi.
If you need more info: shoot!
Thanks!
Symptoms:
I cannot see if this is a good idea and how to proceed with implementing WPML for my custom post type.
Questions:
Is it a good idea to structure my custom post type with separate fields for each language?
How should I proceed with implementing WPML for my custom post type?
Welcome to the WPML support forum. Thanks for contacting us.
While waiting for one of my colleagues to help with this ticket, and based on what you've described, allow me to walk you through some initial debugging steps.
2. Once you’ve installed ACFML, I recommend setting the Multilingual Mode of your field groups to “Same fields across languages.” This option will automatically apply the most suitable translation preferences for each field type.
That’s a great starting point, and if needed, you can later switch to Expert mode for more control. For example, text fields are translatable by default, but if you have a field like “dimensions” and prefer not to translate it, you can change its translation preference to “Copy.”
In short:
- Go to "WPML > Support > Debug Information" (link)
- Copy the Debug Information from there.
- Find the private field I activated and paste that information.
Looking forward to hearing back from you.
Nico
The topic ‘[Closed] ACF and Divi’ is closed to new replies.
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.
