This morning I uploaded beta-2 of wp-SwimTeam v1.41. This build adds intelligence and error messages during the export process (rosters only for now) to detect an unusual, but critical situation, which occurs when the plugin is unable to generate a temporary file. The temporary files are used to hold the generated data which is eventually sent to the browser for download.wp-SwimTeam Beta (488 downloads)
I have finally released v1.40 of wp-SwimTeam. Thanks to everyone who helped test the new features and flush out any bugs. This release has a slew of new features and functionality.
- This update requires phpHtmlLib v2.6.7 or later!
- Fixed initializion bug when Adding Events to an Event Group. Events were by default not being assigned to the correct group.
- Fixed pagination bug when managing large number of events. When paging through events the GUI would get confused.
- Fixed Event Group bug which was propagating the wrong event group to subsequent actions.
- Added support for Mixed Gender and Combined age groups.
- Added support for Mixed Gender and Combined Events.
- Added support for exporting mixed gender event entries in SD3 and HY3 formats.
- Added support for mixed gender events when importing events.
- Fixed bug resulting in database error when generating RE1 roster.
- Re-implemented Roster Export functionality – multiple formats can now be exported. The export can also be limited one gender.
- Added support for age groups where min age and max age are identical.
- Added smart processing of 0 as min or max age in HYV event imports, mapping 0 to minimum or maximum age setting as appropriate.
- Fixed bug in USS Number generation.
- Fixed bug in HY3 entries generation where E1 record did not contain gender.
- Fixed reported entry count when exporting SDIF, count was off by 2x.
- Fixed bug exporting roster by single gender which resulted in no swimmers.
- Fixed bug which prevented proper HY3 meet entry generation for Opt-In swim meets.
You can find the update in the WordPress plugin repository or on your Dashboard.
This morning I released beta-8 of wp-SwimTeam v1.40. This beta release addresses a couple problems.
- I have fix the problem when exporting the roster by a single gender in Hy-tek format results in an empty roster.
- I have fixed the problem where the entry count is off by 2x when export meeting entries in SD3 format as compared to HY3 format.
There was some other minor debug code cleaned up nothing visible on the Dashboard.wp-SwimTeam Beta (488 downloads)
I have just uploaded beta-5 of wp-SwimTeam v1.40. This is a minor update, the only fix is to the generation of the USS Number when used as swimmer labels. Previously the USS Number was being computed in YYMMDD format where as the USS Swimming SDIF specification calls it out in MMDDYY format.wp-SwimTeam Beta (488 downloads)
This afternoon I fixed a couple of minor bugs and pushed out v1.34.963. The primary new feature in this release is the ability to export Meet Entries to Hy-tek Team Manager. I have had lots of requests to support Hy-tek over the years so I am happy to say I can finally support it!
As anyone who has read my postings over the past few years knows, I am no fan of Hy-tek. Between the closed data format and the awful user interface, it amazes me that their products have become the defacto standards for Swim Team and Swim Meet management but they have. If you want to play in this space you need to interface with Hy-tek. Fortunately some smart guys decoded the HY3 checksum and through lots of experiments some other people have figured out the HY3 file format so building on the work of others, I can now export a roster and meet entries in HY3 format.
I would appreciate feedback in this area as I have tested what I can but there is no such thing as too much testing and I may not have envisioned every scenario. There is also a very strong possibility that some of the fields in the HY3 format may not be in the right place or contain the right data.
I also fixed a number of issues when browsing Parents, Swimmers, and the Roster where the Search function wasn’t working correctly. Most of these problems were due to the SQL changes I made to address performance issues but a couple of them were due to allowing search against fields which are computed as opposed to extracted from the database.
Tonight I posted an early build of wp-SwimTeam v1.34. You can download it and manually install it if you would like to try it. This build introduces the ability to export Meet Entries in Hy-tek HY3 format which can be imported directly into Team Manager and Meet Manager.
This build also addresses a number of bugs I’ve encountered, the most notable being the inability to generate a single swimmer roster export in SDIF and HY3 formats. Instead of just one swimmer, the entire roster was exported. This has been fixed. The CSV export was not affected by the bug.
Please let me know if you run into any issues. I plan to release this later today after some more testing.
If you run into any problems, please let me know. I’d like to release this update in the next day or so.
Over the last few days I have been working the Hy-tek HY3 equivalent of exporting SDIF meet entries. For the most part the logic is largely the same but the Hy-tek Meet Entries format is different enough that it isn’t a simple port. In particular, relay entries have me a bit stumped.
In SDIF it is possible to assign any number of swimmers to a relay event as an “Alternate” using the “A” designation in the leg field of the F0 record. As near as I can tell, the Hy-tek equivalent doesn’t exist. A relay team can be defined in the HY3 F1 record and the heat and lane assignment can be set in the F2 record. Swimmers are designated in the F3 record. So I am somewhat stumped – do I just define the relay teams and then let the assignment of swimmers to the relay teams happen within either Team Manager or Meet Manager or do I keep track of the number of potential swimmers and create the maximum number of relay teams and simply assign swimmers to each team so they can be sorted out later?
The other dilemma I face has to do with the swimmer id field which is not the same as the registration number field. The swimmer id field is an internal database field which connects D1, E1, and F3 records to the same swimmer. Within my plugin I have unique swimmer ids in the form of database record identifiers that I know will be unique. Should I use them or is simply starting at 1 and sequencing the number of swimmers as using that as an id sufficient?
My guess is the answer to both of these questions will be “it depends” and I’ll need to experiment. Life would be so much easier if Hy-tek would simply support the SDIF format correctly instead of the half assed way they do it now.
This morning I released an update for wp-SwimTeam. This version addresses a few issues and completes the Hy-tek Team Manager Roster Import functionality. You can find it on the Download and Installation page or through the WordPress Dashboard and the Plugin Repository.
- Completed Hy-tek Roster export. All fields that can be mapped into some sort of logical Hy-tek Team Manager field are now supported. TM supports up to three custom fields in the roster import file, if optional swimmer fields are enabled, the first three (or fewer) will be mapped into the corresponding TM custom field.
- Fixed bug where in some instances, the first name would be blank.
- Fixed alignment (right instead of left) of Swimmer Id field on SDIF F0 records in entries export.
- Fixed minor white space issue in PHP source code which in some cases seems to cause the Job Commitment Report to hang.
In the processes of getting ready for our first meet I found some swimmers who had scratched still appeared in the entries SDIF file. Odd, this isn’t supposed to be. Looking into the problem I found that only Freestyle was being processed correctly, all other strokes were not being recognized for Opt-In or Opt-Out.
I have fixed this bug and uploaded a new version as well as pushed it to the WordPress plugin repository.
I have just pushed out v1.29.903 of wp-SwimTeam. This update addresses a couple of bugs, notably with the Job Commitments report, and adds some new functionality.
New in v1.29:
- Fixed bug which prevented the Job Commitment report from running correctly.
- Fixed bug which caused “$credit” to appear in the CSV version of the Job Committment Report instead of the actual number.
- Added new option to set initial value on swimmer labels with numeric sequences.
- Fixed bug with SDIF profile when Geography was set to US which resulted in a broken form.
- Elimited some debug code which generated output when exporting entries.
Also included in this build are all of the changes included in the v1.28 beta release which I never formally made available.
- Added button to Swim Team User Profile form to quickly open user’s WordPress User Profile form.
- Tidied up several of the reports to make them consistent. Each should now display the HTML report on screen when exporting another format.
- Re-implemented download solution for actions which generate downloadable files (e.g. CSV, SDIF, etc.)
- Phase 1 of Hy-tek HY3 export support. Roster can be exported in HY3 format which imports into Hy-tek Team Manager.
- Fixed bug which enabled job signup for all users regardless of setting on Jobs Options tab.