[wp-trac] [WordPress Trac] #63484: Attempt to read property "name" on bool - wp-admin/nav-menus.php :1221

[WordPress Trac]

#63484: Attempt to read property "name" on bool - wp-admin/nav-menus.php :1221
--------------------------+------------------------
 Reporter:  apermo        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Menus         |     Version:  3.0
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------

Comment (by SirLouen):

 Replying to [comment:4 apermo]:
 > @avinashbhosale I have no method how to reproduce it. And since it is a
 logical flaw, I have not tried to.

 Just FYI, the massive amount of abandoned tickets (with patches) due to a
 lack of reproduction reports. My theory is that, barely anyone, would be
 interested in pushing on this kind of ticket, when on the other side there
 are plenty of reports with a lot more additional devices like reproduction
 reports, patches, unit tests, etc… waiting for review.

 1. Many of them, are simply not reproducible (despite being a logical
 flaw)
 2. Others are reproducible, but by wrong conditions implemented in some
 plugins.

 And yes, I agree that sorting this logic issue will lead to better code,
 as sometimes refactoring or preemptively sorting future deprecation
 notices are good practices. But for some reason, most people, as I say,
 prioritize full reports than half-baked reports that end in the graveyard
 of forgotten tickets.

 My advice: whenever you can, build a minimal reproduction model. I built
 it as an example for this report the other day in the #core-test triage
 session (I'm posting in #37026 to showcase). But again, this is 100%
 optional, and is just meant to help to push things forward.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63484#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform