next »

[haldera]

How can I make the logout button be redirected to a specific page?  I have the calendar being used off of a website that I created, and would like anyone who logs out of the calendar to be forced back to the home page of the website, instead of the anonymous calendar page.  I don't know enough about CGI to do that.  Could someone help me out?

[DanO]

** How can I make the logout button be redirected to a specific page? **

One way might be to make a new template containing an HTML meta refresh or JavaScript code on it to direct users where you want them to go. You'd then have to modify the 'Logout' link on the calendar template to point to the new template by adding "&template=Template_Name_Here" (without the quotes) to its URL.

JMO

Dan O.

------------------

[haldera]

I've tried that.  Unfortunately, it doesn't actually log them out.  If they hit the back button or re-enter the direct link, they are back into the calendar.  The logout CGI link that comes with the calendar destroys the cookies.  I would like to have it destroy the cookies as well as redirect to a page of my choice.

Does that make sense?

------------------

[DanO]

** The logout CGI link that comes with the calendar destroys the cookies. **

And is what I suggested you continue use when I said "You'd then have to modify the 'Logout' link on the calendar template to point to the new [CalendarScript] template".

I didn't say to completely replace the link altogether. The way I suggested would still go through CalendarScript which should delete the cookies.

Dan O.

------------------

[haldera]

Ok, I tried that, utilizing a different template that had a meta refresh tag in it.  When the logout script ran, it did actually log out the user.  However, it merely moved the user back to the login screen (which is where they are forced to start from) instead of going to the template page.  I thought that if I pointed the link to the calendar.pl?template=newtemplate.html&command=logout page, it would both logout, and go to the newtemplate.html page.  Did I think about this wrong?

------------------

[DanO]

** I thought that if I pointed the link to the calendar.pl?template=newtemplate.html&command=logout page, it would both logout, and go to the newtemplate.html page. **

It is suppose to.

I'm afraid without being able to see it for myself, I couldn't say what is occurring.

Dan O.

------------------

[DanO]

** it merely moved the user back to the login screen **
Just a thought, do you have the calendar set to 'require log-in'?

If so, what I suggested above will probably not work since the new template is part of the calendar which they would need to be logged into to see.

Dan O.

------------------

[haldera]

Yes, I actually used the login script from much2.com, which worked wonders by the way.  I have it so when you click over to the logon script, it immediately takes you to the login page.  After you enter your login information, it automatically takes you to the correct calendar.  Unfortunately, after you click logout, it takes you back to the login screen, instead of the main site.  I would be more than happy to email you screen shots, if that would help.

------------------

[DanO]

Let me think about the problem and I'll get back to you in a couple of days.

Dan O.

------------------

[DanO]

All I can think of is putting a conditional in the login.html template something like:

<% if($main::in{command} eq "logout") %>

# meta redirect or JavaScript here

<% } else { %>

# current template code

<% } %>

Something similar should probably be used to remove the log-IN form from the page and also display a message about the redirect and also provide a manual link for browser which won't automatically forward users.

JFYI

Dan O.

------------------

[haldera]

Excellent!  Thanks so much for that, it worked wonders!  Your idea about the second page is definitely a good one, I will be putting that in today.  But in the mean time, it just flashes the login page really quick, then refreshes back to the opening page of the website, as I wanted.  I have to leave the logIN page, because I need customers to login.  It works perfectly as I needed it to, thanks.

Also, I needed to add a { on the first line, at the end, just so you know.  Like this:

<% if($main::in{command} eq "logout") { %>

------------------

[This message has been edited by haldera (edited December 06, 2005).]

[DanO]

** Your idea about the second page is definitely a good one **

I never suggested a second page. All changes I suggested are in the very same template, just in separate places.

** I have to leave the logIN page, because I need customers to login. **

Yes but they don't need to do it when they just logged out (which is what the if($main::in{command} eq "logout") condition tests for) and are being redirected elsewhere. It will just limit what is seen by the user in between, hopefully reducing the possibility of them thinking they missed something (and maybe trying to go back... again and again and again, etc.). But it's up to you.

** I needed to add a { on the first line **

Good catch.

Dan O.

------------------