[wp-trac] [WordPress Trac] #51555: Privacy Page: Does it need to be a Page? Also, is a warning an error?

[WordPress Trac]

#51555: Privacy Page: Does it need to be a Page? Also, is a warning an error?
----------------------------+-----------------------------
 Reporter:  bkjproductions  |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Privacy         |    Version:  5.5.1
 Severity:  normal          |   Keywords:
  Focuses:  privacy         |
----------------------------+-----------------------------
 When defining the Privacy Page, why does it specifically have to be a
 **Page** content type? It could very well be a Post or another content
 type. As a Page, it sort of then has to live in the ''hierarchy'' of
 Pages. In many situations, we might want to use a special custom post type
 that has no hierarchy. Or, we may want to set it as a Post of category
 "Legal" and then we would have other legal-ish Post content in that same
 category. Or we could have a pop-up. Or it could be in the footer. And so
 on--- there are many places a Privacy notice could appear, because, as
 indicated on the support article about this
 [https://wordpress.org/support/article/wordpress-privacy/] "Every website
 is different." (It would be good to explain somewhere ''why'' we have to
 define a Privacy Page in this manner, anyway--- does it create some sort
 of XML feed or appear in a META tag in the header or something useful and
 easy to track for compliance?)

 **Proposal:** Allow ''any'' post type to be set as the Privacy Page.
 **Even better:** Add a checkbox to indicate "We have implemented some
 other method of a Privacy Page (such as a popup)."

 **Also, a slight bug:** Going to the **Settings: Reading** panel, there is
 a message that warns:
 ''Warning: these pages should not be the same as your Privacy Policy page!
 ''
 when I have not defined the Privacy Policy page. While that may be an
 important message, it is curious to see it and was not something that I
 would consider doing anyway. Interestingly, if I define a **Posts page**
 here, that message goes away. (That is, it appears when I have defined
 both the **Homepage** and the **Posts page.**) If you have to keep this
 warning here for some reason, perhaps make the warning not-red, maybe
 caution color, if that is possible, and add a link over to the Privacy
 Policy panel in WP Dashboard.
 Suggest to use class
 {{{
 .notice-warning
 }}}
  rather than
 {{{
 .notice-error
 }}}
 since this is not really an error.

 [[Image()]]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51555>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform