This project is mirrored from Pull mirroring updated .
  1. 02 Oct, 2012 1 commit
  2. 01 Oct, 2012 1 commit
  3. 28 Sep, 2012 2 commits
  4. 26 Sep, 2012 2 commits
  5. 21 Sep, 2012 1 commit
    • david.verdin's avatar
      [feature] Widely extended logs when the log_module parameter is activated with... · bf06d141
      david.verdin authored
      [feature] Widely extended logs when the log_module parameter is activated with the value 'scenario': all scenario results are evaluated.
      Remember that extended logs can be limited by the IP or the email of the user, using the 'log_condition' parameter.
      [*change] log_module and log_condition are now declared in sympa.conf instead of wwsympa.conf
      Remember these parameters syntax:
      log_module: can take the value "scenario"
      log condition: takes a character string as value. The form is "ip=<an.ip>,email=<an_email>". You can pu ip alone, email alone or both, with the comma-separated form.
      git-svn-id: 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce
  6. 20 Sep, 2012 4 commits
  7. 19 Sep, 2012 1 commit
  8. 14 Sep, 2012 1 commit
  9. 12 Sep, 2012 2 commits
    • etiennemeleard's avatar
      [feature] Enhancing the custom_action functionnality : · 1c728c49
      etiennemeleard authored
      Custom actions are used to run specific code and/or display user defined templates.
      They can be executed in list or global context (it is up to you to decide what to do in both cases).
      You can create a <your_action>.pm module under etc/custom_actions or etc/<robot>/custom_actions (<your_action>_plugin package) with a "process" sub to add custom processing.
      In list context you can also create it under expl(/<robot>)?/<list>/custom_actions.
      You can also create a <your_action>.tt2 file at the same place to display your template. You don't need the <head/> section or the <body/> tag.
      The HTML code in <your_action>.tt2 can make use of the parameters this way: [% cap.1 %] for param1, [% cap.2 %] for param, and so on.
      If the module is not defined the template is displayed.
      You can even have a robot-common <your_action>.pm module with a specific <your_action>.tt2 for each robot as the file (.pm or .tt2) is conducted in this order :
        - expl/<robot>/<list>/custom_actions (if list context and robot support)
        - expl/<list>/custom_actions (if list context and no robot support)
        - etc/<robot>/custom_actions (if robot support)
        - etc/custom_actions
      Your custom action is reachable using URL:
        - http://your-sympa-server-root-url/ca/your_action/param2/param2/param3/... in global context
        - http://your-sympa-server-root-url/lca/your_action/listname/param2/param2/param3/... in list context
      The module process sub receive @cap entries as arguments (the List object is prepended to the argument list in list context).
      The module process sub return value can be either :
      	1 to parse and display the custom action related tt2
      	<a global action name> to display its template
      	ca:<other_custom_action> to parse and display another custom action related tt2
      	a hash which entries will override $param ones, in case "custom_action" or "next_action" are present they act as described above.
      Example : (etc/custom_actions/
      package foo_plugin;
      sub process {
      	my $arg = shift;
      	return 'info' if(ref($arg) eq 'List'); # Show list info page if in list context
      	return 'ca:bar' if($arg eq 'bar'); # Show bar custom action tt2 if first arg is "bar"
      	return {name => 'John'} if($arg eq 'barbar'); # Show foo.tt2 (own tt2) after putting "John" under the key "name" in $param
      	return {name => 'John', next_action => 'review'} if($arg eq 'barbarbar'); # Same thing, but showing review page
      	return 1; # Just showing own tt2 (foo.tt2)
      git-svn-id: 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce
    • etiennemeleard's avatar
      [-change] Tidying the review page a bit. · 78c2e9c9
      etiennemeleard authored
      git-svn-id: 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce
  10. 11 Sep, 2012 9 commits
  11. 10 Sep, 2012 4 commits
  12. 07 Sep, 2012 1 commit
  13. 04 Sep, 2012 1 commit
  14. 30 Aug, 2012 3 commits
  15. 31 Jul, 2012 1 commit
  16. 30 Jul, 2012 4 commits
  17. 26 Jul, 2012 2 commits