Hello -
We have both a staging site and production site at different URLs, and each site has a unique license key for Toolset.
When we push from production to staging, we always "lose" the correct key for staging (it gets replaced with the production key on the push) and then Toolset reports that it's the wrong key for the site.
We are hoping to learn where in the database this registration key is store so that we can ensure it remains set correctly for our staging site when we push to it from production.
Thanks for any pointers. Tried searching the options table for different key names I thought might be a hit but couldn't come up with it.
Also, if you could please copy todd@jambase.com on this ticket that would be appreciated.
He's on the "Team" in our account.
Also, if you could please copy todd@jambase.com on this ticket that would be appreciated.
Hi, I wish I could but I don't have the ability to arbitrarily add users to the communications for each ticket. Does he have a direct login for https://toolset.com? If so, it might be easiest if he adds a reply while logged in. Normally Users who reply have the option to receive automatic notifications for each subsequent response.
We are hoping to learn where in the database this registration key is store so that we can ensure it remains set correctly for our staging site when we push to it from production.
Well the information is stored in the wp_options table under the wp_installer_settings key, but it's obfuscated, possibly gzipped, and is part of a serialized data structure...not exactly an easy fix. Instead you can define a key string constant in the wp-config.php files specific to each environment:
define('OTGS_INSTALLER_SITE_KEY_TOOLSET', 'YOURKEYHERE');
It will be far easier to automate keys per environment this way using an automated deployment process or script.
https://toolset.com/faq/how-to-install-and-register-toolset/#automatic-toolset-registration-using-php
