[Resolved] ways to register WPML apart from plugin-install-dot-php ?

Hi Mihai, thanks for sharing this.

Unfortunately, here's the reason that I wrote that "I know that we can in theory set a PHP constant with the registration key but that's problematic in our case, also related to our hosting setup."

We can't add our license keys to wp-config.php because that's part of our git code repository, and we can't add license keys to our code due to security policies.

Is there a way to handle this within the WordPress UI? There used to be some other URL where we could register WPML because that's what I used in the past to register WPML in production on Pantheon and it was working for almost two years until this week, and now I can't seem to find the URL or documentation about this other UI option.

Thank you, Mihai. Based on what you shared, I created a workaround for wp-config.php which enables us to use this constant but also keep the license keys out of our code repository for the sake of security -- never put license keys in your code repo! -- and flexibility in case we need to quick add or edit keys.

If it helps to share it here for others who use Pantheon, this is the solution that I created:

We now store WPML license keys inside of text files, where the name of the text file matches the Pantheon environment name or the local Lando subdomain.

So the license key for the live environment is `live.txt`, a multidev env named 'wpml' would use a key named `wpml.txt`, and a local env with a URL like `mylocalenv.lnod.site` would use a key named `mylocalenv.txt`.

We place these keys in a path that is private and *not* under version control, and Pantheon provides an existing path helps with this:

wp-content/uploads/private/

On Pantheon, that's a symlink for this path:

/files/private/

We use SFTP to create text files within a 'wpml' subfolder that we created within this path, and we insert the license keys into our text files.

From there we have the following code within wp-config.php to load the correct license key files automatically.

I hope that this helps anyone else who is facing the same problem, who needs a secure, flexible solution.

/* 
 * Define WPML license keys, based on environment name
 * 
 * For example, a multidev domain named 'wpml' would have a license key file named 'wpml.txt'; the live env would use 'live.txt'; and Lando envs like 'localwww.lndo.site' would use a file named 'localwww'.
 * License keys are stored within this folder, managed by SFTP: wp-content/uploads/private/wpml/ , aka /files/private/wpml on Pantheon
 * This path is not under version control, intentionally, to keep license keys out of our code repo for improved security and flexibility.
 */
if ( isset( $_ENV['PANTHEON_ENVIRONMENT'] ) ) {

	// Prepare the license key path, where we'll find the WPML license key files
	$wpml_license_key_path = ABSPATH . 'wp-content/uploads/private/wpml/';

	// Determine what the license file filename is
	if ( isset( $_SERVER['LANDO_APP_COMMON_NAME'] ) ) {
		// For Lando, use the local subdomain, such as maybe 'localwww'
		$wpml_expected_license_file = $wpml_license_key_path . $_SERVER['LANDO_APP_COMMON_NAME'] . '.txt';
	} else {
		// For other environments, use the Pantheon env name, e.g. 'maintenance', 'dev,', 'test', 'live'
		$wpml_expected_license_file = $wpml_license_key_path . $_ENV['PANTHEON_ENVIRONMENT'] . '.txt';
	}

	if ( file_exists( $wpml_expected_license_file ) ) {
		// Get the WPML license key from the text file, and tell WPML to use it as the environment's license key.
		$wpml_license_key = file_get_contents($wpml_expected_license_file);
		define( 'OTGS_INSTALLER_SITE_KEY_WPML', $wpml_license_key );
	}
}