Missing feature: Adding/editing users

Bug #1058445 reported by Terri
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Postorius
Medium
Unassigned

Bug Description

There is currently no way to add or edit users from the web interface according to Florian's list of missing features. We should fix that!

Revision history for this message
George Chatzisofroniou (sophron) wrote :

Hello,

I have a few questions on this feature.

* I guess there should be a 'user index' with a list of all the stored users. But how should we treat the auto-registered users (those that are created when new members are added to a mailing list and don't have a display name)? Should they exist to that list?

* Where will the association of a user with its mail addresses take place? I think there should be an option to add or edit the associated addresses when registering or editing a user.

* Let's say a user has two addresses (<email address hidden> and <email address hidden>) in a Mailman environment. Which one of them should i use to create the URL for his detail page. It could be either '/<email address hidden>/' and '/<email address hidden>/'.

* I think all the actions about the users should lie under a 'Users' option on the main menu. If so, where can i request an icon similar to the other ones (Lists, Todos, Settings, Logout) for this entry?

* What's the difference with this feature: https://bugs.launchpad.net/postorius/+bug/1058446

Thanks in advance.

Revision history for this message
Terri (terriko) wrote :

1. The user index should contain all users, regardless of how they were added (it'll just be confusing otherwise and I can't think of any reason to divide up the subscribers)

2. That's actually all done within Mailman core, so take a look at how it's done there.

3. Again, check how Mailman core does it, but if I recall correctly we can search users by either email address and get the same person. I believe users have a canonical number and possibly a "primary" address you can use as an index.

4. Florian can probably help with this; I think he set up the original. I'd suggest that you set up a separate bug for it so it doesn't get buried in this larger bug.

5. They're probably duplicates and can be marked as such (I'll do this in a minute). I was cutting and pasting from Florian's email and probably just wasn't paying enough attention. We may eventually want to divide this bug up into several smaller pieces, but there's no obvious division there.

Revision history for this message
Terri (terriko) wrote :

Related bug https://bugs.launchpad.net/postorius/+bug/1062860 has a nice list of the old options:

"""
The options present in the Members list for the admin are restricted and do not look like those for Mailman 2.

1. Members are not hyperlinks to individual member settings page

2. Checkbox options not present:

unsub - unsubscribe
mod - posting of user will be moderated
hide - hide user from members list
nomail - delivery of messages to member disabled
ack - member gets acknowledgments of post
not metoo - member does not get copies of their own postings
nodupes - member does not get duplicates of other postings
digest - member gets messages in digest
plain - gets messages in plain text
language - lookup field for member's language

Revision history for this message
Florian Fuchs (flo-fuchs) wrote :

Hi there,

thanks to George we now have a form to add new users to the Mailman core, as well as a user list and a small detail page!

One thing, we need to accomplish now is to keep the user records in the core in sync with the ones in the postorius database (everytime someone connects via browserId, a new user record is created through django.contrib.auth. Those records are the ones that are relevant when logging into postorius).

Fortunately, I think it's not that complicated to do that. Django provides a hook on certain model actions, so it would be easy to "listen" to new contrib.auth users being created and create a new record in the core (if necessary). (There's already a small unfinished code snippet at the end of models.py.)

What do you guys think?

Revision history for this message
Terri (terriko) wrote :

Note to self: we probably will not keep mailman in sync with django users by default, florian's going to open a new bug for perhaps making syncing optional.

Changed in postorius:
status: Triaged → Fix Committed
Changed in postorius:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers