the project number field if blank).
- Add a new number option 'X', which counts among ALL projects, not just the
ones in the same division/cat.
- Add a padding argument to N or X (N0...N9) defaults to 2 for N, and 3 for X.
- Adds 3 columns to the project table:
- projectsort: for storing the expanded text
- projectnumber_seq: for storing the N or X number for projects
- projectsort_seq: for storing the N or X number for the sort order
- Add a new config option for sorting, and expand the text for the
projectnumber.
- Change the default sorting for reports and project lists to use the
projectsort category.
- Remove the gvrsf_tn option from the database, it's not needed now.
number, and an option to create numbers automatically
- Completely remove all references (hopefully) to the Tour ID
- Add a Tour type report
- Rework the student report query so it actually makes sense. It really should
be a whole bunch of left joins based on the students. Using comma (cross)
joins creates situations where if the right side of the join doesn't have
information, it wipes out the left side. (Happened before with emergency
contact info).
- Remove the (two) old custom tour reports
- Add 4 new tour reports to the database:
- ALL tours for the committee, tour list for students,
student emergency contact info for tour coordinators, and
a list of tour assignments for students
reports require admin access) can define a list of reports out of all the
reports, and tag each one with a category and comments.
- Add all except the ceremony scripts as "Custom" reports. The My Reports
system can handle links to custom reports now, but not the ceremony scripts.
They're too special. I think they should be moved out of the Reports Area.
- Clean up some report variables to avoid collisions with local names
($options, and $stock)
- Implment a new screen for report generation that lets the user set the
format, stock, and year of the report.
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.
- 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. :)
- 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
