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.
I recently had a report from a user regarding a problem importing a HYV event file. This event file was using Event Numbers with a one character suffix (in their case A-J). I didn’t know using a character suffix was a legal event number and had never encountered one previously.
It turns out it is fairly common, particularly with High School and YMCA teams. Since the database had defined the Event Number as an integer field, adding support for these “suffixes” as I am calling them wasn’t simple.
This build of wp-SwimTeam adds support for non-numeric Event Numbers and needs testing. I have added, updated, imported, and deleted event numbers and all seems to be working correctly. I have also exported SDIF and HY3 entry files which also look correct. However, I would appreciate some testing from someone who is more familiar with these sort of event numbers than I am.
Please checkout the beta release and provide feedback on any problems you encounter.
This evening I uploaded v0.64-beta-3 of Google Forms. This version adds a check for the WordPress HTTP API cURL transport and issue a notification if it isn’t present.
There was a substantial change to the WordPress HTTP API between 3.6.1 and 3.7. I don’t know the full details of the change but what I found in pretty extensive testing is the streams and fsockopen transports work in 3.6.1 with the Google Forms plugin but from 3.7 and later, they do not.
However, the cURL transport does work and as long as it is available, the plugin will work as it always has. The problem is I cannot find any way to work with sites that don’t have the cURL transport available so I have added this check and issue a notice when it isn’t present.
Please download and test out this beta version and report any issues found.
WordPress Google Form v0.63 introduced a change which allowed the plugin to work on newer versions of PHP, notably 5.4 and 5.5. Unfortunately that change has broken support for checkboxes.
For those who are new to the plugin or never needed to know how it worked, what the plugin does is retrieve the HTML for the form from Google and render it within the context of WordPress. When the form is submitted, it is actually submitted within the context of WordPress. The data is collected by the plugin and then submitted to Google. The retrieval from and submission to Google is done with the WordPress HTTP API. In particular, the wp_remote_get() and wp_remote_post() functions are used to retrieve and submit the form.
To complicate the problem further, Google uses Python as the backend for their form processor where as WordPress uses PHP. For the most part, the fact that they are based on different scripting languages isn’t a big deal. Until you get to checkboxes. Checkboxes in Python are handled differently than they are in PHP.
I had solved the compatibility problem a couple years ago (see this thread on the wp-hackers mailing list) using a small jQuery script which fixed the form variables on the WordPress side and manual construction of the body parameter for wp_remote_post() when submitting the data to Google. This solution worked fine until I received a bug report that nothing was being submitted on a site which was running PHP 5.4.x.
Fortunately the user who encountered the problem provided me with a patch that I was able to fold in which changed the way the body parameter was constructed (array instead of a string) which worked with PHP 5.4.x and also worked with older versions. However, I didn’t test it thoroughly as I have had several reports that checkbox content was not being submitted correctly. Uh-oh. I was able to verify the problem fairly quickly and was able to push out a version which essentially reverts how the body parameter is constructed (string instead of an array). The problem is, this build doesn’t work with newer versions of PHP.
I have PHP 5.5 running on an Ubuntu virtual machines for testing and so far, I have not found a solution which (a) works with PHP 5.5. and (b) submits checkboxes correctly.
This evening I released beta-2 of the upcoming v0.64 release of WordPress Google Forms. This build addresses a problem recently reported on the Support Forum where the responses for checkboxes wasn’t being recorded properly.
I was able to verify this problem using one of my test forms and began looking into it. It turns out, the changes made in v0.63 to allow the plugin to work with later versions of PHP 5.4 breaks the ability to uses checkboxes. This build employs a similar method of submitting parameters to Google that versions prior to v0.63 did.
Handling checkboxes has long been a challenge due to the different ways which Python (used by Google) and PHP (used by WordPress) handle the assignment of checkbox values to a named parameter.
Please download this build and test and let me know if you run into any issues.
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.
I have just uploaded beta-8 of Email Users v4.6.3. This build addresses an unusual out of memory situations which affected sites with very large numbers of users. You can find a detailed write up of the problem here.
The change s required to address this problem are pretty substantial so I would appreciate any testing people can do, I don’t want to break anyone’s email system!
In the process of working with a user providing a Dutch translation, I found a number of strings which were not properly set up for language translation. This build provides no new functionality, only changes to support translation.
This build also replaces the French translation files with new ones as the files in the release could not be opened with Poedit nor would they be loaded by WordPress. Not sure what happened but the files were corrupt.
Note: Updated to beta-3 late in the afternoon on 12/30.
This morning I posted the first beta of WordPress Google Form v0.64. There is no new functionality in this version, it just addresses a bunch of strings which were not properly set up for language translation.
If you want to provide a language pack for WordPress Google Form, this is the best version to work from. I am currently working with a user who is working on a French translation.