function in the config editor to one that checks where ALL variables marked
with year=-1 exist for FAIRYEAR. If it doesn't, it creates them. This
function gets called in three places:
- On installation
- On rollover
- Whenever the database is updated
We should, now, be able to just insert new variables with year=-1, and they
will be automatically updated for the current year with the default value.
(no more going into the variable editor to make sure the copy is done).
- Fix the superuser account creation in the install script
the current year
- Add 2 new config options.
- 'participant_student_tshirt_cost' allows the cost of each fair tshirt
to be set (vancouver charges $10 for tshirts, because not all
students want them), this also adds a 'none' option to the tshirt
selection box, and a note indicating the tshirt cost if the costs is
nonzero.
- 'regfee_show_info' adds a "Registration Fee Information" to the main
student registration page, showing a breakdown of the registration
fee computation (including tshirts, per_student and per_project
registration, and indicates the total.
- Convert the tshirt field to VARCHAR(32) instead of enum so the "none" option
described above works, also, some fairs may want to add more optoins, like
female/male sizes.. so turn this into a text field for those fairs. The next
step would be to make a config option for the tshirt options. :)
editor what type of variable to expect. It can be yesno, enum, text
(default), number (unimplemented), or blank (default behaviour of the current
system). In response, the editor will use pull down lists instead of text boxes
for things like "Yes", and "No", or enumerated fields.
- Update the descriptions and type of existing variables.
Add two new projectnumber options: c=category shortform, d=division shortform, eg (JLS01 = Junior, Life Science, Project #01)
Add shortform field for age category
Fix bug in config editor where it was updating values for ALL years, instead of just the current year!
Bump version number to development version
should contain. If the config doesn't find those variables for the current
year, they are automatically copied in from year=-1. This means that
we can update a database and add new config variables and not have to manually
add each variable to the current year. It also means someone can't mess
up the system and accidentally delete config variables, because they
will be recreated.
- Missing: Having a project judged more than once by different judging teams is
untested, I don't htink it'll work properly, still working on that part.
- Missing: Auto updating the configuration if any of the variables are missing.
- Missing: A way to preserve judging questions (like willing_chair), so the
user doesn't delete them and break the scheduler, OR, notice saying that the
question has been deleted and the scheduler won't use the chair calculations,
then we need a way to add them back in with the click of a button.
