Platform

Updates / Bug Fixes

• We've expanded reCAPTCHA protections to other forms on the platform. When we initially rolled out the reCAPTCHA integration last week, it was only used on petition creation and signature forms. We've now expanded reCAPTCHA to the user sign-up form; petition creator, event host, and group member contact forms; comment and petition flagging; and RSVP forms.
  
  As a reminder reCAPTCHA is an optional integration that can be configured from your organization's Settings > Integrations page. (Google is not considered an authorized subprocessor under GDPR for reCAPTCHA.)†
  
  
• As part of our response to the spam attack that targeted a small number of our customers, we're automatically unsubscribing the emails we've identified to be part of that spam attack. For the organizations that were targeted, we've already communicated with you and unsubscribed the old signatures connected to this spam. Going forward, if these email addresses are used to take action on any customer sites, they'll be automatically unsubscribed. 
  
  
• We've changed what happens when an admin deletes a signature and the signer doesn't have any other actions on the site. Now, after the signature is deleted, the admin will be asked if they want to fully delete the member record (which, after the signature is deleted, and if there are no other actions associated, is only the email address). We've also updated the API so that deleting the final signature/attendee record of a user will automatically delete their separate member record. †
  
  
• We've fixed the way left popovers are displayed. Previously, their arrows overlapped the border of the help box, but this is fixed.
  
  
• We've updated the code that suggested a correct email address if the user had typed an address that's one letter off from common emails domains. (For example, typing hello@gmai.com will lead us to suggest that the user may have meant hello@gmail.com.)
  
  
• We're now allowing admins to export the list of bounces, drops, and automatic unsubscribes from the Settings > Deliverability page. 
  
  
• We're working on a project to rewrite large portions of the javascript that powers the application to make it more modern, efficient, and reliable. This modernization process will also unlock future features and improve our ability to evolve the platform. 
  
  
• We've also split our javascript so only the required pieces of the current page are loaded. This change ensures that those page-specific chunks are loaded more quickly.
  
  
• We've updated the default language for the cookies consent banner. We've also added a new option that allows users to choose 'essential cookies only' which hides the banner but does not allow non-essential cookies. †
  
  

Petitions

Updates / Bug Fixes

• We've fixed an error that occurred when a user attempted to sign a petition with Facebook, chose not to share Facebook data, was redirected to the petition page, used the back button to return to Facebook, and then allowed Facebook to share their data. Now we handle this series of steps more gracefully, and the user will be able to sign. 
  
  
• We've added a new Content Updated At field to the tech bits section of the petition's admin Details page. This timestamp will reflect when the petition's title/who/what/why/image/location fields were most recently updated (the fields that are available from the petition creator's edit page). This information could be used to track active vs. inactive petitions or be used for other internal metrics. †
  
  
• We've changed the help text we use for the name fields of the petition signature form. We're no longer using "real name" in our help text, but instead using "your name." We hope this change will make it clear that users can enter their chosen name, even if it's not the same as their legal name. †
  
  

Events

Updates / Bug Fixes

• We've fixed an issue where events with certain special characters in the title or description were failing to sync to EveryAction because EA didn't support use of those characters. We're now removing unsupported characters before syncing to EA.
  

Nothing new in groups or VisitThem.

† This feature required new text strings. If you're using the platform in a language other than English, you may need to provide updated translations.