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
I recommend 2 plugins: User Role Editor: This plugin allows you create new roles and adjust their capabilities. Hide Admin Menu: This plugin allows you hide menu items based on user role. You just need to select which menu items will be hidden for curtain roles.
You could just write a custom Dashboard Widget: Tutorial How to Add Custom Dashboard Widgets in WordPress In this article we will show you how you can customize dashboard widgets in WordPress. Documentation Dashboard Widgets API The Dashboard Widgets API (added in WP 2.7) makes it very simple to add new widgets to the administration … Read more
Altering the WHERE clause There’s a filter named posts_search that allows to filter the SQL WHERE clause used for the query during search (when WP_Query::is_search() returns true and WP_Query->s is set): add_filter( ‘posts_search’, ‘wpse134392PostsSearchSQL’, 20, 2 ); function wpse134392PostsSearchSQL( $sql, $wp_query ) { // Alter SQL clause here return $where; } Custom ORDERBY To intercept … Read more
Okay, this looks tricky, but I think it’s possible. The user-new.php file calls wp_dropdown_roles() to output the list of roles. The wp_dropdown_roles() function calls get_editable_roles() to get the list of roles to output. The get_editable_roles() function has a filter, editable_roles. So, you should be able to add a filter for editable_roles, such that, if the … Read more
You can find and replace instances of the old URL in your database but it’s best to use a tool that handles serialized data such as BackupBuddy to avoid breaking things like some plugins. Hope this helps!
I don’t believe WordPress sends HTTPS requests unless it has been told to do so. It sounds like you need to undo some previous configuration — most likely change/remove the FORCE_SSL_LOGIN constant. You may have plugins participating as well though. Make sure to check that. Reference: http://codex.wordpress.org/Administration_Over_SSL
admin_init runs on admin pages, not the front end. The equivalent front end action, init, is too early to check is_page. A safe action for redirection is template_redirect: function xyz() { if( is_page( 172 ) && ! current_user_can(‘update_core’) ) { wp_redirect( home_url() ); exit; } } add_action( ‘template_redirect’, ‘xyz’ );
The way you describe it, it sounds as if WordPress was installed to your root directory. That however doesn’t explain why http://localhost:8888/wp-admin/ doesn’t work, unless you renamed the directory..? Try accessing http://localhost:8888/wp-login.php