Skip to content
Snippets Groups Projects
Commit f3488c54 authored by K. Clair's avatar K. Clair
Browse files

better patch file for do not make renamed lists have status pending

parent 0f682568
Branches
Tags
No related merge requests found
diff --git a/sympa-6.1.3-src/src/etc/scenari/rename_list.owner b/sympa-6.1.3-src/src/etc/scenari/rename_list.owner diff --git a/sympa-6.1.3-src/src/etc/scenari/rename_list.owner b/sympa-6.1.3-src/src/etc/scenari/rename_list.owner
new file mode 100644 deleted file mode 100644
index 0000000..d155639 index d155639..0000000
--- /dev/null --- a/sympa-6.1.3-src/src/etc/scenari/rename_list.owner
+++ b/sympa-6.1.3-src/src/etc/scenari/rename_list.owner +++ /dev/null
@@ -0,0 +1,4 @@ @@ -1,4 +0,0 @@
+title.gettext restricted to list owner -title.gettext restricted to list owner
+ -
+is_owner([sender]) md5,smime -> do_it -is_owner([sender]) md5,smime -> do_it
+true() smtp,md5,smime -> reject(reason='rename_list_listmaster') -true() smtp,md5,smime -> reject(reason='rename_list_listmaster')
diff --git a/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in b/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in diff --git a/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in b/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in
index 2ca5bab..4c3d066 100644 index e9f3853..e51c2ac 100644
--- a/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in --- a/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in
+++ b/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in +++ b/sympa-6.1.3-src/wwsympa/wwsympa.fcgi.in
@@ -10134,7 +10134,9 @@ sub _restrict_values { @@ -10134,9 +10134,7 @@ sub _restrict_values {
sub do_rename_list_request { sub do_rename_list_request {
&wwslog('info', 'do_rename_list_request()'); &wwslog('info', 'do_rename_list_request()');
- my $result = &Scenario::request_action ('create_list',$param->{'auth_method'},$robot, - # riseup allows uses to rename their lists even though our list creation is moderated
+ # riseup allows uses to rename their lists even though our list creation is moderated - # the rename_list scenario just requires that the user is the list owner
+ # the rename_list scenario just requires that the user is the list owner - my $result = &Scenario::request_action ('rename_list',$param->{'auth_method'},$robot,
+ my $result = &Scenario::request_action ('rename_list',$param->{'auth_method'},$robot, + my $result = &Scenario::request_action ('create_list',$param->{'auth_method'},$robot,
{'sender' => $param->{'user'}{'email'}, {'sender' => $param->{'user'}{'email'},
'remote_host' => $param->{'remote_host'}, 'remote_host' => $param->{'remote_host'},
'remote_addr' => $param->{'remote_addr'}}); 'remote_addr' => $param->{'remote_addr'}});
@@ -10251,9 +10249,9 @@ sub do_rename_list {
}
# set list status to pending if creation list is moderated
- if ($param->{'status'} eq 'pending') {
- &report::notice_report_web('pending_list',{},$param->{'action'},$list);
- }
+# if ($param->{'status'} eq 'pending') {
+# &report::notice_report_web('pending_list',{},$param->{'action'},$list);
+# }
if ($in{'new_robot'} eq '$robot') {
$param->{'redirect_to'} = "$param->{'base_url'}$param->{'path_cgi'}/admin/$in{'new_listname'}";
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment