Ticket #77 (new defect)

Opened 2 years ago

Chained form pages cause an infinite loop

Reported by: mg Assigned to: somebody
Priority: normal Milestone:
Component: form-core Version:
Severity: normal Keywords:
Cc:

Description

If FirstPage? and SecondPage? both include Formal's ResourceMixin?, and FirstPage? returns a SecondPage? instance from its form's callback method, then Formal goes into an infinite loop.

What's actually happening here is that FirstPage? sees a POST and treats it as a form post. The form is processed. The form's callback eventually gets called and returns a SecondPage?. SecondPage? sees a form post and treats it as a form post. SecondPage? finds the named form (it's "cached" on the request) and processes the form. etc, etc.

Sadly, the only fix for this (for now, at least) is to redirect to another URL that displays SecondPage?. Request args or even the session can be used to transfer data from FirstPage? to SecondPage?.

Chaining pages would be very nice but it's not obvious how SecondPage? will be found when the URL the browser POSTs to resolves to the FirstPage? instance.