Field Manager: Login Unsucessful

  • wrstaff
    Asked on February 3, 2016 at 7:16 PM

    I'm trying to use the field manager which was recommended to me by the support team.  I'm going to http://fieldmanager.jotform.io/, logging in using my Jotform login credentials and the page says "Login Successful.  Please wait while redirecting..."  Then the page never redirects and I'm still on the login page.

  • Charlie
    Replied on February 4, 2016 at 3:52 AM

    Apologies for the inconvenience.

    I tried the Field Manager App but was not able to replicate the problem. May we know if you are logged in to your JotForm account (https://www.jotform.com) while opening the app?

    You can refresh the page and see if you are able to bypass the log in page for the 2nd time. Make sure though to allow authorization on it. You can also try using a different browser and see if that gives you a different result, I'm using Google Chrome right now. We'll wait for your response.

  • wrstaff
    Replied on February 4, 2016 at 11:13 AM

    When I attempted to login to the Field Manager App yesterday, I was also logged into my Jotform account.  Today, I tried logging into just the Field Manager App without having Jotform open using IE 11 and experienced the same problem.

    I was able to login to the Field Manager App successfully using Chrome both while not logged into Jotform and while logged into Jotform.

  • Charlie
    Replied on February 4, 2016 at 12:38 PM

    I tried using my IE browser and visited http://fieldmanager.jotform.io but still was unable to replicate the problem. I tried without logging in to www.jotform.com.

    Here's my screencast:

    Field Manager: Login Unsucessful Image 1 Screenshot 20

     

    It works on your Chrome and in my IE11, my best guess would be that there's a cache problem on your IE at that time. Have you tried clearing your cache on IE? See if that resolves the problem.

    If you have an add-on/plugin/extension in your browser, similar to a ad-blocker, then it is possible that it may be blocking our scripts and resources.