Hi,
\If so, I'm sure you need to buy another license for your staging site. Staging site use for a fixed time - can't use together with the main site forever.
Because no any theme validate purchased code can allow you use one license for 2 sites running.
Best Regards,
PenciDesign
Thank you for your response and we love your theme!
\Let me see if I can clarify my question a bit.
\Assumption:
\1. License key is stored in database
\2. Even if you have two license if you migrate the database between two instances there will be a problem because there isn't an easy way to switch the two keys.
\Our requirements:
1. We need to keep two instances of the theme running for as long as we use your theme.
\2. One on our staging server and one on our production server.
\3. We will need to migrate the database back and forth between both servers in order to test plugin updates and other server software updates several times a month. We also produce a ton of content so we have to test with the most recent database.
\4. We get over 1 million hits a year so we must test everything in a staging environment and can not risk updating with out tests on our staging server first.
\Question:
What do I need to do to insure that:
\1. We are fulfilling our legal requirements for license. <--Im assuming we need two license
\2. We don't trigger some security issue(or breaking the theme) by running the wrong license on the wrong ip address after database migration .
\Thank you,
\Seth
Hi,
\This theme allow you for 1 month before the aleart message appears on screen - so you can do config on staging server in this time without activate the theme.
\If you want to use more time on this, you can activate the theme on staging site. When you moved everything to main site, let's remove the theme on the stagin site first before activate the theme on main site
Best Regards,
\PenciDesign
Here is the situation I am worried about:
Production server (with license A)
Staging server (with license B)
Moving database back and forth between servers to test and make changes.
We are using your theme on our production site. We would like to set up a staging server that will allow us to test changes before pushing them to production. After reading the license policy I realize that I must have one license for each instance of the theme I use.
My workflow sometimes involves moving the database from our staging server to our production server or vice versa. How do I deal with licenses in this scenario and avoid having my theme "turned off" when I need to migrate the database back and forth from production to staging? We are happy to purchase more licenses if we need but it would be nice if we could pay more to use one license for two sites.
Thank you and I hope my question was clear,
Seth
Want to join this conversation or access attachments? Sign in first.
Open your ticket archive, review validated licenses, and continue product support conversations from one customer portal.
