This morning I posted beta-8 of Swim Team v1.42. I hope to formally release it in the next day or two barring no reported issues. This update addresses a few more areas where I missed the changes to how files are included. This manifested itself mostly through usage of shortcodes but there were a few other spots too (e.g. event management).
This evening I posted beta-7 of Swim Team v1.42. This build addresses a problem reported earlier today. This bug manifested itself when there isn’t an active season which would be the case when the plugin is first installed. It is also possible to set all seasons inactive in which case, the same problem was present.
This morning I have posted a new build, v1.42 beta-6 of the Swim Team plugin. This beta release makes a major change to how the plugin includes the various files the plugin uses. Historically, Swim Team modified the PHP include_path as part of the initialization to include the paths where included files are expected. In newer versions of PHP this seems to cause some problems for some users.
I have changed the plugin to eliminate the need to modify the PHP include_path however the process of doing so required touching almost 100 files within the plugin. I have been through all of the menus and tabs and believe I found accounted for every file which included but there is always a chance I have missed something.
Please report any problems and I will do my best to fix it quickly.
This morning I released beta-2 and very quickly afterward, because I found a bugs, beta-3, then beta-4 of Email Users v4.6.10. This beta-4 build addresses a couple enhancements that were recently raised in the Support Forum.
Templates – while not exactly templates per se, the Post/Page notification email will now allow the user to change the email subject and body content. It will still be initially populated based on the default template.
Hooks – there are now two hooks which other plugins and themes can use to modify the behavior of wp_mail(). The two hooks are mailusers_before_wp_mail and mailusers_after_wp_mail. The primary use for this is to account for other plugins which modify the sender address.
Additionally, the Notification email process now has a preview of what the email will look like based on the current settings. The preview will not reflect any changes made to the subject or email content until it is submitted.
This afternoon I released beta-1 of Email Users v4.6.10. This build fixes a problem reported in the Support Forum today. I will likely try and address some of the recent enhancement requests before making a formal release. It is likely that most users would not have seen this problem unless their PHP error reporting level was more strict than typical settings.
I have just posted beta-1 of Email Users v4.6.9. This build addresses an issue reported with template replacements not working correctly when using sender overrides. Additionally, I have added support for blog and author template replacements in user and group emails.
I have uploaded beta-2 of Google Forms v0.70. This build has one minor fix. While minor, it is important to me. This build fixes an issue when the Email Admin option is enabled but the Send To address is not specified. By default the Blog Admin email address should be used in this situation however no mail was being sent at all.
While looking into a Support request I discovered a bug in the generation of the jQuery validation script which caused a syntax error. This syntax error could potentially cause problems with redirection upon form submission.
While fixing the above bug I also added support for embedded images which had been requested recently. When you design your form Google now allows the insertion of images and now Google Forms will display them properly.
You can find this update on your Dashboard or in the WordPress plugin repository.
Another minor update to Google Forms to fix a bug reported late last week. It turns out I left out a named array parameter in a call to wp_update_post(). What is interesting is this problem manifests itself differently on various installations. I never saw the error reported however when the offending line was pointed out, it was obvious to me what was wrong.