Flintstone
New Member
@Yaros: I am guessing that you are the person to ask about this.
Whenever I am making changes to my site I create a staging instance so that I can make changes and update plugins without risking breaking my live site... as you know, this is a convention used by most web developers.
The problem is that I never know whether my site will work properly when I copy it back from staging because alidswoo is licensed to https://mydomain.com and not https://staging.mydomain.com so I can't run it on my staging server.
Can you please allow us to follow this well established convention by allowing alidswoo to be used on both https://mydomain.com and https://staging.mydomain.com? It would make our lives a heck of a lot easier and leave us with a lot less downtime.
To be clear, I am not asking for alidswoo to be licensed to any old subdomain. I am simply asking for the license to cover "https://staging.mydomain.com."
Whenever I am making changes to my site I create a staging instance so that I can make changes and update plugins without risking breaking my live site... as you know, this is a convention used by most web developers.
The problem is that I never know whether my site will work properly when I copy it back from staging because alidswoo is licensed to https://mydomain.com and not https://staging.mydomain.com so I can't run it on my staging server.
Can you please allow us to follow this well established convention by allowing alidswoo to be used on both https://mydomain.com and https://staging.mydomain.com? It would make our lives a heck of a lot easier and leave us with a lot less downtime.
To be clear, I am not asking for alidswoo to be licensed to any old subdomain. I am simply asking for the license to cover "https://staging.mydomain.com."
