| 3 | | Yea, this is somewhat similar to setting `WP_ENVIRONMENT_TYPE` to `development`. However the "environment types" functionality doesn't seem to be particularly useful for setting development mode. It seems unclear and harder to use, and buggy in some cases. The `setenv` and `getenv` functions don't seem to be enabled or to work reliably in some cases. Also the `WP_ENVIRONMENT_TYPE` constant was deprecated, but is still needed/required in these cases which makes it... weird :) |
| | 3 | Yea, this is somewhat similar to setting `WP_ENVIRONMENT_TYPE` to `development`. However the "environment types" functionality doesn't seem to be particularly useful for setting development mode. It seems unclear and harder to use, and buggy in some cases. The `setenv` and `getenv` functions don't seem to be enabled or to work reliably in some cases. |
| | 4 | |
| | 5 | Another very big disadvantage there is that setting WP_ENVIRONMENT_TYPE to 'local' means it cannot be set to 'development' and vice-versa. That makes the whole functionality pretty useless. |