Title: Allow by IP Range
Last modified: August 30, 2016

---

# Allow by IP Range

 *  Resolved [invisiblue](https://wordpress.org/support/users/jayharle/)
 * (@jayharle)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/allow-by-ip-range/)
 * Any plans to include the ability to allow by IP range, users to see the site 
   without logging in? And then users outside of the range would need to login.
 * [https://wordpress.org/plugins/wp-force-login/](https://wordpress.org/plugins/wp-force-login/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [Kevin Vess](https://wordpress.org/support/users/kevinvess/)
 * (@kevinvess)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-6505761)
 * Not exactly, but there may be a new version released in the near future that 
   would allow users to pass a boolean (true or false) value to stop the plugin 
   from redirecting. This would offer more flexibility for users to stop the redirect
   for _any_ reason and not just limit them to whitelisting absolute URLs.
 * Thanks for your interest in the plugin and stay tuned for future updates!
 *  Thread Starter [invisiblue](https://wordpress.org/support/users/jayharle/)
 * (@jayharle)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-6505886)
 * Thanks Kevin!
 *  [allenlee007](https://wordpress.org/support/users/allenlee007/)
 * (@allenlee007)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-8532689)
 * You mention in this old thread that there may be a new feature developed “that
   would allow users to pass a boolean (true or false) value to stop the plugin 
   from redirecting.”
 * Any help on disabling the Force Login plugin within a session if a querystring
   name:value pair is passed through in the url – essentially whitelisting the whole
   site if the querystring is ever recognized within a browser session.
 *  Plugin Author [Kevin Vess](https://wordpress.org/support/users/kevinvess/)
 * (@kevinvess)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-8534586)
 * Yes – in version 5.0 I added the new `v_forcelogin_bypass` filter that allows
   you to pass a boolean (true|false) value to stop the plugin.
 * Here is an example of how to use the filter:
    [https://gist.github.com/kevinvess/641aad7cbe5bb42a751ef8ba7fee74ce](https://gist.github.com/kevinvess/641aad7cbe5bb42a751ef8ba7fee74ce)
 * Also, checkout my LinkedIn article for more details about the updates in version
   5.0:
    [https://www.linkedin.com/pulse/new-features-force-login-50-kevin-vess](https://www.linkedin.com/pulse/new-features-force-login-50-kevin-vess)
 * Lastly, you asked:
 * > Any help on disabling the Force Login plugin within a session if a querystring
   > name:value pair is passed through in the url
 * Checkout the Force Login Wiki on GitHub for examples of the different methods
   for whitelisting dynamic URLs, including a query string name:value pair:
 * [https://github.com/kevinvess/wp-force-login/wiki/Whitelist-Dynamic-URLs#method-3—page-url-based-on-query-string-parameters-andor-values](https://github.com/kevinvess/wp-force-login/wiki/Whitelist-Dynamic-URLs#method-3—page-url-based-on-query-string-parameters-andor-values)
 * Thanks!
 *  [allenlee007](https://wordpress.org/support/users/allenlee007/)
 * (@allenlee007)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-8543253)
 * Thanks much for pointing out the bypass function. Very helpful feature. So the
   only way that the bypass would persist for a user session would be if every subsequent
   link within the page contained the same querystring var.
 * Any idea on how I can append the “bypass querystring” to all url links rendered
   on the wordpress page only when the “bypass querystring” is recognized by the
   my_forcelogin_bypass function?
 * I am embedding this site within a software application and would like for the
   page to remain ForceLogin protected “in the wild”, yet totally bypassed when 
   embedded within the application. Hope that makes sense.
 *  Plugin Author [Kevin Vess](https://wordpress.org/support/users/kevinvess/)
 * (@kevinvess)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-8543892)
 * The `v_forcelogin_bypass` filter allows you to bypass Force Login for any condition.
 * The examples I linked to are just examples of how it could work. You’ll need 
   to write your own conditional statement to meet your specific needs for when 
   to bypass Force Login.
 * > I am embedding this site within a software application and would like for the
   > page to remain ForceLogin protected “in the wild”, yet totally bypassed when
   > embedded within the application.
 * It sounds like you need to figure out how your application can pass a session
   key/value to your WordPress site that it can check for. And if the key exists
   or has a specific value, then bypass Force Login.
 * As for exactly how you can pass this session data from your application, I won’t
   be able to help through here. I suggest you hire a developer to help you integrate
   your application with WordPress.
 * Thanks for using Force Login!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Allow by IP Range’ is closed to new replies.

 * ![](https://ps.w.org/wp-force-login/assets/icon.svg?rev=1904031)
 * [Force Login](https://wordpress.org/plugins/wp-force-login/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-force-login/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-force-login/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-force-login/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-force-login/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-force-login/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Kevin Vess](https://wordpress.org/support/users/kevinvess/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/allow-by-ip-range/#post-8543892)
 * Status: resolved