Platform

Updates / Bug Fixes

• Infrastructure improvements.
  
  
• In Chrome, some buttons in the platform lost their styling. We've updated our CSS and normal button styling should be restored. 
• Authenticated REST API consumers can now retrieve activity histories for a particular member. This may be useful if you'd like to aggregate a member's activities across several different toolsets into a single self-service dashboard. More information on this API endpoint is available here: http://developers.controlshiftlabs.com/#members.
  
  
• Lock icons didn't display correctly when viewing pages in RTL languages (e.g. Hebrew and Arabic). This has been fixed.
  
  
• Member search now accepts names not just email addresses. Please note: Only full matches will be displayed. This means that if you search 'Pete', only members with the name 'Pete' will be returned, not users with the name 'Peter' or 'Peterson', etc.
  
  
• We've updated the contact messages page (located at /org/messages) to make it easier for admins to view and interact with messages. The new page includes two sections: one for messages sent from site visitors to campaign creators and one for messages sent from campaign creators or decision makers to the organization. †
  
• Some users reported having difficulty resetting their passwords. To help diagnose any issue, we've expanded the alert box on the password reset page. This alert box will include additional error messages. †
  
  
• Content included under CMS > Content (e.g. /org/contents/...) now includes a History tab, which will include a log of any changes made to pieces of content in the organization's main locale. †
  
  
• We're continuing our preparation for the EU's GDPR. Our current iteration includes new settings to ensure that organizations receive appropriate consent to process personally identifying information. More information on this will follow.
  
  
• In emails sent through the platform, names that included apostrophes and/or quotes were not escaped properly. We've made some changes, so the from name shown on emails from people with those bits of punctuation in their name (e.g. Claudia Jean "C.J." Cregg) will display correctly. 

Petitions

Updates / Bug Fixes

• On the petition signature form, custom fields with numbers in the short name caused signatures to fail. This is now fixed, and you can feel free to number your short names.
  
  
• Some users reported that they were unable to accept invitations to become secondary admins on campaigns. Usually this was because the user was logged into another account whose email address didn't match the email address that the invitation was sent to. We still require these email addresses to match, but we've now implemented better error messaging to ensure that people know what's happening.
  
  
• Effort and Landing Page descriptions allow html, but html tags were being shown when the Effort/Landing Page's landing page (a.k.a. the map page) was shared on social media. The html is now escaped in social shares.
  
  
• Admins can now move petitions into Efforts (previously it was only possible to move a petition into a Landing Page). In order to move a petition into an Effort, the petition must first have an associated decision maker. The petition can also not have a decision maker that is already included in the effort, nor can the petition already be associated with another Effort or Landing Page. Once those requirements have been met, admins can move the petition into the Effort from the Effort's admin > Decision Makers and Petitions > Petitions >  Move Petition Into Effort.  Admins can also move petitions into an Effort from the petition's admin page > Details tab > Associations section.
  
  
• When interacting with a petition's association section, the modals were not visible if the admin had just added a decision maker to the petition. Instead, the admin had to reload the petition page before clicking the association modals. Now, there's no need to reload.
  
  
• On tablet scrolling down a petition page and then rapidly scrolling back up would sometimes lead to the petition signature form running into (and overlapping) part of the header. We've adjusted the code to make sure that doesn't happen anymore.
  
  
• Apostrophes in a petition's title would sometimes not be correctly escaped when displayed in the share by email modal. This led to visible html instead of apostrophes, but is now fixed.
• We've updated URL variables used in platform emails (e.g. {% petition_url %} in the Forward After Signing message) to use https by default. This won't change user experiences (because users would have been directed to the https version of your site anyway), but it may improve email deliverability.
  
  

Events

Updates / Bug Fixes

• When admins designate a new host of an event, the user receives an email thanking them for agreeing to be the host. However, that email was not being sent if the event in question was an unlaunched/draft event. We've fixed this issue.
  
  
• The event moderation dropdown is now translated.
  
  

Groups

Updates / Bug Fixes

• It is now possible for admins to archive groups that are no longer active. This will remove these groups from search results, and prevent users from seeing the group page. If a user navigates to the archived group's page, they'll be automatically redirected to the group collection's lookup page. Admins can also restore and reactivate groups if needed. †
  
  

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