Changes between Initial Version and Version 3 of Ticket #56234
- Timestamp:
- 07/16/2022 11:20:12 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #56234
- Property Keywords 2nd-opinion added
-
Property
Component
changed from
GeneraltoI18N
-
Ticket #56234 – Description
initial v3 1 e.g. _doing_it_wrong,...1 e.g. `_doing_it_wrong`,... 2 2 3 3 - general consensus for software is that errors in logs should always be in English 4 4 5 - these errors will only show with WP_DEBUGenabled, therefore a development errors and developers who work with WP have to speak English, otherwise wouldn't be able to understand the code in the first place5 - these errors will only show with `WP_DEBUG` enabled, therefore a development errors and developers who work with WP have to speak English, otherwise wouldn't be able to understand the code in the first place 6 6 7 - even if you are not a developer but use WP_DEBUG, these are not issues you can fix yourself. You need to get in touch with your hoster, your developer, the plugin developer from where this error is from or even WP core. This is much easier if the error is in English and you can google it easily. Furthermore it's much easier to only receive these errors in English for the support who you contact - rather than in the 50 different supported languages by WP.7 - even if you are not a developer but use `WP_DEBUG`, these are not issues you can fix yourself. You need to get in touch with your hoster, your developer, the plugin developer from where this error is from or even WP core. This is much easier if the error is in English and you can google it easily. Furthermore it's much easier to only receive these errors in English for the support who you contact - rather than in the 50 different supported languages by WP. 8 8 9 9 - many (most?) plugins do not pass a translatable strings to these, which means you end up with a language mix-mash … … 11 11 - when using a multi-lingual site, we (= the admin) get the error in all kinds of languages, we do not even speak (since the translations were created by contracted agencies). Making it unnecessarily hard to track down the exact English text, so we can check it in code. 12 12 13 In some instances where these may be used translation may not be loaded yet (which is why we have a function exists "__"check), which means that in some cases you end up with english errors anyway.13 In some instances where these may be used translation may not be loaded yet (which is why we have a `function_exists( '__' )` check), which means that in some cases you end up with english errors anyway. 14 14 15 15 The sensible thing to do is, to remove translations from error logged things all together. 16 16 I'm happy to provide a PR. 17 17 18 Related https://core.trac.wordpress.org/ticket/53125 (and https://core.trac.wordpress.org/ticket/56198#comment:6 which made me open this ticket finally) 19 20 18 Related #53125 (and ticket:56198#comment:6 which made me open this ticket finally)