This evening I made a beta-4 beta-5 version of Email Users v4.3.15 available for download from this site. I still hope to incorporate as many translation package updates as I can before the final release. This latest beta version has some more tuning to aid in translation.
Download the beta release and please let me know if you run into any issues.
This afternoon I made a beta version of WordPress Google Form v0.46 available for download from this site. I have not posted this version to the WordPress plugin repository yet as I’d like to get some additional testing done on it before doing so.
There are a could of significant new features and a few bug fixes in this version.
Columns! You can now have your form rendered in columns. To have a two column form, add the attribute columns=’2′ to your short code.
When enabled, the simple math CAPTCHA will now appear above the Submit button instead of below it.
Some minor CSS updates to support the new column feature.
Download the beta release and please let me know if you run into any issues. You can see an example of multi-column support on my Multi-Column Test Bed Form.
This afternoon I released v0.45 of my WordPress Google Form plugin. After validating the changes I made in the beta with a user who was dealing with a polluted jQuery script, it looks like moving the jQuery script into the WordPress footer action is the right answer.
I’ve made a subtle but potentially significant change to WordPress Google Form that I am looking for some people to try out. The plugin generates a jQuery script on the fly to perform a number of actions depending on the shortcode attributes present and their setting.
Historically the jQuery script has been output as part of the form code but I’ve seen a number of cases lately where another plugin or in some cases, the theme, is manipulating the page content which ends up affecting the jQuery script.
In one case I looked at this weekend something, I am still not sure what, is injecting paragraph elements into the HTML after it detects a closing DIV tag. For the most part this isn’t a big deal except, there are closing DIV tags in the jQuery script as part of the CAPTCHA functionality. The CAPTCHA functionality injects a DIV which holds a second DIV and some other input elements and labels. What ever is injecting the P elements into the HTML after every closing DIV is causing my script to have syntax errors when the page loads.
To solve this problem I have moved to loading of the jQuery script into the WordPress footer action. In my testing making this change has zero effect on the functionality but I’d like some other people to test it and provide me feedback.
This morning I released v0.44 of WordPress Google Form. This is a minor update which addresses a problem reported in the WordPress Plugin Support Forum. This update fixes the problem where the settings which are on by default, cannot be turned off. You can find the update in the WordPress Plugin Repository or as an update on your WordPress Dashboard.
This morning I released v0.39 of my WordPress Google Form plugin. This update addresses the corner case exposed when using WordPress Google Form with the Unite theme from Paralleus. To solve this incompatibility I’ve introduced a new short code attribute called unitethemehack which defaults to off. By turning it on, WordPress Google Form will modify the Google Form HTML to protect the Submit button(s) from being manipulated by the Unite theme.
Today I released v0.38 of my WordPress Google Form plugin. If you look at the change log you’ll see I actually released it a couple times today (ugh).
Release v0.36 addressed a bug when the Browser Check option was enabled. I susquently released v0.37 because I didn’t tag v0.36 correctly and the WordPress Plugin Repository didn’t see the update. I then released v0.38 because I left some debug code active that I used to chase down the problem I originally fixed in v0.36.
I apologize for the multiple updates, it certainly was not my intention. You can find v0.38 on your Dashboard Update or in the WordPress Plugin Repository.
This morning I release an update to phpHtmlLib which resolves an issue for users still running sites based on PHP 5.2. The recent update to address early PHP 5.3.x releases contained code which was not 5.2.x compatible. This update addresses that problem. You can find the update on the Download and Installation page or as a Dashboard Update from the WordPress plugin repository.
This morning I released v1.36.973 of wp-SwimTeam. This build addresses a bug which prevents Users from signing up for job from the Jobs tab.
Yesterday I released v1.35.971 which addressed a problem when there were zero swimmers (aka a new installation) in the system. This bug caused some of the pages to display oddly for the Roster and list of Swimmers. Lastly, I enhanced the registration email such that it includes the Optional Field data defined for a swimmer. This enhancement is only included when using HTML formatted email. The Plain Text email continues to be very brief in nature.
This afternoon I released the v0.33 update to WordPress Google Form. This update introduces a new setting which allows users who are using the email notification to turn off the Bcc to the Blog Admin feature. This setting is on my default to match the behavior of the plugin prior to v0.32.
Several other minor bugs were also fixed which affected how default plugin settings are handled. You can find the update in the WordPress Plugin Repository or on your WordPress Dashboard Update notification.
What happened to v0.32? I failed to update the version number in the plugin file before tagging the relase in the WordPress plugin repository so I had to increment the version number again.