License key validation does not work with new license key format from MaxMind

[oschwald]

The current license key validation fails on new license keys from MaxMind, e.g., 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. It appears that the current validation requires the keys to match ^[A-Za-z0-9]{16}$:

geoip-detect/data-sources/manual.php

Lines 139 to 156 in d42e18c

	public function validateApiKey($key) {
	$message = '';
	$key = trim($key);
	if (mb_strlen($key) != 16) {
	$message = __('The license key usually is a 16-char alphanumeric string. Are you sure this is the right key?', 'geoip-detect');
	if (mb_strlen($key) < 16) {
	$message .= ' ' . __('Do not use the "unhashed format" when generating the license key.', 'geoip-detect');
	// Unhashed: 13char alphanumeric
	}
	$message .= ' ' . sprintf(__('This key is %d chars long.', 'geoip-detect'), mb_strlen($key));
	} else if (1 !== preg_match('/^[a-z0-9]+$/i', $key)) {
	$message = __('The license key usually is a 16-char alphanumeric string. Are you sure this is the right key?', 'geoip-detect');
	$message .= ' ' . __('This key contains characters other than a-z and 0-9.', 'geoip-detect');
	}
	if ($message) return $message;
	return true;
	}

The new license keys match [A-Za-z0-9]{6}_[A-Za-z0-9]{29}_mmk. The length may also increase in the future. See these release notes for more information.

[benjaminpick]

Thank you for notifying me!