• last updated 16 hours ago
Constraints: committers
Constraints: files
Constraints: dates
file db-error.adp was initially added on branch oacs-5-10.

Make this template more robust to the casual invocation from the outside

This should actually be moved to the lib directory, as it is intended as an include

Whitespace changes

Test ad_dimensional_sql

Test ad_dimensional

file dimensional-procs.tcl was initially added on branch oacs-5-10.

Make spelling consistent

Quote unallowed HTML according to acs-tcl.documentation__check_proc_doc

Rename proc according to convention enforced in acs-tcl: naming__proc_naming

Reinstate the notnull validation constraint where missing

    • -1
    • +1
    • -2
    • +2
    • -2
    • +2
  1. … 10 more files in changeset.
re-add notnull value constraint on message_id

This constraint was removed about 14 days ago. Without this constraint,

errors like the following will show up....

[30/Aug/2022:14:07:29.820625][3102633.7f152c28d700][-conn:openacs.org:default:0:196214-] Error: rp_handler no-script-abort: errorMsg can't read "message(forum_id)": no such variable while serving GE

T /forums/message-view?message_id HTTP/1.1

: ad_url </forums/message-view> maps to file </var/www/openacs.org/packages/forums/www/message-view.adp>


: can't read "message(forum_id)": no such variable

: while executing

: "forum::get -forum_id $message(forum_id) -array forum"

Probably, in many more cases, the incorrect removal of the notnull constrain performed by [1]

requires the same fix.

[1] https://github.com/openacs/forums/commit/c403e3134ce4e73ba94a80540a8b0f3cb1651ed0#diff-d35c736495ede0174fb39791ab660c5cd1a4ca467db2c4741cfc935167d7e5a8

    • -2
    • +2
handle clases, where "nt_load_end" is not provided

Replace message keys inside message keys. Many thanks to Monika Andergassen.

Harden page contract

Make script more robust to agents that won't specify the tmpfile via using the api to retrieve the file information

Fix typo

template::element validation reform: do not run custom user-defined validation on fields that are not formally correct

Rationale: user-defined validation often assumes some basic consistency of the submitted value. When this is not formally correct, users might have to reimplement the whole formal validation in their custom fields in order to prevent exceptions. By preventing their custom blocks from being executed, users can rely on their custom fields to be run only against sane values.

Restore formatting in procs doc

Normalize indentation according to editor hints

comment tags, which are NOT supported by HTML5, allow "abbr" in enhanced text

Fix query syntax

improve styling for Bootstrap 5

provide exception handler for cleanup

further improve recording, when just navigational timing is effective

Improved robustness

When not nt_con_st or nt_con_end is provided, set nt_tcp_time to 0

Reduce verbosity

Test template::util::list_to_lookup

Deprecate template::util::nvl

Deprecate template::util::list_to_array

Deprecate template::util::is_true, implemented as a simple string command oneliner since 2015 and inline occurrences

  1. … 19 more files in changeset.