Go to the first, previous, next, last section, table of contents.
In many templates there are template parts (see the introduction at the beginning of this chapter) used to display a list of records from the database. All of them (with the notable exception of the query by example search result, See section sqledit_search.html.) use the same library and comply to the following part description for their display.
table,
then the part used to display the search results will be row.
Otherwise the part used will be entry.
... <table> <!-- params 'style' => 'table', 'columns' => 2 --> <!-- start row --> <tr> <!-- start entry --> <td> <a href='_URL_'>_NAME_</a> (_COUNT_) </td> <!-- end entry --> </tr> <!-- end row --> </table> ...
... <ul> <!-- start entry --> <li> <a href='_URL_'>_NAME_</a> (_COUNT_) <!-- end entry --> </ul> ...
... <ul> <!-- start entry --> <!-- start company --> <li> _COMPANY-NAME_ _COMPANY_URL_ <!-- end company --> <!-- start customer --> <li> _CUSTOMER-NAME_ _CUSTOMER-ACTIVITY_ <!-- end customer --> <!-- end entry --> </ul> ...This subdivision is always an alternative, that is, either the company part or the customer part will be displayed, never both. This is mainly used to specify a part that many contain records from different tables so that they are displayed in a specific way. The exact semantic associated with these subparts is defined by the cgi-bin.
_DEFAULTROW_ was not found in the
template, See section Database table tags.
Go to the first, previous, next, last section, table of contents.