[Resolved] Added ACF repeater items not shown in translation

Thanks, it definitely works better now. All repeater rows (posts) are present, in the original language and translation.

BUT in the API the related posts are still in the original language, even though they have a translation. The code works locally, this is how I build the response object:

```php
$id = $request->get_param('id'); // The ID is the post ID of the original language, or the different post ID of the translation
$portal = get_post($id);

$moduleSlug = $request->get_param('module');
$module = get_page_by_path($moduleSlug, OBJECT, 'module'); // This post ($module) is translated correctly, all fields are in the original language or translated language

$module->blocks = array_map(static function ($block) {
return $block['block'];
}, get_field('blocks', $module->ID) ?? []); // "blocks" now contains the correct related posts from the repeater field, unlike before, but just in the original language, not in the translation of $module.
```

That is good to know that it can work, thanks!

That may work in your example because the post (module) is loaded in the main query. But how do you get the translated posts if you do not have a main query, e.g. with `get_field('blocks', $module->ID)`?

By the way, the code I am posting at the moment is from the active theme "rest/index.php"

The first part is correct. For the second part:

We wrote a separate endpoint for the rest API, see the code above or the `rest/index.php` file. The URLs would be:

* Default: /wp-json/wp/v2/portal/195/module/innere-staerke
* EN: /en/wp-json/wp/v2/portal/195/module/psychological-resilience-bi

The code in question:

```php
$module->blocks = array_map(static function ($block) {
return $block['block'];
}, get_field('blocks', $module->ID) ?? []);

// Append the featured image to each block
$module->blocks = array_map(static function ($block) {
$block->acf = get_fields($block->ID);

return $block;
}, $module->blocks);
```
Where $module->ID is 439.

In your sandbox, yes. In our production environment, no.

That is what I initially thought, that everything is configured correctly but there is some kind of weird bug that you have to remove and add something again to fix this. I don't know.

Thanks, that was it. Alternatively, that's what I did, was to append "?lang=en" to the URL.

Yeah, I could confirm the issue. If I add another field to the original language (post type block), save it, delete it again, save it, and then edit the translation, all fields are there, untranslated. Just like you did with the module post. Do I have to translate everything again, or why does WPML not recognize that these fields were previously translated? Where are the translations gone?