One way to achieve this is by looping through the parent pages and fetching their respective children pages ids. The resulting arrays can then be merged and used in the ‘post__not_in’ variable. add_filter( ‘parse_query’ , ‘exclude_pages_from_admin’ ); function exclude_pages_from_admin( $query ) { global $pagenow,$post_type; $pages = array(‘1′,’2′,’3’); foreach ( $pages as $parent_page ) { $args … Read more
What about (1) current_screen? action hook, or a condition for (2) get_current_screen() in your conditional and then calling wp_redirect? Both give you a WP_Screen object which has several parameters, including a $parent_base property that can give broader inclusion if needed, too. Here’s the property list from the codex: $action Any action associated with the screen. … Read more
There is a global variable containing the current page in the admin area, called $pagenow. You can use this to detect where the user is now. Now, in your case, you are on admin.php and there are 3 parameters set in the URL, page, delete and id. So: if( in_array( $pagenow, array(‘admin.php’) ) && ( … Read more
You indicated that your login page is your home page. If you want all non-logged in users to then be directed to the home page to log in, you need to check a couple of things: Is the user logged in? Is the current page the home page? You can do these things with is_user_logged_in() … Read more
You can’t. WordPress stores the passwords in the DB as hashes of the user password using a salt which is unique to the install. In an import situation (unlike full migration) you will probably not have the same salts in the new site and password validation will fail. You should just notify the users that … Read more
by default the editor role should not have access to plugins nor appearance menu. But maybe this roles is already customised in your installation? here is a list of editor default capabilities via functions.php you can remove everything in the appearance menu like so: $role_object = get_role( ‘editor’ ); $role_object->remove_cap( ‘edit_theme_options’ ); to remove access … Read more
You cannot enable or disable plugins wholesale for specific user roles. A plugin’s ‘active-ness’ is not determined per-user. If you attempted to actually deactivate a plugin for a specific user role, then any time a user with that role logged in the plugin would be deactivated for every user that visited your site. A user … Read more
After talking to my hosting provider, many a times, the issue finally got resolved. Solution: Fixing directory and file permissions. I was told that: All directories should have the permission 755. And, all files should have the permission 644. Once, the hosting provider reset permissions of all the directories and files present in the folder … Read more
admin_init is called after wp-admin/menu.php is included, so the access check has already been executed and the admin_menu action has fired by the time you execute test_options(). Remove the admin_init hook and call test_options() directly, or find another way of structuring your code so that the admin_menu hook is set up correctly. You might think … Read more
I had some problems upgrading to 3.0.3 on a multi-site installation. I had used the automatic upgrade and it failed, but luckily, downloading and extracting the new files from WP.org and uploading them directly fixed it. I would try that first. If that doesn’t work, try re-uploading your backup files. You did make a backup, … Read more