Naming suggestions for Menus and Tabs + minor text changes
| Project: | User mailman register |
| Version: | 6.x-1.3 |
| Component: | User interface |
| Category: | support request |
| Priority: | minor |
| Assigned: | anoopjohn |
| Status: | closed |
Jump to:
I have a few suggestions for the naming used for tabs, menus and fieldsets. If you are OK with this I can submit a patch that does these changes.
In the user profile page
-----------------------------
Tab:
Mailing Lists register -> Mailing Lists Subscriptions
Fieldset:
Mailing list subscriptions -> Mailing Lists Subscriptions
In Admin >> Site Configuration Menu
-------------------------------------------------
Menu:
Mailing Lists register -> User Mailman Register
In Admin >> Site Configuration Menu >> Mailing Lists register
--------------------------------------------------------------------------------
Page Title:
Mailing Lists register -> User Mailman Register
Comment:
If checked, user must subscribe at least to one mailing list. -> If checked, user must subscribe to at least one mailing list.
Comment:
If checked, mailing list subscription is displayed in the register new user form. You have also to grant can subscribe to ... to the anonymous user in the User Mailman Register permissions.
-> If checked, a "Mailing Lists Subscriptions" section will be displayed in the new user registration form. You will also have to grant "can subscribe to " for each applicable mailing list, to "anonymous user" in the User Mailman Register permissions, before the list shows up in this section.
Comment:
Retrieve the display name of mail address from Profile name fields. Multiple fields have to be comma separated. Optional.
-> Enter the name(s) of the profile field(s) from which to retrieve the display name for the user. You can enter multiple fields separated by commas; eg: profile_firstname, profile_lastname. Optional

#1
Absolutely yes, my english is provided by a country which is quite mind closed about languages integrations :-)
However i've to say that the 6.x.1 release probably will not be supported anymore because i'm working on the 6.x.2 release, so a patch for the last one is also appreciated.
#2
Suggestions applied in the incoming beta1 release with some modifications.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.