Released on January 31, 2024. Updates described below may not be immediately available. To view the latest version of WildApricot in your browser, clear your cache.
What's new
DMARC requirement for custom domains
The DNS settings for custom domains must now include a DMARC record in addition to the already-required SPF and DKIM records. The DMARC record is a TXT record that provides a protocol for how emails should be processed.
This is a requirement implemented by Gmail and Yahoo as part of their new authentication guidelines regarding emails. As a result, Gmail and Yahoo will no longer process emails sent from custom domains that do not include DMARC, SPF, and DKIM records.
Note: If you do not use a custom domain with WildApricot, you don't need to do anything.
If you have a custom domain but do not update your DNS records, this new requirement will prevent you from using your custom domain as the primary From email address for your WildApricot account, and your From email address will revert to @wildapricot.org.
Check your custom domain status
If you have a custom domain, conduct a domain status check within your WildApricot account to verify that all 3 DNS records are present and correct.
Follow these steps:
1. In the admin view, navigate to Website > Settings and select Domain name.
2. In Domain name management, click each Check button.
View our article on Custom domain setup for more details.
Note: WildApricot's Support team cannot help you manage your custom domain's DNS settings as these settings are managed through a private account with your DNS provider and are unique to each customer.
Refer to your DNS provider’s help center if you need assistance with updating the DNS records for your custom domain.
Updates made to your DNS settings can take up to 2 days to go into effect. This delay is determined per DNS provider.
View Emailing from your custom domain for additional information.
Implementation of new email authentication protocols
With this release, we've implemented backend changes in the way WildApricot authenticates emails in order to align with the new requirements from Google and Yahoo. Implementation of the new DMARC requirement, explained above, is one part of these changes.
In addition, our email headers now feature an Unsubscribe link to meet the new opting-out requirements for emails effective February 1, 2024.
See Gmail and Yahoo's bulk sending requirements for 2024 and Emailing from your custom domain for more information.
Infrastructure upgrades
This release includes several backend infrastructure upgrades that improve product performance. These improvements won't result in any visible changes for users.
Feature enhancements
Widget functionality improvements
In response to Google's implementation of Tracking Protection, a new Chrome feature that restricts access to third-party cookies by default, this release includes improvements to WildApricot's widget functionality.
To learn more, view our article on Cookies.
WordPress integrations
Websites using WordPress integrations should update their plugins to the latest version for enhanced security.
API updates
No changes to WildApricot's public API were included in this release. To view a comprehensive list of the API updates released in 2023, including Swagger links, please view Public API 2023 updates.
To learn more about our public APIs, view WildApricot's APIs in our help center.
Bug fixes
- Fixed a bug that allowed new members with a status of Pending to access restricted polls
- Fixed a problem that caused some new members who logged in for the first time to be automatically logged out after clicking the checkbox to accept the organization's Rules and Terms
- Corrected a problem that prevented some accounts from being able to upgrade their billing plans within the admin view
- Fixed a bug preventing some admins from seeing the page options when they assigned the Website editor permission to Limited administrators
- Fixed a problem affecting the automatic deactivation of some PayFlow accounts after their WildApricot accounts were deleted
- Addressed an issue that affected the member SSO login experience for one account
