2017-07-19 23:42:42 +02:00
< ? php
/**
Privacy: Move privacy policy page to `Settings` menu for consistency.
The page was originally placed under `Tools` so that it would be grouped with the pages to export and erase personal data, since they're all part of the effort to bring privacy management tools to Core ahead of GDPR's deadline. After more consideration, though, it makes sense to move this page to the `Settings` menu, since it's fundamental purpose is to configure an option, rather than to facilitate a recurring task. This keeps all of the configuration pages in a single place, making them consistent and easier to find.
Exporting and erasing personal data are recurring tasks, so they still make sense under the `Tools` menu.
Props xkon, helen, melchoyce, allendav, desrosj, ocean90, azaozz.
Fixes #43873.
Built from https://develop.svn.wordpress.org/trunk@43145
git-svn-id: http://core.svn.wordpress.org/trunk@42974 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-05-03 18:41:22 +02:00
* Privacy Settings Screen .
2017-07-19 23:42:42 +02:00
*
* @ package WordPress
* @ subpackage Administration
*/
/** WordPress Administration Bootstrap */
require_once ( dirname ( __FILE__ ) . '/admin.php' );
2018-05-03 21:31:21 +02:00
if ( ! current_user_can ( 'manage_privacy_options' ) ) {
2018-03-09 16:04:33 +01:00
wp_die ( __ ( 'Sorry, you are not allowed to manage privacy on this site.' ) );
}
2017-07-19 23:42:42 +02:00
2018-03-09 16:04:33 +01:00
// "Borrow" xfn.js for now so we don't have to create new files.
// wp_enqueue_script( 'xfn' );
$action = isset ( $_POST [ 'action' ] ) ? $_POST [ 'action' ] : '' ;
if ( ! empty ( $action ) ) {
check_admin_referer ( $action );
if ( 'set-privacy-page' === $action ) {
$privacy_policy_page_id = isset ( $_POST [ 'page_for_privacy_policy' ] ) ? ( int ) $_POST [ 'page_for_privacy_policy' ] : 0 ;
update_option ( 'wp_page_for_privacy_policy' , $privacy_policy_page_id );
add_settings_error (
'page_for_privacy_policy' ,
'page_for_privacy_policy' ,
2018-04-13 19:56:20 +02:00
sprintf (
2018-05-02 03:58:21 +02:00
/* translators: %s: URL to Customizer -> Menus */
2018-04-13 19:56:20 +02:00
__ ( 'Privacy policy page updated successfully. Remember to <a href="%s">update your menus</a>!' ),
'customize.php?autofocus[panel]=nav_menus'
),
2018-03-09 16:04:33 +01:00
'updated'
);
} elseif ( 'create-privacy-page' === $action ) {
2018-04-30 16:47:21 +02:00
if ( ! class_exists ( 'WP_Privacy_Policy_Content' ) ) {
require_once ( ABSPATH . 'wp-admin/includes/misc.php' );
}
$privacy_policy_page_content = WP_Privacy_Policy_Content :: get_default_content ();
2018-03-09 16:04:33 +01:00
$privacy_policy_page_id = wp_insert_post (
array (
2018-04-30 16:47:21 +02:00
'post_title' => __ ( 'Privacy Policy' ),
'post_status' => 'draft' ,
'post_type' => 'page' ,
'post_content' => $privacy_policy_page_content ,
2018-03-09 16:04:33 +01:00
),
true
);
if ( is_wp_error ( $privacy_policy_page_id ) ) {
add_settings_error (
'page_for_privacy_policy' ,
'page_for_privacy_policy' ,
__ ( 'Unable to create privacy policy page.' ),
'error'
);
} else {
update_option ( 'wp_page_for_privacy_policy' , $privacy_policy_page_id );
2018-04-13 19:56:20 +02:00
2018-05-03 22:06:21 +02:00
wp_redirect ( admin_url ( 'post.php?post=' . $privacy_policy_page_id . '&action=edit' ) );
exit ;
2018-03-09 16:04:33 +01:00
}
}
}
2018-03-10 15:01:31 +01:00
// If a privacy policy page ID is available, make sure the page actually exists. If not, display an error.
2018-03-09 16:04:33 +01:00
$privacy_policy_page_exists = false ;
2018-04-13 19:56:20 +02:00
$privacy_policy_page_id = ( int ) get_option ( 'wp_page_for_privacy_policy' );
2018-03-09 16:04:33 +01:00
if ( ! empty ( $privacy_policy_page_id ) ) {
2018-04-13 19:56:20 +02:00
$privacy_policy_page = get_post ( $privacy_policy_page_id );
if ( ! $privacy_policy_page instanceof WP_Post ) {
add_settings_error (
'page_for_privacy_policy' ,
'page_for_privacy_policy' ,
__ ( 'The currently selected privacy policy page does not exist. Please create or select new page.' ),
'error'
);
} else {
if ( 'trash' === $privacy_policy_page -> post_status ) {
2018-03-09 16:04:33 +01:00
add_settings_error (
'page_for_privacy_policy' ,
'page_for_privacy_policy' ,
2018-04-13 19:56:20 +02:00
sprintf (
2018-05-02 03:58:21 +02:00
/* translators: URL to Pages Trash */
2018-04-13 19:56:20 +02:00
__ ( 'The currently selected privacy policy page is in the trash. Please create or select new privacy policy page or <a href="%s">restore the current page</a>.' ),
'edit.php?post_status=trash&post_type=page'
),
2018-03-10 15:01:31 +01:00
'error'
2018-03-09 16:04:33 +01:00
);
} else {
2018-04-13 19:56:20 +02:00
$privacy_policy_page_exists = true ;
2018-03-09 16:04:33 +01:00
}
2018-04-13 19:56:20 +02:00
}
2018-03-09 16:04:33 +01:00
}
get_current_screen () -> add_help_tab ( array (
'id' => 'privacy' ,
'title' => __ ( 'Privacy' ),
Privacy: Move privacy policy page to `Settings` menu for consistency.
The page was originally placed under `Tools` so that it would be grouped with the pages to export and erase personal data, since they're all part of the effort to bring privacy management tools to Core ahead of GDPR's deadline. After more consideration, though, it makes sense to move this page to the `Settings` menu, since it's fundamental purpose is to configure an option, rather than to facilitate a recurring task. This keeps all of the configuration pages in a single place, making them consistent and easier to find.
Exporting and erasing personal data are recurring tasks, so they still make sense under the `Tools` menu.
Props xkon, helen, melchoyce, allendav, desrosj, ocean90, azaozz.
Fixes #43873.
Built from https://develop.svn.wordpress.org/trunk@43145
git-svn-id: http://core.svn.wordpress.org/trunk@42974 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-05-03 18:41:22 +02:00
'content' => '<p>' . __ ( 'This page provides settings with which you can manage your site’s privacy policy.' ) . '</p>' ,
2018-03-09 16:04:33 +01:00
) );
get_current_screen () -> set_help_sidebar (
'<p><strong>' . __ ( 'For more information:' ) . '</strong></p>' .
'<p>' . __ ( '<a href="#">Documentation on privacy</a>' ) . '</p>'
);
require_once ( ABSPATH . 'wp-admin/admin-header.php' );
2017-07-19 23:42:42 +02:00
?>
2018-03-09 16:04:33 +01:00
< div class = " wrap " >
Privacy: Move privacy policy page to `Settings` menu for consistency.
The page was originally placed under `Tools` so that it would be grouped with the pages to export and erase personal data, since they're all part of the effort to bring privacy management tools to Core ahead of GDPR's deadline. After more consideration, though, it makes sense to move this page to the `Settings` menu, since it's fundamental purpose is to configure an option, rather than to facilitate a recurring task. This keeps all of the configuration pages in a single place, making them consistent and easier to find.
Exporting and erasing personal data are recurring tasks, so they still make sense under the `Tools` menu.
Props xkon, helen, melchoyce, allendav, desrosj, ocean90, azaozz.
Fixes #43873.
Built from https://develop.svn.wordpress.org/trunk@43145
git-svn-id: http://core.svn.wordpress.org/trunk@42974 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-05-03 18:41:22 +02:00
< h1 >< ? php _e ( 'Privacy Settings' ); ?> </h1>
2018-04-13 19:56:20 +02:00
< h2 >< ? php _e ( 'Privacy Policy page' ); ?> </h2>
< p >
2018-05-03 02:07:22 +02:00
< ? php _e ( 'As a website owner, you may need to follow national or international privacy laws. For example, you may need to create and display a privacy policy.' ); ?>
2018-05-03 02:18:21 +02:00
< ? php _e ( 'If you already have a privacy policy page, please select it below. If not, create one.' ); ?>
2018-04-13 19:56:20 +02:00
</ p >
< p >
2018-05-01 13:43:22 +02:00
< ? php _e ( 'The new page will include help and suggestions for your privacy policy.' ); ?>
< ? php _e ( 'However, it is your responsibility to use those resources correctly, to provide the information that your privacy policy requires, and to keep that information current and accurate.' ); ?>
</ p >
< p >
2018-05-03 02:18:21 +02:00
< ? php _e ( 'After your privacy policy page is set, we suggest that you edit it. On the edit page screen you will find additional privacy information added by your themes and plugins.' ); ?>
2018-05-01 13:43:22 +02:00
< ? php _e ( 'We would also suggest reviewing your privacy policy from time to time, especially after an update. There may be changes or new suggested information for you to consider adding to your policy.' ); ?>
2018-04-13 19:56:20 +02:00
</ p >
2018-03-10 15:01:31 +01:00
< ? php
if ( $privacy_policy_page_exists ) {
$edit_href = add_query_arg (
array (
2018-04-13 19:56:20 +02:00
'post' => $privacy_policy_page_id ,
2018-03-10 15:01:31 +01:00
'action' => 'edit' ,
),
admin_url ( 'post.php' )
);
2017-07-19 23:42:42 +02:00
2018-04-13 19:56:20 +02:00
$view_href = get_permalink ( $privacy_policy_page_id );
2018-03-10 15:01:31 +01:00
?>
2018-04-13 19:56:20 +02:00
< p class = " tools-privacy-edit " >< strong >
2018-03-09 16:04:33 +01:00
< ? php
2018-03-10 15:01:31 +01:00
printf (
2018-05-02 03:58:21 +02:00
/* translators: 1: URL to edit page, 2: URL to view page */
2018-04-13 19:56:20 +02:00
__ ( '<a href="%1$s">Edit</a> or <a href="%2$s">view</a> your privacy policy page content.' ),
2018-03-10 15:01:31 +01:00
$edit_href ,
$view_href
);
?>
</ strong ></ p >
< ? php
}
?>
2018-04-13 19:56:20 +02:00
< hr >
< table class = " form-table tools-privacy-policy-page " >
2018-03-09 16:04:33 +01:00
< tr >
< th scope = " row " >
2018-04-13 19:56:20 +02:00
< ? php
if ( $privacy_policy_page_exists ) {
_e ( 'Change your Privacy Policy page' );
} else {
_e ( 'Select a Privacy Policy page' );
}
?>
2018-03-09 16:04:33 +01:00
</ th >
2018-04-13 19:56:20 +02:00
< td >
2018-03-09 16:04:33 +01:00
< form method = " post " action = " " >
2018-04-13 19:56:20 +02:00
< label for = " page_for_privacy_policy " >
< ? php _e ( 'Either select an existing page:' ); ?>
</ label >
2018-03-09 16:04:33 +01:00
< input type = " hidden " name = " action " value = " set-privacy-page " />
2018-03-10 15:01:31 +01:00
< ? php
wp_dropdown_pages (
array (
'name' => 'page_for_privacy_policy' ,
'show_option_none' => __ ( '— Select —' ),
'option_none_value' => '0' ,
'selected' => $privacy_policy_page_id ,
'post_status' => array ( 'draft' , 'publish' ),
)
);
wp_nonce_field ( 'set-privacy-page' );
2018-04-13 19:56:20 +02:00
submit_button ( __ ( 'Use This Page' ), 'primary' , 'submit' , false , array ( 'id' => 'set-page' ) );
?>
</ form >
< form method = " post " action = " " >
< input type = " hidden " name = " action " value = " create-privacy-page " />
< span >
2018-05-03 21:31:21 +02:00
< ? php _e ( 'Or create a new page:' ); ?>
2018-04-13 19:56:20 +02:00
</ span >
< ? php
wp_nonce_field ( 'create-privacy-page' );
Privacy: Move privacy policy page to `Settings` menu for consistency.
The page was originally placed under `Tools` so that it would be grouped with the pages to export and erase personal data, since they're all part of the effort to bring privacy management tools to Core ahead of GDPR's deadline. After more consideration, though, it makes sense to move this page to the `Settings` menu, since it's fundamental purpose is to configure an option, rather than to facilitate a recurring task. This keeps all of the configuration pages in a single place, making them consistent and easier to find.
Exporting and erasing personal data are recurring tasks, so they still make sense under the `Tools` menu.
Props xkon, helen, melchoyce, allendav, desrosj, ocean90, azaozz.
Fixes #43873.
Built from https://develop.svn.wordpress.org/trunk@43145
git-svn-id: http://core.svn.wordpress.org/trunk@42974 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-05-03 18:41:22 +02:00
2018-04-13 19:56:20 +02:00
submit_button ( __ ( 'Create New Page' ), 'primary' , 'submit' , false , array ( 'id' => 'create-page' ) );
2018-03-10 15:01:31 +01:00
?>
2018-03-09 16:04:33 +01:00
</ form >
</ td >
</ tr >
</ table >
2017-07-19 23:42:42 +02:00
</ div >
2018-03-09 16:04:33 +01:00
< ? php
include ( ABSPATH . 'wp-admin/admin-footer.php' );