• last updated 55 mins ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
strangely, parameter CommDefaultSiteTemplate_p was set on wrong package_id

Before this change, the install from repo on dotlrn led to error below.

this change makes sure, that the used "package_id" is the package_id from dotlrn.

: ERROR: -20000: The specified package 702 AND/OR parameter CommDefaultSiteTemplate_p do not exist in the system

: CONTEXT: PL/pgSQL function apm__id_for_name(integer,character varying) line 13 at RAISE

: PL/pgSQL function apm__set_value(integer,character varying,character varying) line 6 at assignment

oacs-5-10=# select * from apm_packages where package_key like '%dotlrn%';

package_id | package_key | instance_name | default_locale

------------+-------------------------+----------------------------+----------------

1843 | dotlrn-bm | dotLRN Bulk Mail Applet |

1850 | dotlrn-faq | dotLRN FAQ Applet |

1868 | dotlrn-forums | dotLRN Forums Applet |

1886 | dotlrn-fs | dotLRN File Storage Applet |

1933 | dotlrn-news | dotLRN News Applet |

1981 | dotlrn-portlet | dotLRN Portlet |

1998 | dotlrn-assessment | dotLRN Assessment Applet |

2040 | dotlrn-bootstrap3-theme | dotLRN Bootstrap 3 Theme |

oacs-5-10=# select * from apm_packages where package_id = 702;

package_id | package_key | instance_name | default_locale

------------+-------------+------------------------+----------------

702 | acs-subsite | #acs-kernel.Main_Site# |

moved theme setting to theme package (dotlrn-bootstrap3-theme)

This make sure that in the loading sequence, the theme is available when one

tries to switch to it.

    • -1
    • +1
    /openacs-4/packages/dotlrn/install.xml
added "dotlrn-bootstrap3-theme" to dependencies to make it installable via "install.xml" for install-from-repository

    • -2
    • +3
    /openacs-4/packages/dotlrn/dotlrn.info
fixed dependencies

improved log messages

bump maturity from 1 to 2

fixed typo in filename of image

Cleanup stale sse connections

Introduce a new delivery method for notifications based on Server Sent events

By subscribing to /notifications/sse/subscribe one will receive notifications as JSON messages. This can be used e.g. to update a UI in real time based on events on the system.

    • -0
    • +245
    /openacs-4/packages/notifications/tcl/notification-sse-procs.tcl
Retrieving the datasource should not depend on the fact that a driver is configured

    • -2
    • +2
    /openacs-4/packages/search/search.info
    • -8
    • +6
    /openacs-4/packages/search/tcl/search-procs.tcl
bump upstream version number from 7.5.1 to 7.6.0

bump upstream version number from 11.4.8 to 12.0.2

avoid triggering exception, when provided host header field cannot be resolved.

avoid error, when page_contract is called without an ns_set and without an open connection

fixed typo

Compute the columns as weel when creating a multirow from a list

Test converting to and from a multirow and a list

The test reveals that when converting a list into a multirow, the columns will not be set correctly

title always exists now, ensure it is not empty instead

Introduce the toolbar parameter at the richtext superclass level, so

that formpages created with editors expecting this spec, like ckeditor4,

will not fail to load using other editors that do not expect it

db quote via the api

    • -1
    • +1
    /openacs-4/packages/xowiki/tcl/weblog-procs.tcl
Do not omit line breaks when rendering text interactions as textareas, e.g. in exam protocols

Many thanks to Markus Moser

Removed calls to deprecated NaviServer functions in legacy packages

  1. … 32 more files in changeset.
Removed calls to deprecated NaviServer functions

Removed calls to deprecated NaviServer functions

    • -1
    • +1
    /openacs-4/packages/xowf/tcl/iprange-procs.tcl
replaced calls to "ns_httpget" in legacy packages

bump version number of upstream package to 7.5.1

bump version number to latest upstream release

Avoid calls to deprecated NaviServer functions

Initializing a formfield with an invalid spec fails as expected, however, it appears to leave behind the formfield object, which many automated tests will now consider a failure

Ensure the formfield object is destroyed when reading the spec fails