Forum .LRN Q&A: dotlrn installation instructions updated

Please upgrade file-storage and dotlrn-fs to HEAD to get these changes.

1. updated note about "content-repository-content-files" directory
which is now included in the "acs-core" CVS alias, so it does not
have to be created manually.

2. added information about the new "attachments" package which is
currently used by "forums" and "calendar". Exising installations of "forums" and "calendar" will not break without this package, but attachments funcationality will not be available.

Oops.

I prematurely declared victory. After mounting dotlrn, attachments, and notifications, setting the kernel parameters, and restarting the server, I didn't see the (+) beside dotLRN in the sitemap. And I have this error message in my logs:

 Error: Error sourcing /var/lib/aolserver/servers/dotlrn/packages/dotlrn/tcl/dotlrn-init.tcl:
Database operation "0or1row" failed (exception NSDB, "Query was not a statement returning rows.")
    while executing
"ns_db 0or1row $db "select $function_name ()""
    invoked from within
"db_exec_plpgsql $db $full_statement_name $sql  $statement_name"
    invoked from within
"if {[regexp -nocase -- {^s*select} $test_sql match]} {
            db_qd_log Debug "PLPGSQL: bypassed anon function"
            set selection [db_ex..."
    ("uplevel" body line 6)
    invoked from within
"uplevel 1 $code_block "
    invoked from within
"db_with_handle db {
        # plsql calls that are simple selects bypass the plpgsql 
        # mechanism for creating anonymous functions (OpenACS - ..."
    (procedure "db_exec_plsql" line 13)
    invoked from within
"db_exec_plsql rename_folder {}"
    (procedure "fs::rename_folder" line 3)
    invoked from within
"fs::rename_folder -folder_id $folder_id -name {User's Folders}"
    (procedure "dotlrn_fs::add_applet" line 7)
    invoked from within
"dotlrn_fs::add_applet"
    (procedure "AcsSc.dotlrn_applet.AddApplet.dotlrn_fs" line 1)
    invoked from within
"AcsSc.dotlrn_applet.AddApplet.dotlrn_fs"
    ("uplevel" body line 1)
    invoked from within
"uplevel $func_and_args"
    (procedure "apply" line 3)
    invoked from within
"apply $proc_name $arguments"
    (procedure "acs_sc_call" line 6)
    invoked from within
"acs_sc_call dotlrn_applet $op $list_args $applet_key"
    (procedure "dotlrn_community::applet_call" line 2)
    invoked from within
"dotlrn_community::applet_call $applet AddApplet [list]"
    ("foreach" body line 3)
    invoked from within
"foreach applet [dotlrn_community::list_applets] {
            ns_log notice "dotlrn-init: calling ${applet}::AddApplet"
            dotlrn_community::..."
    ("uplevel" body line 14)
    invoked from within
"uplevel 1 $transaction_code "
    (procedure "db_transaction" line 1)
    invoked from within
"db_transaction {

        ns_log notice "dotlrn-init: dotlrn is instantiated, about to call dotlrn_applet::init"

        # this may seems strange, bu..."
    invoked from within
"if {[dotlrn::is_instantiated]} {

    set package_id [dotlrn::get_package_id]

    # make sure we aren't inheriting permissions from dotlrn's parent o..."
    (file "/var/lib/aolserver/servers/dotlrn/packages/dotlrn/tcl/dotlrn-init.tcl" line 30)
    invoked from within
"source $__file "

Any idea on what happened, and how to proceed?

This thread tracks dotLRN port on Postgresql

https://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=00051T&topic_id=15&topic=dotLRN%20Development

About the data change violation ( from previous forum answers) acs-kernel/sql/acs-create.sql has one way to deal with it - temporarily disable the trigger. Though that solution did not work for me, placing all add_child statements outside transaction worked. I dont remember the thread but Dan explained this as problem with the trigger when in a single transaction two or more add_child calls are made.