If you updated to any of the wp-SwimTeam v1.16.x releases you must update again to v1.17.707. I inadvertently introduced a bug which prevented almost all of the registration (season, swim meet, etc.) actions. I quickly fixed this bug once I became aware of it, I apologize for any inconvenience.
Tag Archives: release
wp-SwimTeam v1.16.704 now available
This morning I posted an update to wp-SwimTeam.
This release fixes a couple more places where the first and/or last name should appear but was being displayed as “N/A”. It turns out I had re-used the same code which I had fixed a couple weeks ago in some other spots so the problem was the same. This time I fixed it by moving the solution down into a parent class and eliminated a bunch of redundant code. Hopefully it is gone but there is an outside chance I missed one.
Anyone who has used wp-SwimTeam may recall that the actions used to be buttons across the bottom of the widget I frequently use to display data. This worked well until I had more actions than I had room for buttons. My solution was to move the actions into a drop down list and many of the tabs used this model. This release reconciles the inconsistencies so all tabs now use the drop down action model.
I have started work on some of the event changes I have posted about, hopefully I’ll have some new functionality in the next week or so.
phpHtmlLib v2.6.3.3563 released
This evening I released a new version of the phpHtmlLib plugin which wp-SwimTeam depends on. This update addresses a number of PHP5 deprecated function warnings which are commonly seen when running under PHP5 with E_STRICT set. I also fixed an icon bug which appeared on the GUI widget used across wp-SwimTeam when there was no data to display.
The update also removes the documentation and examples from the version of the plugin hosted in the WordPress plugin repository since they are only useful for developers. A full version of the plugin including documentation and examples can be downloaded from the Download & Installation page.
Can’t add new Swim Team Job?
I ran into a problem this past week that I am not sure will affect anyone else but my own swim team. Our volunteer coordinator let me know that she was unable to add new jobs. I couldn’t replicate the behavior in my development area which required me to debug it on the live server (ugh).
Because most of the things I add and/or changes I make to wp-SwimTeam are for the MacDolphins (but not always), I usually test them on the MacDolphins web site before releasing an update. When I first added the Jobs module to wp-SwimTeam I had defined column names in the database table. At some point I decided to be more descriptive with my names and changed the column names. I think, but I can’t be sure, that I did this before publicly releasing the plugin update. WordPress usually, but unfortunately not always, handles database schema changes correctly and will change column names.
In my case, WordPress, for whatever reason, didn’t change the column name, it defined a new one. While this isn’t of itself a real problem, having a few unused columns in the database isn’t preferred, it isn’t a real big problem either. Except that the default value for the column was never defined (oops) and at some point, MySQL (maybe MySQL5) started to care that the column wasn’t initialized.
The net result was we was we were unable to add new jobs because MySQL was returning an error message due to the uninitialized column that wp-SwimTeam wasn’t accounting for. The simple solution for us was to simply delete the columns that shouldn’t have been there in the first place and won’t ever be there for people using the plugin now.
In the process of chasing this problem down, I found an area of my database interface where I wasn’t properly accounting for possible database errors. I have updated the database interface class and the Jobs module which sits on top of it. Over time I will also retrofit this change into other parts of the plugin as I work on them.
Look for a plugin update to be released in the next day or so.
Sandbox-SwimTeam theme v3.0.360 available
It has been a while since I touched my Sandbox-SwimTeam theme but with Swim Team season gearing up, it was time I did some maintenance as I had put it off last season. A lot has changed in WordPress since I originally put this together almost four years ago.
I have just released v3.0.360 of the theme which you can download from the Sandbox-SwimTeam theme page. This update has a lot of bug fixes, most of which bring it update to date with WordPress 3.3. The big new feature is support for WordPress Navigation menus.
Important: You will need to re-enter your theme settings! The way theme settings are stored is different from the original implementation and there is much more checking done now. The theme now properly uses the WordPress Settings API.
I had wanted to build a new theme for our Swim Team this season but time to do so is elusive. I’ve decided to do a short term fix and update Sandbox-SwimTeam which will give me some breathing room to work on a new theme over the next few months without impacting the swim team adversely.
WordPress Google Form v0.24 fixes UTF-8 bug
Recently a couple people have reported problems with international (or UTF-8) characters. The UTF-8 characters were not being passed correctly from the form on the WordPress site on to Google. I had planned to look into the problem this coming weekend but a wpGForm user (cablop.net) beat me to it and has provided the fix (thank you very much!).
I have incorporated the fix and tested it and was able to submit a couple Spanish words that have UTF-8 characters. The update should appear on your Dashboard shortly.
wp-SwimTeam v1.14.674 now available
I have addressed the bug which slipped through the last build and released v1.14.674. There was a situation when querying for a users first name or last name against a username where the first or last name didn’t exist, the WordPress API returned an empty array and sometimes returned a one element array containing an empty string. I am not sure if this is due to different versions of PHP or some other nuance but this update correctly accounts for both situations. The bug manifested itself as a warning from the phpHtmlLib plugin (which wp-SwimTeam depends on).
The update should appear in the WordPress Dashboard shortly and is available now from the Download Page.
wp-SwimTeam v1.13.669 available
This afternoon I posted an update to wp-SwimTeam. You can get v1.13.669 from the download page or update from the WordPress plugin repository (recommended). This update fixes several bugs:
- First and last name were displayed as “N/A” on the Users list on both the Swim Team tab and the Manage tab.
- The default values for “State or Province” and “Postal Code” were not stored correctly so in a new installation, the registration form would not work until these fields were set in the Options.
- Removed borders from sections of the Options->Swim Team form that were used for debugging the form layout and had inadvertently been left behind. Some other minor tweaks to the layout were also made.
- Rudimentary 3.3.1 testing has been performed.
The update is already in the WordPress plugin repository so you should see notification on your Dashboard soon.
WordPress Google Form v0.23
This evening I released v0.23 of my WordPress Google Form plugin. This update fixes a situation where CSS declarations were output as plain text as part of the form. I believe the cause of this was due to an appearance theme for the form being specified in the Google Form Designer. The update should roll out via the WordPress Dashboard Update failrly soon.
WordPress Google Form update – v0.22
Yesterday I received a report from someone using WordPress Google Form that their checkboxes weren’t working. This was very confusing to me because last weekend I spent a bunch of time fixing and testing the checkbox problem.
It turns out the jQuery script which fixes the checkboxes to work with PHP was never running. Why wasn’t it running? Because jQuery wasn’t ever loaded. Why wasn’t jQuery loaded? Because wpGForm never loaded it! It turned out the website which reported the problem was using a theme that doesn’t use jQuery and therefore never loaded it.
Well the WordPress Google Form plugin, which needs jQuery, didn’t load it either. I (and I can only assume other people) was never seeing a problem because either the theme or another plugin was loading jQuery.
The v0.22 update corrects this problem which was somewhat of a corner case, but a problem none the less.