Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #8592, comment 248


Ignore:
Timestamp:
05/25/2025 05:20:15 PM (9 months ago)
Author:
SirLouen
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8592, comment 248

    initial v1  
    774. Try to set the first page as parent for the new second page
    885. 🐞 It's not listed
     9
     10I was reviewing all answers for the last 15 years+ if this could be a `good-first-bug` because the solution can be as simple as [https://core.trac.wordpress.org/attachment/ticket/8592/8592.4.diff this patch]
     11
     12But it's not. After a while, some users detected many additional problems like:
     131. Parent ⇾ Child private inheritance (say Child is public and parent is Private, what in that case?)
     142. Issues with Password-Protected pages
     153. Parent status, limiting the possible status of their child.
     16
     17Here with more detail:
     18https://core.trac.wordpress.org/ticket/8592#comment:162
     19
     20Furthermore, be aware that all the comments were being talked around Classic Editor, pre-Gutenberg era. Nowadays, with those patches you can still edit the Parent directly, for example, in the Quick Edit form. But if you go into the page, you will see a Combo Box in the Parent field, which is managed by Gutenberg. Some additional refactor is needed there (and maybe a ticket upstream).
     21
     22If you consider taking this report, please take all this into consideration.