Platform

New

• We changed our translation management tool. Instead of Transifex, we're now using Crowdin: https://crowdin.com/. We're excited for this change because it should make updates to source strings and translations faster and easier to manage.
  
  Existing translators should have already received invitations to join Crowdin. If you're interested in providing translations and you haven't received a Crowdin invitation, please get in touch.
  
  CrowdIn is better in a multitude of ways but we are most excited for the workflow improvements which should eliminate the need for customers to message us to have translations pulled into the application.
  
• We've made a series of updates to our new Upland Mobile Commons integration. This integration allows organizations to sync phone number information to Upland Mobile Commons and use that information to send text messages to supporters. Newly released updates include: 
  • We now create a separate Mobile Commons group for each petition or event. This will allow admins to easily send text messages to all signers/attendees of a petition/event. 
    
    
  • Admins can now specify a custom opt-in path on a per-petition and per-event basis. This allows organizations to send a custom series of welcome messages to users who are subscribed via a specific petition or event. To customize the opt-in path, go to the petition or event's admin page > Settings > After RSVPing. †
    
    
  • We now show the users most recent ControlShift action as a custom field on their Mobile Commons member page. Organizations who wish to see that information will need to add two new custom fields to your Mobile Commons account.
    
    
    
  • When syncing supporter information to Mobile Commons, we now check to see if the user was already present in the organization's Mobile Commons supporter list. New users will have new_mobile_subscriber set to true on the signature details page, in signature export, and in webhooks. †

Updates / Bug Fixes

• Previously, the cookies banner was introducing a horizontal scroll because it was a few pixels wider than the rest of the page. This has been fixed.
  
  
• We've released documentation about the essential and non-essential cookies that are used on the site. You can learn more here: https://support.controlshiftlabs.com/hc/en-us/articles/360001593536. 
  
  
• We're now allowing organizations to translate organization names for new locales before the locale is published (fully publicly visible).
  
  
• We fixed an issue where the Settings pages was broken for languages that have more than two 'count' translations (e.g. languages that  instead of "1 petition" or "## petitions" use "1 petition," "[few] petitions," "[many] petitions", etc.)
  
  
• Separately, we fixed an issue where certain blast emails couldn't be viewed by admins because the recipient count variable in translation text wasn't working correctly. †
  
  
• We fixed an issue where the Settings > Content > Drip Emails page was not loading correctly.
  
  
• We've updated the way we display the facebook (and other) share buttons on small-but-not-yet-mobile-sized screens. 
  
  
• We now allow admins to set and regenerate HMAC signing secrets for webhook endpoints on the Settings > Integrations > Webhooks page. For more information about HMAC Signing of webhooks and other webhook security features, see our developer docs: https://developers.controlshiftlabs.com/#webhook-endpoints †
  
  
• We've completed a long running project to rewrite large portions of the front-end code that powers the application to make it more modern, efficient, and reliable. This portion of the project includes updates to: signature count and recent signers list; category selection during petition creation and editing; setting a petition's short URL; and event and petition page autofocus and scroll. 
  
  This project will allow us to more quickly maintain and improve the application into the future and has already resulted in improvements to page load speeds, with more to come.
  
• We've fixed an issue that was preventing syncing information to Action Network if the the user already existing in Action Network and their email address in Action Network included capital letters.
  
  

Petitions

Updates / Bug Fixes

• Admins can now filter the petition list to show campaigns that have gone dormant. This may be useful for organization who have data privacy rules that require them to delete signature information after a signature has been inactive for some amount of time. 
  
  Dormant campaigns are campaigns that haven't had been edited or updated, been signed or had a blast email sent recently. By default petitions are considered dormant after 12 months, but admins can set a different time frame in Settings > Options > Petitions. †
  
  
• We've fixed a bug that was preventing signatures from being added via embedded forms if the organization had reCAPTCHA enabled. 
  
  
• We've fixed an issue where including the URL for wide images in the petition update section would cause the image to overrun the update box when it was embedded.
  
  
• We've updated the decision maker message help text section so that it's not longer included in in popover. This unifies the mobile and desktop designs. 
  
  
• We've updated the code that powers the petition locking/unlocking interaction on petition's edit page. We also fixed a bug that made clicking to lock/unlock not work for admins. 
  
  
• We fixed a bug where 'time ago' strings  (e.g. in the recent signers list, where it says "Kristy A. 2 Minutes Ago.") were not translated properly for all languages.
   
• We updated the "Show progress bar by default" string in Efforts' admin settings to be translatable. †

Events

Updates / Bug Fixes

• On the host recruitment page, the "description" field label was always in English. It's now translatable.  †
  
  
• On event admin pages, we allow org admins to move an event into a calendar by completing the URL for the calendar. In that modal, we were incorrectly included the slug of the event. This has been fixed.

Groups

Updates / Bug Fixes

• We've added a 200 character limit for forum post titles.
  
  
• We've completed a large project aimed at modernizing the code that powers group forums. The code updates will allow us to make future improvements to the forum experience for group members. 

† 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.