[wp-trac] [WordPress Trac] #54516: Full site editing/REST-API: modify permission checks to use post type.

[WordPress Trac]

#54516: Full site editing/REST-API: modify permission checks to use post type.
-------------------------------------------------+-------------------------
 Reporter:  peterwilsoncc                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  REST API                             |     Version:  5.9
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:  rest-api
  test-info                                      |
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  has-patch needs-unit-tests needs-testing => has-patch needs-
     unit-tests needs-test-info


Comment:

 Replying to [comment:42 manfcarlo]:
 > Adding some keywords with the hope this will get addressed in the
 current cycle. The
 [https://core.trac.wordpress.org/ticket/54516#comment:40 previous summary]
 is still current.

 Reading through the report, I can see two problems of why this is not
 progressing:
 1. Unless for some reason, a core dev gets hands on this topic, reviews
 the code narrowly, and decides to move this forward, this is going to
 stall forever.
 2. From a testing perspective, I can barely figure out an idea on how to
 test this, to the point where
 [https://core.trac.wordpress.org/ticket/54516?replyto=42#comment:28 the
 original report was closed]. But from there I have to admit that I'm
 completely lost and can't fully understand the reasons why this was
 reopened in a glance.
 3. To generate some additional traction more than `needs-testing` and
 `needs-unit-tests`, what this patch needs is a
 [https://make.wordpress.org/test/2025/05/15/building-the-testing-use-case
 /#back-end-enhancements-and-new-features Testing Use Case]: some
 reproduction steps for the current issue after the patch, a minimal plugin
 that reproduces the issues, or whatever detailed information that can help
 reproduce the current issue and how your patch solves this before and
 after (again, reproducing the issue in advance, not something
 theoretical). Sure, anyone like me could read the current state of the
 code and figure out such a Testing Use-Case. But it's a massive task for
 someone who is picking this up from scratch, and it's completely foreign
 to the problem (like my case, compared with someone that is already hands-
 on in the problem, like you). So I recommend developing a `use-case` to
 leverage this. Furthermore, some Unit Tests always help to extrapolate the
 Use-Case, but they are also hard for someone foreign for the same reasons.
 4. Since we don't have neither `unit-tests` nor a `use-case` I think it's
 going to be specially challenging to move this forward.

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