Mike Walsh's random thoughts and musings …
Posts tagged Bug
WordPress Google Form Bug with default CSS
0123 days
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.
Quick bump to v0.14 for WordPress Google Form
0126 days
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.
WordPress Google Form v0.13 fixes “back” bug
0I 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.
Support for multi-page Google Forms?
5219 days
I received an email the other day about my WordPress Google Form plugin wondering whether or not it should work with multi-page Google Forms It hadn’t even occurred to me to test it as none of the forms I had needed myself were multi-page forms but my gut reaction was I didn’t think it would work.
I took a look at a multi-page Google Form and have determined that the current (v0.10) version of the WordPress Google Form plugin (aka wpGForm) will not work with multi-page forms. No real big surprise but I want it to be clear before someone else wastes their time trying to make it work.
From looking at the form code it may be possible to support multi-page forms in the future but it will require some additional jQuery scripting and more importantly, some time to dedicate to it. I hope to look at this soon but I have a couple of WordPress theme projects that I need to get off my plate before I can go back to wpGForm.
WordPress Google Form v0.10 released
0226 days
Yesterday I committed the final changes (and still missed a few typos – ugh) to the WordPress plugin repository. The v0.10 release addresses the problems with required fields on a Google Form. I’ve heard from several people who’ve told me this fixes the problems they were seeing but if you run into something, add a comment here and I’ll do my best to take a look at it.
Note: I’ve also changes the beta download link to resolve to the WordPress download so the beta is no longer available.
Form Validation Working!
8230 days
I have required field form validation working. I haven’t released it yet but in my testing, it appears to catch all of the fields I defined as required. WordPress Google Form incorporates the jQuery Validation plugin.
When a page loads, the jQuery script runs and scans the Google form for required fields. For each required field it finds it adds the gform-required class to the input or textarea tag. When the validator runs, it looks for fields which have the gform-required class and if any are empty, a label is added with the gform-error class.
The gform-error class is defined in the default CSS to display the text in red and float it to the right of the input.
As can be seen in the image, if there isn’t enough room to the right of the field, the error will be shown just below it. As with most CSS solutions, there are a bazillion ways to customize the output, I have elected to use something real basic and let the plugin user add more CSS if desired.
If you would like to try this early release of the plugin and give me some feedback, you can download it here. The version in the WordPress repository is still the older v0.9 release.
WordPress Google Form (108)
GForm validation bug PoC
0232 days
This afternoon I spent some playing with a jQuery Form Validation plugin to determine if it will help me resolve the issue with required fields. The initial results look fairly promising as I was able to tag a couple fields on a test form and they were flagged when I submitted it.
In the image above, the jQuery Validation plugin added the “Thus field is required” when I submitted the form with those fields empty. This is exactly the behavior I want, the challenge now is to scale my Proof of Concept (PoC) to work in the generic case of the plugin. The Google form defines a block for each input field and the class the denotes a field as required is assigned to one of the DIV blocks that wraps the label and form element (e.g. INPUT or TEXTAREA tag) as opposed to the form element tag itself. This makes finding the required elements a little tricky.
The real challenge I think will be input groups (e.g. radio buttons and check boxes). I need to do some jQuery research before I have a solution but assuming I can figure out which elements to select, I believe this will solve the problem with required fields.
WordPress Google Form bug with required fields
0Google forms allow fields to be designated as required. When running the form using the standard Google URL, the form will be validated and presented back to the user if any of the required fields are not entered. There is an issue (aka bug) with required fields in the current version of the plugin.
If a user submits a form that is embedded in WordPress using the plugin, because there are missing fields the form processing does not complete. There is no indication for the user that something is wrong, the form is simply presented again without any of the fields having data in them.
To resolve this I am looking at doing form validation on the client side using a jQuery plugin. Hopefully I will have this resolved fairly quickly as I need this to work correctly for my own project. My testing didn’t take into account a user not completely the form correctly. Oops. This bug affects all versions of WordPress Google Form up to and including v0.9.
Stay tuned.
Enhanced Calendar broken
0494 days
There is a CSS bug with Enhanced Calendar that I need to resolve. I hope to have an update posted in the next day or two.
wp-SwimTeam v0.2.488 – bug for scratches
702 days
There was a bug in the scratch process where if you started on the Meets tab when the Scratch action was selected, there was not a list of swimmers presented for the user to scratch. When starting on the Roster page and selecting a swimmer to scratch did work properly. The bug has been fixed and v0.2.488 is now available for download and both paths, starting with a meet or starting with a swimmer, now work correctly. The same bug would have affected Opt-In meets as well.
Recent Comments