Skip Navigation

[Resolved] Support for Staging to Production Migration

This support ticket is created 4 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Minesh 4 years, 3 months ago.

Assisted by: Minesh.

Author
Posts
#2043401

Hi Guys

I have purchased Toolset for our company, but I have come across a small issue. I have created a key for both staging.website.com and website.com. However, the way our development process is set up, we never actually edit/modify our production server. We simply synchronise the database over to production. As a result, the Toolset plugin appears to be unregistered on our production site (website.com), due to the key being associated with the staging URL.

Is there a way to create a wildcard domain key. Or at least have the same key for staging and production?

Gary

#2043519

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Here is the how you can register the site key when you migrate your site to different domain.
=> https://toolset.com/faq/how-to-install-and-register-toolset/#migrating-registration-to-a-different-domain

There is no way to have a same site key for stating and production. Its already mentioned with the following doc:
=> https://toolset.com/faq/how-to-install-and-register-toolset/#automatic-toolset-registration-using-php


Important: each site key is unique to the URL of the site you are using it with. For example, when you move a site from a testing URL to a final, production one, you need to register a new key for the production site and update it in the wp-config.php file.

#2043795

Thank you for the response, however none of the information actually helps my problem.

When a website is developed, it is usually worked on in a dev/staging environment. It is considered bad practice to edit a live production site. As such, large companies generally develop/test their work on a sub domain and push the results to production. Without touching the production environment.

How am I supposed to do this if you do not allow a key to be shared between, dev.website.com, staging.website.com and website.com?

This is not a niche problem just for a company, this is standard practice across the web industry?

Gary

#2044023

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

When a website is developed, it is usually worked on in a dev/staging environment. It is considered bad practice to edit a live production site. As such, large companies generally develop/test their work on a sub domain and push the results to production. Without touching the production environment.

How am I supposed to do this if you do not allow a key to be shared between, dev.website.com, staging.website.com and website.com?
==>
I understand your concern.

But as shared:

Important: each site key is unique to the URL of the site you are using it with. For example, when you move a site from a testing URL to a final, production one, you need to register a new key for the production site and update it in the wp-config.php file.

As on now, you will have to create a unique site key for your staging and production environment. We do have internal talks about improving how we handle the site keys and we will do our best to improve this in near future.

I'm afraid that ,as of now, I do not have any solution or workaround to offer.