Tung Du

Hi @roman89,

Yes, your content won’t be indexed unless you whitelist the IP of search engines.

Update: It worths noting that RSA doesn’t work with page caching plugins, so if you use any, your content may be cached and served by your web server, then your content may be exposed to the public (and search engines).

• This reply was modified 5 years ago by Tung Du.

About your question, it breaks due to this PR: https://github.com/10up/safe-redirect-manager/pull/182

Hi @freezhao, which WP version are you using? If you’re using anything < 5.3, you can try to update (remember to backup) to WP 5.3 which introduced a new way to handle large images. See: https://make.www.ads-software.com/core/2019/10/09/introducing-handling-of-big-images-in-wordpress-5-3/.

Hi @tobiaseigen,

In your case, you can consider using regex to achieve the previous behavior. For example: redirect /news/(.*) to /news-stories/$1.

Hi @martinbraun, the common case would be cache plugins cause RSA to not work. I will test WPFC with RSA to see if I can reproduce your issue. In the meantime, you can check the FAQ section of the RSA page for more information about cache plugins:

Most commonly, Restricted Site Access is not compatible with some page caching solutions. While the plugin hooks in as early as it can to check visitor permissions, its important to understand that some page caching plugins generate static output that prevents plugins like Restricted Site Access from ever checking individual visitors.

To the extent that sites blocked by this plugin should not need to concern themselves with high scale front end performance, we strongly recommend disabling any page caching solutions while restricting access to your site. Keep in mind that most page caching plugins do not cache the “logged in” experience, anyhow. Also note that the plugin is fully compatible with other caching layers, like the WordPress object cache.

Hi @scamartist26, Simple Page Ordering doesn’t support attachment because attachment works differently. Page and hierarchical post types are supported by default, post and custom post type can be supported by either one of two methods you mentioned above (we don’t need both).

Hope that helps!

@desmith, for your issue, you can fix temporarily by removing the HTTP_CLIENT_IP or unset it.

Or you can create a mu-plugin to avoid modifying the main plugin, mu-plugin is loaded first so you can use it to alter $_SERVER, like this:

$_SERVER['HTTP_CLIENT_IP'] = $_SERVER['HTTP_X_FORWARDED_FOR'];

• This reply was modified 5 years ago by Tung Du.

Hi @desmith, in the get_client_ip_address() method, the headers listed there are processed one by one, and it returns the first valid IP immediately. So if HTTP_X_FORWARDED_FOR contains the correct and valid IP, the only value can take over it comes from HTTP_CLIENT_IP. REMOTE_ADDR has the least priority when detecting client IP. Can you check if HTTP_CLIENT_IP has value?

It’s impossible to cover all network architecture, so I will discuss with our team to see if we should add a filter to the headers in get_client_ip_address(). I think it will be the most flexible solution for complicated networks.

Hi @nige-mcilwaine, I’m sorry for the late reply. Can you test again with the latest version of WordPress and Restricted Site Access? In my test, adding new users and resetting password work as expected.

Glad that you found the solution!

For your question:

Short answer: No, RSA doesn’t support restrict the direct access to attachment.

Long answer: Restricted Site Access hooks to parse_request to limit access to your site to visitors, so it won’t have any control over the direct link of the attachment which is processed directly by your webserver.

Hope that helps! I’m marking this top as resolve. If you have any other question, please open a new topic, we’re happy to help!

• This reply was modified 5 years ago by Tung Du.

@artus2000 Can you clarify your question a little bit: How do you want to restrict access to the attachments?

We use private IPs for the development of this plugin, so yes, it will.

When I list more than one range in the wp config, it only picks up the first range:

It’s expected behavior because you can’t redefine a constant.

You can whitelist multiple IP range like this:

define( 'RSA_IP_WHITELIST', '192.168.1.0/24|192.161.3.0/24|192.161.4.0/24' );

• This reply was modified 5 years ago by Tung Du.

Hi @wpyoji,

We confirmed this issue and working on the fix. The fix will be shipped in the next update soon.

Meanwhile, you should use https://your-domain.com/vendor_dashboard/shop_settings/ to update your bank information.

Best,
Tung Du

• This reply was modified 5 years, 8 months ago by Tung Du.

Hi @myriamrichardportfolio,

Thank you for letting us know. We tested and confirmed this is an issue of our plugin. We will fix it in the next release.

Best,

Tung.