Google Forms v0.68 released

Another minor update to Google Forms to fix a bug reported late last week.  It turns out I left out a named array parameter in a call to wp_update_post().  What is interesting is this problem manifests itself differently on various installations.  I never saw the error reported however when the offending line was pointed out, it was obvious to me what was wrong.

A new version (v0.68) has been posted to the WordPress plugin repository.

Google Forms v0.66 available

This evening I released v0.66 of Google Forms.  This version fixes two major issues:

  1. The conflict with WordPress SEO has been resolved.  The implemented solution will likely be replaced with something which runs less frequently.  However, the solution implemented in v0.66 should make sites running both Google Forms and WordPress SEO a little happier.
  2. Due to a bug, all form submissions have been logged regardless of the plugin setting.

You can find the update on the WordPress plugin repository or on your Dashboard.

Google Forms v0.66-beta-2 available

I have been working on resolving a plugin conflict between WordPress SEO and Google Forms.  Based on some help from the WordPress SEO plugin author I have made some small changes to Google Forms which I believe will alleviate the conflict.

I am looking for people who’ve been dealing with this problem to test this out, if you have a few minutes, please download this beta and give it a run through.

Google Forms Beta (31986 downloads )

Email Users v4.6.6-beta-3 available

Over lunch I posted beta-3 of Email Users v4.6.6.  This build addresses an issue with User Groups integration when using a non-English version of WordPress.  A value embedded in the form was translated which the form processing logic wasn’t handling correctly.  This problem also could have manifested itself if a group name contained a hyphen (dash) character.

Email Users Beta (24498 downloads )

Google Forms v0.65-beta-1 available

Shortly after releasing v0.64 I received a report of data corruption from a Google Forms user.  I took this report very seriously and immediately reverted the stable tag for Google Forms back to v0.63 while I looked into this users report.  The last thing I wanted to do was introduce a bug which resulted in corrupted posts.

I spent some time looking through my plugin code and tried a couple experiments but could not replicate the behavior the user reported.  My gut feel was we’re dealing with a plugin conflict however it is hard to know for sure.

The user and I ended up swapping some email and I got a list of plugins they were running.  I initially thought I would try and replicate their problem by installing the same set of plugins but quickly figured out that wasn’t possible.  Nor was it possible to examine all of the code for the plugins looking for what I suspected was a conflict in a “save_post” action or call to wp_update_post().

In doing some research I learned (unfortunately I can’t find it in the Codex) that beginning in WordPress 3.7 there is a new save_post action for Custom Post Types:  save_post_{$post_type}  Whoo-hoo!  This didn’t exist when I originally wrote Google Forms, so my plugin, much like many other plugins which define Custom Post Types, define a save_action which then has to determine if the post is relevant to the plugin or not before doing anything to it.

I quickly implemented the new action and removed the old action and Google Forms is behaving as it should in my testing.  I have uploaded this latest beta to my site and beat on it a bit and cannot corrupt any data.  I am very confident now that Google Forms should never touch anything other than it’s own post data.

Because of the reported corruption, I would encourage beta testers to backup their database before installing this update JUST TO BE SAFE but I think the corruption risk is very low.  Please let me know if you run into anything unusual.

In this v0.65 beta I have also changed the name of the plugin from “WordPress Google Form” to “Google Forms” as it is more representative and the plugin repository now prohibits the use of “WordPress” in a plugin name.  There is a chance you’ll have to reactivate the plugin depending on how you install this beta.

Google Forms Beta (31986 downloads )

Google Forms v0.64-beta-7 available

This afternoon I released beta-7 of Google Forms v0.64.  I expect this to be the final beta release.  It contains a few minor fixes, most notably the warning from the cURL check regarding calling a non-static function statically.  Additionally, some new “placeholder” information has been added to the Form Definition form which disappears when the user starts entering text into the field.

Google Forms Beta (31986 downloads )

Google Forms v0.64-beta-6 available

I have just released beta-6 of Google Forms v0.64 which is a CRITICAL update for anyone who loaded beta-5.  Beta-5 had a serious bug which if you had defined more than one form using the Dashboard UI, would corrupt the content of all of the saved forms so every form would display the same content.  Beta-6 fixes this issue!

Google Forms Beta (31986 downloads )

wp-SwimTeam v.1.41-beta-2

This morning I uploaded beta-2 of wp-SwimTeam v1.41.  This build adds intelligence and error messages during the export process (rosters only for now) to detect an unusual, but critical situation, which occurs when the plugin is unable to generate a  temporary file.  The temporary files are used to hold the generated data which is eventually sent to the browser for download.

wp-SwimTeam Beta (10427 downloads )