Preferences

[DeeTheDev]

Fixes #579

• Add backend ability for members to change messaging preferences, when authenticated or with an auth access token.
  • When authenticated, store preferences in the use, then expose options to frontend
  • When unauthenticated, member must have an access token in the URL params to make an API call for preferences subscriptions, API returns masked user fields along with preferences, then expose options to frontend
• Test

Frontend:

• Add Preferences component to be used with routes:
  • /preferences for authenticated members
  • /preferences-public for members that have been provided an access token (to allow preference changes)
• Localize all language

Admin:

• Add messaging preferences fields to MemberDetailsPage"

Webapp top navigation "preferences" tab

Preferences page

Preferences saved message (when member authenticated)

Preferences saved message (when member NOT authenticated)

Admin Messaging Preferences section

[rgalanakis]

I don't think this is ideal (should be like {preferences: {subscriptions: []}} but it's admin so easy to change later.

[rgalanakis]

@DeeTheDev as I mentioned elsewhere, we need to expose the 'public url' in admin (the one to /preferences-public with the auth token). This is important because it's what CS will give out if someone wants to unsubscribe.