Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp,v diff -u -r1.1 -r1.1.2.1 --- openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp 14 Feb 2019 09:36:39 -0000 1.1 +++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp 11 Mar 2019 08:43:27 -0000 1.1.2.1 @@ -22,14 +22,14 @@
Authorities
acs-authentication can have multiple authorities, each one
-represent an specific configuration of authenticatication. For
+represent a specific configuration of authenticatication. For
instance, in your openacs installation you can have users related
to different authorities, some of them might authenticate locally
since they are external or invited, others belongs to your
corporate network and already have users, so might authenticate
against LDAP and others in your own work office might use PAM for
authentication because your local system authentication. Plus you
-might define an specific implementation (using the set of SC) to
+might define a specific implementation (using the set of SC) to
connect to your client DB, which is in another DB, and allow your
clients login to certain parts of your website. Then, this is right
way to handle all those set of users, that already might have an
Index: openacs-4/packages/acs-automated-testing/www/admin/testcase.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-automated-testing/www/admin/testcase.adp,v
diff -u -r1.25 -r1.25.2.1
--- openacs-4/packages/acs-automated-testing/www/admin/testcase.adp 31 Jul 2018 11:49:49 -0000 1.25
+++ openacs-4/packages/acs-automated-testing/www/admin/testcase.adp 11 Mar 2019 08:43:27 -0000 1.25.2.1
@@ -20,7 +20,7 @@
@url_blurb;noquote@
Because the current test package uses in-memory variables
Index: openacs-4/packages/acs-core-docs/www/acs-core-docs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/acs-core-docs.adp,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/acs-core-docs/www/acs-core-docs.adp 7 Aug 2017 23:47:48 -0000 1.2
+++ openacs-4/packages/acs-core-docs/www/acs-core-docs.adp 11 Mar 2019 08:43:27 -0000 1.2.2.1
@@ -34,7 +34,7 @@
4
7 A The results of an automated test are optionally written to an
-xml file.
+XML file.
General overhaul of package management
Install-from-local and install-from-repository can be used to install the provided packages based on a acs-core installation. This means that also DotLRN can be installed from repository or -from local into an existing OpenACS instance.
Install-from-repository offers filtering functions, allows to +from local into an existing OpenACS instance.
Install-from-repository offers filtering functions, allows one to install optionally from head-channel (for packages not in the base channel of the installed instance). Install-from-repository works more like an app-store, showing as well vendor information
Packages can be equipped with xml-based configuration files
Index: openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp,v
diff -u -r1.6.2.1 -r1.6.2.2
--- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 2 Mar 2019 19:30:05 -0000 1.6.2.1
+++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 11 Mar 2019 08:43:27 -0000 1.6.2.2
@@ -184,7 +184,7 @@
TAG=1
# What release version are we building; version format should be
-# dashes rather than dots eg. OACS_VERSION=5-0-0b4
+# dashes rather than dots e.g. OACS_VERSION=5-0-0b4
OACS_VERSION=5-0-0b4
DOTLRN_VERSION=2-0-0b4
@@ -239,7 +239,7 @@
mkdir tarball
cd tarball
cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core
-mv opeancs-4 openacs-${OACS_VERSION//-/.}
+mv openacs-4 openacs-${OACS_VERSION//-/.}
tar -czf ../openacs-${OACS_VERSION//-/.}.tar.gz openacs-${OACS_VERSION//-/.}
cd ..
Index: openacs-4/packages/acs-core-docs/www/tutorial-specs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-specs.adp,v
diff -u -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/acs-core-docs/www/tutorial-specs.adp 10 Mar 2019 21:47:15 -0000 1.4.2.2
+++ openacs-4/packages/acs-core-docs/www/tutorial-specs.adp 11 Mar 2019 08:43:27 -0000 1.4.2.3
@@ -34,7 +34,7 @@
emacs. Examine the file. Find the version history (look for the tag
<revhistory>
). Add a new
record to the document version history. Look for the <authorgroup>
tag and add yourself as
-a second author. Save and exit.
Process the XML file to create html documentation. The html +a second author. Save and exit.
Process the XML file to create HTML documentation. The HTML
documentation, including supporting files such as pictures, is
stored in the www/docs/
directory. A Makefile is provided to generate html from the xml,
Index: openacs-4/packages/acs-lang/www/doc/i18n-design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-design.adp,v
diff -u -r1.7 -r1.7.2.1
--- openacs-4/packages/acs-lang/www/doc/i18n-design.adp 30 Apr 2018 08:19:34 -0000 1.7
+++ openacs-4/packages/acs-lang/www/doc/i18n-design.adp 11 Mar 2019 08:43:27 -0000 1.7.2.1
@@ -165,7 +165,7 @@
Message catalog lookups can be potentially expensive, if many of
them are done in a page. The templating system can already
-precompile and and cache adp pages. This works fine for a page in a
+precompile and cache adp pages. This works fine for a page in a
specific language such as foo.en.adp
, but we need to
modify the caching mechanism if we want to use a single template
Index: openacs-4/packages/acs-mail-lite/www/doc/imap-install.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/imap-install.adp,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/acs-mail-lite/www/doc/imap-install.adp 19 Feb 2018 18:33:47 -0000 1.2
+++ openacs-4/packages/acs-mail-lite/www/doc/imap-install.adp 11 Mar 2019 08:43:27 -0000 1.2.2.1
@@ -58,7 +58,7 @@
# aolserver4 recommends descriptors limit (FD_SETSIZE) to be set to 1024, # which is standard for most OS distributions - # For freebsd systems, uncomment following line: + # For FreeBSD systems, uncomment following line: ulimit -n 1024
Note: This does not fix any problem associated with a crash, only makes problem evaporate for low volume traffic sites.
Index: openacs-4/packages/ajaxhelper/www/doc/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/ajaxhelper/www/doc/index.adp,v diff -u -r1.2 -r1.2.2.1 --- openacs-4/packages/ajaxhelper/www/doc/index.adp 7 Aug 2017 23:48:03 -0000 1.2 +++ openacs-4/packages/ajaxhelper/www/doc/index.adp 11 Mar 2019 08:43:27 -0000 1.2.2.1 @@ -86,7 +86,7 @@ <a href="#" onClick="\@request;noquote\@">Send Request</a> -Consult the api-doc for more information about other parameters you +Consult the API-doc for more information about other parameters you can pass on to the ah::ajaxrequest proc.It is very important to note, that not all parameters and +
It is very important to note that not all parameters and features mentioned in this use case should be displayed to the user at all times. Depending on the use case, a good guess with pre determined parameters should be made for the user (e.g. no need to Index: openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp,v diff -u -r1.5 -r1.5.2.1 --- openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp 4 Aug 2018 09:34:07 -0000 1.5 +++ openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp 11 Mar 2019 08:43:27 -0000 1.5.2.1 @@ -23,7 +23,7 @@ Depending on the settings, the display of the assessment will vary:
The root folder is a "super folder" for all the files in that specific instance of file-storage, and it is created -automatically when the file-storage package is instanciated.
+automatically when the file-storage package is instantiated.When a user wants to make an attachment to an object in your package, she is shown the contents of the file-storage root folder mapped to your package instance. The user is also given the option @@ -66,8 +66,7 @@ instance of attachments in the entire system. The same instance is just re-mounted)
First, you must select a file-storage instance that will provide the files you can attach. If you do not already have an instance of file-storage that you want to use for your package instance, you Index: openacs-4/packages/calendar/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/calendar/www/doc/requirements.adp,v diff -u -r1.4 -r1.4.2.1 --- openacs-4/packages/calendar/www/doc/requirements.adp 30 Apr 2018 13:54:22 -0000 1.4 +++ openacs-4/packages/calendar/www/doc/requirements.adp 11 Mar 2019 08:43:27 -0000 1.4.2.1 @@ -20,7 +20,7 @@ people to keep track of events as they normally would on a paper calendar while giving them the opportunity to share these events with other parties. Various types of additional information related -to a calendar item, such as an URL, a map indicating a +to a calendar item, such as a URL, a map indicating a meeting's location, et cetera, can also be managed through the Calendar application. The Calendar application also provides different end-user specifiable presentation formats for viewing Index: openacs-4/packages/general-comments/www/doc/design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/general-comments/www/doc/design.adp,v diff -u -r1.4 -r1.4.2.1 --- openacs-4/packages/general-comments/www/doc/design.adp 24 Jul 2018 19:07:28 -0000 1.4 +++ openacs-4/packages/general-comments/www/doc/design.adp 11 Mar 2019 08:43:27 -0000 1.4.2.1 @@ -66,7 +66,7 @@ recording and editing user comments. An optional return_url can be specified which will be provided as a link to the user within the general-comments pages. This is useful for the user to return to the original page after making a comment.
The other procedure, general_comments_create_link, is a wrapper procedure -that returns an html fragment for a link which points to the +that returns an HTML fragment for a link which points to the location of the mounted general_comments package. There are various switches that will be useful to package developers:
Index: openacs-4/packages/news/www/doc/design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/news/www/doc/design.adp,v diff -u -r1.7 -r1.7.2.1 --- openacs-4/packages/news/www/doc/design.adp 8 Feb 2019 13:00:50 -0000 1.7 +++ openacs-4/packages/news/www/doc/design.adp 11 Mar 2019 08:43:27 -0000 1.7.2.1 @@ -212,7 +212,7 @@ first column of the table), is shown. For example, bulk-archiving and deleting of published items can be effected in this way. For archived items, one can re-publish or delete them. -
Note, that releasing/revoking can be done for an item +
Note that releasing/revoking can be done for an item individually as well, following the ID# link in the second column which leads to /admin/item. On that page, a new revision can be added. There is no UI to edit a revision; A new revision Index: openacs-4/packages/oacs-dav/www/doc/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/oacs-dav/www/doc/index.adp,v diff -u -r1.5 -r1.5.2.1 --- openacs-4/packages/oacs-dav/www/doc/index.adp 17 May 2018 14:19:23 -0000 1.5 +++ openacs-4/packages/oacs-dav/www/doc/index.adp 11 Mar 2019 08:43:28 -0000 1.5.2.1 @@ -58,7 +58,7 @@
oacs_dav::handle_request determines the package_id that should
handle the URI. This is based on the standard OpenACS site_node Tcl
API. After the package is found, the root folder for that package
-is retreived from the dav_package_folder_map table. Using the
+is retrieved from the dav_package_folder_map table. Using the
folder_id, and the URI of the request, the
content_item__get_id
pl/sql(plpgsql) procedure is
called to find the item_id for the request. If no item_id is found
Index: openacs-4/packages/richtext-xinha/www/resources/xinha-nightly/plugins/OacsFs/popups/insert-image.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/richtext-xinha/www/resources/xinha-nightly/plugins/OacsFs/popups/Attic/insert-image.adp,v
diff -u -r1.3 -r1.3.2.1
--- openacs-4/packages/richtext-xinha/www/resources/xinha-nightly/plugins/OacsFs/popups/insert-image.adp 29 Mar 2018 08:15:53 -0000 1.3
+++ openacs-4/packages/richtext-xinha/www/resources/xinha-nightly/plugins/OacsFs/popups/insert-image.adp 11 Mar 2019 08:43:28 -0000 1.3.2.1
@@ -63,7 +63,7 @@
var f_url = document.getElementById("f_url");
var url = f_url.value;
if (!url) {
- alert("You have to enter an URL first");
+ alert("You have to enter a URL first");
f_url.focus();
return false;
}
Index: openacs-4/packages/rss-support/www/doc/bboard.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/rss-support/www/doc/bboard.adp,v
diff -u -r1.2 -r1.2.2.1
--- openacs-4/packages/rss-support/www/doc/bboard.adp 7 Aug 2017 23:48:29 -0000 1.2
+++ openacs-4/packages/rss-support/www/doc/bboard.adp 11 Mar 2019 08:43:28 -0000 1.2.2.1
@@ -11,11 +11,11 @@
/rss
). Note that
-rss-support is a service package and a singleton.impl_id
as follows
select acs_sc_impl__get_id('RssGenerationSubscriber','bboard_forum'); Index: openacs-4/packages/dotlrn/tcl/community-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/tcl/community-procs.tcl,v diff -u -r1.234.2.2 -r1.234.2.3 --- openacs-4/packages/dotlrn/tcl/community-procs.tcl 1 Mar 2019 11:04:53 -0000 1.234.2.2 +++ openacs-4/packages/dotlrn/tcl/community-procs.tcl 11 Mar 2019 08:44:11 -0000 1.234.2.3 @@ -1289,7 +1289,7 @@ {-drop_target deregister} {-only_member_p 0} } { - Returns a html fragment of the subcommunity hierarchy of this + Returns a HTML fragment of the subcommunity hierarchy of this community or if none, the empty list. Brief notes: this proc always shows the subgroups of the Index: openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl,v diff -u -r1.72.2.2 -r1.72.2.3 --- openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl 1 Mar 2019 13:58:40 -0000 1.72.2.2 +++ openacs-4/packages/acs-api-browser/tcl/acs-api-documentation-procs.tcl 11 Mar 2019 08:45:13 -0000 1.72.2.3 @@ -296,7 +296,7 @@ ad_proc -public api_type_documentation { type } { - @return html fragment of the API docs. + @return HTML fragment of the API docs. } { array set doc_elements [nsv_get doc_type_doc $type] append out "$type
\n"