This project is mirrored from Pull mirroring updated .
  1. 11 Oct, 2019 1 commit
  2. 11 Sep, 2019 1 commit
  3. 02 Aug, 2019 1 commit
  4. 26 Jul, 2019 1 commit
  5. 02 Jul, 2019 1 commit
  6. 28 Jun, 2019 1 commit
  7. 26 Jun, 2019 1 commit
  8. 24 Jun, 2019 1 commit
  9. 24 May, 2019 1 commit
  10. 16 May, 2019 1 commit
    • seblgr's avatar
      Prevent unnecessary DB access in add_list_member · 5c3b724e
      seblgr authored
      In add_list_member the value $current_list_members_count is discarded if max_list_member == 0 (default setting).
      This prevents the "high db load" produced by the successive DB accesses.
  11. 26 Apr, 2019 1 commit
  12. 03 Apr, 2019 1 commit
    • VERDIN David's avatar
      When changing a list's admin two times in the same second, the list admins... · 3f39f564
      VERDIN David authored
      When changing a list's admin two times in the same second, the list admins cache is not updated. Consequently, when trying to add a third admin in the same second, the second one is not in the cache at the time.
      Obviously it does not sound like a recurrent scenario and I met this problem when running a test file only.
      However, it is possible that this happens more often when trying to make batch modifications in the shell. And also, it made my test fail which is an engineering problem: it could be misguiding about the cause of a test failure.
      So I changed the expiration test, replacing "<" by "<=" and it solves the problem.
      I don't see any side problem that could result from this change bu I commit it separately anyway because the cache is very sensitive.
  13. 08 Mar, 2019 1 commit
  14. 03 Mar, 2019 2 commits
  15. 24 Feb, 2019 1 commit
  16. 08 Feb, 2019 1 commit
  17. 07 Feb, 2019 1 commit
  18. 04 Feb, 2019 1 commit
  19. 03 Feb, 2019 9 commits
    • IKEDA Soji's avatar
      rebase & fixup · d5b31fec
      IKEDA Soji authored
    • IKEDA Soji's avatar
      Update version numbers. · e67fbc06
      IKEDA Soji authored
    • IKEDA Soji's avatar
      [-change] Database schema: inclusion_ext_* fields in subscriber_table and... · 9fc38317
      IKEDA Soji authored
      [-change] Database schema: inclusion_ext_* fields in subscriber_table and admin_table to give the last time of inclusion from external data sources.
      "External" means that it is not include_sympa_list or not including list on local domain.
      Note that if inclusion_ext_* field is updated, inclusion_* field must be updated at the same time.
      Known bug:
        - If data source is a list included from the other external data source(s), it will be treated as non-external and move_user request on corresponding users will be allowed.
    • IKEDA Soji's avatar
      [change] Data sources: outdated users will be expired only when all data... · ae01bc36
      IKEDA Soji authored
      [change] Data sources: outdated users will be expired only when all data sources of the list has succeeded inclusion.
      By this change, if there are data sources with nosync_time_ranges set, deletion of outdated users can be delayed 24 hours at most.
      [change] Database schema: included_* and include_sources_* in subscriber_table and admin_table were deprecated.  inclusion_* fields will be used instead.
    • IKEDA Soji's avatar
      Switch to new code. · 95b40ab3
      IKEDA Soji authored
    • IKEDA Soji's avatar
      Refactoring (mostly rewritten). Introducing new classes... · c1b7e324
      IKEDA Soji authored
      Refactoring (mostly rewritten). Introducing new classes Sympa::Request::Handler::include, Sympa::DataSource and its subclasses. Sympa::Datasource was deprecated.
      And some fixes:
        * [bug] Now include_remote_file, include_sympa_list and include_remote_sympa_list paragraphs may have nosync_time_ranges subparameter.  No reason they don't have it.  include_file stil doesn't have it.
        * [-feature] include_voot_group has not been implemented, and it was invalidated.
        * [bug] include_ldap_query and include_ldap_ca data sources did not implement "regex" option of "selection" subparameter.  Now they support it.
        * [bug] LDAP multiple values in custom attribute with include_ldap_ca was broken.
        * [-feature] include_sql_query and include_sql_ca stores inclusion data in temporary file so that big data sources will be handled safely.
      Tentative change:
        * include_ldap_query, include_ldap_2level and include_sql_query won't clear (overwrite) gecos if retrieved value was empty or undefined.  Now they clear (overwrite) gecos in such cases.
    • IKEDA Soji's avatar
    • IKEDA Soji's avatar
      Copyedit: Suppress unused or redundant codes. · 099c8b66
      IKEDA Soji authored
    • IKEDA Soji's avatar
      Fix inconsistencies on parameter names. · 5539e755
      IKEDA Soji authored
  20. 29 Jan, 2019 1 commit
  21. 28 Jan, 2019 1 commit
  22. 25 Jan, 2019 1 commit
  23. 18 Jan, 2019 1 commit
  24. 15 Jan, 2019 1 commit
    • IKEDA Soji's avatar
      [bug] WWSympa: On list config page, default settings of list scenarios are... · c0ea8d06
      IKEDA Soji authored
      [bug] WWSympa: On list config page, default settings of list scenarios are ignored.  And if user updated configuration, the first option in select box is saved.
      Fixed by assigning defaults in Sympa::ListDef.
      [change] The feature making symbolic link "*.default" to assign default values are deprecated.
  25. 14 Jan, 2019 1 commit
  26. 10 Jan, 2019 1 commit
  27. 04 Jan, 2019 1 commit
    • IKEDA Soji's avatar
      Inconsistent location of messge footer/header files #507 · 4bca7ac9
      IKEDA Soji authored
        - Message footer/header files of domain/site default are put in `mail_tt2` subdirectories while those of list config are not.
          Fixed by put all of them in consistent location without intermediate directories (See also Notes below).
        - Entries for header/footer files in `edit_list.conf` were ignored.
        - File names themselves of header/footer were changed:
          `message_header`, `message_header.mime` etc.
          This is due to concideration about conflict between files and directories with domain names (See also Notes below).
        - Header/footer files with `.mime` extension:
          Previously, files with this extension were always preferred, then files without extension were used.  This behavior has not been documented.
          Now files with extension will be searched only in case `footer_type` is `mime`.  Files without extension will be searched in both cases.
        - Files with older names/paths in list/domain/site config directories will be copied to new location during upgrading process.
        - Template files with old names in families (`message.header.tt2` etc.) will be used as before and will be copied to new location during instantiation. If files with new names (`message_header.tt2` etc.) will be preferred, if they will be added.
      Known bug:
        - There are no web UI to edit global footer (`message_global_footer`).
  28. 03 Jan, 2019 1 commit
  29. 08 Dec, 2018 1 commit
  30. 01 Dec, 2018 1 commit
  31. 25 Nov, 2018 1 commit