I have been working on resolving a plugin conflict between WordPress SEO and Google Forms. Based on some help from the WordPress SEO plugin author I have made some small changes to Google Forms which I believe will alleviate the conflict.
I am looking for people who’ve been dealing with this problem to test this out, if you have a few minutes, please download this beta and give it a run through.
This morning I released v0.65 of Google Forms, a long overdue update. I have been sitting on this release for a while because of one outstanding issue I was aware of which I simply haven’t had time to chase down. The ability to email the end user upon form submission broke at some point, I am not exactly sure when but it has been reported a few times recently. It turns out, it only worked if email to the admin was also enabled.
Here are the highlights from the Change Log:
Implemented “save_post” for custom post type eliminating general purpose “save_post” (only option prior to WordPress 3.7) action which could potentially, if not handled correctly by another plugin, corrupt post data.
Formally deprecated the gform shortcode by updating README file.
Added flush of rewrite rules upon plugin activation and deactivation.
Implemented protocol relative URLs for loading jQuery script from Microsoft CDN to avoid mixed-content warnings when serving over https.
Fixed layout of CAPTCHA options on settings page.
Fixed bug with preset values as part of the URL which contain spaces.
Fixed bug sending End User email upon form submission.
Refactored construction of email headers based on experience with Email Users plugin.
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:
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.
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.
Please report any issues with this new functionality ASAP and I will try to address them quickly.
I did some additional testing with UTF-8 characters over the weekend and everything is working as expected. With no known issues outstanding I have released v0.64 this morning. You can find the update on your Dashboard or download it from the WordPress Plugin Repository.
Fixed a number of strings which were missing translation wrapper functions.
Reverted to manually constructed body parameter for wp_remote_post() to allow checkboxes to be properly passed to Google.
Fixed warnings generated by calls to static functions which were not declared static.
Added check for HTTP API cURL transport and issue a warning when not present. There was a change between WordPress 3.6.1 and 3.7 to the WordPress HTTP API and the streams and fsockopen transports are unable to post form values back to Google using wp_remote_post().
Added a setting to allow hiding the cURL transport missing message on the Dashboard.
Added a check to ensure jQuery script isn’t output more than once.
Remove hook into “the_content” to reduce potential conflicts with other plugins (e.g. WordPress SEO plugin by Yoast).
Added placeholders for some of the form fields when defining a Form within the UI.
I finally had a chance to do some final testing of Email Users v4.6.3. To the best of my knowledge there are no outstanding issues so I have released it today. You can find the update on your WordPress Dashboard or in the WordPress Plugin Repository.
Bug Fixes and Enhancements
Fixed several strings which were not properly set up for language translation.
Re-added French translation file as it had gotten corrupted somehow and wouldn’t load in WordPress.
Added Dutch translation support (thank you Bart van Strien).
Fixed bug where sites with large numbers of users would exhaust memory.
Updated Spanish translation (thank you Ponc J. Llaneras)
Added additional options for BCC limit.
Fixed several CSS bugs on Settings page.
Initial implementation of Paid Memeberships Pro integration.
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.
Empty User Groups from the Groups plugin are no longer displayed when sending group messages or notifications.
Please do some testing with this build, I would like to release it fairly soon. I have limited knowledge of Paid Memberships Pro so it could use some testing. My experience with PMP is it is pretty fragile, I had to mess with my WordPress database just to get users assigned to PMP groups.
This morning I released v1.41 of wp-SwimTeam. You can find the update on your WordPress Dashboard or in the WordPress plugin repository. This release addresses two bugs, one of which is pretty significant but would not affect a site where the age groups were already set up.
Fixed bug which resulted in warning regarding extra output upon plugin activation. This was introduced in the WIP role code and as the result of a reference to a non-existing role.
Fixed a serious bug which prevented creation or update of standard age groups. If age groups were already set up, this bug was unlikely to be encountered but for new installations, it was a significant issue.
Update: Around noon EST I updated the build to beta-10 to fix another bug.
This morning I posed beta-9 of the upcoming Email Users v4.6.3 release. This build includes an updated Spanish translation as well as several new options for the BCC Limit setting targeted at sites with very large numbers of users (e.g. 4k, 13k, etc.).
This build also moves some debug code I have been using to chase down the memory issue under the control of the Email Users Debug setting (which is on the plugin settings page – Dashboard->Settings->Email Users). I have found this code to be really useful chasing down this odd memory problem however I don’t want it running all the time so putting it under the control of the debug setting makes sense. When debug is enabled, if you choose the “Send to Users” menu (Dashboard->Email Users->Send to Users) and examine the source HTML code for the page, you will find a section of code which looks similar to this:
This sort of information is tremendously helpful when chasing down odd behavior.
I am hoping to get a couple more translation updates before I do the v4.6.3 release along with some testing from a couple of sites with large user counts. In the meantime, you can download the latest beta version here.