• last updated 14 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix typos, improve translations

    • -2
    • +2
    ./catalog/acs-subsite.it_IT.ISO-8859-1.xml
amend to last commit (dirty editor buffer)

    • -1
    • +1
    ./catalog/acs-subsite.it_IT.ISO-8859-1.xml
improve message key

- The message was confusing, especially to novices:

There is no "OpenACS parameter file", but a "NaviServer configuraiton file"

- bumped version number to 5.10.1b7

    • -1
    • +1
    ./catalog/acs-subsite.da_DK.ISO-8859-1.xml
    • -1
    • +0
    ./catalog/acs-subsite.de_DE.ISO-8859-1.xml
    • -1
    • +1
    ./catalog/acs-subsite.en_AU.ISO-8859-1.xml
    • -3
    • +2
    ./catalog/acs-subsite.en_US.ISO-8859-1.xml
    • -1
    • +2
    ./catalog/acs-subsite.es_CO.ISO-8859-1.xml
    • -1
    • +3
    ./catalog/acs-subsite.es_ES.ISO-8859-1.xml
    • -1
    • +1
    ./catalog/acs-subsite.es_GT.ISO-8859-1.xml
    • -1
    • +1
    ./catalog/acs-subsite.fr_FR.ISO-8859-1.xml
    • -1
    • +3
    ./catalog/acs-subsite.gl_ES.ISO-8859-1.xml
  1. … 9 more files in changeset.
Dont fail when pk_formatted is empty.

New parameter "scroll_to" for parameter page

The new parameter allows the code to jump to a named parameter in the

parameter editing page. This is very useful for pages with a high

number of parameters, if just one parameter should be changed.

Bump version number after catalog changes

Don't append a dot to the confirmation_url to avoid 'dead URL'-problems in e-mail clients. Put the URL in quotes.

Don't append a dot to the confirmation_url to avoid 'dead URL'-problems in e-mail clients.

    • -1
    • +1
    ./catalog/acs-subsite.de_DE.ISO-8859-1.xml
Cleanup obsolete queries

    • -35
    • +0
    ./tcl/email-image-procs-postgresql.xql
Do not assume lob as storage backend for the email image and rely on the api

Add reference to further context about this feature

Harden the page contract and ensure that:

- for chat rooms in the chat package, only the chat class enforcing permissions is used

- for other chat ids, either the id is an object the user can read, or the user can at least read on the current connection package

Cleanup commented code

Only allow valid privileges in the privs parameter

restrict substitution in string

Made .xql file more consistent by using dot notation

OpenACS for PostgreSQL uses since the release of 5.10.0 the dot

notation for the SQL function acs_permission.permission_p() to ease

portability with Oracle.

In general, one has to be careful that during an upgrade from an older

OpenACS version (e.g. 5.9.*) directly to 5.10.1 to upgrade process

does not depend on the dot notation, otherwise the upgrade will fail.

One should be safe for most UI functions in this respect.

    • -2
    • +2
    ./www/admin/site-map/index-postgresql.xql
Harden page contract

Update italian localization

    • -0
    • +1
    ./catalog/acs-subsite.it_IT.ISO-8859-1.xml
  1. … 4 more files in changeset.
Cleanup of external binaries: always use "util::which" to resolve binaries

  1. … 4 more files in changeset.
improved spelling

Improved navigation bar menu structure

Before, the "admin" pulldown contained item "Advanced", which was pretty

unclear. The new label for the subsite administration is now "Subsite Adminsitration".

    • -0
    • +1
    ./catalog/acs-subsite.en_US.ISO-8859-1.xml
Fix selector for the click all list callback

Cleanup long deactivated code

    • -1
    • +0
    ./www/admin/site-map/index-postgresql.xql
Fix typo

Improve documentation

Cleanuo commented code

Whitespace cleanup

Move custom calendar widget javascript implementation out of the core.js and into a separate file

In core/maintained packages, this widget is used only by template::widget::textdate (which in turn is used nowhere). For this widget, we can include the relevant code on-demand.

Direct usages found in unsupported packages have been adapted by adding the extra requirement on the fly.

It is unclear if we should keep maintaining a calendar widget in our codebase, however, as the current one still works (kudos to the original author), we do not deprecate it for the time being.

It is also true that a custom widget provides a way to customize the look and feel of date fields, which is otherwise completely delegated to the browser.

Various packages, including the core, provide custom css styling for the current widget.

  1. … 2 more files in changeset.
Fix the idiom used to cut the query parameters from the URL

Handle null dates