On 10/23/20 11:19 AM, Mark Sapiro wrote:
Here's a thought. For Affinity/Empathy at least, how about using Mailman core's user as the Affinity registered user. I.e., if someone's first interaction is to register with Affinity, have that registration create a core user to keep the Affinity registration data. This core user already accommodates a display_name and password and email address(es).
If the person already is a core user when registering for Affinity, just update the core user as needed, probably only a password reset or just setting it if it is currently None.
Then you don't have the issue of another, separate registration for Affinity.
This would be more difficult for Postorius/Hyperkitty because those users are Django users, but that isn't an issue for Affinity.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle.
I do want to apologize for my tone Mark. I was wrong in the way I communicated.
-- Brian Carpenter Harmonylists.com Emwd.com