From e96ecf2f9317b0f7d547e86bcaf67b3aebecd8ea Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Mar 2011 13:44:42 -0400 Subject: [PATCH 1/1] response --- doc/forum/postsignin_redirect_not_working.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/forum/postsignin_redirect_not_working.mdwn b/doc/forum/postsignin_redirect_not_working.mdwn index fdef56375..bc8855b7b 100644 --- a/doc/forum/postsignin_redirect_not_working.mdwn +++ b/doc/forum/postsignin_redirect_not_working.mdwn @@ -14,3 +14,17 @@ Then when it runs for postsignin its supposed to pull it out and send the user t Full code is available on the plugin page: [[plugins/contrib/justlogin]]. I searched the site and there's very little info available for postsignin or redirect. Perhaps I'm using the wrong function? + +> I don't know why you end up on the prefs page. Have you tried +> looking inside the session database to see what postsignin +> parameter is stored? +> +> But, `cgi_postsignin()` assumes it can directly pass the postsignin cgi +> parameter into `cgi()`. You're expecting it to redirect to an url, and it +> just doesn't do that. Although I have considered adding a redirect +> there, just so that openid login info doesn't appear in the url after +> signin (which breaks eg, reload). That would likely still not make your +> code work, since the value of postsignin is a url query string, not a +> full url. +> +> I'd suggest you put a do=goto redirect into postsignin. --[[Joey]] -- 2.39.5