Patterns for detecting staging websites
In the KB I read:
Are development and staging websites considered an activation?
You can activate them to get updates and support, but they will not count towards your activation limit.
Local development should always be detected and not count towards your activation limit. We also have quite a few rules in place to detect if a website is a staging site or not. We also have a list of popular staging domains we always exclude:
.cloudwaysapp.com
.cloudwaysapps.com
.flywheelsites.com
.flywheelstaging.com
.kinsta.cloud
.kinsta.com
.wpengine.comIf you activate Admin Columns Pro it will give you feedback if a development or staging site was found.
My staging websites are hosted at sitename-ext.staging.companyname.ext and are (as expected) not recognized as staging website. Would you consider extending staging patterns? The patterns Elementor uses do cover my use case:
TLD (Top-level Domains) that are not considered as a license use:
dev (example.dev)
.local (example.local)
.test (example.test)
.staging (example.staging)
.example (example.example)
.invalid (example.invalid)Subdomains that are not considered as a license use:
dev.* (dev.example.com) this can also be implemented as follows:
exampledev.* (exampledev.example.com)
local.* (local.example.com)
test.* (test.example.com)*.test.* (example.test.example.com)
staging.* (staging.example.com)
*.staging.* (example.staging.example.com)
staging[0-9].* (staging6.example.com)
*.staging[0-9].*(example.staging6.example.com)
stage.* (stage.example.com)
*.stage.* (example.stage.example.com)
In specific cases the following may also be used:
dev-*.pantheonsite.io (dev-example.patheonsite.io)
test-*.pantheonsite.io (test-example.pantheonsite.io)
staging-*.kinsta.com (staging-example.kinsta.com)
staging-*.kinsta.cloud (staging-example.kinsta.cloud)
*.myftpupload.com (example.myftpupload.com)
*.cloudwaysapps.com (example.cloudwaysapps.com)
*.ngrok.io (example.ngrok.io)
*-dev.ksysweb.com (example-dev.ksysweb.com)
*-stg.ksysweb.com (example-stg.ksysweb.com)
*stg.wpengine.com (examplestg.wpengine.com)
*dev.wpengine.com (exampledev.wpengine.com)
*stg.wpenginepowered.com (examplestg.wpenginepowered.com)
*dev.wpenginepowered.com (exampledev.wpenginepowered.com)
(For WordPress, Your Way sites) staging-[a-z0-9]+-.*.wpcomstaging.com (WordPress.com )
*.flywheelstaging.com (example.flywheelstaging.com)
autopilot-(.*)\.pantheonsite\.io (autopilot-example.pantheonsite.io)
(For Dreamhost sites) *.stage.site (example.stage.site)
(For Dreamhost sites) *.dream.press (example.dream.press)
In my dashboard / website overview the staging website is recognized, sorry.
It would be neat when I duplicate a website from live to staging, it would hold the license details. Now the license gets deactivated.
Not a big deal, but would be handy.
Thanks for your feedback.
If specific staging sites aren’t recognized automatically, we can add their pattern to our system.
Unfortunately, we can’t change the behavior when duplicating a website. Each site requires its own license because it contains a unique key/token used to identify it with our license service.
You must be logged in to reply to this topic.