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.
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.
