Actually, there are 2 issues in your code: You were using PHP custom file name instead of menu_slug. You were not using action and method attributes of form tag. When you were submitting form WordPress redirecting into admin.php?on=Turn+Registration+On which is not a valid page. add_submenu_page function 4th parameter must be unique menu slug of your … Read more
A bare-bones version would look something like: function deny_post_date_change_wpse_131049( $data, $postarr ) { $user = wp_get_current_user(); // var_dump($user); die; // debugging if (in_array($user->ID,array(14,19))) { unset( $data[‘post_date’] ); unset( $data[‘post_date_gmt’] ); } return $data; } add_filter( ‘wp_insert_post_data’, ‘deny_post_date_change_wpse_131049’, 0, 2 ); I expect that in practice you probably want more complicated logic but that should get … Read more
wp_update_post does not update post_name
This is what I used, if I’m understanding you correctly. UPDATE wp_posts SET post_date=NOW(),post_date_gmt=NOW(),post_modified=NOW(),post_modified_gmt=NOW(); Worked for me.
You are correct; WordPress will not update custom database columns using wp_update_post() or wp_insert_post(). Instead of creating custom database columns, consider using post meta and/or taxonomy APIs. If you must altar the wp_posts table, you will need to update your custom columns on your own and you may run into issues with various other plugins … Read more
Turns out WordPress do not recommend updating GUID thus its disallowed. But we can update it using sql query: global $wpdb; $wpdb->update($wpdb->posts, [‘guid’ => $newGUID], [‘ID’ => $postID]);
It depends on where you’re using this. Is global $post giving you the specific post that you want to update? Your WordPress update post code looks right to me, but is the if-statement valid, and is $post->ID yielding the correct int?