-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multisite support? #8
Comments
I'd also love to know about multisite support. |
@roytanck I ended up extending this a bit for multisite. I don't know what your needs are but maybe this can help. I added this function to the very bottom of the expire-user-passwords.php file, right before the final
"Spoke" is our internal word for blogs/subsites. In addition, in render_submenu_page() in includes/class-settings.php, I've updated the form to the following:
The additional checkbox added to the form, which only appears on the main site of your multisite network, sets a flag in the $_REQUEST object that the function above this form code checks for. If present, it then loops through each blog/subsite/spoke of the network and assigns those settings to each. It still allows overriding on a specific blog/subsite/spoke and overwriting the overrides if done again from the main site and broadcast out to the network. Hope this helps. |
@kkerley Thank you for sharing your code. My team has opted to create our own (internal) plugin solution, which I'm unfortunately unable to share. |
Thank you for continuing this plugin. Team members found it to work well on a single site WordPress install. We're looking into deploying it on multisite installs as well, and I'm wondering whether this is supported.
The plugin seems to check user roles before determining whether a user's password should expire. On multisite, the same user can have different roles on different subsites. Does Expire User Passwords take this into account? Would you recommend running the plugin in multisite, and if so, should we network-activate it?
The text was updated successfully, but these errors were encountered: