This project is mirrored from https://github.com/sympa-community/sympa.git.
Pull mirroring updated .
- 29 Feb, 2020 1 commit
-
-
IKEDA Soji authored
-
- 16 Feb, 2020 1 commit
-
-
IKEDA Soji authored
-
- 12 Feb, 2020 1 commit
-
-
IKEDA Soji authored
Fixed by correcting query.
-
- 02 Feb, 2020 1 commit
-
-
IKEDA Soji authored
-
- 29 Jan, 2020 1 commit
-
-
IKEDA Soji authored
-
- 23 Nov, 2019 1 commit
-
-
Stefan Hornburg (Racke) authored
These log messages are not useful for normal debugging and are cluttering the logs unnecessarily.
-
- 11 Oct, 2019 1 commit
-
-
IKEDA Soji authored
-
- 11 Sep, 2019 1 commit
-
-
Stefan Hornburg (Racke) authored
-
- 02 Aug, 2019 1 commit
-
-
IKEDA Soji authored
-
- 26 Jul, 2019 1 commit
-
-
IKEDA Soji authored
-
- 02 Jul, 2019 1 commit
-
-
IKEDA Soji authored
-
- 28 Jun, 2019 1 commit
-
-
Luc Didry authored
-
- 26 Jun, 2019 1 commit
-
-
IKEDA Soji authored
-
- 24 Jun, 2019 1 commit
-
-
IKEDA Soji authored
[bug] mtime for cache file like .last_change.admin on some filesystems like NFS with Linux was not updated. Fixed by updating it explicitly with utime().
-
- 24 May, 2019 1 commit
-
-
Luc Didry authored
-
- 16 May, 2019 1 commit
-
-
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.
-
- 26 Apr, 2019 1 commit
-
-
Luc Didry authored
-
- 03 Apr, 2019 1 commit
-
-
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.
-
- 08 Mar, 2019 1 commit
-
-
IKEDA Soji authored
-
- 03 Mar, 2019 2 commits
-
-
IKEDA Soji authored
Replace Sympa::List::load_list_of_scenarios() with Sympa::Scenario::get_scenarios().
-
IKEDA Soji authored
This will fix several bugs due to confusion with function and parameter.
-
- 24 Feb, 2019 1 commit
-
-
IKEDA Soji authored
Administrators upgrading from earlier versions have to run upgrade_sympa_password.pl to decrypt and rehash older passwords.
-
- 08 Feb, 2019 1 commit
-
-
IKEDA Soji authored
-
- 07 Feb, 2019 1 commit
-
-
IKEDA Soji authored
A name of the source by which user was actually included will be stored in inclusion_label_* field of the table.
-
- 04 Feb, 2019 1 commit
-
-
Xavier Bachelot authored
-
- 03 Feb, 2019 9 commits
-
-
IKEDA Soji authored
-
IKEDA Soji authored
-
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 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 authored
-
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 authored
-
IKEDA Soji authored
-
IKEDA Soji authored
-
- 29 Jan, 2019 1 commit
-
-
IKEDA Soji authored
Fixed by typos not loading information soon.
-
- 28 Jan, 2019 1 commit
-
-
IKEDA Soji authored
[bug] If a list parameter had a value "default", default value (if defined) was used instead of the value itself. Fixed by removing a code replacing value "default". Exception is the case of scenarios: For compatibility, special value "default" will stand for default scenario name.
-
- 25 Jan, 2019 1 commit
-
-
Luc Didry authored
-
- 18 Jan, 2019 1 commit
-
-
IKEDA Soji authored
-
- 15 Jan, 2019 1 commit
-
-
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.
-
- 14 Jan, 2019 1 commit
-
-
IKEDA Soji authored
-