Also already accepted/rejected/never started authorizations for registration should...

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

diff --git a/templates/xml/admin/admin_list_point_accounts.xml b/templates/xml/admin/admin_list_point_accounts.xml
index 7a5cfe18e118127c8b5288525077da620c2cfcaa..76f28c63d0f0ef3ed6b0c00194c57e9305a5bec4 100644 (file)
--- a/templates/xml/admin/admin_list_point_accounts.xml
+++ b/templates/xml/admin/admin_list_point_accounts.xml
@@ -5,7 +5,7 @@ This template provides meta data for listing points accounts
 @author                Roland Haeder <webmaster@mxchange.org>
 @version       0.2.1-FINAL
 @copyright     (c) 2003 - 2009 by Roland Haeder
-@copyright     (c) 2009 - 2012 by Mailer Developer Team
+@copyright     (c) 2009 - 2015 by Mailer Developer Team
 @license       GNU GPL 2.0 or any newer version
 @link          http://mxchange.org
 
@@ -28,9 +28,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
@@ -94,4 +94,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>