@author Roland Haeder <webmaster@mxchange.org>
@version 0.2.1-FINAL
@copyright (c) 2003 - 2009 by Roland Haeder
-@copyright (c) 2009 - 2011 by Mailer Developer Team
+@copyright (c) 2009 - 2016 by Mailer Developer Team
@license GNU GPL 2.0 or any newer version
-@link http://www.mxchange.org
+@link http://mxchange.org
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
-MA 02110-1301 USA
+MA 02110-1301 USA
//-->
<admin-entry-meta-data>
<!--
Call-back function which should all following parameter handled over
to. This will always be type of string but we like homogene XMLs.
+ Keep 'name' empty for numerical array indexes (array keys).
//-->
- <admin-callback-function type="string" value="adminFooEntriesBar" />
- <!--
- Array index from HTTP POST data array for identifying every data row
- //-->
- <post-data-identify-index type="string" value="id" />
+ <callback-function type="string" value="adminFooEntriesBar" />
<!--
Name of the database table where the entries should be read/write from/to.
//-->
- <database-table type="string" value="table_name" />
- <!--
- The following three lists must have the same count of list entries, else an
- error may occur.
- //-->
+ <database-table name="" type="string" value="table_name" />
<!--
And all column names to read/write, leave this list tag empty for all (*).
//-->
A column name list entry. The type is always string, or do you have
numerical column names?
//-->
- <database-column-list-entry type="string" value="foo" />
+ <database-column-list-entry name="" type="string" table="" value="foo" alias="" function="" />
</database-column-list>
<!--
"Filter" call-back functions to call back for piping the fetched data
<!--
A call-back function list entry
//-->
- <callback-function-list-entry type="string" value="someFooCallback" />
+ <callback-function-list-entry name="" type="string" value="someFooCallback" />
</callback-function-list>
<!--
Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
int, float, bool, array. If the type 'array' is provided, the parser
searches for a tag called "extra-parameter-<value>-list(-entry)", by
<value> is the value from the 'value' attribute. Please check out the
- examples below.
- Keep 'name' empty for numerical array indexes (array keys).
+ examples below. In addition to that you need to maintain <value>_list
+ in all corresponding elements, see admin_edit_show_surfbar_urls.xml for
+ an example.
//-->
<!--
A simple string example with a numerical index, int and float are similar.
<!--
Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
//-->
- <enable-modify-entries type="bool" value="false" />
+ <enable-modify-entries name="" type="bool" value="false" />
<!--
The table column which should be taken for the ids (see first parameter).
This' type can again only be 'string' (remember why?).
//-->
- <table-id-column type="string" value="id" />
+ <table-id-column name="" type="string" value="id" />
<!--
The table column which should be taken for user ids
This' type can again only be 'string' (remember why?).
//-->
- <table-userid-column type="string" value="userid" />
+ <table-userid-column name="" type="string" value="userid" />
<!--
Raw userid column ($key) to skip which is always an invalid (?) entry
This' type can again only be 'string' (remember why?).
//-->
- <raw-userid-column-key type="string" value="userid" />
+ <raw-userid-column-key name="" type="string" value="userid" />
+ <!--
+ Cache file to delete
+ //-->
+ <cache-file name="" type="string" value="some_foo" />
</admin-entry-meta-data>