[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.
It might also help after refreshing the repository info from the WordPress Dashboard > Updates page. Refer to the attached image for more details.
If the bug exists, please try the following steps and let us know your feedback.
1) Make sure to make a complete backup of your site, files, and database before proceeding
2) Go to PHPMyAdmin and select the database
3) Open the wp_options table
4) Delete the wp_installer_settings key
I verified the key matches what's present on the https://wpml.org/account/sites/ (it's pasted directly from that page), and the URL matches what's visible on the local site I'm testing with.
I found and deleted the wp_installer_settings record in wp_options. Refreshing the Plugins page after that made the error message about the constant go away, but the registration status did not change on the page. I additionally rechecked for the wp_installer_settings record on the database and it had been readded (it was for sure a different record, the option_id had changed). Refreshing the Plugins page once more showed the OTGS_INSTALLER_SITE_KEY_WPML constant error was back.
Thank you for the updates. Please visit WPML>>Support>>Installer Support and check whether you are getting any warning messages. Refer to the following article for more details.
I am not testing this on the hidden link production site, as I do not have direct code access (code must be deployed through a lengthy process) and testing this intentionally provokes an error (not something we want on a production site). I am testing on my LOCAL environment, which means I am trying to register on hidden link . It has it's own distinct key on the WPML account page, and that's the key I am using. I don't have a way to securely demonstrate the key I'm using, but maybe I can explain that it is my only key starting with a capital "J" and ending with a capital "N".
I access the installer log and it came with several instances of the error "wpml: Unable to register: Site key not matching". I've attached a screenshot showing the whole screen with the errors beginning at the bottom. Hopefully this might provide you with additional troubleshooting information, and will also allow you to verify what I said above about being on the local hidden link site.
Thank you for the updates. Please share the WordPress debug.log (not WPML debug information) with us so we can collect more details. Refer to these docs for instructions.
To enable the WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
Then the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug (visit the site backend pages it show the warning and also the Installer Log page) and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).
Fortunately since I am on the development environment logging was already enabled. Unfortunately, debug.log did not have any WPML related errors. https://pastebin.com/KZEMNdNY
I'm in contact with my devops team trying to see if we can securely share that information, though I'm not sure how I would be able to securely forward it to you.
One of my team directors asked if there was any way we could schedule a live screen share, maybe through a Zoom or Google Meet. That way we could answer any architecture questions you might have immediately. Is that possible?
Thank you for the login information and details. The FTP credentials are working fine for me. However, the site is asking for an authentication code during login. Please check the following message.
An Authentication Code has been sent to the email address associated with your account. Look for an email with "Login Authentication Code" in the subject line.
Thank you for the updates. I can now access the site's backend. We would like to check if the issues still exist in a minimal setup. Therefore is it okay if we deactivate a few plugins on your staging site?
Also, could you please let us know which plugins are mandatory for your custom theme? This will help us to avoid any site crashes while deactivating plugins.
I might recommend using Health Check's Troubleshooting Mode to try disabling plugins without potentially breaking the site hidden link That said, you have permission to affect this staging site in any way you need.
Lots of plugins have some of their functionality called up the the theme unfortunately, so disabling them may break some aspect of the site. I know that major core functionality is provided by:
- Advanced Custom Fields PRO
- Ogletree Deakins Data Structures
- Ogletree Deakins Query
Thank you for the feedback. We will test it further and get back to you as early as possible. Please wait.
--
Thanks!
Bigul
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
