Implemented but not functional

“Fairly similar” to your local install is not enough then. What exactly makes the plugin work on one instance but not the other? The plugin is identical in both instances, right?

I offer a guess at one major difference in your two installations: This plugin will only do its “thang” on a Multisite Network enabled version of WordPress: https://codex.www.ads-software.com/Create_A_Network

https://www.ads-software.com/plugins/more-privacy-options/installation/

If the plugin is not “Network Activated” then it will not do what you want.

Network Activate the plugin through the ‘Network Plugins’ menu in WordPress
Set multisite “Network Visibility” option at Network-Settings page

The line 184 blogname php notice is not a deal breaker. Just means the subject field of the email heading to SuperAdmin is missing the blogname. Thanks for the debug there.

Thanks for the response and explaining the issue and updating the plugin.

Unfortunately, I was not able to resolve the issue and ended up writing a function to do the job. Although I reckon your update is not related to my issue, I would test it … but my site is launched and getting its peak in traffic at the moment.

FWIW, I tested network activating the plugin on both sites as well as not, so maybe that wasn’t the issue. I also tried a few other things like re-saving permalinks, which tends to help with other plugins once in a while.

My guess is that it’s W3tc-related. I’d guess 50%+ of the “issues” I encounter seem to tie back to that plugin but, unfortunately, I don’t often have opportunity to turn that off on production. So, I never know.

Or, .htaccess is another thing that is obviously not exactly the same in both environments, so maybe that’s it.

Thanks again. I like this plugin and wanted to use it. Wanted to provide feedback just in case it’s useful to others or reveals potential fix for others.

I do not have W3tc caching enabled so I can’t test, but if cache is stale, then a stale blog_public option would/could be the culprit, but you could see/test that if switching up the backend settings elsewhere.

I had a similar issue on a multisite network and what fixed it for me was disabling the page cache on the sites that were not supposed to be accessible to the public.
The behaviour I was experiencing was that pages were being cached when an editor was logged in and viewing pages they had made changes to.

To disable the page cache on individual sites you first need to go to the Network Settings for W3TC and de-select the option that says “Use single network configuration file for all sites.”
You will find this option in My Sites -> Network Admin -> Performance -> General Settings. The option is in the block of Miscellaneous settings.

Then you need to disable the page cache for each individual site that you don’t want to be publicly accessible. You’ll find this setting in Site -> Performance -> General Settings.

Hope this helps!