This document describes the workings of Silva from the point of view of a Silva site Manager role. This role has the same rights as a Zope manager.
For the purposes of locating objects, the Silva installation is assumed to be ‘default’, where Silva is installed at the root level of a Zope instance, and named ‘silva’. All paths in this document begin with “/silva”.
ZMI refers to the Zope Management Interface
SMI refers to the Silva Management Interface (where Silva Authors, Editors and Chief Editors work).
ZPT is a Zope Page Template.
To limit confusion, we rarely use the word “user”. Silva has several built in roles (Author, Editor, Chief Editor, Manager). These are always spelled with a capital letter.
A person viewing public pages (anonymously) is a ‘Visitor’.
Let’s start with a few tips which are good to know.
In the ZMI of the Silva root, “Silva /edit…” is the third tab. In between comes the Services tab, which contains Silva application logic, further detailed below .
In the ZMI on lower levels, there is not normally a Services tab, and the second tab is called “Silva /edit…”. That takes you to the SMI at the current level.
A few key aspects are defined in the Zope properties tab of the Silva root. See the Properties section below (e.g. to change the help location).
Objects in the Silva root
Silva Root icon
What follows is a quick listing, with links to more information, of the objects found in a Silva root. Most of these items have code that resides on the file system.
In the ZMI, at “/silva/manage” or “/silva/manage_main”, you’ll see a number of Zope and Silva objects. Silva objects are Publications, Folders, Documents, etc.
Note that if Silva content objects are present in the root publication, those items will be mingled in the ZMI contents listing as well.
This folder contains information about Silva members, i.e. Zope users who have been assigned a Silva specific role. Normally this folder should be left alone; the Member objects are created implicitly on demand. Removing a Member object does not revoke the roles from the corresponding user; it only removes the additional information available via the “user settings” page of the SMI.
All Silva Services are found in the Silva root in the ZMI, some services can also be found in Site Preferences (Site configuration) via the user meny drop-down.
Click on the Services tab in the ZMI to see the full list of Service options or select Site Preferences from the user menu drop-down in the SMI. Most services have settings that can be modified.
The Silva Extension Service (Silva Extensions management)
This service allows configuration of Silva core and extension products. Your own and third party extensions can be activated and deactivated here. Silva News is an example of an extension – it’s not part of the Silva core – that must be installed on the file system. Depending on what’s been installed the listing will change.
Following are several other default services:
service_files (Silva Files Service)
Controls storage of Silva File objects
service_members (Silva Membership Service)
Controls membership / subscription issues.
service_message (Silva Message Service)
Set up email address for workflow support.
Simple Silva backup
acl_users in listing
Fig. 1. View of the Silva (Literature) root in the ZMI.
To make a simple Silva backup:
Place a check in the checkbox by the Silva root.
Choose Export at the base of the listings and Export your site.
A pop up dialog will allow you to save a .zexp file.
To import a Silva site place a zexp file in the import directory of your Zope instance
Choose Import at the base of the listings.
Select the zexp of the Silva site.
Read Troubleshooting.txt inside the Silva product download.