Tag Archives: Bug

03.25.12
by

Custom Confirmation problems with v0.26

In v0.26 of WordPress Google Form I changed how I was handling the custom confirmation page as many people had told me they didn’t like the redirection which caused a rapid page reload.  The new mechanism does a partial page reload using Ajax so the effect is much more graceful but I have heard from several people that it isn’t working for them.

If you are having this problem, please let me know so I can figure what is going on as it is working fine in my development and testing area.  I am still looking for a more graceful solution but the model I used before supporting multi-page forms simply won’t work with multi-page forms.  Multi-page forms are too important and commonplace not to support them.  Sort of a catch 22 for now but I am trying to find a viable alternative.

03.21.12
by

WordPress Google Form v0.25 now available

Today I was alerted to an issue where my WordPress Google Form plugin wasn’t behaving correctly. This turned out to be due to the prefix attribute in the gform shortcode not handling it correctly. I have fixed the problem with the prefix attribute and a couple of other things and pushed out a release on the WordPress plugin respository.

Version 0.25

  • Fixed problem with checkbox processing when using the prefix attribute.
  • Fixed problem with hiding legal links when using the prefix attribute.
  • Fixed problem with legal=’off’ attribute not being processed correctly.
03.13.12
by

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.

03.12.12
by

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.

03.05.12
by

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.

02.24.12
by

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.

02.18.12
by

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.

02.18.12
by

wp-SwimTeam v1.13.669 bug

There is still a bug I missed in the first nane / last name section of the code which I updated yesterday.  If you haven’t already updated, I recommend holding off until I fix this other problem.  I hope to have a fix available in the next hour or two.  The bug manifests itself in a PHP warning from the phpHtmlLib plugin but that is not where the source of the problem is.