Skip to content Skip to sidebar

Home › Support › English Support › [Closed] Transferring sites to new accounts - new site keys are invalid

[Closed] Transferring sites to new accounts - new site keys are invalid

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
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -
- 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: 

This topic contains 10 replies, has 0 voices.

Last updated by Kor 2 months ago.

Assisted by: Kor.

Author Posts
February 12, 2026 at 2:45 pm #17817471

vivekP

As per previous support ticket filed, we are an agency attempting to transfer a client site to another custodian, which means that the WPML license the site is using must be swapped with a new one. We were instructed to hardcode these keys in wp-config.php but we still get the message:
"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."

The keys belong to an account held by dan.mcgraw@hopeindustrial.com, and are for the following sites:
hidden link
hidden link
hidden link
February 12, 2026 at 3:34 pm #17817606

Kor

Thanks for your patience. Here is the ticket. Please let me know once you have edited the wp-config.php file and removed all redirection code or any other entries that may be interfering with the registration process.
February 12, 2026 at 4:08 pm #17817727

vivekP

I have updated hidden link to disable all redirection code running in wp-config.php - please resume your diagnostics.
February 12, 2026 at 6:37 pm #17818342

Kor

Thanks for your patience. I will need to escalate this to our 2nd Tier Support for further investigation. I will get back to you once I've feedback.

February 16, 2026 at 4:58 pm #17826641

Kor

Thanks for your patience. I’ve received feedback from our 2nd Tier Support team, and they have asked you to follow the solution shared by another user in this thread: https://wpml.org/forums/topic/unable-to-register-live-site-key-on-site-hosted-with-pantheon/#post-14177555 . Could you please try and let us know how it goes?

February 18, 2026 at 7:36 pm #17833805

vivekP

I've looked at this response. I have coded the key switching in wp-config exactly as the reply indicates:

if (isset($_ENV['PANTHEON_ENVIRONMENT'])) {
switch($_ENV['PANTHEON_ENVIRONMENT']) {
case 'live':
define( 'OTGS_INSTALLER_SITE_KEY_WPML', '--redacted--' );
break;
case 'test':
define( 'OTGS_INSTALLER_SITE_KEY_WPML', '--redacted--' );
break;
case 'dev':
define( 'OTGS_INSTALLER_SITE_KEY_WPML', '--redacted--' );
break;
}
}

To note, the later line incorrectly references "defined" as the function to set the constant - it should be "define".

The text that follows is very unclear as to whether it is a reply to a previous attempt or if it's remarking on the code that is provided as the actual solution. I don't believe it is helpful in this case - if you disagree, I would appreciate being guided through the steps they have taken that is in any way different from the above approach.

To be clear, I haven't even gotten the DEV site to successfully register its key - there is no point to trying to register LIVE if we cannot perform updates on the DEV site properly.
February 19, 2026 at 1:11 pm #17836052

Kor

Thanks for your reply. Please allow me to check with our 2nd Tier Support and I will get back to you as quickly as possible.

February 19, 2026 at 6:43 pm #17836963

Kor

Thanks for your reply. Could you try using the custom code below instead? Please let me know how it goes. 

if(!defined('OTGS_INSTALLER_SITE_KEY_WPML')){
	switch($_ENV['PANTHEON_ENVIRONMENT']){
		case 'live':
			$site_key_wpml = 'your-site-key-for-live';
			break;
		case 'test':
			$site_key_wpml = 'your-site-key-for-test';
			break;
		case 'dev':
			$site_key_wpml = 'your-site-key-for-dev';
			break;
		default:
			$site_key_wpml = 'your-site-key-for-default';
	}

	defined('OTGS_INSTALLER_SITE_KEY_WPML', $site_key_wpml);
}
February 23, 2026 at 8:19 pm #17844359

vivekP

I included the code as instructed. Here is an excerpt from our log showing that it was detected:

[23-Feb-2026 20:17:08 UTC] [WP-CONFIG] Loading Pantheon wp-config.php for environment: dev
[23-Feb-2026 20:17:08 UTC] [WP-CONFIG] Defining OTGS_INSTALLER_SITE_KEY_WPML as f569...... for environment dev

Error still persists: "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."
February 25, 2026 at 7:40 pm #17852901

vivekP

NOTE: Due to the transfer of custody of the client site to another developer, I am asking for this ticket to be transferred to a different account: dan.mcgraw@hopeindustrial.com

A contact form submission from this account has just been filed. Please close this ticket and pursue further investigation with that entity instead. Thank you.
February 26, 2026 at 7:20 am #17854031

Kor

Thanks for your reply. Unfortunately, it’s not possible to transfer the ticket to another account. Instead, please ask your client to open a new ticket or start a live chat and refer to this issue: https://wpml.org/forums/topic/transferring-sites-to-new-accounts-new-site-keys-are-invalid/ so our team can review it directly.

The topic ‘[Closed] Transferring sites to new accounts – new site keys are invalid’ is closed to new replies.