+<?xml version="1.0" encoding="UTF-8" ?>
+<!--
+This template provides meta data for editing URLs of the surfbar in the admin
+area.
+
+@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
+@license GNU GPL 2.0 or any newer version
+@link http://www.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
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+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
+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
+//-->
+<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.
+ //-->
+ <admin-callback-function type="string" value="adminEditEntriesConfirm" />
+ <!--
+ Array index from HTTP POST data array for identifying every data row
+ //-->
+ <post-data-identify-index type="string" value="url_id" />
+ <!--
+ Name of the database table where the entries should be read/write from/to.
+ //-->
+ <database-table type="string" value="surfbar_urls" />
+ <!--
+ The following three lists must have the same count of list entries, else an
+ error may occur.
+ //-->
+ <!--
+ And all column names to read/write, leave this list tag empty for all (*).
+ //-->
+ <database-column-list>
+ <!--
+ A column name list entry. The type is always string, or do you have
+ numerical column names?
+ //-->
+ <database-column-list-entry type="string" value="url_id" />
+ <database-column-list-entry type="string" value="url_userid" />
+ <database-column-list-entry type="string" value="url" />
+ </database-column-list>
+ <!--
+ "Filter" call-back functions to call back for piping the fetched data
+ through (can be left empty, no call-back function will be called)
+ //-->
+ <callback-function-list>
+ <!--
+ A call-back function list entry
+ //-->
+ <callback-function-list-entry type="string" value="bigintval" />
+ <callback-function-list-entry type="string" value="addMemberSelectionBox" />
+ <callback-function-list-entry type="string" value="" /> <!-- No callback function! //-->
+ </callback-function-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>
+ <!--
+ A list entry for a single extra parameter. 'type' can now be: string,
+ 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.
+ //-->
+ <!--
+ A simple string example, int and float are similar.
+ //-->
+ <extra-parameter-list-entry type="string" value="" />
+ <!--
+ A one-dimensional array with some entries
+ //-->
+ <extra-parameter-list-entry type="array" value="member">
+ <!--
+ Our 'member' array
+ //-->
+ <extra-parameter-member-list>
+ <!--
+ A bool entry in the 'bar' array, all other types are added in a
+ similar way.
+ //-->
+ <extra-parameter-member-list-entry type="bool" value="false" />
+ <extra-parameter-member-list-entry type="bool" value="true" />
+ <extra-parameter-member-list-entry type="bool" value="true" />
+ <!--
+ The brackets [] are required for addMemberSelectionBox(),
+ please read there for details.
+ //-->
+ <extra-parameter-member-list-entry type="bool" value="url_userid[]" />
+ </extra-parameter-bar-list>
+ </extra-parameter-list-entry>
+ <!--
+ A simple string example, int and float are similar.
+ //-->
+ <extra-parameter-list-entry type="string" value="" />
+ </extra-parameter-list>
+ <!--
+ Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
+ //-->
+ <enable-modify-entries 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="url_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="url_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="url_userid" />
+</admin-entry-meta-data>