Community wiki

Community wiki
Sitemgr User Manual

 back to ManualSitemgr

Manage categories and pages

The content inside a sitemgr website is organised using categories and pages. Categories may contain other categories, creating a hierachical category-tree this way. Each category may contain pages, too. At the top-level (the site) you cannot create pages, you have to create at least one category first. Pages themselves contain the content, provided by the modules, which may be visible for the page only, for the category or for the whole site (site-wide).

Create a new category

In order to create a new category, you have use the Conten-Manager, respecitvely edit Mode. You access this mode, using "Edit Site" from the general menue or switching to Edit-Mode if you have an Administration-Module available in your website. To create a new category, you have to click "View full index" inside the Navigation-Module first and than click the small Icon next to "Site Index". You will geht to yourdomain//index.php?menuaction=sitemgr.Categories_UI.edit.

Edit a category

Access the Edit-Mode (see above) and click on "Edit category" next to the category name. Edit:

  • Category Name: Will be shown in Navigation elements
  • Sort order: relevant for Navigation elements
  • Parent: use this to make this category become a subcategory of the chosen parent-category
  • Category description: Used in Navigation elements, as additional information
  • Index: which page should be displayed as the index of the category, default is an "Automatic Index"
  • State: Categories are part of the publishing workflow, too
  • Permissions: You can set the permissions (Read/Write) on Group and User-Level (for a public site you may use anonymous).

Delete a category

Just press the delete button next to the category. Make sure, that you don't need any of the associated pages anymore.

Create a new page

Looking on the Full-Index in Edit-Mode (see above) just click the "add page to category" Icon next to the category.

Edit a page

Name: Used as an ID and for the URL (?page_name=...).
Ttile: Displayed in Navigation Modules
Category: (where should this page be visible/which access permissions should be applied)
State: Concerning the publishing workflow
Checkbox to hide form condensed site index: At the moment site is hidden in all Navigation elements, if checked.

Editing page content

There are two interfaces for creating and editing content blocks. The first one is called “content manager” and works inside the eGW interface, the second works in interaction with the generated web site and we call it “editing mode”.

The content manager

The interface for creating content blocks is the same on each level of scope, besides that when editing blocks on a lower level you can see all the blocks that have been defined on a higher level, and will be displayed on the website together with the blocks you are editing. I will refer to this interface as the content manager.

In each content manager, there is a section for each content area, where you can add blocks selected from a menu of all available modules. Once you have added a new block, it appears amidst all other blocks of the content area. Those defined on higher level scopes are only displayed, those pertaining to the scope (site-wide, category or page) you are managing are editable.

Editing mode

In order to use editing mode, you must add a site-wide administration block to your website (viewable only by registered users). This block has a dropdown menu where you can switch between production mode (viewing the website in its public state), draft mode (viewing the website in the prepublished state, i.e. how it will look after you commit any pending changes, you only see prepublished elements, no draft-status onew) and edit mode. In edit mode, you will see the same content as in draft mode and draft-status elements, but in front of each content block you will see a link “Edit block”. Activating this link will pop up a new window for editing it.

Editing a block

In both the content manager and the editing window that opens in editing mode, the interface for editing the block is the same. There are three standard interface elements you can edit for each block:


Each module defines a default title for blocks it generates. The block title is not necessarily displayed in each content area. It depends on the block transformer defined for the content area by the site template you use. Here you can override the default title with a customized title that will only be used by the block you are editing


You can control the visibility of each block for the different user roles defined by sitemgr: site administrators, eGroupWare users (which include site administrators) and the anonymous user. Evidently you can also make the block visible for everyone which is the default.


Here you can change the order in which the blocks are displayed by defining a different integer for each block.

When you first create a content block, sitemgr automatically creates a version for it. For each version, you have to edit the module specific arguments, each of which is preceded by an explanatory label. The input elements for arguments can be of different types: checkboxes, selectboxes, textareas, textfields. In the case of text input, you can use the same template variables as are used in the site template. But be aware that this only works if the module puts the same variable into its output, which need not necessarily be the case.

