Admin preferences and setup

• Use wiki page staging and approval: If this is unchecked, the feature is completely off.
• Unique Naming convention: a prefix is used to indicate staging copy: This is compulsory for the feature to work. Basically staging copies of (approved) wiki pages are marked and recognized by having a prefix in front of their name. For example, if the prefix is set to "*", which is the default, the page "*Using Tiki" will be the staging copy of the page "Using Tiki". If you like, you can replace the prefix with something more meaningful, e.g. "On staging - ". Note, however, that if you change the prefix after initial configuration, you will need to rename the old staging copy pages in order to preserve the link between staging and approved versions. Otherwise, new staging copies based on the new prefix will begin to be used.
• Hide page name prefix: If selected, the prefix will be hidden in the page name that is shown on top of pages as they are viewed and edited (there is already will be a separate message on these pages to indicate to a user that he is viewing a page which is staging copy). The prefix is still shown on other pages, e.g. lists of pages, etc... as they will be relevant in those cases.
• Category for staging pages: It is highly recommended to select a category to put staging pages in. You can then set permissions for this category, for example, edit perms and view perms both for registered users only. When staging pages are edited, they are automatically placed in this category when a user saves the page. This happens regardless of what other/no categories are selected by the user.
• Category for approved pages: This is compulsory for the feature to work. You have to select a category to put all approved pages in. You can then set permissions for this category, for example, edit perms for system admins only, and view perms for everyone. The edit button of pages that are in this category will be redirected to the staging page, providing convenient access to edit the staging instead of the approved page. This edit button will be shown based on the edit perms the user has for the staging page, not the approved page. If the staging page does not exist yet, it will be created transparently. In the above example, if you click on edit while viewing "Using Tiki", you will be sent to edit "*Using Tiki". Note, though, that you can still edit the approved page manually by accessing tiki-editpage.php url directly, e.g. tiki-editpage.php?page=Using Tiki, unless you set the "Force bounce..." setting below. Approved pages will automatically be placed in this category when they are approved. This happens regardless of what other/no categories are selected by the user.
• Category for pages out of sync: If "Delete staging pages at approval" is not activated, it is highly recommended to select a category to identify pages that are out of sync. When a user saves edits to staging pages, they are automatically placed in this category regardless of what other/no categories are selected by the user. At the same time, when these staging pages are approved, they are taken out of that category. If this setting is off, staging pages are always considered "out of sync" and there will be no indication, so setting this is really useful. Moreover, you can review pages that are out of sync through browsing the category.
• Force Redirect of editing of approved pages to staging: As mentioned above, you can already limit edit permissions by user group under Category Admin. However, if you really want to, you can force redirect all requests of tiki-editpage.php for pages in the approved pages category to go to the staging copy. This may be useful to totally prevent direct editing of the approved version through direct tiki-editpage URL. NOTE: Even WITHOUT this selected the edit icons will redirect the user to edit the staging copy - it just does not prevent direct URL access.
• Categorize approved pages with categories of staging copy on approval: If selected, the categorization of the approved page is set to that of the staging page upon approval, with the exception that auto-categorization of the special categories configured in this system are not affected (on approval, the approved copy will not have the category for staging pages set, and will continue to have the category for approved pages set).
• Replace freetags with those from staging pages on approval: If selected, this replaces the freetags set on the approved page to those in the staging page upon approval.
• Copy new freetags of approved copy (to tags field) when editing staging pages: If selected, when a user edits a staging page, freetags that are in the approved copy but not in the staging page will automatically be inserted into the freetags field. An editor/document reviewer will have a chance to change these tags before his final edit before approving.
• Delete staging pages at approval: As soon as a page is approved the staging page is deleted
• If not in the group, edit is always redirected to the staging page edit: This allow you to create new pages in a staging status.