[Resolved] You are using an invalid site key defined as the constant
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue with WPML registration despite using the correct 10-character alphanumeric site key. The error message indicates an invalid site key defined as the constant OTGS_INSTALLER_SITE_KEY_WPML, likely in wp-config.php. Solution: 1. Verify the site key for case sensitivity and ensure it matches exactly what is provided in the WPML account. Use the following code snippet to check:
2. Refresh the repository information from the WordPress Dashboard > Updates page. 3. If the issue persists, follow these steps: - Ensure a complete backup of the site, files, and database. - Access the site's database via PHPMyAdmin. - Navigate to the wp_options table and delete the wp_installer_settings key. 4. Check for any warning messages in WPML>>Support>>Installer Support. For more details on checking the installer support log for errors, visit WPML support documentation. 5. Consider potential conflicts with caching mechanisms or specific architectures like Bedrock that might affect key validation.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please contact us through the WPML support forum.
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.
Thank you for the details. The issue is existing after the initial testing on your site. It shows the following warning in a minimal setup.
You are using an invalid site key defined as the constant OTGS_INSTALLER_SITE_KEY_WPML (most likely in wp-config.php). Please remove it or use the correct value in order to be able to register correctly.
I have one question: In which file do you add the *OTGS_INSTALLER_SITE_KEY_WPML* code? It does not appear in the wp-config.php file or functions.php of your theme.
We are still working on this. Just to make sure, please visit https://wpml.org/account/sites/ and make sure you are registered for the staging with hidden link URL or hidden link URL.
Because the site admin URL is hidden link and hidden link is showing the following error now.
This page isn't working
*****.site redirected you too many times.
Try deleting your cookies.
ERR_TOO_MANY_REDIRECTS
We are registered under the hidden link domain. Are you trying to say we need to be registered under the hidden link domain?
I'm still able to access the back end of the site through hidden link as I still am logged in, but I can confirm I am also seeing the ERR_TOO_MANY_REDIRECTS on the front page of the site. We haven't made any changes to the site. We also don't see any code changes that might have caused this issue (we noticed the addition of duplicator and twentytwentyfour and not much else). Using my backend access to the site and the Site Health Troubleshooting tool I can confirm that enabling sitepress-multilingual-cms (WPML) is what is causing the redirect issue.
Since it's not a code change, I'm assuming there was a database change that caused this redirect issue. Would you like us to "reset" the staging site by pulling a working copy of the database into it and recreating the test admin account? Or do you know the cause of the issue and can move ahead?
We are using that same structure with our live site. It's the same structure through all of the sites we're currently using with WPML. It's a side effect of being on the Roots Bedrock architecture; that's just where the WordPress folders and files are in the filesystem.
Sorry for the late response. We were looking for a possible workaround for this. Unfortunately, we are unable to reproduce the issue exactly on our testing servers and sites.
While checking through SFTP we see that there are 3 environments and 3 keys defined in your setup. Normally, this shouldn’t cause any issues. However, if the data is cached (such as in deep op cache or object cache), it’s possible that this could lead to some misinterpretation. Maybe it will be a conflict with Bedrock architecture also.
Therefore please check it and let us know your feedback.
