1 <?xml version="1.0" encoding="UTF-8" ?>
3 This is an admin XML template for all other XML templates which provides meta
4 data for editing/deleting/changing database entries. If you want to write your
5 own templates, please keep this header except *this* description and the author
8 @author Roland Haeder <webmaster@mxchange.org>
10 @copyright (c) 2003 - 2009 by Roland Haeder
11 @copyright (c) 2009 - 2011 by Mailer Developer Team
12 @license GNU GPL 2.0 or any newer version
13 @link http://www.mxchange.org
15 This program is free software; you can redistribute it and/or modify
16 it under the terms of the GNU General Public License as published by
17 the Free Software Foundation; either version 2 of the License, or
18 (at your option) any later version.
20 This program is distributed in the hope that it will be useful,
21 but WITHOUT ANY WARRANTY; without even the implied warranty of
22 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
23 GNU General Public License for more details.
25 You should have received a copy of the GNU General Public License
26 along with this program; if not, write to the Free Software
27 Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
30 <admin-entry-meta-data>
32 Call-back function which should all following parameter handled over
33 to. This will always be type of string but we like homogene XMLs.
34 Keep 'name' empty for numerical array indexes (array keys).
36 <callback-function type="string" value="adminFooEntriesBar" />
38 Name of the database table where the entries should be read/write from/to.
40 <database-table name="" type="string" value="table_name" />
42 The following three lists must have the same count of list entries, else an
46 And all column names to read/write, leave this list tag empty for all (*).
48 <database-column-list>
50 A column name list entry. The type is always string, or do you have
51 numerical column names?
53 <database-column-list-entry name="" type="string" value="foo" />
54 </database-column-list>
56 "Filter" call-back functions to call back for piping the fetched data
57 through (can be left empty, no call-back function will be called)
59 <callback-function-list>
61 A call-back function list entry
63 <callback-function-list-entry name="" type="string" value="someFooCallback" />
64 </callback-function-list>
66 Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
67 is provided, we have more than two parameters to handle over to the
68 call-back function. See function handleExtraValues() for details.
70 <extra-parameter-list>
72 A list entry for a single extra parameter. 'type' can now be: string,
73 int, float, bool, array. If the type 'array' is provided, the parser
74 searches for a tag called "extra-parameter-<value>-list(-entry)", by
75 <value> is the value from the 'value' attribute. Please check out the
76 examples below. In addition to that you need to maintain <value>_list
77 in all corresponding elements, see admin_edit_show_surfbar_urls.xml for
81 A simple string example with a numerical index, int and float are similar.
83 <extra-parameter-list-entry name="" type="string" value="foo" />
85 A simple bool example with a numerical index, value can only be 'false' or 'true'
87 <extra-parameter-list-entry name="" type="bool" value="false" />
89 A one-dimensional array with a numerical index and with some entries
91 <extra-parameter-list-entry name="" type="array" value="bar">
95 <extra-parameter-bar-list>
97 A bool entry with a numerical index in the 'bar' array, all
98 other types are added in a similar way.
100 <extra-parameter-bar-list-entry name="" type="bool" value="true" />
102 A float entry with a alpha-numerical index in the 'bar' array.
104 <extra-parameter-bar-list-entry name="my_key" type="float" value="1.2345" />
105 </extra-parameter-bar-list>
106 </extra-parameter-list-entry>
107 </extra-parameter-list>
109 Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
111 <enable-modify-entries name="" type="bool" value="false" />
113 The table column which should be taken for the ids (see first parameter).
114 This' type can again only be 'string' (remember why?).
116 <table-id-column name="" type="string" value="id" />
118 The table column which should be taken for user ids
119 This' type can again only be 'string' (remember why?).
121 <table-userid-column name="" type="string" value="userid" />
123 Raw userid column ($key) to skip which is always an invalid (?) entry
124 This' type can again only be 'string' (remember why?).
126 <raw-userid-column-key name="" type="string" value="userid" />
127 </admin-entry-meta-data>