|
SfDBT
|
January 5, 2020 at 3:19 am
Hi,
I am trying to work on the sfdbt.org website using a staging site sfdbt.org/staging but I have received a notification about the license. I was hoping I could work on the site without any downtime using a staging site but license issues would cause me to look for a different solution as I wont be purchasing an additional licence just for development. Can you please advise if there is a solution for this?
Thank you
Mike
|
|
Tony
|
January 6, 2020 at 4:31 am
Hi Mike,
The license key is used for support and one-click updates on a single site, we allow for some staging tld’s (eg example.dev) and subdomains (eg staging.example.com) and you don’t need to purchase an additional license for a staging site.
If our system does not support the URL for your staging site (a /staging/ subdirectory is currently not) then the simplest solution is to not use a key on the site at all. The key does not affect EE’s functionality in any way other than updates so leave the key blank and update EE (and it’s add-ons) manually on the staging site:
https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#ee4-manual-update
|
|
mdeyerinkc
|
January 17, 2020 at 5:09 pm
I’m having the same issue. I’m running a staging / development instance in a sub folder (/dev) – and I’m receiving the “Your support license key is only valid for one domain at a time, and our licensing system has detected that you are using your license key on multiple domains…” message at the top of my staging site dashboard. Updating manually, as suggested, is pretty onerous given that I have eight EE plugins I’m using.
|
|
Josh
|
January 18, 2020 at 9:45 am
If you can change your staging/development instance into a subdomain (instead of a subfolder) then you can run the same key on both sites.
Any of the following subdomains will allow the key to be used on the staging site and it won’t count toward the one site per key limit:
‘dev.’, ‘staging.’, ‘dev-‘, ‘test-‘, ‘live-‘
(because when the site has a subdomain like any of the above it will be recognized by the update server as a staging site)
|
