I have uploaded a preliminary build of wp-SwimTeam v1.40-beta-1. This build introduces new functionality to support mixed gender and combined age groups. It also fixes a number of small bugs I encountered along the way.
I have not done thorough testing on it as I don’t have access to MM and TM right now to validate the changes. However, I am reasonably confident that the changes I’ve made will have little to no impact on Hy-tek compatibility.
If you run into any issues, let me know and I’ll get them fixed as quickly as I can.
I am working on some new functionality to support mixed gender events. While I am at it I have decided to fix a limitation with the current Age Groups where the need to define overlapping age groups works but causes some discrepancies on the roster and other reports.
I have enhanced the definition of an Age Group so it can either be “Standard” (which is what it has always been) or “Combined”. A combined age group can support mixed genders and/or age ranges that span multiple age groups. By differentiating two types of age groups it cleans up the issues with overlapping age groups too.
Here are a couple of screen shots of what the changes look like. I am running through some testing now to make sure everything still works.
As I noted a couple days ago, I have started a “renovation” of sorts to my WordPress Google Forms plugin. I have defined a Custom Post Type which makes it much easier to set up a form. It is no longer necessary to worry about the syntax of a long complicated short code! Here are a couple images of what the Dashboard UI looks like.
Adding a form to a post or page is as simple as adding the
Unable to process Google Form short code.
short code where N maps to the form’s post id. The short code syntax for each Google Form appears in the list of forms.
The Google Form Edit Screen has fields which map directly to all of the short code attributes that were defined in the original short code.
There is no change of operation on the front end – the form should continue to operate as it has previously. If you’re interested in testing this new version, I hope to have a beta available fairly soon which also has some other new features.
Moving to a Custom Post Type may allow for some more robust field validation using the jQuery Validation plugin! Stay tuned for more details on that as I don’t think it will be in the first release of Custom Post Types.
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.
I see on my Dashboard that WordPress 3.4 is out today. I knew it would be out soon as I follow the WordPress Hackers and WordPress Testers mailing lists but have not done anything with it yet. In the past I have tried to do a basic smoke test against one of the release candidates before the final release is out but this time I haven’t had the time to do it.
So the answer to “will it work?” is “I don’t know!”. I realize that isn’t a very good answer and I will try to test it in the next few days. My recommendation is to hold off until I’ve done some basic testing. I am not aware of anything that will break based on what I know is coming but until I test it, you never know!
I don’t have much documentation for wp-SwimTeam. It is on my to-do list but I haven’t made it a priority. When I first started the plugin, there were not a lot of options and capabilities but that has changed over the past three years. I get a few questions each week on where to start in order to use the plugin. Today I wrote up a quick summary of the steps necessary to get wp-SwimTeam setup and usable.
I also frequently get asked about the various short codes available to put swim team information in posts and on pages. I’ve started adding more information to the Demo site so the syntax of the short codes is clearer. See this post as an example of the various ways a Swim Meet schedule can be displayed.
There is a pretty serious bug in the last couple of releases. It appears that the changes I made to support Multi-Site affected the Jobs module.
It appears that jobs that have already been committed to one user appear as available to all other users.
I am at a Lacrosse tournament and have limited access from my phone to be sure. For now, I recommend putting your Jobs module in “Admin” sign up mode until I investigate later tonight. Use the Jobs tab on the Options menu to disable User job sign up.
One of the changes I made in the last week has introduced a pretty significant bug in the Jobs module. If you assign a set of jobs from the Swim Meet tab, it may unassign a bunch of previously assigned jobs, possibly even from prior seasons. I have identified the bug and am in the process of fixing it.