#2 Design flaw in "Late Signup" page

[Tim Mensch]

The "Late Signup" page exists to allow a chef to enter people who came to a meal late. The current system shows a list of all members and allows the chef to edit input fields by each member to indicate what guests were brought (as well as to check off which members arrived late).

The page causes a server error when too many fields are present in one POST request. I attempted to change the POST request limit in the server (lighttpd), but was unable to find the right value to tweak. I patched the problem on the live site by preventing a few old members from being listed, and reducing the number of fields as much as possible (removing duplicates from the same household, for instance).

However, the real solution will be to rewrite the late-signup page as follows: Each member will be listed alphabetically along with their current reservation information and a link that takes you to a page that will allow you to modify the reservation information for that member.

[Tim Mensch]

Logged In: YES
user_id=1809101
Originator: YES

As an additional "feature": On the page to modify an individual's reservation details, the reservation should be able to be canceled by the chef as well as added.

By the way, the reservation information you should be able to modify for an individual should include:
* Any children belonging to that individual's household.
* Number of guests in each age range.
* Any other adult members of that same household.

All of these fields should be filled in (either with numbers for the guests or checked/unchecked boxes for the children and other adults) with the existing values when this page is presented.

The "OK" button on this page should return the user to the "Late Signup" page.