#44055 closed defect (bug) (fixed)
Don't show notice to the privacy policy guide when user cannot view the guide
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.9.6 | Priority: | high |
Severity: | normal | Version: | 5.1 |
Component: | Privacy | Keywords: | gdpr dev-reviewed |
Focuses: | Cc: |
Description
The privacy policy guide is only viewable if current_user_can( 'manage_privacy_options' )
but WP_Privacy_Policy_Content::notice()
has no such check, leading an editor to an empty page.
Change History (13)
#2
@
7 years ago
- Owner set to azaozz
- Resolution set to fixed
- Status changed from new to closed
In 43248:
#3
@
7 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Reopen for 4.9.6 consideration.
#5
@
7 years ago
- Keywords 2nd-opinion added
Hmm, should editors be allowed to edit the wp_page_for_privacy_policy
? I'm guessing no, so maybe a better solution to this would be to add a map_meta_cap
callback that makes current_user_can( 'edit_post', get_option( 'wp_page_for_privacy_policy' ) )
return false
?
This ticket was mentioned in Slack in #core by desrosj. View the logs.
7 years ago
This ticket was mentioned in Slack in #gdpr-compliance by allendav. View the logs.
7 years ago
This ticket was mentioned in Slack in #gdpr-compliance by azaozz. View the logs.
7 years ago
#12
@
7 years ago
- Keywords dev-reviewed added; fixed-major commit dev-feedback removed
Nevermind regarding comment:7, it's a good idea to leave the cap check, see ticket:44079#comment:7.
I'm actually not sure if editors on "single" installs should not be able to see the privacy policy guide? Generally they are trusted as much as admins (have
unfiltered_html
capability, etc.).In any case, the notice should have the same capability requirement as the guide.