Quick turnaround for another beta release, wp-SwimTeam v1.40-beta-9 is now available. This release addresses a bug generating a HY3 meet entry file when a swim meet is set up as Opt-In.wp-SwimTeam Beta (849 downloads)
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 flew out to Phoenix and back this week and had some airplane time to work on wp-SwimTeam. I have completed what I am calling “Phase 2” of the Event Model changes. Events can now be assigned to a swim meet AND the Opt-In/Opt-Out system is working in the Event Mode (which I had broken in v1.18).
The majority of the work in this build is related to Events and their connection to swim meets which is the precursor to Phase 3 which will be the generation of Meet Entries in SDIF format that can be imported into tools like MeetManager and WinSwim. I have also fixed quite a few bugs in the report manager which were present when either the User or Swimmer option count was set to zero. There was some logic that didn’t test right and would result in using the default count which is 5. So if you have seen checkboxes without labels on the User or Swimmer report generator, this has been fixed.
Please let me know if you run into any issues. I am doing some testing with our team right now and we have our pre-season open house this weekend which tends to result in a good chunk of our registrations. Assuming all goes well, I’ll release an update to the WordPress repository early next week if not sooner.[download#14#image]
I have tracked down the problem that was causing the opt-in/opt-out list to be displayed incorrectly when called from the wpst_meet_report short code. I have fixed the problem and made a new release available. The release is now available from the Download page and has been committed to the WordPress Plugin Repository. It should appear as an automatic update from the WordPress automatic update process in the next couple of hours.
Over the past week or so I’ve been working on some new functionality that is finally ready to go. The opt-in/opt-out module has been based on strokes since the initial implementation and this model worked well for the MacDolphins but some other teams prefer to register (or scratch) swimmers on a per event basis.
Events have been supported for a while but other than adding them to a swim meet, nothing has been done with them. The existing event functionality is the basis for the results work I hope to complete some day. Because the Event information is already defined, allowing the Opt-In/Opt-Out module to be based on the actual events was pretty straight forward. There is a new setting on the Options->Swim Team tab which controls which Opt-In/Opt-Out model wp-SwimTeam uses (Event or Stroke). By default it will continue to use Stroke since that was the original functionality.
The new functionality had a ripple effect across much of the plugin, causing changes to the Reports module and other places too. While working on the Reports I decided to expose the Job Assignments and Swimmers Reports for all users however non-admin users will only see their own job assignments or their own swimmers. This new functionality also came from one of the MacDolphins parents who wanted to be able to see which jobs she had signed up for. In the same conversation, another parent asked me if I could make it so she could see if she had scratched her swimmers. These two requests led to exposing some of the Reports in a limited fashion to all users.
The last major feature is the ability to run a report that shows the parents of active swimmers and their status against the volunteer (jobs) commitment set by the team (set it to zero for no commitment). This is a feature our volunteer coordinator has been after me to implement for some time. While the Report works fine, it is a little slow, particularly the first time it is run so be patient.
The new version modifies the database tables so PLEASE BACKUP your database before you install it. I don’t expect any issues and I’ve been running it on the MacDolphins site for the last two days but it is always a good idea to backup your database before upgrading.
There are still some things to improve – I’d like the list of events a swimmer can be registered for be limited to the events for their age group but don’t have good solution for that right now. I am considering using icons across the action bar instead of the drop down menu. I had moved away from buttons because they didn’t fit but the dropdown actions are confusing so don’t be surprised to see icons in the near future if I can find some I like!
The WordPress plugin repository has been updated so the plugin should begin to auto-update soon too but in the meantime, you can find the latest release on the download page.
I have completed all of changes to support the opt-in/opt-out event model I described late last week. I have not released the update yet as I am still doing some testing. I have it running on the wp-SwimTeam demo site. You can see an example of what one of the reports would look like when swimmers are registered on an event basis instead of a stroke basis.
If you switch from the stroke based model to the event based model for opt-in/opt-out, you may see some empty or unknown events for existing records. These are due to a non-existent event id in the record. It doesn’t really hurt anything but does look odd on the report so I plan to look into it.
I am looking for someone to do some testing before I release an update, if you want to help, get in touch with me.
I’ve had an ongoing dialog with a team in Texas using wp-SwimTeam that has a much different usage model for participating in Swim Meets than the MacDolphins do. Instead of registering or scratching for a meet, their team has their swimmers register for particular events. In speaking with a parent of one of our year round swimmers, they do the same type of thing for their year round meets.
Wp-SwimTeam doesn’t currently support this usage model but I can see the need to do so. The system already allows the definition and assignment of events to a swim meet, it needs to be extended to allow swimmers to register to particular events instead of the global Opt-In/Opt-Out option which is currently available.
I don’t plan to eliminate the current usage model because it works well for our swim team but I plan to extend it by allowing what I am referring to as the Opt-In/Opt-Out usage model which will either be by Stroke (the existing model) or by Event (the new model).
Fortunately the data model I set up when I first implemented Opt-In/Opt-Out will handle this change fairly easily with one exception. For some odd reason I called the field in the database which stores the stroke code ‘eventcode’. This was a bad idea and I am going to change it to ‘strokecode’ in the next release of the plugin which will cause a bump in the database version. This isn’t the first time I’ve changed a database column name so I am not too worried about it but I wanted to be up front about what I am doing and why.
In the current Opt-In/Opt-Out Stroke based usage model a user can start from a swim meet and update all of their swimmers on a per meet basis or they can start from a swimmer and update all of the meets on a per swimmer basis. This will remain the case.
However, for the Event based usage model all action will have to be initiated from the swimmer, it will not be possible to update multiple swimmers for a single meet. This change is due to the swimmers being in different age groups so the events have to be relevant to a swimmer which isn’t possible (or easy anyway, I guess anything is possible) for multiple swimmers.
What about swim ups? I am not sure how I want to handle swim ups right now. In the first implementation I will allow an Admin user to register a swimmer into any event but a parent/guardian (standard user) will only be allowed to register their swimmer for the events that correspond to the swimmer’s age group.
Feel free to comment on whether or not I have missed anything and I am looking for someone to validate the usage model once I have it up and running on the wp-SwimTeam Demo site.
I have just released wp-SwimTeam v.1.5.579, you can find it on the download page and shortly, via the automatic plugin updater. This release fixes an issue which has bothered me personally for a long time.
There was a problem in the E-mail Confirmation code for both registrations and opt-in/opt-out. This same code was used for the new Jobs module so it existed there too. For a long time the confirmation e-mails were duplicated and if a swimmer had to two contacts, only one of them would receive the e-mail. I have finally found and fixed this problem so e-mail confirmation should be cleaner and sent to the appropriate people.
I have just posted v1.1.533 of the wp-SwimTeam plugin. This version includes the first pass of Contextual Help for all plugin screens and forms. I have added and/or clarified some of the information to (hopefully) make it more clear what particular areas of the plugin are for and the actions which can be performed.
This version also fixes a number of minor bugs that I encountered, most were due to typos in the SDIF constants that were exposed when I turned the WP_DEBUG flag on.
I added one significant new feature: It is now possible to configure the Opt-In/Opt-Out system to support opting in or out of Full, Partial, or Both types of swim meets. Control over this setting, which defaults to BOTH, is on the Options page under the Swim Team tab.[download#7#image]
The MacDolphins finished the TSA summer swim season this week. We have dealt with a lot of weather issues this year. TSA holds their swim meets on Tuesday evenings (most leagues I am familiar with hold them on Saturday morning). Dealing with thunderstorms is one of things we deal with here in North Carolina almost every afternoon in the summer time and this season was particularly bad. We had two meets end early and three meets rescheduled to another day.
Dealing with all of the changes really played havoc with our meet preparation. Even though I’ve made it really easy for parents to scratch their swimmers (e-mail, web site, and text message), we still have a fair number of no-shows. It was bad enough the last couple weeks that I’ve decided I want to track it.
I plan to add an option to the Opt-In/Opt-Out system which will allow a user with the proper permissions to go back and mark swimmers as No-Shows. This will show up on the Opt-In/Opt-Out reports as a new section. I’ll probably put it right at the top. I am hoping this will help us track our repeat offenders and they will make a better effort to let us know when they are not swimming.