Mike Walsh's random thoughts and musings …
Posts tagged release
wpGForm v0.28 released
540 days
This morning I released an update to my WordPress Google Form plugin. I can only assume very few people are using the email confirmation feature because it wasn’t working and I didn’t hear about it until this past weekend! The email confirmation feature (add the attribute email=’on’ to your short code) will notify the WordPress administrator that a form submission has been made.
The update is now committed and should appear on your WordPress Dashboard shortly.
WordPress Google Form v0.27 released
051 days
This afternoon I have released v0.27 of my WordPress Google Form (aka wpGForm) plugin. This release has some new functionality but more importantly, reverts the custom confirmation page to the redirect method which was present from v0.11 to v0.025.
If you prefer the AJAX style custom confirmation, which I do, it is still available by adding the short code attribute style=’ajax’ to your gform short code.
Changes for v0.27 are:
- Added ability to check and warn for old and/or unsupported browsers. There is an option on the WordPress Google Form settings page to enable this check. When an old or unsupported browser is detected, a message will be displayed on top of the form. The browser check is based on the same functionality that WordPress uses on the Dashboard.
- Changed default custom confirmation behavior has reverted back to using a javascript redirect as it did from v0.11 through v0.25.
- Added new shortcode attribute, style, to control how confirmation pages should be handled. There are two options: style=’redirect’ which is the default and style=’ajax’which loads the page content via AJAX.
- Added new CSS classes to support errors and warnings for the browser check and the inability to load Google Forms.
- Cleaned up Options page GUI.
wpGForm now has email notification
3I’ve received a couple of requests to have an email notification sent out when a form is submitted. Today I released v0.26 which supports a new attribute (email=’on|off’) on the gform shortcode. By default email notification is off but when set to on, an email to the blog administrator will receive an e-mail indicating a form was submitted. The email also contains the URL for the form, and date and time the form was submitted.
While I was working on this version, I also decided to see if I could make the custom confirmation work like my original implementation which did not use a Javascript redirect. I had switched to the redirect when I added support for multi-page forms because the mechanism I was using previously no longer worked.
Email can be sent in either HTML or Plain Text formats, there is a new option on the settings page. By default email notifications are sent in HTML format.
The v0.26 version switches from a Javascript redirect to an Ajax page load using jQuery. In my testing it seems to work pretty well and is much less intrusive than the redirect was. Let me know if you run into any problems with it.
The v0.26 release is now available from the WordPress plugin repository and an update will appear on your WordPress Dashboard.
Sandbox-SwimTeam theme updated to v3.1.372
065 days
This morning I posed an update to my Sandbox-SwimTeam theme. This update addresses a number of CSS bugs which primarily affected the login page.
Sandbox-SwimTeam theme v3.0.360 available
081 days
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
785 days
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.
WordPress Google Form v0.23
096 days
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
0Yesterday 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.
WordPress Google Form minor update – v0.21
3107 days
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.
Yet another update! WordPress Google Form v0.18 available
6109 days
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!
Recent Comments