load_plugin_textdomain not working anymore since wp 6.8

[canic]

Hey,

we have upgraded some of our sites, after 6.8 the page don't translate anymore correctly.

Its a Plugin, in the header we have
Text Domain: sw-immosuite

and in the init hook we call
load_plugin_textdomain( 'text-domain', false, dirname( plugin_basename( FILE ) ) . '/languages/' );

Anyone knows anything about it or has the same problem?

[swissspidy]

I hope this is just example code, but if your text domain is sw-immosuite, then you should use that in the load_plugin_textdomain() call. Not 'text-domain'.

If you otherwise have a minimal reproducible example code, e.g. in a GitHub Gist or so, that would be helpful.

I also recommend reading ​https://make.wordpress.org/core/2025/03/12/i18n-improvements-6-8/ to learn more about changes in 6.8. Though preventing translations from loading wouldn't be an intentional change :-)

[canic]

Hey,

thanks for your reply.

You're right, it's just example code.

I found out through WP Query Monitor that the .mo file is being loaded, but when I check the "Doing it Wrong" tab, I see one message from WP Core.

It's strange, because even when I remove load_plugin_textdomain and rely on the header comment for loading the text domain, it still doesn't work.

Replying to swissspidy:

I hope this is just example code, but if your text domain is sw-immosuite, then you should use that in the load_plugin_textdomain() call. Not 'text-domain'.

If you otherwise have a minimal reproducible example code, e.g. in a GitHub Gist or so, that would be helpful.

I also recommend reading ​https://make.wordpress.org/core/2025/03/12/i18n-improvements-6-8/ to learn more about changes in 6.8. Though preventing translations from loading wouldn't be an intentional change :-)

[canic]

Small update:
Found out when loading within "plugins_loaded" the language token get succesffully loaded.

When calling load_plugin_textdomain in the "init" action, the path doesn't get modified to plugins/path/languages.

Isn't init the right position to call load_plugin_textdomain? Or is it too late.

Replying to canic:

Hey,

thanks for your reply.

You're right, it's just example code.

I found out through WP Query Monitor that the .mo file is being loaded, but when I check the "Doing it Wrong" tab, I see one message from WP Core.

It's strange, because even when I remove load_plugin_textdomain and rely on the header comment for loading the text domain, it still doesn't work.

Replying to swissspidy:

I hope this is just example code, but if your text domain is sw-immosuite, then you should use that in the load_plugin_textdomain() call. Not 'text-domain'.

If you otherwise have a minimal reproducible example code, e.g. in a GitHub Gist or so, that would be helpful.

I also recommend reading ​https://make.wordpress.org/core/2025/03/12/i18n-improvements-6-8/ to learn more about changes in 6.8. Though preventing translations from loading wouldn't be an intentional change :-)

[canic]

Final update: We're using ACF PRO, and it seems there's a bug in ACF when combining load_plugin_textdomain and register_block_type while using i18n in blocks. I'm now creating a bug report in the ACF community.

Thanks anyway!

Replying to canic:

Small update:
Found out when loading within "plugins_loaded" the language token get succesffully loaded.

When calling load_plugin_textdomain in the "init" action, the path doesn't get modified to plugins/path/languages.

Isn't init the right position to call load_plugin_textdomain? Or is it too late.

Replying to canic:

Hey,

thanks for your reply.

You're right, it's just example code.

I found out through WP Query Monitor that the .mo file is being loaded, but when I check the "Doing it Wrong" tab, I see one message from WP Core.

It's strange, because even when I remove load_plugin_textdomain and rely on the header comment for loading the text domain, it still doesn't work.

Replying to swissspidy:

I hope this is just example code, but if your text domain is sw-immosuite, then you should use that in the load_plugin_textdomain() call. Not 'text-domain'.

If you otherwise have a minimal reproducible example code, e.g. in a GitHub Gist or so, that would be helpful.

I also recommend reading ​https://make.wordpress.org/core/2025/03/12/i18n-improvements-6-8/ to learn more about changes in 6.8. Though preventing translations from loading wouldn't be an intentional change :-)