I was able to solve this problem by using the admin_body_class filter to add a class name to the <body> element of the admin page, and writing selectors for that class in my stylesheet. add_filter( ‘admin_body_class’, ‘add_status_classes’ ); function add_status_classes( $classes ) { $post_meta = get_post_meta( get_the_ID() ); $is_darkmode = $post_meta[‘_is_post_dark_mode’]; if ( $is_darkmode ) … Read more
Aha, I finally got it working: <?php /* Plugin Name: Akismet Better Privacy Notice Description: Inform users about what’s actually happening with their data */ add_filter ( ‘akismet_comment_form_privacy_notice_markup’, ‘better_display_comment_form_privacy_notice’ ); function better_display_comment_form_privacy_notice() { echo sprintf( ‘<p class=”akismet_comment_form_privacy_notice”>’ . ‘Warning: This site uses Akismet to filter spam.’ . ‘ Until or unless I can find a … Read more
If you look in the plugin’s directory plugins/wpmp_switcher/wpmp_switcher.php on line 53 you will see this: add_action(‘wp_footer’, ‘wpmp_switcher_wp_footer’); so you can either remove this action and call it in your theme your self with: remove_action(‘wp_footer’, ‘wpmp_switcher_wp_footer’); or you just make sure that wp_footer(); is inside your wrapper>footer divs.
pre_get_posts is correct. the code from will prevent any non-admin from seeing anyone else’s posts. http://blog.rutwick.com/display-only-the-posts-authored-by-the-current-wp-user-on-the-posts-page-in-the-back-end to limit that to only 1 post type you’d add in one more condition and check $typenow == ‘your_custom_post_type’: add_action(‘pre_get_posts’, ‘filter_posts_list’); function filter_posts_list($query) { //$pagenow holds the name of the current page being viewed global $pagenow, $typenow; //$current_user uses … Read more
as this is a default field, i don’t think it is possible to achieve what you want with the help function hooks, however you can do this by editing edit-form-advanced.php file inside wp-admin folder, the code you may want to edit is located in line # 291, this is the input type for title field … Read more
Priority All hooks & filters have a priority. Those are used to order the functions that are attached to hooks. By default the priority is 10. As the default is 10, there’s a big chance that your filter/action gets hooked too early and therefore can’t affect the actual output. Edit: Imagine that the plugin hooks … Read more
Solved – I didn’t realize wordpress overwrites the functions in the default theme if I place them in my child theme functions.php. So all I had to do was paste them into my functions.php and edit how I want them.
To fire a hook you can use following functions: do_action – executes a hook created by add_action. do_action_ref_array – execute functions hooked on a specific action hook, specifying arguments in an array. This function is identical to do_action, but the arguments passed to the functions hooked to $tag are supplied using an array. If you … Read more
Since you are using OOP, you probably want to architecture your plugin more efficiently. This is fine, but you’ll be the one to structure your classes and build them. So what if you put it in the __construct() function? That’s fine, as long as you initiate a new instance of the class. Putting it in … Read more
You can try adding a query var using the ‘query_vars’ filter like so: add_filter(‘query_vars’, ‘my_plugin_query_vars’); function my_plugin_query_vars($vars) { $vars[] = ‘login’; return $vars; } That may populate $wp_query->query_vars, if not I have successfully used the get_query_var function in one of my projects, try something like: function my_plugin_display() { if(get_query_var(‘login’)) { include( ABSPATH . ‘/wp-login.php’ ); … Read more