Forum .LRN Q&A: dotLRN some basic questions.
Greetings, I'm just getting tuned into the dotLRN project and had a few basic questions. 1.) From the Installation instructions NEW! forums replaces bboard and sloan-bboard. After cvsing the dotlrn packages I don't see forums. Where can I get it? 2.) Also I'm a bit confused by the statement "Do not install or remove these packages since they conflict with dotlrn packages: bboard (conflicts with sloan-bboard) portal (conflicts with new-portal) spam (conflicts with bulk-mail)" Do I need a new installation that has never had bboard etc. installed to use the dotLRN package? Thanks very much, Zack.
previously and thats why I didn't have forums. Noticed that bboard
also still comes with the CVS of OpenACS.
We should update our docs, because we no longer use sloan-
bboard, and forums doesn't conflict with the "normal" bboard
package from OpenACS.
That said, dotLRN is in alpha state. You shouldn't install it on
something that has existing "real" data.
psql:forums-forums-create.sql:56: ERROR: Cannot insert a duplicate key into unique index acs_privileges_pk psql:forums-forums-create.sql:90: ERROR: Relation 'forums_forums' already exists psql:forums-forums-create.sql:96: ERROR: Relation 'forums_forums_enabled' already exists psql:forums-forums-create.sql:117: ERROR: Cannot insert a duplicate key into unique index acs_object_types_pk invoked from within "db_source_sql_file -callback $callback $path/$file_path" (procedure "apm_package_install_data_model" line 32) ...I'm going to try again and just install the, packages required to get forums up and running. If anyone can offer insight, I'd appreciate it.
I'm running aolserver 3.3ad13 and postgres 7.2.1 (which may be the problem) on Redhat 7.3.
Unforunately, I can't really test it from there because I think the cvs site-map is broken: I can't create new folders.
I'll update again once I can get a version of cvs that works.
i also found out that the postgres port of forums is not working correctly yet. i will try to have an update to fix this today.
This one is found in /packages/acs-kernel/acs-objects-create.sql
In the function acs_object__update_last_modified, the update statement reads:
update acs_objects set acs_objects.last_modified = v_last_modified where acs_objects.object_id = acs_object__update_last_modified__object_id;
This causes Postgres to give: ERROR: parser: parse error at or near "."
The correct statement should be:
update acs_objects set last_modified = v_last_modified where object_id = acs_object__update_last_modified__object_id;
(Let me know where else I should post this bug.)
in /www/index-postgres.xql the following column needs to be added to the query:
case when last_modified > (now() - 1) then 't' else 'f' end as new_p
in /www/forum-view-postgresql.xql the line:
should be changed to:select count(fm1.*)
in both queries.select count(*)
in /sql/postgresql/forums-messages-package-create.sql the line:
needs to be:select define_function_args ('forums_message_new' ...
select define_function_args ('forums_message__new' ...
Forums is not working after these changes, but we're closer. The bug I'm currently trying to track down is in the plpgsql function: forums_mess_insert_tr, which gives an error:
ERROR: FOR UPDATE: relation "max_child_sortkey" not found in FROM clause
Anyway, that's my update.
some stuff is not working correctly yet, specifically sort_keys but i am trying to figure it out. i am still trying to learn postgres
so please bear with me.
Just let me know if there is anything I can do to help that isn't stepping on your toes. :)
From last night on, the notifications package bombs on installation (Postgres). I don't know if you have a fix coming, so I just thought I'd make sure you knew about it.
Also, I have a question about permissions. When I was playing around with the forums package yesterday (which mostly worked.) I was confused about the permissioning system the forums use. If I, in the site map, give my the public the forum_read privelege in a certain instance of the forum package, do the individual forums and messages inherit this permission?
Yesterday it didn't look like the permissions were being inherited, so each forum had to have forum_read granted to the public explicitly. I hope that was just a bug and not the way it is supposed to work.