In a wordpress network the users are of the network and not an individual blog in the network. This means that technically users do not login to a blog they can only login to the network. If I understand your question correctly, you have nothing to do for what you want, this is how a … Read more
Your comments state that the line in question that gives the fatal error causing your white pages is this line: <div id=”whatstrending”><h1><?php echo get_option(‘radio_options’)[‘blog-header’];?></h1></div> Most notably: get_option(‘radio_options’)[‘blog-header’]; Or more specifically: functioncall()[] This is invalid PHP up until recently, and your new host doesn’t run a version of PHP that supports this. You can fix it … Read more
This is normal behavior for WordPress. As with most things in WordPress, there is a plugin for what you are trying to do. Try this: https://wordpress.org/plugins/peters-login-redirect/
If you’re trying to convert an existing single-site WordPress installation a path-based Multisite, there’s a note on the Codex: You cannot choose Sub-directory Install (for a path-based network) if your existing WordPress installation has been set up for more than a month, due to issues with existing permalinks. If you want to switch to a … Read more
You can use the login_redirect filter: add_filter( ‘login_redirect’, ‘wpse_159078_login_redirect’ ); function wpse_159078_login_redirect( $redirect ) { if( ! current_user_can( ‘update_core’ ) ) { // if it’s not a super admin that’s logging in $redirect = get_home_url(); } return $redirect; } References login_redirect filter get_home_url()
A blank page usually indicate that you have some php error. You should look at your PHP error log file and try to fix the error if there is one.
You have site1 and site2 folders on your server, so Apache is serving those hence the file listing. Multisite however is trying to serve those sites using URL rewriting, so deleting those folders should fix the issue
Multisite vs Role Scoper
Only one thing I can see to solve this problem is to use redirection by .htaccess. But my question is, why don’t you manage to redirect old URLs to the new version, without the /blog ? Because I guess, your concern is most about SEO no ? redirect 301 /blog/ http://www.yourdomain.com/
Is there a built in method to protect pages?