Changes between Initial Version and Version 1 of Ticket #57487, comment 10
- Timestamp:
- 01/21/2023 01:06:05 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57487, comment 10
initial v1 1 1 > There was a discussion in #51064 on the differences between local and development, perhaps it should be revisited. 2 2 3 Yes, but unsure if this problem can be resolved by trying to figure out the differences or if there should be some. Truth is that anybody can develop o n both local and remote WP installs. Don't see why this setting should be limiting.3 Yes, but unsure if this problem can be resolved by trying to figure out the differences or if there should be some. Truth is that anybody can develop or test on both local and remote WP installs. Don't see why this setting should be limiting. 4 4 5 5 > Instead of checking for the development environment WordPress could use in_array( wp_get_environment_type(), array( 'development', 'local' ), true ). 6 6 7 True, but then WP will end up with all sorts of `'development' AND 'local'`, `'development' OR 'local'`, 'development' AND 'staging'`, etc. Why the complexity?7 True, but then WP will end up with all sorts of `'development' AND 'local'`, `'development' OR 'local'`, `'development' AND 'staging'`, etc. Why the complexity? 8 8 9 9 The problem with `wp_get_environment_type()` is that the types are not mutually-exclusive. Also, the intended use of the environment types seem more like "server settings", not "user intent". I.e. should a user be able to set `local` when WP is on a remote server? Should that affect/interfere with development mode?