Mailer project rwritten:

[mailer.git] / templates / xml / admin / admin_list_surfbar_actions.xml

diff --git a/templates/xml/admin/admin_list_surfbar_actions.xml b/templates/xml/admin/admin_list_surfbar_actions.xml
index 9e5bd7615bfb7c679dba5e39d4623fe7589b7294..144d1529b552678817a7d9b8a0baf5591e68f63a 100644 (file)
--- a/templates/xml/admin/admin_list_surfbar_actions.xml
+++ b/templates/xml/admin/admin_list_surfbar_actions.xml
@@ -29,9 +29,9 @@ MA  02110-1301  USA
        <!--
        Call-back function, the extracted data from this XML will then be re-read
        from that function. The most common function this XML uses is
-       adminListEntries() so mostly you can leave this alone unless you have JOINs.
+       doGenericListEntries() so mostly you can leave this alone unless you have JOINs.
        //-->
-       <callback-function type="string" value="adminListEntries" />
+       <callback-function type="string" value="doGenericListEntries" />
        <!--
        Now we need information which template should be loaded and which functions
        shall be called back. So lets start with the main list template. This mostly
@@ -93,4 +93,15 @@ MA  02110-1301  USA
        //-->
        <column-callback-list>
        </column-callback-list>
+       <!--
+       Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
+       is provided, we have more than two parameters to handle over to the
+       call-back function. See function handleExtraValues() for details.
+       //-->
+       <extra-parameter-list>
+       </extra-parameter-list>
+       <!--
+       How the named column shall be logical linked to the above.
+       //-->
+       <where-condition type="string" name="" condition="" />
 </admin-list-data>