Our Weeks Through 2017-11-10

It's been a while, but here's a rundown of what has happened since our last release note. We'll try to be better about posting these regularly.

Platform

Updates / Bug Fixes

Users with full accounts are now able to export a machine-readable log of their activities on the platform. To view this export, log into your account, go to your My Account page, and click the "Download a JSON file of all your platform activity" button (which is right above the line break). Please note that this feature is part of our GDPR compliance preparation. †

Admins can generate a machine-readable log of an user's activities on the platform. To export this log, go to the org admin homepage > People > search for the user's email address and go to their member page > Activity > "Download a JSON file of this member's platform activity" button. Please note that this feature is part of our GDPR compliance preparation. †

Petitions

Updates / Bug Fixes

When global unsubscribes were enabled, users who had created petitions were unable to unsubscribe from all platform communications (because petition creators cannot unsubscribe from their own petitions). We've updated the code so that these users are able to unsubscribe from everything except their own petitions.

When overriding default post-signing behavior at the individual petition level, the Share, Donate, Promoted Petition daisy chain did not allow admins to customize the donation modal. This has been fixed.

Petition categories are now included in the full and incremental CSV exports. These CSV exports are optional and can be used in conjunction with our webhook features.

Previously, partnership information was included in our database as "groups." Given that we have an actual groups feature, we decided to update the name for partnerships to...you guessed it, "partnerships". For many organizations, this will have no visible effect. However, if your organization is using webhooks to process unsubscribe data, the unsubscribable_type field will now show "PartnershipSubscription" rather than "GroupSubscription" when the member unsubscribes from a partnership.

The option to move a petition into a Landing Page was previously included in a block of links that allowed admins to export petition information, view a leaderboard, etc. Because this block's visibility required petitions to be present, it was not possible to move a petition into a newly-created (and petition-less) landing page. The "Move Petition Into Landing Page Hub" option is now visible at all times.

Within efforts, admins are now able to provide translations for nearly all of the effort wrapping content, which includes things like: the how this works text, training text, petition form, etc.

Change.org has removed the API we used to update petition signature count totals. Therefore, we've removed that functionality from the petition admin settings page.

We've added a new team permission, 'petition:Export signatures with minimal data'. This permission allows team members to download a CSV of petition signers that only includes: First Name, Last Name, Phone Number, Postcode, Comment, and ID number.

Donations are now tagged with the source code "daisy-chain" or "donation-page" depending on if the donation came from the after-signing donation modal pop-up or a petition's donation page.

A petition's donation tab would not load if a donation had been made by a since-deleted member. The tab will now work normally.

A petition's donation tab now shows stats, including: total donations by source, number of donations by source, and average donation by source.

Events

Updates / Bug Fixes

As part of our updated event page, the event's image is used when the event is shared on social media.

In addition to the public view of events, we've also updated the event host's manage tools. The new design matches the petition management tools – making it a more coherent experience. †

When event hosts cancelled an event, it was possible for them to trigger the event cancellation email multiple times. We now ensure that attendees are only notified once.

For partner events, if the partnership was configured to show an opt-in checkbox, the checkbox was out of alignment with the rest of the RSVP form. We've now fixed the margin.

After creating an event, the user is now prompted to immediately share the event on social media and by email. The sharing prompt matches the "just launched" view for petitions. †

The thank you for RSVPing to / creating an event emails have been updated to prominently feature the share ask, and they now include links to add the event to Google Calendar, iCal, or another calendar service.†

When sharing is disabled for an event, we no longer include the sharing ask in thank you emails.

The buttons on the page where a petition creator is prompted to invite their signers to an event (or a group organizer is prompted to invite other group members) have been updated to match the other buttons in the platform. †

Event hosts are able to switch the RSVP status of attendees. †

On mobile, event cohosts are no longer shown the button to skip to the RSVP form.

Groups

Updates / Bug Fixes

The groups feature has been updated to use "groups" in the URL, not "local chapters".

When attempting to create a new group, submitting an incomplete form led to an error page instead of a '"can't be blank" error message.

In local groups, the option to Hide Local Group Creation did not actually hide local group creation. Now, when checked, users will not be able to create new groups. When a user searches for a location without a local group, they'll see a message informing them that there is no group in that location and asking them if they'd like to go back to the group collection's lookup page. †

TakeCharge

Updates / Bug Fixes

Donations are now tagged with the source code "daisy-chain" or "donation-page" depending on if the donation came from the after-signing donation modal pop-up or a petition's donation page.