• last updated 33 mins ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
add application_data_links::get_links_to proc (there was only get_links_from)

- Fix for Tcl 8.5: OpenACS did overwrite the Tcl built-in command

"::apply" and broke therefore all scripts/libraries using it.

Changed the name of the OpenACS function to "ad_apply" and altered

the few occurances. The fix works as well with Tcl 8.4. The proper

fix for 8.5 would be to use instead of the function the expand

operator {*}

  1. … 3 more files in changeset.
- fix test files__tcl_file_common_errors

- report errors as such in aa-test (wrote warnings into error log, this was ignored since ages)

- fixed naming in acs-tcl, acs-mail-lite and acs-subsite

  1. … 4 more files in changeset.
Force references to an embedded package's admin or sitewide-admin pages to

be referenced (relative to the embedding package's mount point) as

admin/package-key or sitewide-admin/package-key. This nicely arranges

all admin URLs in a composite package under ${mount-point}/admin, which

among other things will cause the request processor to do the expected

permission check. Backdoor access to the admin pages via URLs like

${mount-point}/package-key/admin or ${mount-point}/package-key/sitewide-admin

is blocked, as the request processor won't do the expected permissions check

for URLs of that form.,

When using AOLserver 4.5 with a config file not containing values for maxthreads,

etc, the pools init code would choose default values that are illegal, causing

an error to show up in one's log file. I've set the default values to those

found in our /etc/config.tcl file.

Added my JSON utilities package. Included are procs to parse a JSON string

into a canonical Tcl list representation, to generate a JSON string from

such a representation (round-tripping works, i.e. JSON -> Tcl -> JSON),

pretty-print JSON strings, set/get attributes, create objects and arrays,

etc.

Removing duplicated -private switch.

Cleaned up APM handling of inherited parameters so that deletion of

a dependency works well now, the parameters page with the APM only shows

parameters specified in the package (rather than include inherited ones),

and the XML file is correclty written.

  1. … 6 more files in changeset.
1. nsv for package inheritance etc wasn't being set up when an admin

interactively created a new package using the APM UI. Changes for

5.6 for parameter inheritance caused that nsv to be referenced in this

case, while it wasn't for 5.5. This caused an error message in a couple

of instances.

2. Modified the package xml generator to only output parameters defined

for the package itself (rather than all, including inherited ones).

  1. … 1 more file in changeset.