Plus, since you are benefiting from my learning process, you probably won't take two hours to learn it!
# An HTML block for the breadcrumb trail
set context_bar [ad_context_bar]
set title "Organizations"
db_multirow orgs orgs_query { }
<master>
<property name="title">@title@</property>
<property name="context_bar">@context_bar@</property>
<if @orgs:rowcount@ gt 0>
<table cellpadding="3" cellspacing="0">
<tr>
<th>Action
<th>Name
<th>Notes
</if>
<multiple name="orgs">
<tr>
<td>
<a href="one?organization_id=@orgs.organization_id@">Details</a>
<if @write_p@>
<a href="add-edit?organization_id=@orgs.organization_id@">Edit</a>
</if>
<if @delete_p@>
<a href="delete?organization_id=@orgs.organization_id@">Delete</a>
</if>
</td>
<td>@orgs.name@</td>
<td>@orgs.notes@</td>
...
</tr>
</multiple>
<if @orgs:rowcount@ gt 0>
</table>
</if>
<if @create_p@>
<ul>
<li><a href="add-edit">Add an organization</a></p>
</ul>
</if>
template::list::create \
-name orgs \
-multirow orgs \
-key organization_id \
-elements {
organization_id {
}
name {
}
notes {
}
} \
-main_class {
narrow
}
db_multirow -extend { item_url } orgs orgs_query {
} {
set item_url [export_vars -base "one" {organization_id}]
}
<master> <property name="title">@title@</property> <property name="context_bar">@context_bar@</property> <listtemplate name="orgs"></listtemplate>
Too many positional parameters specified
while executing
"template::list::create__arg_parser"
(procedure "template::list::create" line 1)
invoked from within
"template::list::create \ "
("uplevel" body line 86)
invoked from within
This error means one of your arguments is being interpreted not as a named switch (-elements ...) but as a positional argument (no switch).This could easiliy be a line that doesn't have the \ at the end, or that has a space character after the \, or some other little typo like that.
Thanks, Lars!
it is not clear from the docs, and may not be obvious, but the -multirow switch lets developer point to a db_multirow statement. in other words, one MUST create a db_multirow statement with a name that matches -multrow switch of the list-builder. the db_multirow statement, in turn, points to an sql query in the corresponding .xql file
db_multirow -to add url columns, use extend with export_vars -to get row number, use rownum; also see rowcount (in docs for the "multiple" template tag)
for the default case, one must specify column name FOLLOWED by comma and sort order such as ASC or DESC
x y --- 1 3 1 4 2 5You may want the output to look like:
1 3 4 2 5or close to that, using an HTML table. Well, the <group> tag does that. Can we do that with list-builder?
Well, quite easily, it turns out.
Just put something like this in the definition of your column (preferably the last one):
last_name {
label "Who"
display_template {
<group column="item_id">@tasks.first_names@ @tasks.last_name@<br></group>
}
}
-main_class {
narrow
} \
-actions {
"Use process" "process-use" "Use a process"
"Task calendar" "my_url" "View task calendar"
} \
set actions [list "Use process" "process-use" "Use a process" "Task calendar" "my_url" "View task calendar"]
-actions $actions \
-multirow vs -page_query it is not immediately clear from the docs, and may not be obvious, but when using pagination, both switches are necessary. the purpose of the -page_query is to fetch the ENTIRE result set, whereas the sql statement used by multirow would fetch only the current page set.
caching with current paginator (not jon griffin's new paginator) use "-page_flush_p 1" to prevent paginator from caching the page set and confusing the hell out of you (when newly added records are suddenly not appearing on the page)
Caroline Meeks adds:- copy acs-templating/tcl-list-procs.tcl and acs-templating/resources/lists from CVS/HEAD to the appropriate locations in 4.6.3 distribution - 4.6.3 does not support the new "noquote" tag; any such tags can be safely removed from templates in versions of openacs prior to 5.0
- you have to use list-procs.tcl version 1.3. - Restart the server, don't just watch the files.
[ any information below that mentions pagination refers to old "broken"
paginator ]
- basically not possible with the current implementation of list-builder,
see http://openacs.org/forums/message-view?message_id=28810
- poor man's hierarchies: one can build db_multirow as a join that
would fetch parent and children records in the same query, and then
use <group column=group_key> tag to iterate over the records with
the same "key" until the key changes (see "group" template tag docs).
in this case, pagination is very hairy, especially with joins:
-> group "key" has to be same as the -page_query "key", where
"key" is the query column
-> if multirow query and page_query use the same joins, then the
page_where_clause will list the same "key" id multiple times:
for instance, project_id in ('455','455','466') - notice 455
appears twice. this causes fewer rows (than page_size) to be
displayed on a page. the solution is to change page_query -
use table aliasing 'spm_projects j', the same as in the
multirow query, but no joins. if we don't do table aliasing,
then the order by will break (order by j.project_id)
- pagination: add the aliased column name to -key: j.project_id - sorting: add the aliased column name to orderby statements in the orderby block - sorting by columns in more than one table (j.project_id p.proposal_id) breaks because both tables need to appear in the page_query, which in turn breaks # of records per page... i thought that wrapping the page_query select in a "select distinct" or select with a group by would yield, but both actually re-sort by the distinct or groupby column, so there is no way to preserve the sort order of the inner select statement... giving up for now until the new paginator is out which may make all of this a moot point.