Forums / Suggestions / Redirect on login - Checkbox as infocollector

Redirect on login - Checkbox as infocollector

Next topic

Author	Message
Bjørn Kaarstein	Monday 04 August 2003 4:01:41 am It would have been a nice option to be able to redirect each specific user to it's own specific node on login. It'd also been rather nice to be able to use checkboxes/radiobuttons as information collectors, as this is very much used in contact forms. Regards Bjørn.
Paul Forsyth	Monday 04 August 2003 3:02:13 pm We have dynamic redirect on logon working fine, as specified in this doco: http://ez.no/developer/ez_publish_3/documentation/customization/tips_tricks/redirecting_after_content_publishing Radio buttons can be used as information collectors. Look at the source of this page in our site: http://www.pobox.co.uk/po_box/contact_us This page was built after advice from Jan, in this thread: http://ez.no/developer/ez_publish_3/forum/developer/radio_buttons_within_forms Paul
Bjørn Kaarstein	Monday 04 August 2003 11:59:43 pm Hi Paul. I'm not quite sure if this is what I mean by dynamic login. I have used this approach in 3.0, in order to redirect all logins to node 19. What I miss is the opportunity to redirect <user1> to node 19, <user2> to node 25 etc. How about an option <redirectToNode> when creating the user in the admin interface? Regarding radiobuttons within forms, I have studied the thread you're referring to earlier. I managed to create the buttons without problems, but I couldn't get any information sent from them. Also here, my suggestion was to have the "information collector" possibility in the admin interface, like we have on a textline. I'll take a look at your source when creating my next form. Thanks a lot! Regards Bjørn
Paul Forsyth	Tuesday 05 August 2003 12:25:52 am You can make the redirect dynamic by creating more tpl logic that ties into whatever you have put into your class objects. A recent site i worked on had something similar where the user group contained a node that pointed to the area i wanted the system to take information from. By pulling this value out and feeding it to the redirect node it worked well. Hope you can get the radio button stuff working. It does work here. The basic idea is that you get the id of the attribute and use that to create post variables for the form. Paul
Paul Forsyth	Tuesday 05 August 2003 12:38:02 am Just mulling over what you have said :) You can use the method i use to make it dynamic for now, but putting forward the suggestion that something in the admin could set a default redirect value would be nice. This would save on coding each time it was needed. Maybe a redirect datatype could be added? This would set a default redirect in a tpl and would be picked up by those forms that support it. Paul