Jakub Potocki, a WordPress developer

Hi Peter,

Thanks for your reply.

I tested exactly that option already.

Results from my staging clone:

• with only WooCommerce + GetResponse Official active, the endpoint
  /wp-json/wp/v2/users?context=edit&per_page=1&page=1
  returns HTTP 200 for an authenticated administrator using an Application Password
• after enabling Wordfence, the same endpoint returns HTTP 401:
  {"code":"rest_user_cannot_view","message":"Sorry, you are not allowed to list users.","data":{"status":401}}
• unchecking the option
  “Prevent discovery of usernames through ‘/?author=N’ scans, the oEmbed API, the WordPress REST API, and WordPress XML Sitemaps”
  did not change the result
• after fully resetting Wordfence and disabling the plugin, the endpoint returns HTTP 200 again
• after enabling Wordfence again on default settings, the endpoint returns HTTP 401 again

So in my environment this issue is reproducible even after:

• full reset
• default settings
• unchecking the username discovery option

Additional note:
I also identified a separate conflict with Really Simple Security. Its “Disable user enumeration” option was also blocking the same integration. After disabling that option, the GetResponse integration worked. However, Wordfence still independently reproduces the issue on staging when enabled.

This suggests the problem is not only that checkbox, but a broader compatibility issue in my environment.

If helpful, I can provide:

• exact request/response output
• plugin list
• reproduction steps

Best regards

Thank you, that would be great. I’m looking forward to it 🙂

• This reply was modified 2 years, 1 month ago by Jakub Potocki, a WordPress developer.

Thank you @mohsinbsf for the reply.
A word of advice, I think Spectra One Theme would gain much more popularity if it was possible to somehow make it multilingual with the free version of Polylang. I would happily transit from Astra Pro to Spectra One, however, for me and my clients this is a deal breaker (paying subscription fee for the functionality, that could be easily bypassed by using a standard theme without additional fees).

• This reply was modified 2 years, 4 months ago by Jakub Potocki, a WordPress developer.