Skip Navigation

[Resolved] Push from dev to production | Migration overwrites production site key.

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)

This topic contains 1 reply, has 1 voice.

Last updated by Minesh 1 month, 1 week ago.

Assisted by: Minesh.

Author
Posts
#2811798
Screenshot 2025-06-09 at 3.06.58 PM.png

Hello.

Our client deploys changes to their sites via a push from staging to production.

I had configured the site keys and registered the production and development sites accordingly.

Following the migration, our production site displayed a banner under the footer reading: "This site is registered on Toolset.com as a development site."

I would like to prevent this moving forward.

Can you clarify which tables, or options will needed to be excluded from our future migrations, so that our staging keys will not overwrite our production keys.

#2811904

Minesh
Supporter

Languages: English (English )

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

Hello. Thank you for contacting the Toolset support.

I would like to know how exactly you registered the staging site.

Have you added the Toolset site key to your staging site's wp-config.php file?

Are you moving whole site and database to production site?

Here is the Doc that shows information how you can register the development site:
- https://toolset.com/faq/how-to-install-and-register-toolset/#registering-toolset-in-a-development-environment

And here is the Doc that shows information migration registration to a different domain (production) site:
- https://toolset.com/faq/how-to-install-and-register-toolset/#migrating-registration-to-a-different-domain