Tag Archives: Bug

02.17.12
by

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:

  1. First and last name were displayed as “N/A” on the Users list on both the Swim Team tab and the Manage tab.
  2. 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.
  3. 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.
  4. 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.

02.12.12
by

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.

02.04.12
by

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.

02.02.12
by

WordPress Google Form minor update – v0.21

This morning I have updated WordPress Google Form and fixed a number of documentation problems and added one minor new feature.  While I am not a big fan of Javascript Alerts, I had a request to allow a message to be displayed upon successful form submission.  I have added a new parameter (alert=’message’) to the gform short code to enable this new functionality.

[gform form='https://docs.google.com/spreadsheet/viewform?hl=en_US&formkey=dEYwbGNYVG9TRUhXellMaDBuZ1RQTHc6MQ#gid=0' confirm='http://localhost/?page_id=435' alert='You da man!']

The new release should appear in the WordPress repository immediately and as Dashboard update fairly soon.

01.30.12
by

Yet another update! WordPress Google Form v0.18 available

I have just released another update to the WordPress Google Form plugin.  Within the HTML code that Google generates for their forms, each input field has  unique identifier (e.g entry.0.group, entry.47.group, entry.6.single, etc.).  There was a bug in the Regular Expression which incorrectly handled these identifiers when then had more than one digit.  This bug is fixed in v0.17.

Why do the identifiers need to be processed?  The need to “massage” the identifiers is due to the fact that WordPress is based on PHP and Google Forms are processed by Python.  The two languages handle passing form parameters slightly differently.  When the form is submitted on the WordPress side, the periods in the id are translated to underscores by PHP.  Inputs like check boxes which may contain multiple values are handled using arrays in PHP where as Python allows the use of the same identifier multiple times.  In order to submit the form values to Google, any value received as an array must be converted to a multi-value and the underscores need to be translated back to periods so they match the Python script on the Google side which actually processes the form and stores the result in a Google Spreadsheet.

There was a mistake in the logic which transforms the identifiers from PHP syntax to Python syntax.  It didn’t correctly handle more than one digit in the identifier resulting in the wrong identifier names being sent to Google.  This also caused loss of input values when a required field was not supplied.

Hopefully this will be the last problem!

01.28.12
by

wpGForm Bugs in v0.15

I have been alerted to a couple of bugs in the current (v0.15) version of wpGForm that I am working on fixing.

  1. Select boxes do not retain their value when going back on multi-page forms.  I’ve already fixed this problem in my development build.
  2. Check boxes are not passing their values correctly.
  3. Sometimes Radio buttons do not retain their values when going back on multi-page forms.

This third item is proving difficult to track down. It is odd that some questions with radio buttons work fine going back and forth between pages but others do not.  If I can fix the check boxes this morning I will likely release an update that addresses the first two bugs and keep working on the third problem.

01.17.12
by

WordPress Google Form v0.15 released

This morning I fixed the problem with the default settings which caused any of the settings which are on by default, to be on no matter what.  Even when the user would turn them off, the plugin would ignore the user setting which was being saved correctly, just ignored being ignored by the during the default check.

I also finished removing the jQuery-Validate plugin as it is no longer used as well as a bunch of debug code and functions which are no longer used.  Updates should appear on your Dashboard soon and it is already available for download in the WordPress plugin repository.

01.17.12
by

WordPress Google Form Bug with default CSS

There is a bug with the current (v0.14) version of WordPress Google Form in that it will always load the default CSS that is shipped with the plugin.  Using the setting to disable loading the default CSS is not saved so it is never turned off.  I am looking into this issue and will post an update as soon as it is fixed.

01.14.12
by

Quick bump to v0.14 for WordPress Google Form

While looking at a CSS styling problem for someone I encountered a minor bug on the Options page.  The plugin wasn’t picking up the default options correctly and in some cases a PHP array index warning would appear on the Options page.  This bug has been fixed and I’ve released v0.14.  You can download it from the WordPress plugin repository or update it from the Dashboard.

01.14.12
by

WordPress Google Form v0.13 fixes “back” bug

I have just committed v0.13 to the WordPress plugin repository.  An update should appear in your WordPress Dashboard fairly soon.  This update fixes a problem when using multi-page Google Forms which have radio buttons and check boxes on them.  When the “Back” button was selected to view the previous page of the form, the previously selected values were not retained.  This bug has been fixed and the “Back” and “Continue” buttons now work as expected.