# STAGING wp-config.php no longer has 'KINSTA\_DEV\_ENV' and 'JETPACK\_STAGING\_MODE' defined

**URL:** <https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881>\
**Category:** Community Guides\
**Created:** [July 10, 2026, 12:31pm UTC](https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881 "2026-07-10T12:31:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haris\_Kaklamanos1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/haris_kaklamanos1/32/5667_2.png) [@Haris\_Kaklamanos1](https://community.kinsta.com/u/Haris_Kaklamanos1)\
**Post date:** [July 10, 2026, 12:31pm UTC](https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881/1 "2026-07-10T12:31:27Z")

</div>

Hello.

Today, I realized that after cloning the LIVE site to STAGING, the following constants are no longer defined at the top of wp-config.php.

```auto
<?php /* BEGIN KINSTA DEVELOPMENT ENVIRONMENT - DO NOT MODIFY THIS CODE BLOCK */ ?>

<?php if ( !defined('KINSTA_DEV_ENV') ) { define('KINSTA_DEV_ENV', true); /* Kinsta development - don't remove this line */ } ?>

<?php if ( !defined('JETPACK_STAGING_MODE') ) { define('JETPACK_STAGING_MODE', true); /* Kinsta development - don't remove this line */ } ?>

<?php /* END KINSTA DEVELOPMENT ENVIRONMENT - DO NOT MODIFY THIS CODE BLOCK */ ?>

```

Our development processes rely heavily on these constants when we want to customize plugin behavior depending on the environment.

We do define ‘staging’ in wp-config.php with

.define(‘WP\_ENVIRONMENT\_TYPE’, ‘staging’ );

but this is done manually, and we need to wait until the cloning process is over. Cloning and DB search and replace take time, especially in larger sites.

Ideally, the newly created STAGING wp-config.php should already declare the environment type, so there is no gap in which STAGING is still considered as being “live”.

Is there a plan to get those constants back?

Is there a bulletproof way to detect a non-production environment during site cloning?

---

<div class="post-metadata">

**Author:** ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)\
**Post date:** [July 10, 2026, 2:08pm UTC](https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881/2 "2026-07-10T14:08:32Z")

</div>

Hello @Haris_Kaklamanos 👋

These constants should be there in wp-config on the staging site. There might be a code on the site preventing this process from completing or a bug in Mykinsta.

However, since this isn’t in regards to DevKinsta, I would advise opening a chat with our Support Team.

> **[Support - Contact Support - Kinsta® Docs](https://kinsta.com/docs/support/contact-support/)**
>
> Find out how to contact Kinsta support, our multilingual support hours, and why we don't offer phone support.

Kind regards 👋

---

<div class="post-metadata">

**Author:** ![Haris\_Kaklamanos1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/haris_kaklamanos1/32/5667_2.png) [@Haris\_Kaklamanos1](https://community.kinsta.com/u/Haris_Kaklamanos1)\
**Post date:** [July 17, 2026, 2:20pm UTC](https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881/3 "2026-07-17T14:20:57Z")

</div>

Hello @VladimirM

The other day I contacted Kinsta support, and they reassured me that Kinsta has removed this feature from the STAGING sync process because it was thought that the feature was not essential or beneficial anymore.

So, I am a bit confused now.

Who should I contact now?

Thanks.

---

<div class="post-metadata">

**Author:** ![Andrew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/andrew/32/2792_2.png) [@Andrew](https://community.kinsta.com/u/Andrew)\
**Post date:** [July 17, 2026, 7:28pm UTC](https://community.kinsta.com/t/staging-wp-config-php-no-longer-has-kinsta-dev-env-and-jetpack-staging-mode-defined/6881/4 "2026-07-17T19:28:49Z")

</div>

Hi @Haris_Kaklamanos1! Thank you for your reply!

I apologize about any confusion that occurred. I understand that you are looking for a way to identify the environment type a site installation is in as your development process relies on knowing this information. This is still possible without having to manually declare the WP\_ENVIRONMENT\_TYPE constant.

As it turns out, our platform already sets the `WP_ENVIRONMENT_TYPE` constant. This replaces the older `KINSTA_DEV_ENV` variable. The `WP_ENVIRONMENT_TYPE` is set to the following values depending on the environment:

Live environment: `production`

Standard staging environment: `staging`

Premium staging environment: `development`

You should be able to use the `WP_ENVIRONMENT_TYPE` value in your development process to determine if the site is on a live, staging or premium staging environment without having to manually define the value in the wp-config.php file.

Please let us know if this helps answer your question, or if you do need any further assistance. We are always happy to help!

Take care!