[Fwd: Re: [PEAR] QFController Action definitions]

Was meant to go to the list too. Hi, you can always call Parent::process() in you process method, that will call the parent method as the name hints at. (for some reason i didn't think about that earlier) I found why my conditionnal jump didn't work. The "jump" action is redirecting to the first invalid page. Thus when i first display the page it directs to page2 because it is invalid. THus doing page2 becomes valid and the next call to conditionalnext goes to page3 as intended. I'm still not sure how to handle that. Arnaud. Mike Carter wrote:

Good evening, I'm wanting to do some custom processing when a person clicks on my 'next' submit button. I've created a test action and linked it to the button in the form fine. When the button is clicked I get greeted with the message "Bang bang" (see below). class Action_ConfirmMember_Next extends HTML_QuickForm_Action_Next { function perform(&$page, $actionName) { die("bang bang"); } What I would like to do is, after calling my custom code, continue using the code provided in the HTML_QuickForm_Action_Next::process() to work out what form to go to next. Looking at the code recently posted by Arnaud it would appear I have to copy and paste the code from the default Next action in to my own actions because I'm over riding the process() method :-/ If this is the case, would it not be better to move all the code in the default HTML_QuickForm_Action_Next::process() to another method in the same class which I could call from my custom process() method ? Maybe I've got the wrong end of the stick? Or just the wrong stick all together? :o) Hope anybody in the know could take the time to explain a little more about it all. Please. Regards,