Couple Questions Regarding FastPass
Hello All,
I beleive that everything is all set up on my end in regards to FastPass. I really like the fact that our users can post threads without actually needing to go through the process of creating a Get Satisfaction account. Definitely a great idea :) I have just one minor concern:
The issue is that if a user attempts to create a question thread when they are not currently signed in, the page redirects them to our company's FastPass login page. After successfully authenticating and creating the FastPass login cookie, the login page that we've built then sends the user to the Referrer URL of the original request. The referrer url contains a get parameter which contains the title of the topic they were creating, but unfortunately it appears that the post description is not saved in any sort of session state. Thus, the user will have to retype their entire post description again, as well as any post tags they may have specified. I'm sure the user could click their browser's back button to re-navigate to the page, but I have a feeling a lot of our users might not know to do this.
I'm wondering if there is a way to specify that the "Sign On" button that the user clicks to be redirected would instead open a new target window? This way, the user can authenticate with our company login page, which will then create the FastPass login cookie and prompt them to close the current window / tab. Meanwhile, there original post would never be closed.
When you get a chance, please let me know what you think.
Thanks,
Chris Myers
I beleive that everything is all set up on my end in regards to FastPass. I really like the fact that our users can post threads without actually needing to go through the process of creating a Get Satisfaction account. Definitely a great idea :) I have just one minor concern:
The issue is that if a user attempts to create a question thread when they are not currently signed in, the page redirects them to our company's FastPass login page. After successfully authenticating and creating the FastPass login cookie, the login page that we've built then sends the user to the Referrer URL of the original request. The referrer url contains a get parameter which contains the title of the topic they were creating, but unfortunately it appears that the post description is not saved in any sort of session state. Thus, the user will have to retype their entire post description again, as well as any post tags they may have specified. I'm sure the user could click their browser's back button to re-navigate to the page, but I have a feeling a lot of our users might not know to do this.
I'm wondering if there is a way to specify that the "Sign On" button that the user clicks to be redirected would instead open a new target window? This way, the user can authenticate with our company login page, which will then create the FastPass login cookie and prompt them to close the current window / tab. Meanwhile, there original post would never be closed.
When you get a chance, please let me know what you think.
Thanks,
Chris Myers
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Good question. I will pull in someone with a bit more technical knowledge to answer this one.
-
Sounds good. Thanks Eric. -
Inappropriate?Hi Chris,
We have an implementation we're working on for the feedback widget that works just like you describe. I'll look into making this available for the main FastPass signover experience. Makes good sense!
1 person says
this answers the question
Loading Profile...


EMPLOYEE