Email Users v4.6.6-beta-2 available

Yesterday on my flight to Phoenix I implemented a feature which was recently requested to use the To field for the recipient address when the BCC limit is set to 1.  There is a new choice in the BCC Limit option on the Settings page:

EU_SS_35

 

If  you’d like to test this new feature, download this beta build and report any issues you encounter.  It will work with both Post/Page notifications as well as group emails.  The only limitation is when used, the user’s email address will be placed in the To header without their display name.

Email Users Beta (258 downloads)

Google Forms v0.65-beta-3 available

This morning I posted beta-3 of Google Forms.  This latest beta addresses an issue reported on the Google Forms Support Forum where extra URL parameters would result in the form not being rendered.

Google Forms has supported additional URL parameters for a while as a mechanism to preset form values.  The problem turned out to be that parameters which contained spaces weren’t being handled properly which resulted in a bad URL.  The bad URL was then used to retrieve the Google Form which failed and resulted in the form not displaying.

This build properly handles spaces in URL parameters and Google ignores, as expected, any parameters it doesn’t know what to do with.  So in the case reported on the Support Forum, the extra parameters added by MailChimp will simply be ignored.

Google Forms Beta (524 downloads)

Email Users v4.6.6-beta-1 available

This afternoon I posted beta-1 of Email Users v4.6.6.  This build addresses an issue reported on the Email Users support forum.  The user reporting the issue was running into a feature that was actually designed into Email Users – the ability to email a user regardless of their Mass Email and Notification settings.

Based on the user’s use use case, I can understand the desire to prevent certain types of users from appearing in the User Recipient List.  So I have added a new option to the settings page which will prevent users who do not have a role on the web site from appearing in the Recipient List.

EU_SS_30

EU_SS_31

EU_SS_32

EU_SS_33

EU_SS_34Please report any issues with this new functionality ASAP and I will try to address them quickly.

Email Users Beta (258 downloads)

Google Forms v0.65-beta-2 available

I received a patch over the weekend from a Google Forms user which I have incorporated into beta-2 of v0.65.  The patch changes how Google Forms loads the jQuery Validation plugin from the Microsoft CDN.  The plugin is now loaded using a protocol relative URL.  This change will eliminate the mixed content message which appears on sites using HTTPS.

There are a couple other minor fixes in this build as well, the most notable a flush of re-write rules upon plugin activation or de-activation in hopes that it will eliminate one of the most common questions I receive (why doesn’t my URL work when I click the View Form button?).

Google Forms Beta (524 downloads)

Google Forms v0.65-beta-1 available

Shortly after releasing v0.64 I received a report of data corruption from a Google Forms user.  I took this report very seriously and immediately reverted the stable tag for Google Forms back to v0.63 while I looked into this users report.  The last thing I wanted to do was introduce a bug which resulted in corrupted posts.

I spent some time looking through my plugin code and tried a couple experiments but could not replicate the behavior the user reported.  My gut feel was we’re dealing with a plugin conflict however it is hard to know for sure.

The user and I ended up swapping some email and I got a list of plugins they were running.  I initially thought I would try and replicate their problem by installing the same set of plugins but quickly figured out that wasn’t possible.  Nor was it possible to examine all of the code for the plugins looking for what I suspected was a conflict in a “save_post” action or call to wp_update_post().

In doing some research I learned (unfortunately I can’t find it in the Codex) that beginning in WordPress 3.7 there is a new save_post action for Custom Post Types:  save_post_{$post_type}  Whoo-hoo!  This didn’t exist when I originally wrote Google Forms, so my plugin, much like many other plugins which define Custom Post Types, define a save_action which then has to determine if the post is relevant to the plugin or not before doing anything to it.

I quickly implemented the new action and removed the old action and Google Forms is behaving as it should in my testing.  I have uploaded this latest beta to my site and beat on it a bit and cannot corrupt any data.  I am very confident now that Google Forms should never touch anything other than it’s own post data.

Because of the reported corruption, I would encourage beta testers to backup their database before installing this update JUST TO BE SAFE but I think the corruption risk is very low.  Please let me know if you run into anything unusual.

In this v0.65 beta I have also changed the name of the plugin from “WordPress Google Form” to “Google Forms” as it is more representative and the plugin repository now prohibits the use of “WordPress” in a plugin name.  There is a chance you’ll have to reactivate the plugin depending on how you install this beta.

Google Forms Beta (524 downloads)

Google Forms v0.64-beta-7 available

This afternoon I released beta-7 of Google Forms v0.64.  I expect this to be the final beta release.  It contains a few minor fixes, most notably the warning from the cURL check regarding calling a non-static function statically.  Additionally, some new “placeholder” information has been added to the Form Definition form which disappears when the user starts entering text into the field.

Google Forms Beta (524 downloads)

Google Forms v0.64-beta-6 available

I have just released beta-6 of Google Forms v0.64 which is a CRITICAL update for anyone who loaded beta-5.  Beta-5 had a serious bug which if you had defined more than one form using the Dashboard UI, would corrupt the content of all of the saved forms so every form would display the same content.  Beta-6 fixes this issue!

Google Forms Beta (524 downloads)

wp-SwimTeam v1.42-beta-3 available

This afternoon I released beta-3 for wp-SwimTeam v1.42.  This builds adds a new option to allow control of the temporary storage used when exporting data to use outside of WordPress.  For now, this new functionality is limited to Roster Export only however if it works, I’ll do it for everything.

wpst_SS_06

Historically wp-SwimTeam has used PHP’s temporary file facility to store the constructed export data and it then sends it to the browser for download.  In a few corner cases, it appears the server configuration won’t allow doing this so I have added a new option to use WordPress transients as temporary storage.  It is a little slower than using temporary files so be patient for the download dialog box to display.  I am hoping this is a viable solution and will allow users who run into this issue, which I assume is security related, to use wp-SwimTeam.

wp-SwimTeam Beta (363 downloads)

wp-SwimTeam v.1.41-beta-2

This morning I uploaded beta-2 of wp-SwimTeam v1.41.  This build adds intelligence and error messages during the export process (rosters only for now) to detect an unusual, but critical situation, which occurs when the plugin is unable to generate a  temporary file.  The temporary files are used to hold the generated data which is eventually sent to the browser for download.

wp-SwimTeam Beta (363 downloads)

Google Forms v0.64-beta-5 available

2/14/2014 Update:  If you have more than one form defined, do not use beta-5, there is a serious bug which corrupts the content of the defined forms so they all contain the same data.

Beta #5 of Google Forms v0.64 is now available for testing.  This update addresses a plugin conflict between Google Forms and WordPress SEO plugin by Yoast.  The new implementation removes the hook into the_content which is a much more robust solution.

Google Forms Beta (524 downloads)