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
saying that the report can only be saved as a new report.
- Add checks to the report_save and report_delete fucntions to ensure system
reports cannot be saved/deleted.
- 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
Add ability to specify an award type to only generate a script for that type
Add ability to specify a year to get the awards ceremony script for that year
Add links to the new options on the main reports page
Add a function to get the email recipients for a given registration id, for now, it just gets the students, but downt eh road it should check if teachers, parents, emergency contacts, mentors, etc should receive fair updates as well.
Implement the code/replacement tags for the two new emails, one for 'forms received, with payment' and the other for 'forms received, without payment'
Whipe out all 'from' of info@sfiab.ca (the old default, we dont want others using it!)
When sending emails, if 'from' is empty, use the $config['fairmanageremail']
Add a warning on the communication page if the fair manager email has not been set
Set the default 'from' for new emails to be the fair manager email
NOTE/FIXME: i added the hooks for the two new emails to be sent, but still
need to fill in the substitution values as well as the "to" - no time now,
will do that tomorrow
Judge manager - delete now deletes the judge completely
Judge list only shows judges active for current fairyear
Clarify a few issues on the judge registration page
Factor XML functiosn out of cwsfregister into separate xml.inc.php
Add xml functionality to ysfstats, and fudge the male/female stats to include "not specificed" genders
Add submit functionality to ysfstats to actually send data to YSF
- Add prize names to the report generator
- Change award name to sort by name, if you want to sort by order, use the
Award--Order column. (Specifying a sort by prize name, and it actually
sorting by order doesn't make sense)
- Only report complete students
- Use tour names instead of numbers
- Not use $email as a temp varaible because that actually overwrites the
$_SESSION['email'], and logs us out, wtf?
- Sort by first tour selection
Add award criteria to getJudgingTeams() result
Modify CUSTOM report judges teams proejcts, to show each award and the criteria/eligibility for each award that the team is assigned to judge.
More ease of use cleanups to awards interface
Add new field award order to student report generator
- Creates a judging team for each special award
- Assigns judges to special awards based on the number of students self
nominated.
- Obeys the judges special award preferences (if enabled), and also
judges that specify if they are a judge for a specific special award
(if enabled).
- Add 2 new config variables.
- Enable the special award scheduler
- Specify the max. number of projects each special award judge can
handle (default: 20)
- Delete an extra blank line in register_participants_students.php
- Overhauled the report generator.. It's more versatile now
- Added 'filter' option to the generator, so you can filter any column by (=,
<=, >=, <, >, IS, IS NOT, LIKE, NOT LIKE). It doesn't support AND or OR
combinations, but that should cover what we need for now. Example: We can
filter "Award Name" LIKE "%Gold%" to generate a report of just the Gold medal
projects.
- Wipe out the report database, and create it again from scratch.
update.48.sql contains an example of how to add additional reports to the
system without knowing the report_ids, because after regions start adding
their own reports, we won't be able to just wipe out the whole report system
to add one.
- We handle more reports now, specifically nametags and table labels, so remove
those files, and update the reports.php file to link the old links to the new
report generator (so people don't get too confused in this transition).
- Beginnings of moving the report generator to proper LEFT JOIN style
constructs instead of just one big massive EQUALS JOIN.
- Add committee member generator
- It is now possible to generate ALL nametags the old system could generate
(needs a DB update before that happens... actually, the report generator
isn't as stable as I hoped.. I'll probably just nuke the report tables the
next upgrade and recreate them all.. I'm probably the only one who has tried
generating a custom report. :)
enough.. Currently we can't produce both a list of judges and a list of awards for each
team with the generator (how the heck would we express that with an SQL statement)
- Add an editor for that generator.. it's not flawless, but it's not hard to
use either.
- Add 19 default reports
- Replace several reports on the report page with the new generator versions
(they pretty much look the same, same info, same sort order, same pagination)
- Add a pulldown menu to the report pages so any report can be generated
- Hardcode add a special award to the top of the list "I do not wish to
nominate for any special awards". Allow the
project_specialawards_link.award_awards_id field to become NULL, and set it
to NULL if the student selects this award.
- Fix the display of the award status based on whether the student has or has
not specified that they do not wish to nominate for special awards.
- Add an option to the project editor to regenerate the project number
- Fix a bug in the project number generation. Include YEAR in the project
number check (and in the number generation) so we don't find a project from
last year (that already has a number), and decide not to generate one for a
project from this year. The $checkNumQuery was returning 2 rows.. one from
2006, one from 2007. Two projects from different years had the same
registrations.num (665983) in my test.. about 10% of the projects at the VDSF
collided with numbers from previous years.