It does sound strange, as there is very little that I thought would impact a multi site. In fact my original development was for a multi site.
I can’t see much difference at a technical level between network activating or individual activation, as there is no internal code in the plugin that differentiates.
I will test when I get a chance.
Can you elaborate how you tested that it was working / not working? What was your test? Also can I check, you are aware that the plugin deliberately does nothing if you are logged in ( in is designed to stop external enumeration only )?
-
This reply was modified 9 months, 1 week ago by
Alan Fuller.
I read the other support posts so yes, I was logged out when doing my tests.
I test using this URL:
https://%%domain%%/wp-json/wp/v2/users
When I network activate, it works when %%domain%% is the name of the main site domain, but does not work on any other site domain of the same multisite install.
Thanks for that – it sound like something related to the rest API. I will test and revert back.
Are you using sub site multi site or sub directory? Are you using any domain mapping on top?
Thanks for bring this to my attention.
I am using domain based multisite where each site has its own domain and there is no parent/child relationships between these domains.
I am using Microsoft IIS as web server and set up rewrite rules accordingly, everything works fine.
As I am a bit in a hurry (sorry), I have deactivated your plugin and added a piece of code in the child theme I use to deactivate the WP REST API, so now user enumaration through REST API is no longer available.
After some more tests, deactivating the whole REST API is a bit violent, so i have to move back.
Any solution on your side will therefore be much appreciated.
Thanks we have tested it and that is right.
Next step is to work out a solution. With the holiday break that won’t be instant I’m afraid. But I will work it out and revert back.
for sure, have a nice holiday season and I hope to hear good news from you next year.
Sorry it has taken a while, took a bit to get debugging working on multi-site.
That is now fixed in version 1.4.6
It was just not setting the default options early enough for network activation.
With 20-20 hindsight you could have worked around simply by saving settings in each sub site.
Anyway that is fixed now.
