Another beta update, #5, for WordPress Google Form v0.61. This update fixes a couple more issues with validation which resulted in some extra jQuery content that was malformed. It only happened IF validation was enabled but no custom validation rules were defined.Google Forms Beta (1870 downloads)
I have just uploaded beta-4 of WordPress Google Form v0.61. This build corrects a couple more jQuery issues when using multiple instances of a form on the same page. In order to use multiple instances of the same form on a single page, you must use the uid parameter with the wpgform shortcode. Usage of this new parameter is outlined in the v0.61-beta-1 announcement.
The uid parameter is not supported in the deprecated gform shortcode.
Please download and test this beta release, all feedback is much appreciated.Google Forms Beta (1870 downloads)
The second beta build of WordPress Google Form v0.61 is now available. This beta build addresses some jQuery syntax errors introduced in the process of supporting multiple form instances. It also addresses a bug where the CAPTCHA would not be output as part of the form under certain circumstances.
Please download and test this new build if you have time and report anything which isn’t working.Google Forms Beta (1870 downloads)
After I have not had any reports of issues since releasing beta-3 so I have pushed out the formal release. You can find v0.59 in the WordPress plugin repository or on your Dashboard.
Enhancements and Bug Fixes in v0.59:
- Added ability to preset values for Google form as part of WordPress URL.
- Added new CSS declarations to default plugin CSS to account for recent changes by Google to Forms.
- Added ability to define fields as “hidden” and preset with a user defined or system defined value.
- Fixed validation limitation which only allowed one validation rule per input.
- Added basic support (CSS, jQuery) to use WordPress Google Form to view a Google Spreadsheet within WordPress.
This morning I released beta-2 of WordPress Google Form v0.59. This build introduces one new feature (hidden fields) and fixes one limitation (validation rules).
Much like validation rules and placeholders, an input field can now be defined as hidden. When a field is defined as hidden, it does not appear to the user when they view the form and the value is set to a fixed value (e.g. a static string) or to something WordPress derives (e.g. the user’s IP address).
The format of the field name is exactly the same as used for validation and placeholders.
Validation has been improved and the limitation of one validation rule per field has been lifted. You can now define multiple validation rules for a single field. Simply enter the field name for each separate type of validation.Google Forms Beta (1870 downloads)
I have finally released v1.40 of wp-SwimTeam. Thanks to everyone who helped test the new features and flush out any bugs. This release has a slew of new features and functionality.
- This update requires phpHtmlLib v2.6.7 or later!
- Fixed initializion bug when Adding Events to an Event Group. Events were by default not being assigned to the correct group.
- Fixed pagination bug when managing large number of events. When paging through events the GUI would get confused.
- Fixed Event Group bug which was propagating the wrong event group to subsequent actions.
- Added support for Mixed Gender and Combined age groups.
- Added support for Mixed Gender and Combined Events.
- Added support for exporting mixed gender event entries in SD3 and HY3 formats.
- Added support for mixed gender events when importing events.
- Fixed bug resulting in database error when generating RE1 roster.
- Re-implemented Roster Export functionality – multiple formats can now be exported. The export can also be limited one gender.
- Added support for age groups where min age and max age are identical.
- Added smart processing of 0 as min or max age in HYV event imports, mapping 0 to minimum or maximum age setting as appropriate.
- Fixed bug in USS Number generation.
- Fixed bug in HY3 entries generation where E1 record did not contain gender.
- Fixed reported entry count when exporting SDIF, count was off by 2x.
- Fixed bug exporting roster by single gender which resulted in no swimmers.
- Fixed bug which prevented proper HY3 meet entry generation for Opt-In swim meets.
You can find the update in the WordPress plugin repository or on your Dashboard.
Quick turnaround for another beta release, wp-SwimTeam v1.40-beta-9 is now available. This release addresses a bug generating a HY3 meet entry file when a swim meet is set up as Opt-In.wp-SwimTeam Beta (981 downloads)
This morning I released beta-8 of wp-SwimTeam v1.40. This beta release addresses a couple problems.
- I have fix the problem when exporting the roster by a single gender in Hy-tek format results in an empty roster.
- I have fixed the problem where the entry count is off by 2x when export meeting entries in SD3 format as compared to HY3 format.
There was some other minor debug code cleaned up nothing visible on the Dashboard.wp-SwimTeam Beta (981 downloads)
This morning I released beta-7 of wp-SwimTeam v1.40. This beta release addresses the problem where exported Hy-tek entries won’t load into Meet Manager. The problem was the E1 records didn’t have the gender specified in columns 14-15. I believe this problem was introduced when I implemented mixed gender events earlier this year.wp-SwimTeam Beta (981 downloads)
This morning I released version 4.6.0 of Email Users. This release addresses the problems with addresses appearing in the CC header instead of the BCC header which cropped up in v4.5.4 and v4.5.5. This version has gone through quite a bit of testing to ensure the problem with addresses was fixed. In addition to this critical fix, there are also a couple of minor new features now available. If you were running Email Users v4.6.0-beta-4, this version is nearly identical. The version is different and the default string for the new footer was trimmed eliminating the version number.
- Significantly improved debug functionality to chase down mail header issues.
- Check added to determine if wp_mail() has been overloaded by a theme or plugin.
- Rewrite of mailusers_send_mail() fucntion to construct headers as arrays instead of as a single string. The string would sometimes not break correctly and recognize the Bcc: field.
- Implemented new email footer option.
- Cleaned up presentation of Options page.
- Implemented new omit display names option.
- Updated language translation files.
You can find this update in the WordPress plugin repository or on your Dashboard.