Disable backwards/forwards if a survey has forks would be what I would
suggest.
Kon
On Wed, 2003-06-18 at 10:13, Matthew Gregg wrote:
> The Fork patch + back/forward/save on surveys == problems.
>
> Here is the deal...
> Build a survey with a fork. Place several questions between the
> fork. Take the survey and don't take the fork. Then save the survey
> without submitting. Now resume the survey, go back to the fork, this
> time take the fork and submit the survey. The questions that you
> forked over this time but answered the first time get submitted.
>
> How to fix:
> - We could disable backwards/forwards if a survey has forks.
> - Make forks play nice with B/F. May be difficult.
>
> I'm just about ready to commit the fork patch, should I with this
> issue? I'll get my updated patch out on list tomorrow.
>
|
