[wp-trac] [WordPress Trac] #33885: meta_form performs a potentially expensive query
WordPress Trac
noreply at wordpress.org
Wed Apr 27 10:01:37 UTC 2022
#33885: meta_form performs a potentially expensive query
-------------------------------------+-------------------------------------
Reporter: jorbin | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 6.0
Component: Administration | Version: 4.3.1
Severity: normal | Resolution:
Keywords: has-patch needs-testing | Focuses: administration,
needs-unit-tests needs-refresh | performance
close |
-------------------------------------+-------------------------------------
Comment (by jb510):
Replying to [comment:100 uzumymw]:
> But what if more than half of the existing WordPress sites will never
migrate to Gutenberg?
> It is actually very possible.
I remember this logic being used to not fix the problems with the menu
edit screen which fails on very large menus due to max_input_vars, the
retort to that for a long time was “use the brand new customizer” because
it didn’t have this problem. Only, the customizer was and still is awful
for managing large menus.
These types of issues need to get fixed, not kicked down the road for
another 10 years.
@jorbin in my experience it’s way more likely large existing sites won’t
be moving to Gutenberg soon if ever. They’re way less likely to be doing
that because of the large existing content library doesn’t really “convert
to Gutenberg”. Some have a lot of custom code rendered completely useless
by Gutenbergs markup. I think a more accurate phrasing would be “large
well funded sites are moving to Gutenberg”, but not all large sites have
the resources to make that transition. This still needs to get fixed for
them and for all the corners of WP that still use the classic editor.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33885#comment:103>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list