community.egroupware.org: Community wiki

  
Community wiki
Sitemgr Administrator Manual
back to ManualSitemgr


Installation

  1. Once you have the sitemgr directory inside your eGroupWare install you can setup it like any other eGroupWare application with the setup program (http://yourmachine/eGW-path/setup/). You should also install the sitemgr-link application, which is is inside sitemgr and has to be moved up in the directory hierarchy.

    cd sitemgr




    mv sitemgr-link ..

    and then install sitemgr-link with setup

  2. Log in to eGroupWare as an admin and create an anonymous eGW user and assign it a password. The only app (I assume) that they should have access to is sitemgr-link. sitemgr-link is a dummy application that redirects eGW users to the generated site.

  3. Users who you wish to see sitemgr (aka contributors) must be given acces to sitemgr, users who you want to be able to link to the sitemgr site from eGW must be given rights to sitemgr-link. The easiest way to do this is to go to User groups and give groups permissions to use the applications.

  4. The sitemgr-site is the directory that serves the dynamic web site. It is located inside sitemgr and works without moving it somewhere else. But it can be located anywhere. For example, you could put it in /var/www/html. You could make the root location of your web server point to it, if you wish (ie, http://yourmachine/ refers to /var/www/html/sitemgr-site if you moved the directory, or to /path/to/eGroupWare/sitemgr/sitemgr-site if you did not). Make a mental note of the directory where you put it and the url that it is accessed by.

  5. In the sitemgr-site directory is a file called config.inc.php. You only have to edit it if you moved the directory. Change the value of the line

    'eGW_path'           => '../../',

    so that the value of $sitemgr_info{'eGW_path'} is '/path/to/eGroupWare/'

  6. You can handle different websites with sitemgr. The first thing to do is to define your new website. SiteMgr defines a default website upon installation, but you will probably have to redefine it. Log in as a eGW administrator and go into eGroupWare's admin application and choose “Define websites” in the sitemgr section. You should see the default website listed, and can choose to edit it. A website is defined by the following values:

    Site_name

    This is not used on the website, but only helps identify a website inside the administration interface.

    Filesystem_path_to_sitemgr-site_directory

    If you did not move the sitemgr-site directory above you can leave this unchanged.

    URL_to_sitemgr-site

    You can also leave this unchanged if you want to access your public website with a url that looks like http:/your.eGW.url/sitemgr/sitemgr-site. If you want a different URL, you either have to move the sitemgr-site directory or to use an alias or a virtual server in your webserver's configuration.

    Anonymous_user's_username

    the account name you created above.

    Anonymous_user's_password

    and the corresponding password

    Site_administrators

    Here you choose the users and/or groups that should have administrator rights for the website. They do not have to be adminstrators in eGW's sense.

  7. You can know log in as on one of the user's you gave administrator rights for the website.. Go to the sitemgr application and select "Configure SiteMgr". Here you can set different values that affect how your site will be presented.

    Site_name

    is used mainly for metadata

    Site_description

    is used mainly for metadata

    Default_home_page

    here you can select the page that will show up first one your website. Evidently there won't be any choice until you create some pages.

    Template_select

    lets you choose between the different site designs that come with sitemgr or any you will create yourself.

    Site_languages

    If you want a multilingual site, you have to set them here. This will let you use the translation interface for translating your content and you can put a selectbox on your website where it's visitors can choose between different languages.

  8. After installation sitemgr does not immediately know about all available modules. The setup routine only installs the modules html,index and toc that every site will need. In order to register all availabe modules select “Manage site-wide module properties” from the administrative menu, and then follow the “Register new modules” link.

  9. That's it. Go to the Outline manager (“Manage categories and pages), add a category or three and check who can view and edit them, then add a page or three to each category, create some content for each page. You can also have content that is visible everwhere on your website (“Manage site-wide content”) or on all pages that belong to a category (“Manage categories and pages” => “Manage category wide content”). Take care to put all categories and pages and blocks you create into published state, otherwise they will not be visible on the website.

  10. Go view your recently created site by clicking on the sitemgr-link application. Voilà!


Maintenance

As a site administrator, you have three privileges/responsibilies:

  1. Define site wide content blocks. These are edited in the same interface as category and page specific blocks.

  2. Choose permitted modules: If you choose “Manage site-wide module properties” from sitemgr's main menu, you will see several rows which all contain four elements: a select box, a button labelled “Select allowed modules', another select box and a button labelled “Configure module properties”. The first select box and its adjacent button in each row permits to choose lists of permitted modules. The first row defines a master list for the whole site which is used when no more specific lists are found for content areas or categories. The following rows each pertain to the different content areas of your site template. Here you can choose to allow some modules for one content areas, and other modules for another one. In the category manager, there is a button “Manage Modules” associated with each category. There you can use the same interface to define lists specific to one category (and all its subcategories, unless overriden). Again you have the choice between one list that pertains to all content areas, and specific lists for each category. When sitemgr has to find a specific value of permitted lists in a given context (a given contentarea in a given category) the following algorithm is used: First it aks for a value defined for the pair contentarea/category. If none is defined, it climbs up the category hierarchy until the site wide value, each time looking for a value defined for the pair contentarea/category. If none can be found, it returns to the given category the search started from, and now asks for values defined for the given category but independent from the contentarea. If there is still none defined, it repeats the same traversal up the category hierarchy. This means that by simply defining one global master list of permitted modules, you can configure the whole site, if you do not need more fine grained control. The lists of permitted lists are never merged, if you define one list for a given context, this list is used in this context.

  3. Define module properties: The lookup algorithm for module properties is exactly the same as for the lists of permitted modules. For each module you can set properties for the whole site, for content areas, for categories, or for combinations of content areas and categories. You access the property editor from the same page where you choose the list of permitted modules. You just use the second select box in each row. By selecting one module and clicking the “Configure module properties” button, you will open a interface for editing the module's properties which ressembles the interface for editing module arguments in the content manager. Be aware that only some modules define properties.



You are here