The 2 issues always happen in my production site:
1. Api error missing resource: No sitekey found for this website -- Unregistered and re-registered many times already
2. PHP Fatal error: Uncaught InvalidArgumentException: Argument $language_code must be a non empty string
To investigate the issue, I need to be able to see the errors on the site I am working on.
On hidden link such errors do not occur in the debug.log so far.
I can only see this warning relative to WPML so far:
PHP Warning: Undefined array key "REQUEST_METHOD" in /home/sensutoy/public_html/wp-content/plugins/sitepress-multilingual-cms/addons/wpml-page-builders/classes/Shared/st/class-wpml-pb-integration.php on line 177
Possible steps:
- Create a new staging and make sure the errors are occurring there too
- Provide me again access to the live site
(Currently password is not valid for admin access to hidden link, and FTP access is not working: Timeout detected. (control connection) Connection failed.)
I am sorry, but you are not answering my questions:
Where do you see the error? Which is the date of the latest entry? Please send me a screenshot.
On hidden link I could not confirm any "PHP Fatal error: Uncaught InvalidArgumentException" error in the debug.log, and I have no access to the server's error_log.
On the staging currently not any errors are found. This might be because it is unclear what is actually triggering this error.
If the error occurs only on the live site, then I need access to the site where I can see the error. I would then take a local copy for debugging.
Please check the video record. It showed where the error happens:
hidden link
On racinghobby.com, I didn't notice "PHP Fatal error: Uncaught InvalidArgumentException", but
"Api error missing resource: No sitekey found for this website" is logged.
Or should I submit another ticket for "Api error missing resource: No sitekey found for this website"?
According to your video, the error "PHP Fatal error: Uncaught InvalidArgumentException" seems not to have occurred again since the 9th of October. If the error occurs again, please let me know.
The error "Api error missing resource: No sitekey found for this website" would mean that the site has an issue with the usage of the Advanced Translation Editor and the usage of credits for automatic translation.
On the staging, the last entry for this error was on 2025/10/11, and after using the Advanced Translation Editor on this site, the error did not occur again, which means that this issue no longer occurs on the staging, or it does not occur as the staging has no credits for AI translation.
If the error keeps occurring with new entries on your live site and you have issues with using the Advanced Translation Editor or the usage of credits for automatic translation, please provide me access to the live site, as I can no longer log in.
When I reported the issue at the beginning, it appeared in server error log. At the time, wp debug was not on. Not sure why it didn't appear in the server error log now.
I didn't notice it in staging site's wp debug log. I didn't use staging site recently.
I can't provide access to live site now, as an ad campaign is running.
On the mentioned ticket, I only find access to the staging site and no download link for a site package.
If you can not provide access to the live site, I suggest you set up a new staging, enable WP DEBUG, and confirm if the error occurs on the staging, too.
The provided password does not allow me to access this site. I can currently not access the live site or staging site with any of the earlier provided credentials.
Note that you had already provided me access to this staging site earlier, and I was not able to confirm the error "PHP Fatal error: Uncaught InvalidArgumentException".
Before providing access, please ensure that this error actually occurs with the current date on the debug.log.
For the second error:
This is a site-specific error. It needs to be investigated on the live site.
Do you need this staging site to operate with automatic translation, or was this site only created for troubleshooting?
Have you maybe switched the site's default language from German to English, or was the site maybe earlier using a different language that is no longer active on the site?
Would you agree if I install a plugin to take a closer look at the database?
About the error:
This error is triggered because WPML’s WPML_Translation_Element::get_translation() method is being called with an empty $language_code, which violates its contract and throws an InvalidArgumentException.
In this case, the call originates from:
WPML_Media_Attachments_Duplication->get_translated_attachment_id()
Which is used during Bricks media translation via translate_bricks_media()
Basically, it looks like there is some corrupted media on the original content, which might not have a language association inside WPML's database tables.
What I did:
1) Made use of WPML > Support > Troubleshooting to set language information for all contents, clearing WPML's cache, and deleting ghost entries.
2) Synced the media at WPML > Settings > Media Translation. To do this, I disabled "Automatically detect best options for translating image texts (alt, caption, title)", then clicked "Setup manually" and ran the sync option for existing content.
Sadly, this did not yet solve the issue. Once you edit the original homepage and save it, the error pops up again.
Except the errors, I didn't find any issue in frontend or using your features yet.
I never changed the default language, but I have added 2 secondary languages and then gave up and used only 1 secondary language which was done before I started translation. Maybe this is the culprit.
You can install a plugin to check the database.
The topic ‘[Closed] PHP Fatal error: Uncaught InvalidArgumentException:’ is closed to new replies.
