_load_textdomain_just_in_time was called too early

Hi @beee,

I hope you are keeping well and thank you for reaching out to us.

We are aware of a similar issue, and our developers are actively working on a resolution. We hope to release a fix as soon as possible.

To help us narrow down the cause of the issue, could you please confirm if you are using the Cloud engine to scan for broken links?

Kind Regards,
Nebu John

I am NOT using the cloud solution, nor do I want to.

I don’t like sharing info like this in a cloud.

Hi @beee,

I’m afraid, I’m not sure whether I understood your last reply. The mentioned logs are notices and it shouldn’t be affecting the workflow of the website. The logs are more related to compatibility and not specifically related to the cloud.

We are already working on a fix and it’ll be soon addressed in the next release.

Sorry for any inconvenience due to that.

Regards,

Nithin

I understand they are notices, but as a developer I work on the development side where there are debug logs active.

Because of this notice (and similar ones from other plugins) the logs are flooded and real error/debug messages get buried.

The answer reg. the cloud is just an (extra) opinion to the question whether I use the cloud engine to scan for links.

• This reply was modified 6 days, 22 hours ago by Beee.

Hi @beee

Thank you for the information.

As my colleague explained we are working to improve it across all the plugins, for local development a possible workaround now is to suppress the Notices https://stackoverflow.com/questions/2867057/how-do-i-turn-off-php-notices keeping warnings and fatal errors.

I understand isn’t an ideal solution but our developers are working on a fix so I hope we can release it as soon as possible.

Best Regards
Patrick Freitas