WPML single post layout

Support
#1

I’ve created a single layout for a custom posttype. That custom posttype used a lot of ACF-fields for its content. Thanks to the amazing flexibility of Loopers, I’ve been able to create a very flexible way of generating content that’s easy to manage and shares a consistent layout. Hooray for Pro on this :partying_face:

The catch: WPML is not translating any single part of this Single Layout. Not the ACF-fields, but also not the text-elements of the single layout. Nothing.
After years of struggle with Pro / WPML, it looked like things got better after migrating from shortcode-storage to HTML-storage, but as it turns out I’m running into issues now I’ve started using a Pro Single Layout.

I’ve also created an archive-layout for this CPT, which shows similar issues.

I’ve shared the real world example in a private note, but I’d be happy to share the solution as a public post, hoping this might help others in the future.

#2

Hello @dhunink,

Thanks for writing in!

You need to translate your custom single layout as well.

  • See the screenshot below

Even if you have translated your custom post item, like the arcade cabinet, since it is using the custom single layout, that layout must be translated too.

Hope this makes sense.

#3

Hi @ruenel,

That would be this setting in WPMl, right?

Scherm­afbeelding 2025-10-31 om 11.24.48
Scherm­afbeelding 2025-10-31 om 11.24.481432×150 9.98 KB

I had that one on earlier, and switched it back on again for the purpose of testing. The result: the page is not displaying anything anymore, as you can see at the url shared in the private note

#4

Hi @dhunink,

I have checked the English version of the page, and it seems that no content has been added. You need to add the translated content manually to get the output.

Hope it helps.
Thanks

#5

Hi @tristup,

the english version is not the original version, that;s the Dutch one, and that one does has content, like the rest of the site. See the secure note on the original post.

#6

Hi @dhunink,

The translation process is not automatic — you’ll need to add the translated content manually for each language you’re supporting. This means that the content in English and German should be added separately to match the base language of your website.

Hope I am able to explain it.
Thanks

#7

Hi @tristup,
that’s not how all other translations on the website works: pages and blogs are translated automatically. In previous discussions, including the beta-section, it was confirmed that the route using the language switcher in Pro is no longer the only route possible. I’m totally confused now.

Could you please check with team-members?

#8

Hi @dhunink,

The WPML’s Translation Editor will not work for Cornerstone Layouts, and does not translate the text. Please go through the following thread on a similar topic.

Thanks

#9

I am quite surprised, to say the least. We started a seriously huge project converting dozens of pages to a custom post type, fully based on the premise that WPML works Pro, after checking and double double checking https://theme.co/docs/wpml. After weeks of hard work and amazing results in Pro with the single layout and archive view, we now have to conclude that Pro is NOT working with WPML on all aspects, if I read the topic you mentioned correctly?

That would be a seriously issue, one we can not easily tackle. Somehow we really need a solution to have the CPT-posts to display in the translated texts as well. If we have to add custom code or, as done in the past, custom WPML configuration settings, that’s okay for the time being.

How are we going to make this work?

#10

Hi @dhunink,

I had a discussion with our development team lead, and he suggested reaching out to the WPML support with this. They might be able to help you on this.

Thanks