Contents
1. Introduction
1.1 Features
1.1.1 Areas features
1.1.2 Site features
1.1.3 Alerts features
1.2 Assumptions
2. Configuration Manager overview
3. Areas
3.1 Areas overview
3.2 Add an area
3.3 Edit basic properties of this area
3.4 Configure theme 'Theme Name' for
area n
3.4.1 Bazaar Style Style at
area level
3.4.1.1 A new
header for your school
3.4.2 Bazaar Style Style at
page level
3.5 Reset properties of theme
themename for area n (Area Name)
3.6 Delete an area
4. Site
4.1 Site configuration
5. Alerts
6. Concluding remarks
With the Configuration
Manager Areas, the overall site configuration and Alerts are managed.
The Area Manager
has the following features, in no specific order:
- Bazaar Style Style: Edit layout and style at Area
level and enable/disable BSS at section and page level. For an introduction
to BSs see appendix 4.2
Bazaar Style Style.
- Areas (general): An Area is separate part of the
website. To a visitor of the website an Area appears as a site on its own.
Areas can be public (accessible to everyone) or private.
Private Areas (also called Intranets) are only accessible with a login name
and a password.
- Set Public/Private: Once an Area is created (either
public or private) the choice cannot be made undone.
- Set Active/Inactive: Any time public and private Areas
can be set to active or inactive and vice versa. Inactive
means that pages and sections in that the Area are completely inaccessible,
even if the URL's are known.
- Merge/Split: The content of Areas can be merged to
other Areas . An Area can also be split into more Areas. Merging or
splitting are done in the Page Manager (edit advanced properties).
- Add: Add an Area to the site, set its name, select
public or private Area, set data folder name, select theme for the
Area.
- Basic properties: Edit the basic properties of the
area: name, area active/inactive, add metadata to the pages in the Area,
select the theme for the area.
- Theme Configuration: Configure the options for the
chosen theme. The available options depend on the chosen theme. Please see
the Table of contents for the
available themes.
- Reset theme: Reset the theme to its default values.
This feature is for pupils that learn CSS. When they have created a mess,
they can copy return.
- Delete: Delete an Area. The Area must be empty, i.e.
all sections and pages must be moved or deleted.
- Home: Set the Area as the 'home' i.e. starting
point of the site.
- Sort order: In the list of Areas the desired order can
be set.
In fact, every
configuration option is a feature. No need to list them here. Please see the
paragraph 4. Site where all
configurations options are discussed.
Not yet
implemented. At this moment the person that installed Website@School receives
alerts.
This chapter elaborates
on other chapters. We assume you have read and done the
General part of the Table of Contents.
(top)
Click the
Configuration Manager
icon, to open the Configuration
Manager dialogue:
![[ Configuration Manager ]](configurationmanager/configurationmanager_overview.png)
configurationmanager_overview.png
Explanation:
-
Menu: Pane with an overview of the selectable managers:
- Areas: Clickable link to
the Area manager, discussed in 3. Areas.
- Site: Clickable link to
the Site manager, discussed in 4. Site.
- Alerts: Clickable link
to the Alerts manager, discussed in 3. Alerts.
- Workplace: Pane to manage the various options of the
managers. No manager selected.
(top)
Areas resemble sites; to the site
visitor Areas appear as separate sites. This paragraph discusses adding
Areas, editing their properties, the Areas' theme configuration and
deleting Areas.
In the Configuration
Manager Menu, select Areas to
enter the Areas dialogue:
![[ Areas, list ]](configurationmanager/configurationmanager_areas_overview.png)
configurationmanager_areas_overview.png
The list of areas is shown, the Areas link is underlined.
Explanation:
- Add an area: Link to the
Add an area dialogue. See paragraph Add an Area.
-
Home icon: A visible home icon indicates the default
(opening) area of the site. Greyed out home icons indicate that these
areas are not the opening ones.
NOTICE:
When no Home icon is set, the Area with the lowest number in the sort
order will be the opening Area. For Sort order, see paragraph Edit basic properties of this
area.
- Trashcan icon: To delete an area, it must be empty
and.
Deleting an area is further discussed in section 4.6 Dele an area
- Pencil icon: Clickable link that gives direct access
to the theme configuration. See paragraph 3.4 Configure theme 'themename' for
area nn.
-
(public/private )Name of the area (nn,nn)
(inactive): One clickable link that gives direct access
to Edit basic properties of an area, see paragraph
4.3 Edit basic properties of this
area.
The different parts of this link refer to:
- (public/private): Whether this is a public or a private
area.
- Name of the Area: The Area name will be displayed on the
website.
- (nn,nn): The first number indicates the number of the area. It is
given to the area when the area is created. The last number indicates
the sort order in this row.
- (inactive): The site is not operational, invisible and cannot be
found, even when the URL is known.
To add an area, in
Areas click Add an area to enter
the Add an area dialogue:
![[ Add an area, entry fields ]](configurationmanager/configurationmanager_area_add.png)
configurationmanager_area_add.png
Explanation:
- Name: Enter the name of the Area. The
name may contain dicritical characters. Enter at least a space; this
produces no name at all. Useful in some themes.
-
Private area [ ] Mark this area as private
(cannot be changed later on): A private are is a non-public
area, i.e. an Intranet, only accessible with a username and password.
NOTICE:
Take care! Once an area is selected as a private area, it cannot be
changed to a public area. Also, when an area is selected as public, it
cannot be changed to a private area. This is a security feature.
-
Data folder: Enter the name of the data
folder for this area.
Keep the name short and descriptive, e.g. no more than 12 (lowercase)
letters and digits and no spaces or punctuation characters. Best practice
is to limit the mane to lowercase letters, digits and underscores.
If the name is not acceptable, this results in an error message.
Website@School tries to construct a suitable directory name based on your
input. If this occurs, accept the suggested name or enter a name that is
acceptable and click [Save].
Every area has an associated data directory. In general files that
belong to an area should be stored in this directory. Note that every
user also has a personal data directory. This directory should be used
for personal files only, and not for files related to the area.
-
Theme: In the dropdown menu a theme for
this area can be selected.
A theme is a set of configurable properties. Together the configured
properties define the visual appearance of an area. The configuration of
the properties is done in the Configure theme 'themename'
for are n dialogue, see 3.4 Configure theme 'themename'
for area n.
The theme can be changed to another theme. The old theme and its
configured properties are retained, so you can return to the previous
theme and it's configured properties, provided you have not
reset it's configuration to default values. In this way, one theme
can have many configurations of its properties, thus quite differing
visual appearances.
- Save: To save your results. After saving your results,
the newly created area will appear in the list of areas.
- Cancel: To cancel your action and return to the Areas
overview.
After saving, the Area is added:
![[ Areas, message= success, area added ]](configurationmanager/configurationmanager_area_addded.png)
configurationmanager_area_addded.png
NOTICE:
Do not forget to add a page to the area. If no page is added, this results in
a painful message for the visitors:
![[ Fatal error, error code 080 ]](configurationmanager/configurationmanager_area_addded_no_page.png)
configurationmanager_area_addded_no_page.png
In the Areas overview, click on the
(public/private )Name of the area (nn,nn)
(inactive) link to open the Edit basic properties of
this area dialogue:
![[ Edit basic properties of this area, entry fields ]](configurationmanager/configurationmanager_area_basic_properties_edit.png)
configurationmanager_area_basic_properties_edit.png
In the Menu the Basic
properties link is underlined.
Explanation:
- Name: The name of the area can be
changed. The name may contain dicritical characters.
-
Active area [ ] Mark the area as
active: - Active: an area must be active before
any files can be served.
- Inactive: if an area is inactive, it is as if it does not exist.
But, the rule of thumb is: everything is public except what is not
public, so please read the notice below.
NOTICE:
1. In general any file in the data folder of any active public area
can be retrieved by anyone as long as the name of the file is
known.
2. If an area is inactive, no files can be retrieved, even if
the name of the file is known. In other words: once an area is inactive,
to a visitor it appears that neither the area nor the files exists anymore.
NOTICE:
The same active/inactive conditions also apply to pages in
areas. Once an area is inactive, to a visitor it appears that the pages
in that area no longer exist. Even if the URL of the page is known, the
page cannot be retrieved.
- Private area [ ] Mark the area as private
(cannot be changed later on): The checkbox is greyed out, i.e. you
cannot use this option. Once an area has been selected as public or private
in 4.2 Add an area, this
selection cannot be undone.
- Data folder (pathname cannot be
changed): Once set in 4.2
Add an area, this path cannot be changed.
- Metadata: Here valid HTML code can be
added as it is used between the >head< and </head> tags. The
code added here can be understood by search engines. For an overview of
possibilities and exaggerated expectations see for example http://searchenginewatch.com/2167931
and for an explanation http://www.w3schools.com/tags/tag_meta.asp
- Sort order: The order in the list of
areas, as shown in the Areas overview and the Page
Manager overview. It's the second number in the name of the
Area. With every created area the number is increased with 10, enabling you
to add other numbers in the row, thus creating an easy to use list.
When the sort order numbers were changed, the user has to logout and login
again to have access to the Page Manager.
- Theme: To change the theme. When
changing to another theme, the old theme configuration of the area is
retained, so it's possible to go back to the previous theme and its
configuration.
- Save: To save your results and return to the Areas
list.
- Cancel: To cancel your action and return to the Areas
list.
Here the properties of the previously chosen theme can be
configured. Each theme has its own configuration options, which are discussed
in their respective chapters. Please go to the Table of contents, paragraph Themes and select
the chosen theme to configure its theme specific options.
Each theme has a set of special options that are the same for every theme:
the 'Bazaar Style Style' (BSS). This subject is discussed in appendix
4.2 Bazaar Style Style.
Below we only explain the technical details and give examples of its
usage.
We will discuss BSS with the Frugal theme as example. The
functionality of BSS is the same in every theme.
![[ Configure Theme 'Theme Name' for area n, boot part ]](configurationmanager/configurationmanager_area_configure_theme-bottom.png)
configurationmanager_area_configure_theme-bottom.png
Explanation:
-
Static style sheet usage [ ] Use static
stylesheet file:
- Checked: a style sheet is used. In the above screenshot the Frugal
style sheet is program/styles/base.css. You can study this
stylesheet with your browser by going to
http://exemplum.eu/program/styles/base.css.
All other theme style sheets can be found at
http://exemplum.eu/program/themes/<themename>/style.css
- Unchecked: No static stylesheet is used. In this case, and if no
other style is used, the browser defines the style.
- Static stylesheet: Location of the
static style sheet file.
-
Extra style usage (area) [ ] Use extra style at
area level:
- Checked: Extra style at Area level can be applied.
- Unchecked: No extra style at area level. If in the next field style
information is given, it's not applied.
-
Extra style at area level: A brief
explanation on the meaning of what you see:
![[ CSS explanation. Selector, property and value ]](configurationmanager/configurationmanager_area_css_explanation.png)
configurationmanager_area_css_explanation.png
-
In the above screenshot, the:
- Comment is everything between /* and */,
- the Selector is 'content with header size h1'. The content
is the page content. Headers with the size 'h1' are the biggest
ones, and
- the Declaration defines what is affected and how it's affected:
'background-color: #FF33FF'. The Declaration always consists of
a property and value pair:
- Property 'background-color' with the
- Value #FF33FF is the color
purple. For example #000000 is black and #FFFFFF is white. Look in
Google under 'hexadecimal color schemer'.
Please try it out yourself. Open the Welcome page with the CKeditor.
In the CKEditor select in the Format menu Heading
1. Type someting and save your work. It could look like:
![[ Frugal theme, purple header ]](configurationmanager/configurationmanager_area_frugal+purple.png)
configurationmanager_area_configure_area_frugal+purple.png
To some, the header h1 has an awful font background color.
When you are using another theme, here is the code to copy and paste
into the theme. However, you learn more by typing it yourself.
/* Demo of Bazaar Style Style sheets */
#content h1 {
background-color: #FF33FF;
}
|
- Extra style usage
[ ] Allow node level style information (Bazaar
Style Style):
-
- Checked: Extra style at page/section level is possible end is shown
on the sections/pages.
- Unchedked: No extra style. If style is applied in sections and
pages, it is not visible in the area.
This BSS feature enables the school to have several themes in one
area, For example: Sophia for the school, Frugal for the pupils of Grade
8, and; within this area for herbert's poetic pages Schoolyard, except for the
cat poem which uses a modified version of the Axis theme. In paragraph
3.4.2 Bazaar
Style Style at page level we will show you how this is done.
- Save: To save your results. After saving your work,
you return to the Areas list.
- Cancel: To cancel your action and return to the Areas
list .
In the next paragraph we will do something more fruitful for the school.
Preparations:
Take a picture. The picture is 3233 KB. Downloading such a big sized image
takes very long on the internet. Resize it with multi-language freeware
Irfanview or any
other image resize program to 1024 x 768 pixels (1229 KB as .png file):
![[ �mage of EPS school ]](configurationmanager/configurationmanager_EPS-1024x768.png)
configurationmanager_EPS-1024x768.png
With a screen capture program, for example multi language freeware
MWSnap or any other screen capture program, resize the picture
to a height of 150 pixels. Save as EPS-1024x150.png:
![[ part of image from EPS school ]](configurationmanager/configurationmanager_EPS-1024x150.png)
configurationmanager_EPS-1024x150.png
Upload the file to the Exemplum Primary School data folder
areas/exemplum.
Here we go:
Open a browser as a normal visitor of the site of the Exemplum Primary
School with the Frugal theme and, in the browsers menu bar and sub-menus,
look for the option 'Page Source'. Use that option to to take a peek
at the source code of the page:
<body>
<div id="top">
</div>
<div id="page">
<div id="header">
<div id="logo">
---> In your browser the line below is veeery long: <a href="/in... 71"></a>, so we splt it.
<a href="/index.php/area/1/Exemplum_Primary_School.html">
<img src="/program/graphics/waslogo-284x71.png"
title="Exemplum Primary School"
alt="image of logo" width="284" height="71"></a>
</div>
<div id="quicktop">
<a href="/index.php/18/About_our_school.html" title="About our school">about</a>
<a href="/index.php/19/How_to_contact_us.html" title="How to contact us">contact</a>
</div>
<h1>Exemplum Primary School</h1>
</div>
---> Here the breadcrum trail starts.
|
This is the upper side of the theme Frugal, i.e. the 'header'
seciton. Try to make sense of the code. If you don't understand it, no
problem, you will in due course.
Previously, we have created an image of the school. It's size is
1024x150 pixels. With the File Manager we have uploaded the image to the
Exemplum Primary School data folder areas/exemplum. In the next
piece of code the Website@School logo is not displayed and the image is
put in the header. Cut and paste it below the
other code about an awful color.
NOTICE:
'Do not forget to change the file path. Your school is not the Exemplum
Primary school...
/* Do not display the Website@School logo */
#logo { display: none;
}
/* Image of EPS in header */
#header {
background-image: url('http://exemplum.eu/file.php/areas/exemplum/EPS-1024x150.png');
background-repeat: no-repeat;
border: 1px #00F dashed;
height: 150px;
}
|
We only show the header, breadcrum trail and sections:
![[ Top of site with example code ]](configurationmanager/configurationmanager_BSS_example.png)
configurationmanager_BSS_example.png
We have put a dotted border around the area that is covered by the
'#header' area. The white space is used for the 'quicktop'
links. That's not exactly what we want.
We have to take a peek in the code to see how that whitespace is created.
The Frugal base.css is located at program/styles/base.css
as can be seen in the 'Static style sheet' field in the Theme configuration.
Point your browser at http://yourschool.org/program/styles/base.css.
You see the code in the base.css file. Look for:
#quicktop {
height: 20px;
background-color: #FFF;
text-align: right;
font-size: 0.95em;
padding-left: 210px;
padding-right: 210px;
}
|
We have to get rid of those 20 pixels to make room for the image. And
since we are here, the font color makes the name of the school rather
illegible, just as the black of the 'about' and 'contact'
links, once the school image fits. So we add:
/* no space for quicktop */
#quicktop {
height: 0px;
}
/* Yellow school name */
#header h1 {
font: #FF0;
}
/* Yellow toplinks */
#quicktop }
font: #FF0;
}
|
This results in:
![[ Top of site with example code ]](configurationmanager/configurationmanager_BSS_example-2.png)
configurationmanager_BSS_example-2.png
Hm, not bad, but... After some fiddling, i.e. positioning the name of the
school and struggling with this piece of code in
program/styles/base.css:
#quicktop a:link,
#quicktop a:visited {
text-decoration: none;
color: #000;
background-color: #FFF;
}
|
cleaning up a bit and bringing some order, we now have:
/* No Website@SChool logo */
#logo { display: none;
}
/* Image of EPS in header */
#header {
background-image: url('http://exemplum.eu/file.php/areas/exemplum/EPS-1024x150.png');
background-repeat: no-repeat;
height: 150px;
}
/* More space for quicktop font and
transparent background */
#quicktop {
height: 40px;
background-color: transparent;
}
/* Yellow school name, size and position */
#header h1 {
color: #FF0 ;
font-size: 2em;
position: absolute;
top: 100px;
left: 5px;
}
/* Yellow colore and transparant
background for picture */
#quicktop a:link,
#quicktop a:visited {
text-decoration: none;
color: #FF0;
font-size: 2em;
background-color: transparent;
}
|
Another idea: get rid of the header and create a drawing of 1024 x 150
pixels with the name of the school calligraphed. Maybe for Herbert's
'cat' theme.
/* No Area title in header */
#header h1 {
display: none;
}
|
How to learn more about BSS and CSS
- The most important source of information is the Static
stylesheet. For theme Frugal it's located at
program/styles/base.css. You can find it by visiting
http://yourschool.org/program/styles/style.css. For all
other themes, you find the style.css in
http://yourschool.org/program/themes/<themename>.
- There is an excellent site where you can find the basics of Bazaar
Style Style. Do the free online course and become an expert. http://www.w3schools.com/css/. Have
fun!
- Last but not least, everything you need to know on the subject can be
found on the Internet. Look for CSS.
Each page/section has its own Bazaar Style Style feature.
![[ Extra style at page/section level ]](configurationmanager/configurationmanager_area_page_level_bss.png)
configurationmanager_area_page_level_bss
Whether style information from pages or sections is passed to the browser
or not is dependent on the checked/unchecked box at 'Extra style usage
(node).
Example:
- Make sure that 'Extra style usage' is checked in the EPS
Area.
- Cut the code from the 'Extra style at area level' in the EPS
Area.
- Go to the Page Manager, click Maximal, the tree expands
- Click on the page icon of section 'News(8). The Advanced dialogue opens.
- In the Edit advanced properties of section 8 in the
field 'Extra style at page/section level', paste the code you
copied from the EPS Area.
- Save your work.
- Go to the EPS home site. It has its basic style.
- Click 'News'
![[ EPS news ]](configurationmanager/configurationmanager_EPS_news.png)
configurationmanager_EPS_news.png
All pages under the section 'News' have the modfied header.
Resetting the theme properties restores the
properties as they were set during the installation of the theme.
NOTICE:
Take care! It is a good idea to copy and paste complex style information to a
safe location before resetting a theme.
NOTICE:
In general it's a bad idea to delete an area. Maybe it contains content
that now seems useless but that might become useful in a year or so. Maybe
it's a better idea to rename the area as Archive: [old
areaname], make the Area inactive and put it at the bottom of the
list of Areas.
To delete an area, in the Areas overview, click the
Trashcan icon to open the Confirm delete of area Area
Name dialogue:
![[ Confirm delete of area Exemplum Parents ]](configurationmanager/configurationmanager_area_delete.png)
configurationmanager_area_delete.png
- Delete: To delete your work and return to the area
managers main screen.
- Cancel: To cancel your unwise action and return to the
Page Manager main screen.
(top)
In the Site
configuration the global parameters for the complete site
are set. In a normal school situation it's not necessary to change any of
these values.
NOTICE:
If you do not know what you are doing here, it might be better to leave the
Site configuration untouched.
In the
Menu, select Site to enter the
Site configuration dialogue:
![[ Site configuration, entry fields. Page bottom ]](configurationmanager/configurationmanager_site_configure-bottom.png)
configurationmanager_site_configure-top.png
configurationmanager_site_configure-bottom.png
Explanation:
-
Internal version number (do not change): Website@School
has two version numbers:
- An external version number: i.e. the release number, for example
0.90.0.
- An internal version number: for example 2011010100. This number is
composed as yyyy-mm-dd-serialnumber. It indicates the version of the
database structure. As soon as the database structure is changed, this
version number also changes. Do not change the number because it's is
used when installing updates.
See also chapter Tools,
paragraph 6. Update
Manager.
- Security code: Its'a SALT. In cryptography, a salt
consists of random bits that are used as one of the inputs to a key
derivation function. The security code is a quasi random generated string.
Each Website@School installation has its unique security code. This feature
makes the session key unique, which adds extra security to passwords and
prevents taking over a session. It's a security feature.
- Session name: WASDATA is the name of the session
cookie. Changing this name adds a bit of extra security. After changing the
name, it's necessary to log out and log in again.
-
Session expiry interval (seconds, default 86400):
Defines when a user session is timed out, in this case after 86400
seconds, i.e. one day. After one day of user inactivity, the session is
timed out, the user is logged out and an error message is displayed.
Also see chapter Logging in and
out, paragraph 4. Error
messages.
The expiry interval can be a point of discussion. It can be lowered,
in which case the risk of losing work becomes higher. It can be extended
which blocks a page in use longer, resulting in error messages for
another users who want to edit that page.
NOTICE:
The best option is to leave it as it is and to save! your
work often and/or deploy some other activity in Website@School management, in
which case the session time is renewed, every time you click
something.
- Maximum allowed login attempts (default 10): After a
maximum of 10 wrong logins, the user is asked if he wants to go to the
'Forgotten your password? procedure. If he persists in logging in, he
is blacklisted. See items below. This is a security feature.
- Login failures interval (minutes, default=12): The
time window in which the blacklist is consulted before deleting a users
failed login attempts. So, a user has to wait 13 minutes before he can
undertake a new login attempt. This is a security feature.
-
Valid bypass interval (minutes, default 30): This item
refers to the 'Forgotten your password?' procedure.
After sending the first mail, containing the one time code, the user has
30 minutes to read and enter the one time code. If the time is exceeded,
the one time code expires.
After the one time code is successfully entered, a second email is sent
with the temporary password. Again there is 30 minutes time to renew the
password. If the time is exceeded, the temporary password expires. This
is a security feature.
NOTICE:
It's easier to remember your password than to do the forgotten
password procedure. For details, also see chapter Logging in and out, paragraph 3. Forgotten your password?.
- Blacklist interval (minutes, default 8): The time a
user is put on the blacklist. In this period, the system is unaccessible
for that user.
- Website title: The text between the <title> and
</title> tags. This title is only visible in Website@School
Management and in the browser title bar. The title is not visible on the
site. This field may be left empty. In that case it is not shown in the
browser. This is a feature for users with a braille terminal or screen
reader.
-
Website From: e-mail address: This e-mail address is
used for outgoing mail, e.g. alerts and password reminders.
This feature enables a From: address that differs from the Reply-to:
address. The From: address must be a valid e-mail address from the
sending mail server.
This is a useful feature when Website@School is installed at an ISP
(Internet Service Provicer) that uses an address like exemplum@isp.com, in
case the ISP has no vadid address for the webserver at that domain. Also
read the next item below.
For details, see RFC 5322: Internet Message Format on http://tools.ietf.org/html/rfc5322.
- Website Reply-To: e-mail address: For example the
webmaster Wilhelmina Bladergroen: w.badergroen@exemplum.eu, or
webmaster@exemplum.eu if you prefer a functional address.
-
Default language (2-letter lowercase code, default
'en'): The language that is used in the login screens and
on the site itself, e.g in the [Go] button in the Areas dropdown menu.
Also see chapter Tools,
paragraph 3.2 Add a new
language where the two letter code is used when adding a new
language.
NOTICE:
After logging in, the user can have her preferred language, also see
chapter Account
Manager, under 3.2.1 Basic, under Lanuage and Redirection
(where to go after login).
- Number of items per screen (in long lists): This
feature cuts long lists in manageable screens, for example in lists like
the Log viewer in the Tools Manager, or the list of all users in the Account
Manager.
- Maximum number screens (in long lists): An intuitive
feature to easily browse and search in lists. Instead of a long explanation
observe this example:
< 1 2 3 4 5 6...>
Page 4 is visible now and is in the invisible 'window' that tries
to keep the used page in the middle of the row for easier searching and
navigation. Try it and enjoy.
-
Default editor: When a user is created, this is the
default editor.
Three editors are available:
- CKEditor: the default WYSIWYG (What You See is What You Get)
editor, also the best choice for blind and visually impaired. What a
difference one character makes :-).
- FCK editor: a WYSIWYG editor for older browsers.
- Plain editor (Text Area), to edit plain HTML.
In the user properties a user can select her preferred editor. Also see
chapter Account
Manager, paragraph 3. Users.
NOTICE:
- With a new installation, the FCEditor is selected as default.
- With an upgrade the existing accounts keeps their selected editor
(FCKeditor or Plain editor). New accounts get the editor as set in
Configuration > Site.
- In case of an upgrade, the default editor is only changed to CKEditor
if the FCKeditor was the previous default editor. If the Plain editor was
selected in the previous version, the default editor stays Plain.
Obviously the webmaster had good reasons for selecting it.
-
Use proxy friendly URLs:
- Proxy friendly: Produces a file path like, for example
/file.php/areas/exemplum/image.png.
- Proxy unfriendly: produces a file path like, for example:
/file.php?file=/areas/exemplum/image.png
Why proxy friendly? Many proxy servers see the question mark in the
path as dynamic data which they do not buffer because 'dynamic'
means the data can differ after each request.
However, an image is static data and thus does not change. When the
question mark is in the path, the proxy server will still request the
image from the server, over and over again.
This feature is useful, for example in a school with Website@School
installed at an ISP that has little or expensive bandwidth. If the school
has a proxy server, each time pupils request a certain page with static
data, the server gets it from the proxy servers cache and not from the
server somewhere on the web.
NOTICE 1:
Proxy friendly URL's do not function at the Dutch ISP XS4ALL. Also see
Appendix A: XS4ALL
installation. NOTICE 2:
Advice: leave it on proxy friendly, unless your webserver has
trouble working with virtual paths and links in pages are unaccessible.
NOTICE 3:
Do not change this setting after your Website@School installation is
already in use for some time. It could be the case that you have to
update a lot of links. After the installation, check if proxy friendly
URLS's function. If not, uncheck the box. Then create users.
-
Fully qualified path to CLAMAV virusscanner program:
During the installation, the install wizard tries to find the path to the
free (not as in beer) CLAMAV virus scanner, but not other virus
scanning software. If found
clamdscan is the first
preference because of it's speed. Otherwise, if available
clamscan is used. If one of them is found, the box (see
below) is automatically checked.
If, for some reason, the box is checked and the virusscanner
does not function, this results in an error message.
NOTICE:
It's a good idea to check the virusscanner after installation. Also
see chapter Installation,
paragraph 4. After the
installation.
- [ ] Scan files for viruses on upload: See above. If
unchecked files are not scanned on upload. This is a security risk. On a
schoolserver it's virtually impossible to prevent the upload of
malicious material.
- Maximum number of files per upload (non Java): That
says exactly what it is. Also see chapter File Manager, paragraph 3. Managing files.
- Maximum height and width for thumbnails: Thumbnails
are automatically created [1] for the FCK editor in a 100 pixels square, in
which the image always retains its aspect ratio. The longest side, either
horzontal or vertical, is reduced to 100 pixels. This keeps thumbnailed
images undistorted and image lists in a proper, well spaced row. [1] If
supported by GD, see the next item.
-
List of allowable extensions in File Manager(comma
delimited): Only allowed extensions, entered comma
separated with no spaces.
NOTICE:
Thumbnails are created with the GD support. Also see chapter Installation, paragraph 2.7 Compatibility which image
extensions are supported.
NOTICE:
It is a good idea to only allow images that are supported by GD. By
preventing the upload of unsupported images, for example .bmp, uploading
and displaying on the internet will be faster. Use a program like Irfanview http://www.irfanview.com/ to resize,
convert and manipulate images
Also see chapter Editors,
paragraph 2. FCK
editor.
-
List of extensions recognised as images
(comma-delimited): Only allowed extensions, entered
comma separated with no spaces.
The FCK editor recognizes images and shows them as thumbnails
when inserting. Unrecognised images extensions, for example
.bmp are shown as question marks and not as thumbnails. Also
see chapter Editors,
paragraph 2. FCK
editor.
-
List of extensions recongised as flash
(comma-delimited): Only allowed extensions, entered
conna separated with no spaces.
The FCK editor als recognises the flash extension.
Also see chapter Editors,
paragraph 2. FCK
editor.
- [ ]Add new pages/sections at the end: Default,
newly created pages and sections are set at the top of the Area or a
section. When this option is checked new pages appear at the end of an Area
or section.
- Save: To save your results. After saving your work you
return to the Configuration Manager main screen.
- Cancel: To cancel your action and return to the
Configuration Manager main screen.
(top)
At this moment (version 0.90.4)
Alerts are not yet fully implemented.
Alerts are sent:
- to the person who installed Website@School (with the initial e-mail address of the installer)
- to Amelia Cackle (also with the same initial address)
The person who installed Website@SChool gets all changes for the ellapsed time period once per 24 hours at the most.
The alert for Amelia Cackle are sent 1x per hour. She receives all changes on Area #2 (the intranet when demodata is installed).
Fine grainded alerts for
- 'every' change
- a change in one or more areas
- a change on one or more nodes (pages/sections)
can be sent to users with an account or without account.
Possibilities:
You can make an alert for a teacher on a page owned by a pupil. When the pupil changes something on his page, the teacher receives an alert, only for that page.
The e-mail addresses of the alerts are not bound to an account, but are completely separated. This is done to be able to send alerts to addresses that have NO account.
In this way, a visitor can take a subscription to the changes on a certain page. For example: subscribe me to this page with the advertisement 'for sale'. When something changes in the price of the advertised articles, the visitor automatically receives an alert.
(top)
Power to the Bazar!
(top)
Author: Dirk Schouten <schoutdi (at) knoware (dot) nl>
Last updated: 2013-07-10