Home
The Toolkit for Online Communities
17201 Community Members, 0 members online, 2238 visitors today
Log In Register
OpenACS Home : xowiki : Weblog
Search · Index
Previous Month August 2014
Sun Mon Tue Wed Thu Fri Sat
27 28 29 30 31 1 2
3 4 5 (1) 6 7 8 (6) 9
10 (1) 11 (2) 12 13 14 15 16
17 18 (1) 19 20 (2) 21 22 23
24 25 26 27 28 29 30
31 1 2 3 4 5 6

Popular tags

ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bugtracker , COMET , cvs , debian , emacs , fedora , FreeBSD , hstore , includelets , install , installation , installers , javascript , libthread , linux , monitoring , naviserver , nginx , nx , OmniOS , oracle , osx , patches , performance

No registered users in community xowiki
in last 30 minutes

Contributors

OpenACS.org

Weblog

Showing 1 - 10 of 820 Postings (summary)

Official test servers

Created by Rocael Hernández Rizzardini, last modified by Michael Aram One hour 44 minutes ago

Test servers are available at http://openacs.innova.uned.es

There's 4 servers: 2 for OpenACS HEAD (pg 8.1 and oracle9i) and 2 for dotLRN HEAD (pg 8.1 and oracle9i). Login info is on the homepage. CVS committers who might need ssh access, please contact Marcos.

We need to set up:

  1. Install spellcheck tools. 
  2. A way to easily do a CVS update and re-run the test cases? probably shell access will be needed. Instructions need to be set on this sense.
  3. Daily reports (by packages? to subscribers)
  4. Probably will be better if everything re-installs each night (not weekly)?

We'll use Innova server (Thanks Innova team!) as our official test server, although if someone else wants to provide / configure another test server, thats is very welcomed!

OpenACS compatibility matrix

Created by Joel Aufrecht, last modified by Gustaf Neumann 08:09 PM, Tuesday

OpenACS requires, at a minimum, an operating system, database, and webserver to work. Many additional programs, such as a build environment, Mail Transport Agent, and source control system, are also needed for a fully effective installation.

Table 2.2. Version Compatibility Matrix

OpenACS Version 3.2.5 4.5 4.6 4.6.1 4.6.2 4.6.3 5.0 5.1 5.2 (core)
5.3 (core)
5.4 (core)
5.5 (core)
5.6 (core)
5.7 (core)
5.8 (core)
AOLserver 3 Yes No
3.3+ad13 Maybe Yes No
3.3oacs1 Maybe Yes No
3.4.4 No
3.4.4oacs1 Maybe Yes No
3.5.5 Maybe Yes No
4.0 Maybe Yes
4.5 No Yes
Naviserver 4.99.4 - No Maybe Yes
Tcl 8.4 Yes No
8.5.4 - Maybe Yes
PostgreSQL 7.0 Yes No
7.2 Maybe Yes No
7.3.2 - 7.3.x No Yes No
7.4 No Yes No
8.0 No Maybe Yes Maybe
8.1 No Yes Maybe
8.2 No tar: no, CVS: Yes Yes Maybe
8.3 No Yes Maybe
8.4 No Yes
9.0 - 9.3 No Yes
Oracle 8.1.6 Maybe Yes Maybe
8.1.7 Maybe Yes Maybe
9i No Yes Maybe
10g No Yes Maybe
11g No Maybe

The value in the cells correspond to the last version of that release, and not necessarily to all minor releases. Empty cells denote an unknown status.

Aliases at CVS

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 12 Aug 2014, at 07:01 PM

Useful aliases for cvs.openacs.org:

  • acs-core *
  • dotlrn-all *
  • dotlrn-extras *
  • contrib
  • project-manager-all
  • xotcl-all
  • dotngo
  • dotwrk

 * These aliases are controlled by OCT and .LRN honchos groups, the packages that belong to these aliases are the ones that are maintained by both groups. They are not to be changed unless approved by OCT and / or .LRN technical comittee.

Below the packages details for each alias:


##################################################################
# OpenACS Core
##################################################################

