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" />
+ <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" />
+ <post-data-identify-index name="" 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" />
+ <database-table name="" type="string" value="surfbar_urls" />
<!--
The following three lists must have the same count of list entries, else an
error may occur.
<!--
Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
//-->
- <enable-modify-entries type="bool" value="true" />
+ <enable-modify-entries name="" type="bool" value="true" />
<!--
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" />
+ <table-id-column name="" 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" />
+ <table-userid-column name="" 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" />
+ <raw-userid-column-key name="" type="string" value="url_userid" />
</admin-entry-meta-data>