JCV

@rsouzaam thanks for sharing the good news. Indeed, latest release fixed the notice.
Thanks guys for your work, much appreciated!

@barn2support I deactivated all plugins but Post table, and still facing the bug.
I switch the blog’s language to English (UK), no more notice. I switched back to French, the notice is back.
I tried to use various WP themes (2025, 2024, etc), notice is always there.

Did you try to change the WP’s default language?

For the record: Wpforms Lite issue introduces also a similar notice for OceanWP users.
For those using both wpforms and oceanwp, they get two notices; the issue is related to wpforms, not to oceanwp, they checked their plugin.

Thanks @skalanter

I debugged on my own a bit, and found out that when I activate wpforms lite plugin, a notice regarding that very plugin and oceanwp is thrown.

I’m gonna investigate first with wpforms-lite plugin makers. Will get back to you should I find an issue related to OceanWP.

Thanks! Closing for now.

Thanks @rsouzaam!

For the records, I’m using an English (UK) WordPress install, with Polylang plugin in French (but deactivating Polylang doesn’t change anything about the notice).

Cheers,

Thanks, I’m using a development environment ?? Just reporting the issue.

I’ve been reporting to all plugin/theme makers I could ??

Hi @skalanter
The message I copied-pasted was the wrong one, sorry. I’ve been warning a lot a of plugin/theme makers lately, I confused some of them.

However, I confirm that very same notice appears with WP 6.7. Here is the correct message:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the oceanwp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Thanks in advance

Hi Edge @barn2pluginsupport

I just reopened the ticket, since WP 6.7 has been published today.

Once the new plugin release will be out and will address the bug, I will close it.

I confirm, thanks @wpchefgadget!

updated to 2.26.14 and the notice persists.

done ??

This worked, thanks @theluckywp !

Thanks! Looking forward to the fix. Thanks so much for your great plugin!

Hi @vmarko

This is great, thank you so much! Looking forward to next release of your plugin!