5 | | Yeah, no. This needs fixed in a patch, not next major version. What a shit show. Sorry, tech bros, you are wrong to think the workarounds are practical for the vast majority of people in the world. That is some tech elitist bs. |
| 5 | This needs fixed in a patch, not next major version. Core team is wrong to think the workarounds are practical for the vast majority of people in the world. And that 6.5 will fix this. People will be running 6.4.3 for a long time, and the people most impacted will be end users any person providing support at any level for WP including designers, builders, web hosts, etc. |
| 6 | |
| 7 | This isn't just a theme and plugin developer issue. To think of it that way is very myopic. This fundamentally impacts users and will continue to impact users for a long time if not fixed in 6.4. |
| 8 | |
| 9 | This isn't a "new feature" to be added in a major version. This is a major bug to be patched in the major version it was introduced in. |
| 10 | |
| 11 | |
| 12 | There will be so many Envato plugins and themes with incompatible archives. |
| 13 | |
| 14 | What is fundamentally the problem here is not understanding how the real world uses WordPress. How real people use WordPress, and how real users approach problems. And that's whom we should be concerned with in the end. Not the developers but the users. |
| 15 | |
| 16 | WordPress is not built solely for developers, nor are all WordPress sites built by developers. WordPress is ultimately for the users. We need to get our priorities straight. |