Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

Tagged: 

This topic contains 58 replies, has 2 voices.

Last updated by Andreas W. 1 month, 3 weeks ago.

Assisted by: Andreas W..

Author Posts
October 19, 2025 at 9:00 am #17496594

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

The issue seems to be caused by the usage of the last image inside the first container of your homepage:
hidden link

Title: sg4001 02bu 5
Attachment ID: 13506

Until now, I have sadly not been able to find out why this media file is causing an error, and I need to ask you for some more patience.

The cause for the error seems to be that you are using a Post Query Loop while calling an image that is not part of the current post.

If you set the dynamic image source {featured_image} for this image, it solves the issue. See screenshot.

This said, even if you see an error coming from WPML, then this might be expected in this case, as your Post Query Loop is using unexpected data that has no relation to the currently visualized post.

image.jpg
October 20, 2025 at 3:43 am #17497442

rhettY

Glad we've found the culprit.

Is this related to both errors? or just to "Uncaught InvalidArgumentException: Argument $language_code must be a non-empty string"?

October 21, 2025 at 4:17 pm #17503845

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

This was only related to "Uncaught InvalidArgumentException: Argument $language_code must be a non-empty string" - can you please confirm if this solved the issue on your live site?

Regarding:
"Api error missing resource: No sitekey found for this website"

You said you do not experience any issue with:
- Advanced Translation Editor
- Automatic translation
- Assignment or usage of credits
- Glossary or translation memory

This makes me think that this error might be a false positive.

Question:
Are you going to use automatic translation on both websites or only on the live site? Would this error require fixing on the staging site?

If you have the same error on your live site hidden link and the site does not operate as expected, then I need access to this site again, as none of the earlier provided credentials are allowing me to currently access the site.

October 22, 2025 at 1:57 am #17504845

rhettY

Same issue on live site

We can't test on live site now. It's running ad campaign

October 22, 2025 at 5:25 am #17505001

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Please go to WPML > Support > Troubleshooting and send me a screenshot of the section
"Your Automatic Translation account id is".

Further, please send me a screenshot from the current ATE Error Log at WPML > Support > ATE Error Log.

Also, please revise WPML > Support > Installer Support and click "Check now". Revise if the API connections and site key registration are working as expected.

Finally, if possible, please confirm if the following features work as expected:
- Advanced Translation Editor
- Automatic translation
- Site Assignment or usage of credits
- Glossary or translation memory

October 22, 2025 at 5:42 am #17505039

rhettY

Automatic Translation account id: 63326234-6363-5735-b662-363262323733#wfprchAipqVmJVQQaL4M4wtt

ATE Error log: hidden link

WPML > Support > Installer Support and click "Check now": all green check

I didn't find any issue using following features:
- Advanced Translation Editor
- Automatic translation
- Site Assignment or usage of credits
- Glossary or translation memory

October 22, 2025 at 5:48 am #17505057

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

This seems to be a false positive, as on the system, it all looks correct.

Can you please confirm at WPML > Translation Dashboard > Translation Tools that the site currently has 41112 credits available?

October 22, 2025 at 7:42 am #17505688

rhettY

Yes there are 41112 credits

October 22, 2025 at 11:00 am #17506854

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

In this case, I would suggest that for now, you can ignore this error, as long as the site operates as expected.

I am escalating the issue to the second-tier support for further revision.

Please let us know when we can take a look at the live site, in case further assistance is needed.

October 23, 2025 at 2:17 am #17510393

rhettY

Ok.

October 30, 2025 at 6:14 am #17531123

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

The second-tier support informed that the issue on your site can only get solved in the following way:

1) Go to https://wpml.org/account/websites/

2) Delete the site URL from the list.

3) Now enter the site URL again. This will create a new site key.

4) Click "Show key" and copy it.

5) Enter the key under Plugins > Add New > Commercial (tab) to re-register WPML. If WPML is already registered here, unregister it first.

If the problem persists after registering WPML with a new site key, please let me know.

October 30, 2025 at 12:29 pm #17532631

rhettY

I've done this several times.

Anyway I will try again.

October 30, 2025 at 8:21 pm #17534260

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Our apologies for the inconvenience!

If those steps do not solve the issue, please let me know.

November 12, 2025 at 11:22 pm #17572988

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

We sadly did not hear back from you within the last two weeks.

Please let us know if further assistance is needed, or simply mark this ticket as resolved.

Best regards
Andreas

The topic ‘[Closed] PHP Fatal error: Uncaught InvalidArgumentException:’ is closed to new replies.