Activity Graph
Created by Gustaf Neumann, last modified by Benjamin Brink 30 Jun 2017, at 07:12 AM
Created by Gustaf Neumann, last modified by Benjamin Brink 30 Jun 2017, at 07:12 AM
Created by Gustaf Neumann, last modified by Benjamin Brink 30 Jun 2017, at 07:11 AM
This is a list of the includelets, which can be included in a xowiki page:
Include an activity graph
List the available form field types of this installation.
List the available includelets of this installation.
Show contents in book mode.
Include bookmarklet button that makes it easy to add the current page as a bookmark in the browser of the client.
List the specified category tree.
Display recent entries by categories.
Include a chat in the current page
Include a chat room
Include a collaboration graph
Include a link to the community including the current page. This includelet is designed to work with dotlrn.
Create a form from the selection
Button to copy a page
Countdown timer
Button to create a new page based on the current one
Include the creation date of the current or specified page in the provided format.
Button to delete the current or a different page
Add a button to submit article to delicious.
Add a button to submit article to digg.
Button to edit the current or a different page
This is the top includelet for the in-class exam, containing a countdown timer and the personal notifications includelet
Include an mp4 image using flowplayer
List the folder tree of the current instance
Include a form menu for the specified Form
Include form statistics for the specofied Form page.
Show usages of the specified form.
Get an instance variable from the current or from a different page.
Include gravatar picture for the specified email
Include the specified HTML file
Include an iframe containing the specified URL
Display a sequence of pages via jquery-carousel, based on book includelet.
Display a sequence of pages via jquery-cloud-carousel, based on book includelet.
Display a sequence of pages via jquery-infinite-carousel, based on book includelet.
Display a sequence of pages via jquery-spacegalleryl, based on book includelet.
Include a Kibana chart identified by the provided hash
Display last visited pages.
Insert a link with extra return URL pointing the current object. This is particularly useful in cases, where a return URL must be created for a page that does not yet exist at time of definition (e.g. for link pointing to concrete workflow instances)
List the most frequent visitors.
Display most popular pages of this wiki instance.
List the categories associated with the current page.
List the general comments available for the current page.
List the pages which are referring to the current page.
List the pages which are referred to the current page.
List the tags associated with the current page.
Name of the publisher, when posting URLs to my yahoo (use in connection with with_yahoo_publisher).
Show users actively in the wiki.
Include random form page (instance of the specified form)
Display recent modified entries.
Include a graph of the (partial) link structure in a wiki, starting either with a page or a folder. When a page is provided, the local link structure of this page is visualized (including incoming and outgoing links of the page; e.g. -page "." for the current page). Alternatively, the content of a folder can be shown.
Include an RSS button referring to pages of the specified time span.
Include RSS content
Provide a selection of pages
Set a parameter accessible to the current page (for certain tailorings), accessible in the page via e.g. the query parameter interface.
Display a sequence of pages via W3C slidy, based on book includelet
Display specified tags.
Include a timeline of changes (based on yahoo timeline API)
List unread items.
List the pages with unresolved references in the current xowiki/xowf package. This is intended for use by admins.
Include a timeline of changes of the current or specified user (based on yahoo timeline API)
Button to view the current or a different page
Include YUI carousel showing the pages of the specified or current folder.
Created by Gustaf Neumann, last modified by Benjamin Brink 30 Jun 2017, at 07:10 AM
Created by Gustaf Neumann, last modified by Benjamin Brink 30 Jun 2017, at 07:08 AM
In order to save files directly in the wiki, just add a link with the content file:yourfile to a page (as for other links, between curly double brackets).
[[file:oacs-dotlrn-vienna-xowiki.pdf|XoWiki Slides from the Vienna OpenACS conference]]
When the file link is added, and the file does not exist, the wiki marks the link with a handle to upload the file. According to the current policies, everybody who is logged-in has sufficient permissions is allowed to edit pages..
Here is an example of a file-link, pointing to the xowiki slides from the the Vienna oacs-dotlrn conference XoWiki Slides from the Vienna OpenACS conference
Created by Michael Aram, last modified by Benjamin Brink 30 Jun 2017, at 07:05 AM
TODO: These OpenACS-URLs are available via GET requests, but as the associated actions are either not safe or not idempotent (or both), they should be made available only via POST instead...
This is more of a problem nowadays as it was earlier, as current browsers (like Chrome or Safari) tend to fetch resources even before the user hits enter in the address bar (i.e. one cannot easily prevent that an unwanted action is taken while entering a similar URL).
In particular the actual (Jan 2014) versions of Safari on Mac OS X 10.9.1 automatically pre-fetches URLs for an url path, when sub-pages were visited in the past, and a user clicks in the url bar (as soon as it shows possible completions). One can e.g. shut down "automatically" the OpenACS server by on /acs-admin/, since Safari might "prefetch" /acs-admin/server-restart.
This page is only a TODO list, that should become a bug report later...
Created by OpenACS community, last modified by Benjamin Brink 30 Jun 2017, at 06:56 AM
Here is some documentation on general OpenACS performance tuning:
Much performance tuning is targeted at the subsystems level, and so you will find some specific tuning information in these pages:
A broad scope of causes can be attributed to OpenACS performance issues. These forum threads help identify useful diagnostic techniques and accurate testing to help narrow the scope of problem areas etc.
Created by Rocael Hernández Rizzardini, last modified by Benjamin Brink 30 Jun 2017, at 06:53 AM
Usually you can do it with templates:
<property name="header_stuff">
....
</property>
But sometimes you want to add it not in just one page, so you usually go to www/site-master.adp, but that is not really good to maintain modularity, so instead, now you can define within your package a tcl callback like this:
ad_proc -public -callback subsite::get_extra_headers -impl my_implementation {} {
return the stuff that should go into the html headers
} {
set scripts "...."
set tags "...."
set text_to_return $scripts
append text_to_return $tags
return $text_to_return
}
Created by Nima Mazloumi, last modified by Benjamin Brink 30 Jun 2017, at 06:52 AM
Requirements: You have OpenSSL installed and created a certificate.
Assumptions:
For an alternative of pound, see Nginx with a sample configuration from Malte.
In order to use Pound for Load-Balancing and SSL encryption follow the below steps. Call "man pound" for a detailed description of the used parameters.
cd /opt/src
wget http://www.apsis.ch/pound/Pound-2.1.6.tgz
tar xzpf Pound-2.1.6.tgz
cd Pound-2.1.6
./configure
make
make install
emacs /usr/local/etc/pound.cfg/usr/local/etc/pound.cfg
User "root"
Group "users"
LogLevel 0
Alive 10ListenHTTPS
Address 1.2.3.4
Port 443
Cert "/www/service0/certs/certificate.pem"
xHTTP 2
HeadRemove "X-SSL-Request"
HeadRemove "X-Forwarded-For"
AddHeader "X-SSL-Request: 1"Service
URL ".*"
BackEnd
Address 127.0.0.1
Port 10000
End
End
End
emacs /www/service0/etc/config.tcl
set httpport 10000
set address 127.0.0.1
Created by irc community, last modified by Benjamin Brink 30 Jun 2017, at 06:47 AM
following dialog from irc (names changed..) shows how to trick the system to pass values from an include to the calling page. This trick needs to be turned into real documentation.
dave: you can't pass stuff up from an include
dave: you have to use upvar
dave: ie: something like this works
michael: but, yes, the order is important. i.e., if i pass a reference to an include and hope to get/use a modified value, the value will be there *after* the <include>
dave: here is what works :)
dave: if you pass a property to a master template
dave: like this
dave: <property name="foo">@foo</property>
dave: <include src="myinclude">
dave: you can upvar #[template::adp_level] foo myfoo
dave: set myfoo "something"
dave: and something will be passed up to the master
dave: but since the code is just one big script
dave: you can't modify code that happens before
dave: we discussed quite a few times a way to work around that
dave: you could upvar something which would be available AFTER the include in the script
michael: i can do the same thing by passing in a reference
dave: yeah
dave: i just though of tha t:)
dave: cool.
michael: and the value will be there after the include
michael: so i just have to move my <property> tags to the bottom of the adp
dave: although that should be documented somehow that an include is modifying stuff in the caller
dave: i don't think you do. I can't remember. did that ages ago for gp and that code is hopefully long gone :)
michael: yeah, i tried it dave:
dave: cool.
tektubby: aha! one of the 7 mysteries of OpenACS solved.
dave: putting property at the bottom works? pretty clever
michael: when referencing the variable (set to "") before the include, i get "" on the calling page
michael: after the include, i get the modified value
Created by Rocael Hernández Rizzardini, last modified by Benjamin Brink 30 Jun 2017, at 06:10 AM
The policy for .LRN is published at .LRN website: Accessibility Policy
Corresponding policy for OpenACS is currently being written and will be published soon.
The conformance level to be satisfied is explained in the "Accessibility Conformance Level" section of the .LRN Accessibility Policy.
The "Accessibility page" refered by the .LRN Accessibility Policy states the conformance level and its domain of aplication for each version of the software.
Note: Although automatic tools, such as TAW and "Cynthia says", may be useful to help the developer/author in addressing accessibility issues by providing informative reports, they can not certify the accessibility level of a page since many things need a manual review. Also, those tools won't be able to check a page protected by user and password (they would report on the login page, the one they can actually reach).
Once the requirements are met, to contribute your code follow these instructions (one of the two):
If you need more information on how to address accessibility, post your questions at the forums