Changes between Initial Version and Version 1 of Ticket #62337, comment 37
- Timestamp:
- 11/19/2024 10:59:56 AM (7 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #62337, comment 37
initial v1 12 12 In order to restore previous functionality myself I would have have to forcefully unload all text domains when my plugin starts up. I don't want to do that, partly for performance. But if 6.7.1 doesn't rectify the issue I may have to. 13 13 14 It's worth noting that unloading NOOP translations does indeed cover a lot of the most common cases, but not all of them. I don't see a good reason to be deliberately beso selective, other than to protect the performance gains for which this change was [I assume] primarily made. I respect the need for performance, but not at the expense of broken websites.14 It's worth noting that unloading NOOP translations does indeed cover a lot of the most common cases, but not all of them. I don't see a good reason to be so selective, other than to protect the performance gains for which this change was [I assume] primarily made. I respect the need for performance, but not at the expense of broken websites. 15 15 16 16 Ideally I'd like to see an action hook that gets fired for `load_theme_textdomain` and `load_plugin_textdomain`. This would allow people to fix the problem as they see fit without compromising performance for everyone else.