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.
There is definitely an issue with the Swim Meet Report, particularly the opt-in/opt-out list, produced by the wpst_meet_report short code. It produces different results depending on whether or not a user is logged in to the web site and what WordPress capabilities the user has. I hope to have a solution this morning as it is causing a fair amount of confusion with my own team!
I noticed an inconsistency on our meet opt-in/opt-out page (which is based on the short code) earlier this week and it was also seen by another team. I suspect there is a bug that I need to track down. In my case the report generated from the short code didn’t include all of the swimmers that the meet report generated from the Options->Reports->Swim Meets tab on the Dashboard included. In looking at it, the Dashboard report was correct, the short code report was not. I plan to chase this down in the next day or so.
A quick turnaround on the bug reported a short time ago. It has been fixed and I have posted v1.7.608 of wp-SwimTeam. This fixes the bug which essentially made the Manage->Users tab almost unusable unless you had a very small number of users.
This release has also been pushed to the WordPress plugin repository so it should be available via the plugin updater fairly soon.
In the latest 1.6.x released I changed the actions on the Manage->Users tab from a row of buttons to a drop down list. In the process I have introduced a bug because none of the controls on the user list (expand, search, page forward, page back, etc.) work. I am working on the issue and hope to have an update out shortly.
It took longer than I wanted and I didn’t get all of the features I wanted done, but I have release v1.6.605 of wp-SwimTeam tonight. This release addresses a number of things my own team has been asking for, in particular with respect to jobs. A number of our parents have asked how they can see which jobs they have signed up for and if they have scratched their swimmers or not. A key new feature in this release is the Swim Meets report is now exposed to all users but the information presented to users is limited to their swimmers and their jobs.
Fixed bug when optional user and/or swimmer field count is zero preventing reports from running.
Added My Jobs tab for all users. User can now easily see which jobs they’ve signed up for.
Added e-mail field to user profile. Users are familiar with the swim team profile, easy to update.
Exposed Swim Meet report to all users allowing users to see their swimmer opt-in/out and jobs easily.
Added Dashboard widget.
Fixed quite a few minor bugs – too many to list!
This release is available now on the Download page and will be available from the WordPress plugin updater later tonight
There is a bug with the User and Swimmer reports which will manifest itself when either the User or Swimmer optional field count is set to zero AND the table where the optional fields are stored is completely empty. I have fixed the bug and checked it but am not quite ready to do a release due to some other changes I am in the process of making not being finished yet. The bug will also manifest itself when trying to export a list of users or swimmers as CSV.
If you run into this problem, let me know – there is a fairly easy work-around that will prevent it from happening.
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.
A new release of wp-SwimTeam is now available for download. It is also available via automatic update from the WordPress plugin repository. This release fixes a couple of bugs and adds two new features, one of which addresses functionality that was coded but never exposed correctly.
Fixed bug in wpst_meet_report short code.
Fixed bug in Add/Update Club Profile due to invalid URL field(s).
Added showmaplinks option to wpst_meet_report short code.
Added URL sanitatization to Google Maps and Mapquest URL fields on club profile.
Added notes to use Google URL shortner for URLs that don’t validate.
I am not sure when it was added but MapQuest now generates “shortened” URLs when mapping an address, I wish Google would do likewise. The URLs that Google Maps generates tend to be a mile long and full of characters. My suggestion is to use Google’s URL shortener to generate a simple URL that can be saved within WordPress easily. That is what I am doing for the MacDolphins web site.
The phpHtmlLib library which wp-SwimTeam depends on has also had a minor bug fix which I found testing URL validation. This plugin can also be updated t v220.127.116.1146 using the WordPress plugin updater or can be downloaded and installed as in the past.
There is a bug in the “Add Swim Club” functionality. I ran into this issue this morning but haven’t had a chance to diagnose it yet. I hope to have it identified and fixed sometime today. I apologize for the inconvenience. To work around this problem I am choosing “None” as the opponent and then adding a note in the description field.
This bug only occurs when the Google Maps URL is used. I am trying to determine what in the Google Maps URL the validation isn’t happy with and why the data is reported as saved when it is not.