Skip to content
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

Plugin ignores set email recipients when network activated #6

Open
mundschenk-at opened this issue Mar 11, 2016 · 4 comments
Open

Plugin ignores set email recipients when network activated #6

mundschenk-at opened this issue Mar 11, 2016 · 4 comments

Comments

@mundschenk-at
Copy link

When the plugin is network activated, the settings are only displayed in the network admin area. Alerts, however, are sent separately for each site on the network, and the settings for email recipients are completely ignored.

Additional info: This is a multisite network with completely separate domains (not sub-domains).

@cixtor
Copy link
Contributor

cixtor commented Jun 1, 2016

Commit 070bf8f addresses this issue, the technical details are available in the description of this pull-request. Feel free to download the dev archive to test these changes now, or wait until we release a new public version of the plugin; thanks for the report.

@mundschenk-at
Copy link
Author

I'm not sure that the pull request actually addresses this problem. Having only settings on the network is fine - I actually don't want to have to set up each site separately. However, the security warnings are then erroneously sent to the site admins instead of the mail addresses configured on the network backend.

Also, but this is a separate question, I don't quite understand the need to store site options in a PHP file instead of the database.

@mundschenk-at
Copy link
Author

I just tried this again with Sucuri 1.8.3. Unfortunately, still the same problem. There are only the network-wide settings (which is fine), but they are not applied properly.

@nobleclem
Copy link

Still a problem in 1.8.8. Just had a false positive alert sent to a site admin. I suspect its the one that triggered the scanning event.

Doing some digging it seems to be related to their use of get_option('admin_email') vs get_site_option('admin_email'). In general all of the CRUD option function calls should be the site versions of them. I currently don't see an easy way of fixing this without affecting other requests in a non-hacking way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants