#44055 closed defect (bug) (fixed)
Don't show notice to the privacy policy guide when user cannot view the guide
| Reported by: | ocean90 | Owned by: | azaozz |
|---|---|---|---|
| Priority: | high | Milestone: | 4.9.6 |
| Component: | Privacy | Version: | 5.1 |
| Severity: | normal | Keywords: | gdpr dev-reviewed |
| Cc: | Focuses: |
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)
#5
@
8 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.
8 years ago
This ticket was mentioned in Slack in #gdpr-compliance by allendav. View the logs.
8 years ago
This ticket was mentioned in Slack in #gdpr-compliance by azaozz. View the logs.
8 years ago
#12
@
8 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.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
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_htmlcapability, etc.).In any case, the notice should have the same capability requirement as the guide.