Allow by IP Range

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!

Thanks Kevin!

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.

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

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

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

Thanks!

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.

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!