templates/xml/admin/admin_edit_show_forced_campaigns.xml

   1 <?xml version="1.0" encoding="UTF-8" ?>
   2 <!--
   3 This template provides meta data for editing forced campaigns.
   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="adminEditEntriesConfirm" />
  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_campaigns" />
  37         <!--
  38         And all column names to read/write, leave this list tag empty for all (*).
  39         //-->
  40         <database-column-list>
  41                 <!--
  42                 A column name list entry. The type is always string, or do you have
  43                 numerical column names?
  44                 //-->
  45                 <database-column-list-entry name="" type="string" table="" value="forced_campaign_id" alias="" function="" />
  46                 <database-column-list-entry name="created_list" type="string" table="" value="forced_campaign_created" alias="forced_campaign_created" function="UNIX_TIMESTAMP" />
  47                 <database-column-list-entry name="" type="string" table="" value="forced_campaign_ordered_clicks" alias="" function="" />
  48                 <database-column-list-entry name="" type="string" table="" value="forced_campaign_payment_api" alias="" function="" />
  49                 <database-column-list-entry name="reload_list" type="string" table="" value="forced_campaign_reload_lock" alias="" function="" />
  50                 <database-column-list-entry name="" type="string" table="" value="forced_campaign_minimum_stay" alias="" function="" />
  51                 <database-column-list-entry name="" type="string" table="" value="forced_ads_id" alias="" function="" />
  52                 <database-column-list-entry name="member_list" type="string" table="" value="forced_campaign_userid" alias="" function="" />
  53                 <database-column-list-entry name="" type="string" table="" value="forced_costs_id" alias="" function="" />
  54         </database-column-list>
  55         <!--
  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)
  58         //-->
  59         <callback-function-list>
  60                 <!--
  61                 A call-back function list entry
  62                 //-->
  63                 <callback-function-list-entry name="" type="string" value="bigintval" />
  64                 <callback-function-list-entry name="created_list" type="string" value="generateDateTime" />
  65                 <callback-function-list-entry name="" type="string" value="bigintval" />
  66                 <callback-function-list-entry name="" type="string" value="bigintval" />
  67                 <callback-function-list-entry name="reload_list" type="string" value="createTimeSelections" />
  68                 <callback-function-list-entry name="" type="string" value="bigintval" />
  69                 <callback-function-list-entry name="" type="string" value="bigintval" />
  70                 <callback-function-list-entry name="member_list" type="string" value="doTemplateForcedCampaignUseridSelectionBox" />
  71         </callback-function-list>
  72         <!--
  73         Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
  74         is provided, we have more than two parameters to handle over to the
  75         call-back function. See function handleExtraValues() for details.
  76         //-->
  77         <extra-parameter-list>
  78                 <!--
  79                 A one-dimensional array with some entries
  80                 //-->
  81                 <extra-parameter-list-entry name="" type="array" value="reload">
  82                         <!--
  83                         Our 'reload' array
  84                         //-->
  85                         <extra-parameter-reload-list>
  86                                 <!--
  87                                 A bool entry in the 'reload' array, all other types are added in a
  88                                 similar way.
  89                                 //-->
  90                                 <extra-parameter-reload-list-entry name="" type="string" value="forced_campaign_reload_lock" />
  91                                 <extra-parameter-reload-list-entry name="" type="string" value="Dhms" />
  92                         </extra-parameter-reload-list>
  93                 </extra-parameter-list-entry>
  94                 <extra-parameter-list-entry name="" type="array" value="member">
  95                         <!--
  96                         Our 'member' array
  97                         //-->
  98                         <extra-parameter-member-list>
  99                                 <!--
 100                                 A bool entry in the 'member' array, all other types are added in a
 101                                 similar way.
 102                                 //-->
 103                                 <extra-parameter-member-list-entry name="" type="bool" value="false" />
 104                                 <extra-parameter-member-list-entry name="" type="bool" value="true" />
 105                                 <extra-parameter-member-list-entry name="" type="bool" value="true" />
 106                                 <!--
 107                                 The brackets [] are required for addMemberSelectionBox(),
 108                                 please read there for details.
 109                                 //-->
 110                                 <extra-parameter-member-list-entry name="" type="string" value="forced_campaign_userid[]" />
 111                         </extra-parameter-member-list>
 112                 </extra-parameter-list-entry>
 113                 <!--
 114                 A one-dimensional array with some entries
 115                 //-->
 116                 <extra-parameter-list-entry name="" type="array" value="created">
 117                         <!--
 118                         Our 'created' array
 119                         //-->
 120                         <extra-parameter-created-list>
 121                                 <!--
 122                                 A bool entry in the 'created' array, all other types are created in a
 123                                 similar way.
 124                                 //-->
 125                                 <extra-parameter-created-list-entry name="" type="int" value="2" />
 126                         </extra-parameter-created-list>
 127                 </extra-parameter-list-entry>
 128         </extra-parameter-list>
 129         <!--
 130         Columns for converting single time selections into a timestamp
 131         //-->
 132         <time-columns-list>
 133         </time-columns-list>
 134         <!--
 135         Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
 136         //-->
 137         <enable-modify-entries name="" type="bool" value="false" />
 138         <!--
 139         The table column which should be taken for the ids (see first parameter).
 140         This' type can again only be 'string' (remember why?).
 141         //-->
 142         <table-id-column name="" type="string" value="forced_campaign_id" />
 143         <!--
 144         The table column which should be taken for user ids
 145         This' type can again only be 'string' (remember why?).
 146         //-->
 147         <table-userid-column name="" type="string" value="forced_campaign_userid" />
 148         <!--
 149         Raw userid column ($key) to skip which is always an invalid (?) entry
 150         This' type can again only be 'string' (remember why?).
 151         //-->
 152         <raw-userid-column-key name="" type="string" value="forced_campaign_userid" />
 153         <!--
 154         Cache file to delete
 155         //-->
 156         <cache-file name="" type="string" value="" />
 157 </admin-entry-meta-data>