Support » Plugin: Force Login » Redirect for GravityFlow plugin links post-authentication

  • Resolved warrencat


    GravityFlow (for Gravity Forms) utilizes a global “inbox” for creating various workflows around Gravity Form submissions. They also provide a method for linking to specific pages other than the global inbox through the use of certain merge tag parameters (see

    What I’ve found is that, if I’m not yet logged in to WordPress and I click this customized Gravity Flow merge tag from an email notification, after I authenticate, I am not taken to the page specified in the merge tag but, instead, I’m taken to the Gravity Flow global inbox. However, if I am already logged in and click the link from the email, I am directed to the correct page as specified in the merge tag.

    I have shared this information with the Gravity Flow development team, but I also wanted to share it with you, as I’m not sure where if the source of the issue lies with the Gravity Flow plugin or the WP Force Login plugin. I wanted to make you aware so that you would be able to test and/or work with the Gravity Flow development team to determine a fix.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Kevin Vess


    Hi– thanks for using Force Login!

    I suspect you might need to bypass Force Login based on some specific GravityFlow criteria to make this work for non-logged-in users.

    Check out the FAQ for some examples of how to bypass Force Login using the v_forcelogin_bypass filter:

    How can I add exceptions for certain pages or posts?

    Force Login Wiki on GitHub

    Unfortunately, I’m unfamiliar with GravityFlow and can’t recommend specific code conditional statements to try. Hopefully GravityFlow support will be able to offer some insight into what you need to make this work.

    If you find a solution to this, please share it here in case it would be helpful to someone else.


    • This reply was modified 2 months, 2 weeks ago by Kevin Vess. Reason: Simplified FAQ link text
    Plugin Author Kevin Vess


    Another thought–

    When visitors (non-logged-in users) are redirected to the login screen, the URL they tried to visit is passed to the login URL as a redirect_to query string in an attempt to send the visitor back to that URL after successfully logging in.

    The redirect_to query string encodes the URL as a string that can be used in a query part of a URL. It could be the visited URL (GravityFlow URL) is altered as a result of this URL encoding?

    Force Login uses the built-in WordPress function wp_login_url( $redirect ) to send visitors to the login screen with the redirect_to / visited URL. That WordPress function then urlencodes the redirect URL passed to it.

    If your issue is caused by the URL encoding, you might need to apply a fix using the login_url filter or use another method for linking to your GravityFlow pages.

    Good luck!



    Thank you for providing this guidance and options for a potential solution.

    Much appreciated!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.