WordPress Google Form Update

I have spent some time comparing low level WP_Http results against wget results and have come to the conclusion that Google Cookies aren’t being passed through the series of redirect which happens when viewing a Google Form with the new URL scheme.

Unfortunately I am not sure what to do about it yet.  The usually very helpful WordPress Hackers mailing list is surprising quiet right now.  I am trying to figure out if I can “remember” cookies and pass them along each time a redirect happens.  I am reasonably confident that is what is needed however making it happen within the WordPress context is another story!

Google change to breaks WordPress Google Form

Last week Google introduced a significant update to Google Forms.  In addition to a very different UI, the format of the public URL has changed AND more importantly, it has broken my WordPress Google Form plugin.

The change only seems to affect forms created from scratch using the new version of Google Forms.  My plugin is dependent on the WordPress HTTP API to retrieve the form from Google and with the new URL format, the API is returning an error.  I am trying to figure out what Google doesn’t like.

What is odd is I am able to successfully retrieve the form using the wget utility (a Unix command line tool for retrieving remote content) however wp_remote_get() doesn’t work.

I wish had some better news to report but right now I am stumped as to why this isn’t working.

If anyone has any ideas, I have posted some of the low level debug stuff on PastBin.

Email-Users 4.4.1-beta-1 available

I have fixed a couple of minor bugs, added German Language support and introduced new functionality to send email to a custom list of users based on meta data.  The ability to target a specific list of users based on user meta data is a feature that was requested a while back on the WordPress support form.

The new Customer Meta Filter List functionality allows the the site to create a custom list of users by adding an action in either the theme’s functions.php file or in a stand-alone plugin.

EU_SS_04 EU_SS_05

Unfortunately I ran into a WordPress limitation while working on this functionality.  The  ability to match user meta data through the WordPress get_users() API doesn’t work as expected with the LIKE and NOT LIKE comparisons.  In an effort to protect the SQL, WordPress wraps the value being compared with wildcards to the match is either too permissive (matches too much) or too restrictive (matches to little).

I have opened a WordPress Trac ticket and submitted a patch for this problem but until it gets fixed (or the patch in the Trac ticket is applied), only standard comparisons work.  The “Last Name: M” example won’t work without the patch nor will the “First Name: Not D”.

I have written an example plugin to create the above filters, you download it and drop it into  your plugins directory to see menus like shown above:

Email Users Custom List (5744 downloads )

Please download and test the beta release.  Report back any issues and I’ll do what I can to fix them quickly.

Email Users Beta (5479 downloads )

Understanding Email-Users Settings

Periodically I receive Help Requests (either from the WordPress Support Forum, a comment on my blog, or an email) for Email-Users.  Most of the requests involve why some users do or don’t receive email.

Each user has two values associated with their user id:

  1. Does the user receive mass email?
  2. Does the user receive post and/or page notifications?

The ability to control these settings by the user from their User Profile page was a feature of Email-Users long before I got involved.  I have enhanced this functionality to allow an Administrator have the ability to change the settings for a specific user as well as adding the ability to bulk change the settings for a large number of users.

The bulk change feature appears under the Email-Users menu as “User Settings”.  Looking at this page will show you the current state of each user with respect to receiving mass email and post/page notifications.

The administrator can also remove the ability for a user to change their own settings through the plugin settings.

When using the “Send Email to User(s)” or “Send Email to Group(s)” feature, the list of users or groups is extracted from the database based on the settings for their user id.  You can always send email to a single user regardless of their setting however if you select more than one recipient, the Mass Email setting for a user is honored and they will be dropped from the recipient list.

Here are some screen shots to illustrate the points made above.

What is holding up the next wpGForm update?

I’ve had a couple questions about the next version of WordPress Google Form.  I have had a beta version of the next release of WordPress Google Form available for a number of weeks.  So what is holding up the release?  This is a pretty busy time of year for me at work (my real job) and combined with the holidays, I just haven’t had a lot of time to work on it.

This next update really changes how I recommend using the plugin and I want to make sure my Help and Support form can support it and right now it doesn’t.  So until I can find a few minutes to update the Help and Support form, I am going to hold off on the release.

WordPress Google Form v0.46 beta 9 available

I’ve updated the beta version of WordPress Google Form v0.46 this morning to beta-9. This beta update adds a significant new feature and one that has been requested a number of times: The ability to require an email address from the person filling out the form is now possible through a setting on the Google Form custom post type (this is not available through the old gform short code).

I would encourage migrating to the new short code and defining forms with the Google Forms Custom Post Type UI as that is where I am adding new functionality.  The way I added the User Email option should also allow me to allow form specific validation rules (e.g. URL required).

Download the beta release and please let me know if you run into any issues.

Google Forms Beta (8556 downloads )

WordPress Google Form v0.46 beta 8 available

I’ve updated the beta version of WordPress Google Form v0.46 one more time to beta-8 and made it available for download from this site. This beta update fixes a redirect problem when using the original “gform” short code. It was not present when using the new “wpgform” short code. I would encourage migrating to the new short code and defining forms with the Google Forms Custom Post Type UI.

Download the beta release and please let me know if you run into any issues.

Google Forms Beta (8556 downloads )

WordPress Google Form v0.46 beta 7 available

I’ve updated the beta version of WordPress Google Form v0.46 yet again to beta-7 and made it available for download from this site. This beta update adds a new settings on the plugin settings page to control the timout value for the WordPress HTTP API. Increasing the timeout appears to help with very large Google Spreadsheets.

Download the beta release and please let me know if you run into any issues.

Google Forms Beta (8556 downloads )

WordPress Google Form v0.46 beta 6 available

I’ve updated the beta version of WordPress Google Form v0.46 to beta-6 and made it available for download from this site. This beta update addresses some typos which caused problems when running with debug enabled and temporarily increases the HTTP_API timeout to 15 seconds to chase down a suspected problem with very large Google Spreadsheets. If increasing the timeout works then I will add another setting to the plugin to allow this to be changed on a per site basis.

Download the beta release and please let me know if you run into any issues.

Google Forms Beta (8556 downloads )

wp-SwimTeam v1.37.976 released

This morning I released v1.37.976 of wp-SwimTeam.  This build addresses a bug which prevents the deletion of Event Groups and fixes several situations where dialog boxes were “floated” to the wrong place pushing them off the page to the right side.

You can find the latest version of wp-SwimTeam on the Download and  Installation page or in the WordPress Plugin repository.