It should be the set of topics names but defined as array of scalars.

POST parameter names are decoded into internal structure, e.g. "multiple.owner.0.gecos" to $new_admin->{'owner'}[0]{'gecos'}.  Inconsistent names may cause fatal error, e.g. by "multiple.owner.0.gecos.foo".  Fixed by passing over such errors.

riseup fixes to templates

with NAT, ISP dynamic hostnames, etc the requesting host means almost
nothing to the end user.

some subscribed users may not have interacted with sympa before,
possibly because they were added by a list admin. Make it more
clear so they know what's going on.

Late changes on svn repo from soji

[bug] If originator address in message contains upper-case letters, "tag this mail for deletion" in archive won't be shown.  Fixed by correcting mhonarc-ressouorces.tt2.  Rebuilding is needed to correct past archives.

[bug] wwsympa: Virtual robots in serveradmin/vhosts and rename_list_request pages were not shown correctly.

[bug][#11020] List admins changes not synchronized with admin_table

Bug description: For some lists we have noticed a synchronization issue with the admin_table: an owner gets added to the list config file (through list family instanciation) but never appears in the admin_table. As a consequence this new list owner is not listed in the list panel on the web interface and does not have the expected privileges.

After a bit of code analysis and debugging I found out that revision 9948 is the cause of the problem: https://sourcesup.renater.fr/scm/viewvc.php/branches/sympa-6.1-branch/src/lib/List.pm?root=sympa&r1=9947&r2=9948

It turns out that List::sync_include_admin() subroutine mights never been run for a list if that list includes members from an external datasource but owner/editors get defined "statically" in the config list. To be more precise:
* List::add_list_admin is called from List::sync_include_admin only
* List::sync_include_admin is called
* from List::new, unless a sync_include() has been ran recently
* from task_manager::sync_include, but only if the list defined editor_include or owner_include parameters

This bug has on impact on any list that includes members from an external datasource but has owner/editor defined inline in the list config file. In our situation most lists based on list families are impacted. For these lists, list owners/editors never get updated in the admin_table.

Revision 9948 should be fixed to check $list->{'last_sync_admin_user'} instead of $list->{'last_sync'}; attached is a patch proposal.

git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12973 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

[bug][#11014] [Comitted by M. Deranek] SQLite: While upgrading Sympa by "sympa.pl --upgrade", upgrading proceduce may fail complaining about non-existent indexes.  Fixed by skipping non-existing indexes and tables to be removed.


git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12972 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

[-bug][#11019][Confirmed by O. Salaün] (Injected by r12310) When bouncers_level*.notification in list config is "listmaster", task_manager.pl crashes due to typo.


git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12971 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

[bug][#11024] [Reported by S. Hornburg, LinuXia Systems] An "obsoleted" list parameter header_list is saved in list config as garbage.  Fixed by removing useless default value.


git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12970 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

[bug][#10969] [Reported by M. Perini, Università degli Studi di Perugia]  In "Listing messages to moderate" page, "Distribute" action fails with error "ERROR (distribute) - Missing argument id|idspam", if it is done in the dialog shown by clicking "View" button.  Fixed by not opening new dialog but transiting confirmation page to choose message topics.


git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12969 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

[bug][#10968] [Submitted by S. Hornburg] Visibility settings in topics.conf were ignored.  Fixed by cheking topics_visibility scenario along with subtopics.


git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12968 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce

git-svn-id: https://subversion.renater.fr/sympa/branches/sympa-6.2-branch@12967 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce