Changes between Initial Version and Version 1 of Ticket #21022, comment 128
- Timestamp:
- 12/11/2022 09:04:03 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #21022, comment 128
initial v1 9 9 Only when you have a plugin that isn't yet compatible yet with the newer version of WordPress, but that should only be a very temporarily situation. That said, for the more serious web admins this will only happen on their development/test/staging site and not (as in: never) on their production site. 10 10 11 But in all seriousness. It's plain ridiculous that this particular security topic/ticket ( ''opened at June 20, 2012!!'') has still not made it into the core of WordPress. The minimum PHP requirement for WordPress has gone up to PHP 7.4 a while ago already so that can't be the reason (anymore) not to tackle this long long overdue security improvement. Please include it in WordPress 6.2.11 But in all seriousness. It's plain ridiculous that this particular security topic/ticket (opened at June 20, 2012!!) has still not made it into the core of WordPress. The minimum PHP requirement for WordPress has gone up to PHP 7.4 a while ago already so that can't be the reason (anymore) not to tackle this long long overdue security improvement. Please include it in WordPress 6.2.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)