Platform

Updates / Bug Fixes

• Updated translations. Thank you to everyone who keeps our translations up to date. Also, an especially big shout out to Skiftet who completed the Swedish translation.
  
  
• We've fixed an issue that was preventing supporter records from saving correctly when being synced to Salsa.
  
  
• We've added additional documentation about the unsubscribes table that's included in our bulk data. You can find more information about what the different unsubscribes mean here: https://developers.controlshiftlabs.com/#bulk-data-files. 
  
  
• We've added additional documentation about using our API to unsubscribe a user from a single petition or event. More info: https://developers.controlshiftlabs.com/#signatures and https://developers.controlshiftlabs.com/#attendees.
  
  
• We're now allowing organizations to create signatures via API. This can be useful for organizations who are collecting signatures from other sources (custom-built apps, facebook ads, etc.) to easily transfer signatures to the CSL platform. More info: https://developers.controlshiftlabs.com/#signatures.
  
  
• For location searches, we've updated the code to use an organization's bounding box to improve results. (The bounding box is set from the admin homepage > Settings > Time Zone & Locale, and represents the organization's geographic purview.)
  
  
• We updated the app's GDPR rules to ensure that data processing consent was shown for UK members post-Brexit.
  
  
• We fixed an issue that was preventing the moderation queue from loading. When a petition event is created, we allow the event creator to email the petition's signers to invite them to the event. While the event invitation email is pending, if the petition is deleted, the moderation queue would not load. We're now deleting pending event invitation emails if the petition that the event is associated with is deleted. 
  
  
• Submitting an empty query on the /org/members page sent the user to the Oops page. Now, you'll see a flash message on the member page.  †
  
  
• In the moderation queue, we allow admins to change the 'from name' for a blast email or specify a different reply-to address. However, those updates didn't work correctly for partnership blast emails (emails that originated from a partner's admin tools). This code has been updated. †
  
  
• We've made additional performance improvements to the unsubscribe API.
  
  
• We've updated our pagination code so that it works correctly on smaller devices. 

Petitions

Updates / Bug Fixes

• We've re-added the Google maps autocomplete to the new petition form. It was temporarily removed in favor of a different location search component, but the autocomplete is back. 
  
  
• For organizations using the email confirmation workflow (a.k.a. double opt-in) the confirmation flow would not work correctly for duplicate signers. Previously, if someone signed a petition, did not confirm their email address, and then signed the petition again, we'd send them a new email asking them to confirm their action. However, the confirmation links in that email were not correctly tokened, so the user could not successfully confirm their second signature. We've updated the code and the tokens are being appropriately added again. 
  
  
• In the thank you for creating/signing a petition emails, we're now allowing organizations to override the default source and utm_source for the Twitter and WhatsApp share buttons. To override the default source, you can update the variable in the emails to {% twitter_share_url source: foo %} and  {% whatsapp_share_url source: foo %} where foo is your chosen source code. Here's an example of code you could use, if you wanted to use wa.thanks as the source code for your WhatsApp button:
  
  <div style="text-align:center;padding-bottom:10px"> <p>
<a href="{% whatsapp_share_url source: wa.thanks %}" style="text-decoration:none"><span style="background-color:#25d366;border:solid 1px #660000;text-decoration:none;color:#ffffff;padding:10px 18px;font-weight:bold">SHARE ON WHATSAPP</span></a></p> </div>
  
  
• We've updated the Promoted Petitions page to have two tabs: one for petitions promoted on daisy chains and one for petitions promoted on the homepage. Previously this page was one long list. 

Events

Updates / Bug Fixes

• We added additional verifications to the automatic emails sent to event hosts and attendees to ensure that variables are written correctly. †
  
  
• For organizations integrating with EveryAction, we're now listing the EveryAction event codes that can be used to ingest EA events and put them on ControlShift map and event listing pages.  †
  
  
• We're now allowing admins to set up event page redirects (from the event page > Admin > Settings > Event Details). This setting may be useful for organizations who want to send attendees to another page (e.g. a Zoom RSVP page) to complete their RSVP, but who still want the event to show on maps and event listing pages. †
  
  
• We allow organizations to embed a calendar's map of events and sidebar list of events on external sites. When a location search does not return any nearby events in that calendar, we prompt the user to create a new event. Previously that event creation button went to the main event creation page, not the calendar's event creation page. So a newly created event would not be included in the calendar. We've updated the code so that users are sent to the correct event creation page.
  
  
• In the thank you for creating/RSVPing to an event emails, we're now allowing organizations to override the default source and utm_source for the Twitter and WhatsApp share buttons. To override the default source, you can update the variable in the emails to {% twitter_share_url source: foo %} and  {% whatsapp_share_url source: foo %} where foo is your chosen source code. Here's an example of code you could use, if you wanted to use wa.thanks as the source code for your WhatsApp button:
  
  <div style="text-align:center;padding-bottom:10px"> <p>
<a href="{% whatsapp_share_url source: wa.thanks %}" style="text-decoration:none"><span style="background-color:#25d366;border:solid 1px #660000;text-decoration:none;color:#ffffff;padding:10px 18px;font-weight:bold">SHARE ON WHATSAPP</span></a></p> </div>
  
  
• If an event has more than one association (e.g. is part of calendar and tied to a petition, is tied to a petition and also tied to a group, etc.) we'll now show all of the associations on the event page.

Groups

Updates / Bug Fixes

• When a group is sponsoring a petition, and that petition has an associated event, we're now automatically associating the event with the group. (Previously the event would only be associated with the petition.)
  
  
• We've removed the local_group_event permissions set. These local group events are now included with all other events in the "Events (All)" category.
  
  
• We now allow local group events to be cloned.

Nothing new in 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.