# Fixing WordPress block translations

**URL:** https://forum.pinegrow.com/t/fixing-wordpress-block-translations/8049
**Category:** Pinegrow WP
**Tags:** wordpress, blocks, feature-request, bug
**Created:** [May 22, 2023, 6:50pm UTC](https://forum.pinegrow.com/t/fixing-wordpress-block-translations/8049 "2023-05-22T18:50:08Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![madjedo](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@madjedo](https://forum.pinegrow.com/u/madjedo)
#### Post date: [June 29, 2023, 11:40am UTC](https://forum.pinegrow.com/t/fixing-wordpress-block-translations/8049/5 "2023-06-29T11:40:07Z")

</div>

So I dont use translatepress. But for WPML i noticed blocks that were also containing some embed media like a youtube video or a block with a inner content block had some issues.WPML would detect strings and I could translate in the back-end, but nothing gets translated on the front-end.

Then I had just random issues with other blocks were certain headlines or paragraphs just did not get translated. And these are not complex blocks. Just paragraphs, headlines and images. Actually the more advanced blocks seems to be working better.

Did some quick testing using the new hybrid blocks. In summary: nothing works at all with them for me.

I don’t understand much of what the topic starter wrote down, but they sure seem to have forgotten to include some things that would make Wordpress understand or recognize certain strings for some block types and is probably why I’m also having same issues.

And I don’t think any of this got addressed on the latest release?

---

_[View the full topic](https://forum.pinegrow.com/t/fixing-wordpress-block-translations/8049)._