acs-core -a openacs-4/packages/acs-admin
openacs-4/packages/acs-api-browser
openacs-4/packages/acs-authentication
openacs-4/packages/acs-automated-testing
openacs-4/packages/acs-bootstrap-installer
openacs-4/packages/acs-content-repository
openacs-4/packages/acs-core-docs
openacs-4/packages/acs-developer-support
openacs-4/packages/acs-kernel
openacs-4/packages/acs-lang
openacs-4/packages/acs-mail-lite
openacs-4/packages/acs-messaging
openacs-4/packages/acs-reference
openacs-4/packages/acs-service-contract
openacs-4/packages/acs-subsite
openacs-4/packages/acs-tcl
openacs-4/packages/acs-templating
openacs-4/packages/ref-timezones
openacs-4/packages/acs-translations
openacs-4/packages/intermedia-driver
openacs-4/packages/openacs-default-theme
openacs-4/packages/notifications
openacs-4/packages/search
openacs-4/packages/tsearch2-driver
openacs-4/ChangeLog
openacs-4/license.txt
openacs-4/readme.txt
openacs-4/bin
openacs-4/content-repository-content-files
openacs-4/database-backup
openacs-4/etc
openacs-4/log
openacs-4/tcl
openacs-4/www

##################################################################
# .LRN aliases
##################################################################

dotlrn-all -a acs-datetime acs-events
attachments bulk-mail calendar faq file-storage
forums general-comments news lars-blogger
weblogger-portlet rss-support trackback oacs-dav
xml-rpc categories dotlrn dotlrn-syllabus new-portal
profile-provider user-profile bm-portlet dotlrn-bm
calendar-portlet dotlrn-calendar dotlrn-portlet
dotlrn-dotlrn faq-portlet dotlrn-faq forums-portlet
dotlrn-forums fs-portlet dotlrn-fs news-portlet
dotlrn-news static-portlet dotlrn-static
dotlrn-homework dotlrn-weblogger evaluation
evaluation-portlet dotlrn-evaluation assessment
assessment-portlet dotlrn-assessment theme-selva
theme-zen dotlrn-random-photo random-photo-portlet
views

dotlrn-extras -a lors lorsm lorsm-portlet dotlrn-lorsm
photo-album photo-album-portlet dotlrn-photo-album
survey-portlet dotlrn-survey survey chat
dotlrn-chat chat-portlet xotcl-core imsld
imsld-portlet dotlrn-imsld

##################################################################
# Project Manager aliases
##################################################################

project-manager-all -a calendar acs-events acs-datetime
acs-mail-lite categories logger
project-manager general-comments
organizations


##################################################################
# xoTCL Stuff + required
##################################################################

xotcl-all -a xotcl-core xotcl-request-monitor xowiki categories
acs-events acs-datetime file-storage oacs-dav
rss-support general-comments




ACS Developer Support

Created by Nick Carroll, last modified by Gustaf Neumann 12 Aug 2014, at 06:57 PM

Package specification Summary for package acs-developer-support

Summary: Profiling for requests including database timing information.
Description: Developer support stores timing and other logged information for requests to support debugging and tuning and supports user switching and a Tcl Shell to invoke arbitrary tcl code on the server.
Maturity: Mature and Standard
This package depends on: acs-kernel acs-templating
Packages that depend on acs-developer-support: None

Bug Tracker Summary for package acs-developer-support

Open Bugs: 5
Latest Bug Opened: 2009-04-07 Link to XoTcl + link to current page in site map
Latest Bug Fixed: 2013-09-16 Optionally collect queries with bind variables substitured.
Top Bug Submitters: Carsten Clasohm (2) Lurch . (2) Christian Brechbuehler (1) Randy O'Meara (1) Dave Bauer (1)
Top Bug Fixers: Gustaf Neumann (4) Jeff Davis (2) Rocael Hernández Rizzardini (1) Malte Sussdorff (1)

Code Metrics Summary for package acs-developer-support

# Tcl Procs 42
# Tcl Lines 704
# Automated Tests 0
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 6
# ADP lines 82
# Include pages (acs-developer-support/lib/) 2
# Documentation pages 2
# Documentation lines 46
Source API-browser

OpenACS TODO List

Created by Dave Bauer, last modified by Gustaf Neumann 11 Aug 2014, at 09:26 PM

