Hm, not sure! Can you dig up the specific error message so I can look into it? It should be in your web server’s error log. If you can’t find it, try using one of the debug modes in WordPress to get access to the PHP error:
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging
We’ve been having a problem getting the debug log to work. But I was able to install ok on another network install with no problems.
Question. For the network settings, I’m trying to find a way to activate on all sub-sites automatically, but then adapt each site depending on unique needs. Most would be standardized, but a few would need the ability to be customized. Is there a way to switch the network settings so that individual sites could override the network settings or to bulk activate on all sites and have new site have the plugin activated (but still customizable)?
So the way Authorizer is currently built, if you Network Activate it, then you have the option of setting certain options at the network level that override any options of the individual sites. For example, at the network level you can set the auth backend (CAS, LDAP, or Google) that all sites use; you can list individual users that will have access to all sites in the network; and you can set the authentication policy (public vs. private; allow all external users vs. allow specified external users).
That’s the opposite of what you’re thinking (individual sites override network settings), but I think you can make it work in your situation. Any thoughts?
Re: the install error, it might have been a conflict with another plugin, but without seeing specific error messages I’m not sure.
I’ll mark this as closed and open a new question about the second question.
