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.
I’ve been out of pocket for the past few weeks, for anyone who has submitted a bug or help request, I apologize. I am back in North Carolina and have some time to address some of the questions and help requests which have queued up since before Christmas. I have answered a few Email Users and WordPress Google Form questions in the WordPress Support Forum but if you haven’t heard back from me, don’t hesitate to ping me again.
This morning I released version 4.6.2 of Email Users. This release addresses several translation issues and updates the Bulgarian translation. More importantly, this release adds an integration with ItThinx Groups! This new feature is one that has been requested several times and I finally had the time to work on it.
I am close to releasing Email Users v4.6.2. This update addresses some issues in the README file and some translation string issues on the Options page. There is no new functionality or bug fixes since beta-1.
I would like to get as many of the translations as possible updated before releasing 4.6.2.
This morning I posted the first beta release (beta-1) of Email Users 4.6.2. This release includes integration with the ItThinx Groups plugin. I also took the opportunity to refactor the code for integration so code isn’t unnecessarily loaded when a plugin isn’t installed and clean up the plugin’s ReadMe file.
If you use ItThinx Groups I would appreciate any feedback you can provide.
You may have noticed an influx of content (posts, pages, etc.) related to wp-SwimTeam and wonder where it came from. For the past four years I have been developing, enhancing, supporting, etc. a WordPress plugin called wp-SwimTeam. This plugin can be used to manage the registration, volunteers, participation, and other aspects of running a youth swim team. Several groups have used it for Masters Swimming as well but it is targeted at youth swim teams.
I first started wp-SwimTeam to support our local neighborhood team when my wife was the swim team chair. Over the years it grew in features to the point where it was fairly comprehensive. My children no longer swim and my involvement in swim team has largely ended but I still maintain my plugin because (a) people use it and (b) I still feel it serves a need and it doesn’t take much of my time to continue supporting it.
I have always had a separate web site for wp-SwimTeam but over time that came to make less and less sense. In fact, I had some people contact me on this site and some on the other site so I had questions and solutions on both sites. I decided that I would migrate everything here So I exported all of the content and then imported it. There were a few hiccups, mostly around downloads but I think everything else came over ok.
The old URL redirects to the wp-SwimTeam page on this site. From time to time you may see updates for wp-SwimTeam or phpHtmlLib in addition to the normal flow of information on Email Users and WordPress Google Form.
For the past few days I have been chasing a reported issue where Email Users is putting recipient addresses into the CC header instead of the BCC header. This has been a challenge to chase down. To assist in this I have add a bunch of new debug and checking to Email Users.
Email Users will now check and report if wp_mail() has been overloaded by a plugin or theme. Since wp_mail() is a pluggable function, this is the one area which is really out of the control of Email Users. Simply knowing if wp_mail() has been overloaded is very helpful.
Additionally, I have finally found a way to initiate a complete email which is aborted just prior to the email actually being sent. The content of several internal structures is displayed on the Dashboard so the email headers can easily be examined.
This build is in DEBUG mode which means it will never actually send an email unless wp_mail() has been overloaded in which case all bets are off. Please visit the Settings page first to determine if wp_mail() has been overloaded. If it has, do not send any email but let me know which plugin or theme has overloaded wp_mail().
This morning I pushed out beta-4 for Email Users v.4.5.3. This latest update addresses the duplicate header information discovered by Andy Fragen. I had already fixed the problem with the TO header Andy noted but was unaware of the duplicate MIME-Version header. It turns out, there was also a duplicate X-Mailer header as well.
By default wp_mail() sits on top of PHPMailer. WordPress does not check for either the MIME-Version header nor the X-Mailer header. Unless specifically set, PHPMailer will add its default values for these two headers which is what was happening. It appears that some systems are sensitive to duplicate headers and reject the messages and others do not. This definitely explains why it is difficult to reproduce reports that come in of users not receiving email.
Because wp_mail() is pluggable, other mail implementations may be expecting these headers to continue to exist. What I have done is added two new options to add the headers as Email Users has been doing all along. By default these two options are off because PHPMailer duplicates them and I expect most people use the default WordPress implementation.
I also improved the information panel I added recently to report the existance of any filters which may interact with Email Users. For the most part these filters don’t do any harm however they can change override the FROM information in the email or the format which may be unexpected. The new information in the panel is nothing more than a note that something else may be affecting your email outside of Email Users (e.g. why is my From name different than what I set?).
Please report any issues with this latest beta update.
This afternoon I posted the third beta release of Email Users v4.5.3. There is a pretty significant change in this build so I may bump to v4.6 when I release it.
Yesterday I posted an article about an odd Email Users problem I was looking at. This build fixes (correctly) the problem encountered by that user by properly using get_users() instead of a complex SQL query to retrieve the information used to construct the User Settings page.
In addition to being properly constructed, the User Settings page has a number of fixes including proper sorting and the addition of Search (which I could never get working using the old query).
A second beta release of Email Users v4.5.3 is now available. This beta addresses a problem reported on the WordPress Support Forum where the Dashboard widget was shown to all users as opposed to only users who have some level of Email Users capability.