I have addressed what I hope is the last of the security concerns with Google Forms and resubmitted to WordPress.org for approval. In the meantime, should anyone want early access to the next update, which includes some additional debug features as well as addressing the security concerns, you can download it here.
This afternoon I posted beta-4 of Email Users v4.8.5. This build adds some additional debug information to help chase down slow database queries. When in debug mode, Email Users will now report information about the query like this:
Last week I was notified my Google Forms plugin had a potential security flaw and would be de-listed from the plugin repository until addressed. I have implemented the fixes recommended by the WordPress Security Team and am in the process of getting the plugin listed again.
I would like to enlist some additional testing besides my small suite of test cases with the updated code.
This morning I released v0.87 of the Google Forms plugin. This update includes a new check when saving a form definition. The check scans the HTML from the form to ensure it has the proper HTML structure the plugin expects.
The new version of Google Forms is not supported by the plugin so this check ensures that a user is notified that the form isn’t of the expected format.
You can find this updated on your WordPress Dashboard or in the WordPress plugin repository.
Last night I released Email Users 4.8.2. This version addresses the use of several WordPress deprecated function messages, support for custom email headers and footers, and adds a feature to allow the admin to hide the Email Users menus from non-admin users. Full details can be found in the Change Log.
Minor beta update to add more options for the BCC settings. BCC setting now can be set to 2, 3, or 5 in addition to the other previously available values. These values are basically an aid for debugging, they are not expected to be widely used as few hosting providers enforce limits this small.
Earlier today I released Email Users v4.7.10 which is the formal release of a number of fixes I’ve had in the queue. Now that it is out, I’ve moved on to the first real new functionality in a while which is why this will be v4.8.x.
Recently there was a 1 Star rated review of Email Users which had a comment about not being able to search for a user in a list of potential recipients. As you can see in the comments, I didn’t disagree with the user although what they wanted to do was sort of possible.
I’ve used the jQuery Chosen plugin a couple times and it works great for making SELECT elements much more user friendly. I decided to add it to Email Users to make finding users, particularly for sites which have lots of users, much easier. If you used WooCommerce, you’re familiar with Chosen as that is what WooCommerce uses for SELECT elements as well.
The v4.8.0-beta-1 release is the first implementation of Email Users with the jQuery Chosen plugin integration. Please download it, try it out, and report any issues or concerns.
Implementing Chosen allows for easy search and selection as noted in these images.
From the Send to User(s) page
From the Send to Group(s) page
From the Send to Group(s) page after entering “au” to do some filtering
I have just posted beta-4 of Email Users v4.7.10. This beta update fixes another issue with the line breaks (hopefully the last one) and also adds the capability to use or include the user’s email address when sorting and/or displaying the user selection lists.
I had started looking at bounce issues a while back but never completed the work. It turns out bounce emails are problematic and the PHPMailer code included with WordPress has deprecated support for it. I’ve made some minor changes that may help those trying to use the bounce email address capability.
I stress the “may” aspect of it because my own testing I have been unable to get it to work. I have not seen anything not working from the changes I’ve made but I have not received any bounce emails either. They simply seem to go in the bit bucket as far as I can tell.
Due to this unreliability I am recommending against using the bounce email address feature and have added a warning on the settings page advising as much which appears when a bounce address is set.
From looking at email headers this morning, I believe they are constructed properly. I have no idea when bounced messages are actually routed versus discarded and different email servers seem to do it differently.