Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 16:00 8:00 – 16:00 8:00 – 16:00 8:00 – 16:00 8:00 – 16:00 -
- - - - - - -

Supporter timezone: Europe/Zagreb (GMT+01:00)

This topic contains 3 replies, has 0 voices.

Last updated by Nigel 1 day, 18 hours ago.

Assisted by: Diego Garcia.

Author Posts
February 25, 2026 at 8:16 am #17850016

felixS-23

In Elementor im using dynamic "Post Title" field for displaying my post title in my templates. In the dynamic post title field i set an prefix "Über " - this prefix is not shown in ATE or in string translations, so currently i have no change to translate it in english which should be "About ". How to translate that? Check the screenshot vor better understanding what exactly i mean.

I already tried to search for the exact string in ATE and also in string translations but it does not appear

February 25, 2026 at 11:58 am #17851226

Nigel
WPML Supporter since 02/2016

Timezone: Europe/Madrid (GMT+01:00)

Hi there

Let me try and help you with this.

First, I double-checked on a local test site that this is working normally, that the prefix text is available for translation, and I can confirm that it is.

From the screenshots you can see I added a prefix "Aardvark" (I chose such an unusual word that it would be easy to locate if I had to search for it).

I then used the Translation Dashboard to send the Elementor template for translation (by me, manually).

When I opened the translation job in ATE, the prefix text was offered for translation.

So my first question would be about how you translated the template. Did you send it for translation via the Translation Dashboard? That is the recommended workflow for translating templates, and if followed it should work.

If it is not working, do you have a staging site available for some simple testing.

I'd like to know what happens if you try the same workflow after deactivating the few plugins you have which are Elementor add-ons (e.g. the dynamic content for Elementor plugins) and switch from your child theme to the parent Hello theme. That would help identify if there is a possible conflict from one of these which is affecting the availability of the text for translation.

If the problem persists in that minimal environment then I think we would need a copy of your site to be able to investigate more closely. Would you grant permission for me to install the Duplicator plugin and take a copy of the site to install locally?

I will set your next reply as private in case the next step does involve taking a site copy, for which I will need the login credentials from you.

Screenshot 2026-02-25 at 11.45.35.png
Screenshot 2026-02-25 at 11.42.12.png
February 25, 2026 at 12:53 pm #17851590

felixS-23

Hi Nigel, i also tried this and also tried to completely start the translation new but its still not showing in my ATE. Could it be that its the case that im using an "Elementor Single Page Template" for a custom post type? So its type "Elementor Template"

February 25, 2026 at 2:05 pm #17851789

Nigel
WPML Supporter since 02/2016

Timezone: Europe/Madrid (GMT+01:00)

Every variant of template I create in Elementor to display posts (whether standard posts, pages, custom posts etc.), or even just a section template, it always seems to create a template whose post type is elementor_library.

I don't seem to be able to create anything with post type Elementor Template.

All of the templates I have made, where I have used a prefix for the dynamic post title, in each case the prefix text has been available for translation in ATE.

So, perhaps you could

1. confirm that your workflow is to send the templates for translation from the WPML Translation Dashboard, and

2. give me some specific steps showing how you create a template of the type "Elementor Template".

If we can rule out that the different template types is significant then we can move on to trying to locate the problem on your site.