Mike Walsh's random thoughts and musings …
Posts tagged Bug
Custom Confirmation problems with v0.26
954 days
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.
WordPress Google Form v0.25 now available
058 days
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.
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.
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!
wpGForm Bugs in v0.15
1112 days
I have been alerted to a couple of bugs in the current (v0.15) version of wpGForm that I am working on fixing.
- Select boxes do not retain their value when going back on multi-page forms. I’ve already fixed this problem in my development build.
- Check boxes are not passing their values correctly.
- 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.
WordPress Google Form v0.15 released
0This 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.
Recent Comments