]> git.mxchange.org Git - mailer.git/blob - templates/xml/admin/admin_delete_show_forced_ads.xml
mailer project continued:
[mailer.git] / templates / xml / admin / admin_delete_show_forced_ads.xml
1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!--
3 This template provides meta data for deleting forced ads.
4
5 @author         Roland Haeder <webmaster@mxchange.org>
6 @version        0.2.1-FINAL
7 @copyright      (c) 2003 - 2009 by Roland Haeder
8 @copyright      (c) 2009 - 2012 by Mailer Developer Team
9 @license        GNU GPL 2.0 or any newer version
10 @link           http://mxchange.org
11
12 This program is free software; you can redistribute it and/or modify
13 it under the terms of the GNU General Public License as published by
14 the Free Software Foundation; either version 2 of the License, or
15 (at your option) any later version.
16
17 This program is distributed in the hope that it will be useful,
18 but WITHOUT ANY WARRANTY; without even the implied warranty of
19 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
20 GNU General Public License for more details.
21
22 You should have received a copy of the GNU General Public License
23 along with this program; if not, write to the Free Software
24 Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
25 MA  02110-1301  USA
26 //-->
27 <admin-entry-meta-data>
28         <!--
29         Call-back function which should all following parameter handled over
30         to. This will always be type of string but we like homogene XMLs.
31         //-->
32         <callback-function type="string" value="adminDeleteEntriesConfirm" />
33         <!--
34         Name of the database table where the entries should be read/write from/to.
35         //-->
36         <database-table name="" type="string" value="forced_ads" />
37         <!--
38         The following three lists must have the same count of list entries, else an
39         error may occur.
40         //-->
41         <!--
42         And all column names to read/write, leave this list tag empty for all (*).
43         //-->
44         <database-column-list>
45                 <!--
46                 A column name list entry. The type is always string, or do you have
47                 numerical column names?
48                 //-->
49                 <database-column-list-entry name="" type="string" table="" value="forced_ads_id" alias="" function="" />
50                 <database-column-list-entry name="" type="string" table="" value="forced_ads_userid" alias="" function="" />
51                 <database-column-list-entry name="added_list" type="string" table="" value="forced_ads_added" alias="forced_ads_added" function="UNIX_TIMESTAMP" />
52                 <database-column-list-entry name="" type="string" table="" value="forced_ads_ad_url" alias="" function="" />
53                 <database-column-list-entry name="" type="string" table="" value="forced_ads_click_url" alias="" function="" />
54                 <database-column-list-entry name="" type="string" table="" value="forced_ads_width" alias="" function="" />
55                 <database-column-list-entry name="" type="string" table="" value="forced_ads_height" alias="" function="" />
56                 <database-column-list-entry name="" type="string" table="" value="forced_ads_alt_text" alias="" function="" />
57                 <database-column-list-entry name="" type="string" table="" value="forced_ads_framebreaker" alias="" function="" />
58                 <database-column-list-entry name="" type="string" table="" value="forced_ads_type" alias="" function="" />
59                 <database-column-list-entry name="" type="string" table="" value="forced_ads_views_counter" alias="" function="" />
60                 <database-column-list-entry name="" type="string" table="" value="forced_ads_clicks_counter" alias="" function="" />
61         </database-column-list>
62         <!--
63         "Filter" call-back functions to call back for piping the fetched data
64         through (can be left empty, no call-back function will be called)
65         //-->
66         <callback-function-list>
67                 <!--
68                 A call-back function list entry
69                 //-->
70                 <callback-function-list-entry name="" type="string" value="bigintval" />
71                 <callback-function-list-entry name="added_list" type="string" value="generateDateTime" />
72         </callback-function-list>
73         <!--
74         Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
75         is provided, we have more than two parameters to handle over to the
76         call-back function. See function handleExtraValues() for details.
77         //-->
78         <extra-parameter-list>
79                 <!--
80                 A one-dimensional array with some entries
81                 //-->
82                 <extra-parameter-list-entry name="" type="array" value="added">
83                         <!--
84                         Our 'added' array
85                         //-->
86                         <extra-parameter-added-list>
87                                 <!--
88                                 A bool entry in the 'bar' array, all other types are added in a
89                                 similar way.
90                                 //-->
91                                 <extra-parameter-added-list-entry name="" type="int" value="2" />
92                         </extra-parameter-added-list>
93                 </extra-parameter-list-entry>
94         </extra-parameter-list>
95         <!--
96         Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
97         //-->
98         <enable-modify-entries name="" type="bool" value="false" />
99         <!--
100         The table column which should be taken for the ids (see first parameter).
101         This' type can again only be 'string' (remember why?).
102         //-->
103         <table-id-column name="" type="string" value="forced_ads_id" />
104         <!--
105         The table column which should be taken for user ids
106         This' type can again only be 'string' (remember why?).
107         //-->
108         <table-userid-column name="" type="string" value="forced_ads_userid" />
109         <!--
110         Raw userid column ($key) to skip which is always an invalid (?) entry
111         This' type can again only be 'string' (remember why?).
112         //-->
113         <raw-userid-column-key name="" type="string" value="forced_ads_userid" />
114 </admin-entry-meta-data>