Release Status

See openacs-release-status

Development is taking place on oacs-5-8.

OpenACS Version 5.8 Agenda

  • PostgreSQL 9.2+:
    • Get rid of nonstandard backslash escapes in function definitions
    • Change quote syntax in sql files (single quotes around the functions) to recommended PostgreSQL quoting using (recommended since pg8.0, jan 2005). li>Drop aliases in favor of named function arguments (recommended since pg8.0)
    • Fix wrong function_args, add missing function_args, align default semantics with the defaults in pg (providing "null" as default means the argument is optional)
    • Make OpenACS loadable without any tweaks in the pg config files
  • Use recursive queries for e.g. permission lookup to avoid performance problems in pg 8.4 and newer)
  • ADP: Use byte-compiled function wherever possible in compiled adp-code, support "@var;literal@" when neither quotes nor localization is needed in compiled adp-code
  • Improve support of NaviServer
  • Switch to Tcl 8.5 (TIP #143)
  • Improve scalability: Reduce mutex-stress on util-memoize cache and for cache maintenance in general
  • Code cleanup:
    • Get rid of calls to deprecated code (e.g. ad_tables, ad_parameter, ... in acs-core and main packages)
    • Improve awareness of usage of deprecated code (complain to error.log)
    • Use Tcl 8.5 idioms
    • cleanup of various http-client approaches and introduce a common implementation util::http::get and util::http::post; get rid of other usages, mark these as deprecated
    • page-contracts: Perform checking of all ids in acs-core and main packages to improve error messages and to improve security
  • OpenACS 5.8.1 should be released with main packages

OpenACS Version 5.7 Agenda

  • Support for object management in core 
  • Postgresql 9.0
  • TinyMCE update (fix for random JS injection issue, affecting Safari)
  • Fix for "remember me" issue
  • WCAG2-AA

OpenACS Version 5.6 Agenda

  • global parameters
  • package "embeds" 
  • fix search by package_id
  • core works on Postgresql 8.4

OpenACS Version 5.5 Agenda

  • DONE: Postgresql 8.3 support: especially regarding tsearch2
  • DONE: acs-authentication:
    • fix upgrade, add conditional logic into site wide tcl library so that you can login to perform the rest of the upgrade
  • DONE: tinymce:
    • upgrade to 3.1.1 + language packs
    • HTML Strict cleanup
    • create appropriate parameters for its config in acs-templating
  • acs-mail-lite:
    • DONE: cleanup duplicated procs (bounce)
    • review the parsing of bouncing messages (case user_id 0)
    • DONE: rollout support
  • Documentation improvements as discussed at the Guatemala conference:
    • Make current openacs.org/test-doc source for static files included in the release and provide ease means to achieve this for the release manager
      • DONE (CVS HEAD): Provide in XoWiki an alternative table of contents by nested UL/LI (without JavaScript) for static output
      • DONE (CVS HEAD): Provide in XoWiki a prototype page similar to "book" without edit-buttons etc., using the new table of contents
    • Update openacs.org/test-doc where necessary (incomplete list):
      • DONE: Fix the page ordering for the higher chapters (the original document  had no 3rd. level numbering)
      • update pages in /test-doc which are more recent in openacs/xowiki
      • bump version numbers of OpenACS, where appropriate (some places talk about openacs-5-0, others about openacs-5-1, oacs-5-2-3rc1 or 5-3) 
      • some version numbers of the required components are quite a mess. e.g. some parts say that Postgres 7.3 is required,  some examples talks about postgres 7.4.7 and 8.2.4 in the same listing.
      • also the dotlrn version numbers are old dotrln-2.0
      • Tcl version numbers should be 8.4.19
      • The install section for XOTcl is missing in II.3.4
      • remove ChangeLog from documentation
      • find some other prominent place for the ChangeLog
      • Fix indenting in examples  (e.g. in Rocael's robust web    development framework)
      • overthink Win2000 guidelines.  There are the native compiled packages from Maurizio, including everything from postgres, xotcl ....
    • It is desired to find a single person responsible for overworking the documentation, however, funding is unclear.

OpenACS Version 5.4 Agenda

  • DONE: HTML Strict (openacs core)
  • DONE: finish template::head (daveb)
  • DONE: test acs-mail-lite (complex send)
  • DONE: test notifications (complex send)
  • DONE: new XinHA release, get rid of RTE & HTMLarea, test on Safari
  • DONE: Form builder: add the ID attribute  to the form tag
  • DONE: acs-lang - keepLocalTranslationP to be removed
  • DONE search and intermedia-driver: move intermedia specific stuff to its package
  • DONE: acs-mail-lite - patch for mime::qp_encode bug

Future

  • Split Xinha and TinyMCE into seperate packages see: http://openacs.org/forums/message-view?message_id=2750958
  • Usability ("my account" page)
  • XHTML ?
  • Testing and documentation for recording automated tests using the firefox plugin and the upload feature for it new in automated testing. Probably needs some polishing and should be talked to with Quest who are getting into this.
  • Parameter Scope Patch http://openacs.org/bugtracker/openacs/patch?patch%5fnumber=845 
  • Remove obsolete master template stuff (default and site master template in openacs-4/www, acs-subsite's group-master, and related CSS and images).  Probably in the version which follows 5.5 (probably 5.6).  Also remove the compat master stuff at the same time.

Things to merge into this page

Old 5.0 Roadmap  discussion 

Roadmap discussion 1 

 [Ideas for Boston 2006 Future of OpenACS discussion]

My previous attempt at collaborative roadmap 

A .LRN Roadmap 

Another .LRN Roadmap discussion 


What's on this page?

This page should include work that is planned on and has someone comitted to working on it.

Categories

Created by Torben Brosten, last modified by Gustaf Neumann 09 Aug 2014, at 09:50 PM

Package specification Summary for package categories

Summary: Manage categories in category trees and let users map objects to categories.
Description: Datamodel for category trees with supporting API and management pages. Provides a widget for general categorization of arbitrary objects and tracks which package instances use which category trees. Also supports localization.
Maturity: Immature
This package depends on: acs-kernel
Packages that depend on categories: ajax-filestorage-ui assessment connections contacts cop-base cop-ui curriculum dotlrn-catalog faq file-storage invoices lars-blogger logger project-manager xcms-ui xowiki

Bug Tracker Summary for package categories

Open Bugs: 4
Latest Bug Opened: 2006-07-07 making Categories subsite-aware
Latest Bug Fixed: 2007-05-02 cadmin/category-usage omits first mapped object.
Top Bug Submitters: Branimir Dolicki (3) Ben Koot (2) Lurch . (2) Stan Kaufman (1) Randy O'Meara (1)
Top Bug Fixers: Malte Sussdorff (9) Yves Goldberg (2) Jeff Davis (1) Dave Bauer (1) Branimir Dolicki (1) Ben Koot (1)

Code Metrics Summary for package categories

# Tcl Procs 83
# Tcl Lines 2755
# Automated Tests 3
# Stored Procedures PG: 0 ORA: 0
# SQL Lines PG: 0 ORA: 0
# ADP pages 29
# ADP lines 425
# Include pages (categories/lib/) 6
# Documentation pages 4
# Documentation lines 196
Source API-browser

Feature requests

AN ABBREVIATION/REFERENCE KEY PER CATEGORY AND CATEGORY TREE. In ecommerce package, each bulk upload of associating categories with products requires working with the databases' index for 3 columns, which is not consistent accross sites. This gets laborious to work with after a while. Allowing categories to optionally explicitly define unique references would help with bulk uploading products, building online catalogs etc. and integrating with the [en:ref-unspsc]] package, which is/has a standardized referencing system. (This request from OpenACS.org Bug 1130)

CATEGORY ACTIVE/INACTIVE. Ecommerce needs to have categories include an attribute for each category that identifies if a category is active (in use) or not. That way, large category reference systems, such as http://www.unspsc.org/ can be imported without concern about overloading the shopping basket with categories that contain no products. (This request from OpenACS.org Bug 1130).

CATEGORY LIST/TREE MAP. Each category tree needs to have a list equivalent for speedy referencing, for cases when there might be many thousands of items in a category tree. (This request from OpenACS.org Bug 1130).

Web Forms

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 09 Aug 2014, at 09:22 PM

Use ad_form to create HTML forms. If you work on a page that does not, convert it to use ad_form.

You can grep the toolkit under /packages and see many examples. 

Ad_form can handle many of your possible interactions with the system, such as normal tasks as add and edit data, validate entry form data, etc.

Aditional information here:

http://rubick.com:8002/openacs/ad_form

Use the following in the tcl part of a page to limit access to page requests via post.. to reduce vulnerability to url hack and insertion attacks from web:

if { [ad_conn method] ne "POST" } {
  ad_script_abort
 }

Grouping elements into sections using ad_form

The {-section} list allows to group the subsequent elements (until the next section declaration) into a section. {-section} accepts 4 properties:

{-section \
	section_id \
	{legendtext $legendstring} \
	{legend {name value name value ... name value}} \
	{fieldset {name value name value ... name value}}
}

where:

  • section_id: a string to identify the section (mandatory)
  • legendtext (optional) a string for the legend of the fieldset (section)
  • legend (optional) a list of name value pairs attributes for the LEGEND tag
  • fieldset (optional) a list of name value pairs attributes for the FIELDSET tag

Example

ad_form \
	-name "your_zen_level" \
	-method post -html {enctype multipart/form-data class margin-form} \
	-fieldset {{title "T1" class "C1"} "This really works!!"} \
 	-form {
 
     # Start section 1
     {-section "sec1" {legendtext "Section Title I"} {legend {class myClass id myId}}}
    {zen_comment:text(comment)\
                 {label "template::widget::comment"}\
                 {value "Please enter your comments."}\
                 {html {rows 7 cols 50}}}
    {zen_file:text(file),optional\
                 {label "template::widget::file"}}

    # Start section2
    {-section "sec2" {legendtext "Section Title II"} {fieldset {class myclass}}}
    {zen_multiselect:text(multiselect)\
                 {label "template::widget::multiselect"}\
                 {options {"mark" "emma" "avni" "carl" "don"}}}

    # Unset the section. subsequent elements will not be in any section.
    {-section ""}
    {zen_text:text(text),optional,nospell\
                 {label "template::widget::text"}\
                 {help_text {"Your identification tag number"}}}
    {zen_textarea:text(textarea),optional,nospell\
                 {label "template::widget::textarea"}\
                 {help_text {"Please describe your desired state of being"}}\
                 {html {rows 7 cols 50}}}
}

 

ADP Files

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 09 Aug 2014, at 09:20 PM

  • Avoid putting in Tcl code on ADP pages if possible

    Although AOLserver/NaviServer ADP supports this try to make use of OpenACS Templating or http://your.openacs/doc/acs-templating/. 

  • Pass the "context" and "doc(title)" to the site master template
    Example:
    <property name="doc(title)">@title@</property>
    <property name="context">@context@</property>

Tcl pages

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 09 Aug 2014, at 09:16 PM

  • Avoid putting in HTML in Tcl scripts

    Try to make use of OpenACS Templating or http://your.openacs/doc/acs-templating/. If you can't avoid it try to isolate the HTML into a proc so editing the layout will be easier.

  • Do not use "==" in comparing strings

    Using "if { $string == "foo" }" tries to make a numeric comparison first. Instead make use of "if { "foo" eq $string }" or if you need the negation "if {"foo" ne $string }".

  • Delete the queries from your Tcl files ??

    Since we are now using the query dispatcher it is encourage to make use of .xql files. If you use .xql files kindly delete the sql from the .tcl to avoid confusion. And place a "SQL" place holder on it. (ex. db_1row stmtname "SQL") to make it more readable.

  • Read the Tcl Style guide

    This is the Tcl styleguide (PDF), try to apply relevant guidelines. In particular chapter 4,5 and 7.

Coding Standards - Index

Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 09 Aug 2014, at 09:14 PM

A coding style is always important to maintain quality of the code and in this case, the OpenACS project. Here you'll find a set of links that will guide through our most common standards.

The definitive guide on coding standards can be found at http://openacs.org/doc/style-guide.html

Many stuff has been gathered from many post or guides other openacs community members have done, such as:

Next Page