Even if not all blocks may make sense for each content area, the content manager does not impose on itselft any constraints on which modules you use for which area (Administrators can restrict the available modules for categories and content areas). For example you can use modules that are optimized for side block areas in the central area and you could use a simple html content block on side areas. The following modules are shiped with sitemgr:


simply creates a link to sitemgr's administration interface. Thus you probably would not want to make it visible for anonymous user's but only for eGW users or adminstrators.


shows ads for books on the Amazon website. There is a comment in the modules source file about how it works.


a demonstration of how sitemgr's architecture can be used to realize a simple application for creating a directory of information. It should be adaptable to other needs. At the moment, you need PHP's XSLT extension to use this module.


lets you show content from eGW's bookmarks application


produces a calendar where each days links to eGroupWare's calendar application


produces an index of the pages in the current section.


you can use this module for creating links to files and directories you store with eGW's filemanager

to display  a folder type the path like "/home/yourfolder/" The user will be able to navigate all subfolders, too if you activate this

make sure that you activated the filemanager app for the sitemgr user and that he has the needed filemanger permissions (read) for the folders you want to be available for the all visitors (for non-public websites, there is no need to give the sitemgr users the permission of course)


this module lets you include the content of a file on your webserver into your website


another demonstration of what sitemg's modules are intended for: This module displays the discussions of eGroupWare's forum application on the web site. It does not permit to post, since to implement this, in my humble opinion, the forum application has to be redesigned slightly.


creates a picture galery. You have to name both the filesytem path and the URL to a directory, where images that have a common filename, and are numbered beginning with one, are stored. Once the directory has been found, you can edit a subtext for each image.


displays a form for querying the google website.


a simple “Hello world” module used below in this manual.


probably the most important module, since it plays the role, formerly the simple page content area had, ie. you add html content to the page.


a index of the whole site, formatted for peripheric areas of your web site.


is automatically used with the index GET parameter. You probably would not have to use this block otherwise.


displays a select box for changing the user's site language.


displays a login block


publishes news you edit with eGroupWare's news_admin application. You can choose a category to display.


makes the page redirect to another URL. This is useful, if you want an entry in your menus that links to a page outside your sitemgr site. If you use this module you shouldn't put any other blocks on the same page.


displays a tree like menu to the website.


the site's table of contents, formatted for peripheric areas of your web site.

this block enables website visitors to change the layout-template, great for designing websites together with the customer

is automatically used with the toc GET parameter. You probably would not have to use this block otherwise.

this module is used to diplay wiki articles. The website reader will be able to navigate all articles using the links and you may provide a wiki-search, too. You should think about disable Wiki Links (Wiki Site Configuration, "Enable Wiki Links: No"), otherwise URLS containing capital letters will be interpreted as "Words Smashed together". This module is a very nice way to give people the possibilty to edit the content of the website, without needing to bother about the sitemgr. Just like the Newsadmin can be used to edit news vor the sitemgr news-module.

is only a demonstration of how a module could serve XML content stored on your webserver. It does not do anything useful besides creating a browser from one file to the other. Files have to be named like images in the galerie module. You need PHP's xslt extension to use this module.

Handling versions

For each content block you can create a new version simply by clicking on the “Create new version link”. Once you have several versions of a block, you can change their status at any time. If you want to immediately publish a block, you choose “published”. If you want to register a version for being published at the next commit, you choose “prepublished”. A version that is “preunpublished” is visible on the website, but will be archived at the next commit. Thus if you want to replace some content at the next commit, you have to put the published version into “preunpublished” and create a new version that you put into “prepublished” state. Archived versions will be no longer visible in the content managment interface, but will not be deleted from your database. They can be reactivated in the “Manage archived content” interface.

Manage translations

to be completed

Commit changes

In this interface you see a list of all categories, pages and blocks that are in prepublished or preunpublished state. You can return to any of them for further editing or changing their status, and you can choose between them for commiting. Prepublished content will go public, preunpublished content will go to the archive.

Manage archived content

to be completed

You are here