[wp-trac] [WordPress Trac] #47564: Protect against recursive customizer navigation menu data
WordPress Trac
noreply at wordpress.org
Fri Jun 27 14:02:44 UTC 2025
#47564: Protect against recursive customizer navigation menu data
---------------------------------------+-----------------------------
Reporter: donpark | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future Release
Component: Customize | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-test-info | Focuses:
---------------------------------------+-----------------------------
Changes (by SirLouen):
* keywords: has-patch needs-testing => has-patch needs-test-info
Comment:
Replying to [comment:2 donpark]:
> Only in context of a particular site on WordPress.com. And testing plan,
detailed in the A8C internal Phabricator patch I mentioned (D29638-code),
requires the tester be an Automattician.
If the tester requires being an "Automattician" as you say, this is not
the place to report this. There are some [https://wordpress.com/forums/
WordPress.com forums] specifically for these types of issues. If anyone
from wordpress.com happens to isolate the problem, it can be brought here
for further testing by any contributor.
This post should be left on hold until you have detailed instructions on
how to reproduce this by anyone, anywhere, anywhen. Here are some ideas on
[https://make.wordpress.org/test/2025/05/15/building-the-testing-use-
case/#comment-3314 how to build a Testing Use Case] with, maybe, a minimal
plugin that reproduces the problem (and your patch happens to solve it)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47564#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list