• last updated 12 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Applied patch #239

Applied patch #251

Applied patch #255

Comment: mention __adp_properties as well

avoid error from richtext::get_property proc when contents is empty

adding the template::form::get_elements proc that returns the element names of a form

bug fix for bug #791, added __ prefix to local vars to mimize clobbering

Changed the <trn> tag to use new acs-lang API

Clarified documentation on actions and display_buttons switch to form::create. display_buttons is deprecated

Fixed missing HTML quoting of display value for richtexts bug

Merged 4.6.4d1 (unreleased) to HEAD. This marks the end of the life of the oacs-4-6 branch.

  1. … 808 more files in changeset.
Added comment about a @foo;noquote@ breaking <if> tags

Added API to set errors on form elements

Added comment, because both Jun and I were confused.

applied patch 261, to allow access to variables in -pass_properties. applied patch 249, renames level to __level so the multirow with level name element will not conflict

making all written and read files of the templating system (adp and tcl files) be in the charset of the AOLserver OutputCharset parameter

Added -orderby_name switch to let you specify a name for the orderby filter for your list

Typo in spelling of checkbox_name in the API doc.

Properly quoting values in CSV file

Added -html switch to list builder to let you add HTML attributes to the TABLE tag

  1. … 1 more file in changeset.
Added documentation for the -orderby switch to template::list::orderby_clause

Use template named foo.locale.adp over foo.adp if it exists (e.g. index.da_DK.adp)

- Added @see line for template::util::richtext.

What I'm wondering is why did Lars put it in template::util::richtext

instead of template::widget::richtext, and if it doesn't show up

in template::widget, how does it find it?

Another chapter of "OpenACS Secrets Revealed".

- Merged changes from oacs-4-6 into HEAD.

- Added documentation to the -validate switch of template:::element::create

noting that the special variable $value is what should be used.

Clear the formerror array first, otherwise there are conflicts with multiple forms on one page

1. Added documentation for where_clause and where_clause_eval

2. Added support for DefaultListFilterStyle parameter

Added switch -key to template::list::page_where_clause

Added page_flush_p switch

Removed TODO that's done