• last updated 15 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
improve spelling

whitespace changes

added missing eval statement

provide a short hint how to allow swa always pasting

Whitespace changes

Disable RSS offering in file-storage if the RSS generation service is disabled in rss-support. Bump version numbers and fix dependencies, as the RssGenActiveP parameter is only available in latest rss-support.

Whitespace changes

    • -3
    • +3
    /openacs-4/packages/news/www/index.adp
    • -7
    • +7
    /openacs-4/packages/news/www/index.tcl
    • -13
    • +4
    /openacs-4/packages/news/www/admin/index.adp
    • -17
    • +17
    /openacs-4/packages/news/www/admin/index.tcl
Disable RSS offering in news and news-portlet if the RSS generation service is disabled in rss-support. Bump version numbers and fix dependencies, as the RssGenActiveP parameter is only available in latest rss-support.

    • -7
    • +7
    /openacs-4/packages/news/www/index.adp
    • -6
    • +11
    /openacs-4/packages/news/www/index.tcl
    • -4
    • +8
    /openacs-4/packages/news/www/admin/index.adp
    • -6
    • +9
    /openacs-4/packages/news/www/admin/index.tcl
Whitespace cleanup

Use page contract

Add missing var

Add include contract

Whitespace changes

Add parameter RssGenActiveP to the rss-support package, to enable/disable the RSS generation service. Bump version number.

fix typo

reduce verbosity

reduce verbosity (set verbose_blocking per default to 0), improve speed of dump creation

added example line to ease spotting of the creation of unnamed mutexes

provide name for mutexes to ease spotting potential locks

New method to cleanup all data associated with a community in the throttle object:

if a community is deleted when a user is accessing it, some leftover information will be kept in the object. At the next request this will be interpreted as the community having been left and the system will try to track this event into request_monitor_community_activities. Depending on who comes first, we might try to insert a tuple in the table for an object that does not exist anymore.

Hence, we use this method to cleanup all community info before the actual deletion in dotlrn (happening only downstream).

allow points computation in cases, where some grading schemes fail.

Before, the grading code was overly conservative and refused to

compute achieved points in such cases

Fix expression logic

avoid burst cache hits by using nsvs instead of ns_cache for secret token caching

The problem with the prevision version was that ns_cache has no equivalent

to nsv_array to get in an atomic fashion all key value pairs from the cache.

thefore, for the per-thread caching, a tight loop was used processing

the result of ns_cache_keys. If this was necessary in a high number of

threads, higher lock times were possible (~100ms). The new version

should not face this problem.

Don't be so strict upstream, as here we do not restrict community_key to ltree

Constrain further the characters we allow in the community_key: makes sense upstream as this will become part of a URL, but is even more important downstream, as we implement the community_key as a ltree and therefore we are limited in the type of characters we can allow (See https://www.postgresql.org/docs/current/ltree.html)

Fix typo

Add missing arguments

Rework dotlrn_community::check_community_key_valid_p so that we check also for the community key to not have spaces

Logics have been moved to private api that might or might not become the preferrable api at some point, as it also returns the specific error message together with the boolean

use term "Preview" for testing single test items

new form-field class: boolean_checkbox

behaves like boolean, but provdes just a single checkbox instead of yes/no radio in "boolean"

the output is full compatible with "boolean".

The boolean_checkbox is used in test-item procs for a more slim correct/incorrect specification

    • -2
    • +2
    /openacs-4/packages/xowiki/xowiki.info