This evening I released beta-2 of Google Forms v0.73. This beta build addresses a problem recently reported on the WordPress Support Forum.
This problem appears to be due to a change in the HTML Google generates for the “Other” field. The change in the HTML resulted in the jQuery selector no longer working. A new selector has been implemented in beta-2.
After submission, Google Forms show, unless hidden with CSS, a “Submit another response” link which links back to the Google Docs version of the form. This link is now replaced with the proper link to URL where the form appears on the WordPress site.
Please do some testing with this beta version and report any problems. I will do my best to fix them quickly as I would like to get this version released as soon as possible.
With 70+ downloads of beta-2 and no issues reported, I feel pretty good about releasing v0.70 so this morning I pushed it out. There are no changes since the last beta version with the exception of the version number change.
I have uploaded beta-2 of Google Forms v0.70. This build has one minor fix. While minor, it is important to me. This build fixes an issue when the Email Admin option is enabled but the Send To address is not specified. By default the Blog Admin email address should be used in this situation however no mail was being sent at all.
It took me a little while to get it working as Saturday morning I went down a wrong path initially following another post I had found. When I first read the post I linked to above, I convinced myself that I didn’t want to use the AddMethod solution. I am not sure why, I guess it was because I haven’t been into the code in a while so I was trying to avoid it. It turns out it is definitely the right answer and fairly easy to implement.
The beta build also contains a Serbo Croation translation provided by Borisa Djuraskovic
To see the new functionality in action, check out my Validation Demo Form where the last entry field must begin with a capital letter. The regular expression “[A-Z]” is used to match a capital letter when setting up the validation.
While looking into a Support request I discovered a bug in the generation of the jQuery validation script which caused a syntax error. This syntax error could potentially cause problems with redirection upon form submission.
While fixing the above bug I also added support for embedded images which had been requested recently. When you design your form Google now allows the insertion of images and now Google Forms will display them properly.
You can find this update on your Dashboard or in the WordPress plugin repository.
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.
This morning I released a very minor update to Google Forms. In the process of verifying that I fixed the form submission log I found a typo in one of the internationalization strings and some debug code which was still enabled. Neither issue would cause the plugin to fail but I went ahead and fixed both and released an update.
This evening I released v0.66 of Google Forms. This version fixes two major issues:
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.
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.
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.