Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml,v
diff -u -r1.13 -r1.14
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 27 Oct 2014 16:39:31 -0000 1.13
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 7 Aug 2017 23:47:54 -0000 1.14
@@ -22,22 +22,22 @@
Installing OpenACS packages
An OpenACS package extends your website and lets it do
- things it wasn't able to do before. You can have a weblog, a
+ things it wasn't able to do before. You can have a weblog, a
forums, a calendar, or even do sophisticated project-management
via your website.
- After you've installed OpenACS, you can congratulate
- yourself for a job well done. Then, you'll probably want to
+ After you've installed OpenACS, you can congratulate
+ yourself for a job well done. Then, you'll probably want to
install a couple of packages.
To install packages, you have to be an administrator on
- the OpenACS webserver. Log in, and you'll see a link to Admin or
+ the OpenACS webserver. Log in, and you'll see a link to Admin or
the Control Panel. Click on that, then click on 'Install
software'. Packages are sometimes also referred to as
applications or software.
- At this point, you'll need to determine whether or not
- you're able to install from the repository, or whether you
+ At this point, you'll need to determine whether or not
+ you're able to install from the repository, or whether you
should install from local files.
Basically, if you have a local CVS repository, or have
@@ -48,7 +48,7 @@
from Repository' or 'Install from Local'. Select the package,
and click 'Install checked applications'. The system will check
to make sure you have all necessary packages that the package
- you want depends on. If you're installing from Local Files, and
+ you want depends on. If you're installing from Local Files, and
you are missing any packages, you may have to add the packages
your desired package depends on:
@@ -71,23 +71,23 @@
Mounting OpenACS packages
- After you've installed your packages, you have to 'mount'
+ After you've installed your packages, you have to 'mount'
them in order to make them appear on your website.
Make sure you are logged in, and then click on the
'Admin' or 'Control Panel' link to get to the Site-Wide
- Administration page (at /acs-admin). Click on the subsite you'd
+ Administration page (at /acs-admin). Click on the subsite you'd
like the application to be available at.
Subsites are a way of dividing your website into logical
chunks. Often they represent different groups of users, or parts
of an organization.
Now click on 'Applications' (applications are the same
- thing as packages). You'll see a list of Applications and the
+ thing as packages). You'll see a list of Applications and the
URLs that each is located at. To mount a new application, you
click on 'Add application', enter the Application, title
- (application name), and URL (URL folder name), and you're
+ (application name), and URL (URL folder name), and you're
done.
Test it out now. The URL is based on a combination of the
@@ -109,7 +109,7 @@
Configuring an OpenACS package
- After you've installed and mounted your package, you can
+ After you've installed and mounted your package, you can
configure each instance to act as you would like.
This is done from the Applications page. Log in, go to the
@@ -127,7 +127,7 @@
Setting Permission on an OpenACS package
- After you've installed and mounted your package, you can
+ After you've installed and mounted your package, you can
configure each instance to act as you would like.
This is done from the Applications page. Log in, go to the
@@ -196,20 +196,20 @@
cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-subsite/www/index* /var/lib/aolserver/$OPENACS_SERVICE_NAME/www
- Edit the new index.adp to change the text; you shouldn't need to edit index.tcl unless you are adding new functionality.
+ Edit the new index.adp to change the text; you shouldn't need to edit index.tcl unless you are adding new functionality.
How do I change the site-wide style?
- Almost all pages on an OpenACS site use ACS Templating, and so their appearance is driven by a layer of different files. Let's examine how this works:
+ Almost all pages on an OpenACS site use ACS Templating, and so their appearance is driven by a layer of different files. Let's examine how this works:
A templated page uses an ADP/Tcl pair. The first line in the ADP file is usually:
<master>
- If it appears exactly like this, without any arguments, the template processer uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file.
+ If it appears exactly like this, without any arguments, the template processor uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file.
@@ -261,12 +261,12 @@
Finding the problem
- We start with the page that has the error. In the URL it's http://myserver.net/events/event-info.tcl, so open the file /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/events/www/event-info.tcl. It contains this line:
+ We start with the page that has the error. In the URL it's http://myserver.net/events/event-info.tcl, so open the file /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/events/www/event-info.tcl. It contains this line:
set can_register_p [events::security::can_register_for_event_p -event_id $event_id]
We need to know what that procedure does, so go to /api-doc, paste events::security::can_register_for_event_p into the ACS Tcl API Search box, and click Feeling Lucky. The next pages shows the proc, and we click "show source" to see more information. The body of the proc is simply
return [permission::permission_p -party_id $user_id -object_id $event_id -privilege write]
- This means that a given user must have the write privilige on the event in order to register. Let's assume that the priviliges inherit, so that if a user has the write privilige on the whole package, they will have the write privilege on the event.
+ This means that a given user must have the write privilige on the event in order to register. Let's assume that the priviliges inherit, so that if a user has the write privilige on the whole package, they will have the write privilege on the event.