Allow the fair to choose calling the signature page either a signature page or a permission form.
Add a comment box for each judge that can only be read by a committee member. Adding a comment will set a flag in the "manage judges" list.
Add "Update User" button to the list of judges so that a committee member can update a judge to the current year without having to log in as the judge.
A flag in the configuration variables under Particpant Registration
must be set to enable this.
Project types are Experiment, Innovation, and Study
Comment text box has been added to the project editor. This is only seen by
fair administrators and not by the student. Information related to project
safety can be flagged here. If text is present in this box, a flag appears
in the Registration Management list.
Project summaries longer than one page now print out properly. Blank pages
are still sometimes printed after long sumaries.
Choose Email Recipients query has been modified so that the most recent
email address for judges is now used.
Reports Editor has been changed so that cheques can be written for
individual students as well as one cheque per project. New report
data (split) has been added to make this work.
(install3 doesn't like including that file). That's ok, because eventually
all passwd handling will be done through user.inc.php (and the generate could
even be inlined into set_password). But for now, just copy the existing
generatePassword, and call it something different so the function names don't
clash.
over 3 files)
- Fix a bug to always save the old password (unless it was a reset password)
- Fix a bug to save the old password even when the user sets a new one
{$type}_password_expiry_days. This allows the $config variable to be updated
and everyones password will expire based on the new value. To implement
this, the password expiry column in the users table has been changed to
passwordset, and a PHP script is used to convert the expiry dates to set
dates (based on the _password_expiry_days)
- Cleanup the password entry checking
- Load all config variables for the db_update.php script. Just in case an
update script wants access to $config
fields that shoudl never be required. I do it this way so I don't have to duplicate
the field select array in user.inc.php for the requried fields too.
- Swap the City and Address2 locations so that Address1 and Address2 are on top
of each other, instead of beside each other.
already exist, they will be guided through the process of adding a role to
their existing account.
- Do a database update, and merge anyone who has managed to create 2 accounts
into a single account.
- Still testing this, but it seems to be working
variable, this will allow the committee to specify exactly what they
wish to collect (and which fields are requried)
- Insert config variables for volunteers and committee
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
- Allow user_personal.php to handle committee members
- Add password field if the editer in user_personal has access_super
- Allow a committee member to edit anyone in user_personal.php
- Convert auth_required to user_auth_required, and check for both a user type
and an access level (if committee)
- Convert the committee to the new user system (BIG change :)
- Remove the ^M from admin/committees.php
