Managing Webs

Adding, renaming and deleting webs are all web-based operations.

Overview

A TWikiSite is divided into webs; each one represents one subject, one area of collaboration. Administrators can add/rename/delete webs.

Choose Web Template

There are two methods used to create a new web. First you can use a specially designed TemplateWeb. This is an invisible web that begins with an underscore "_" character (for example _default). All topics in the template web will be copied into your new web.

The second method is to use an existing web as a template web. This may be useful if you already have a web that you would like to use as a starting point. Only topics that have names beginning with Web... (like "WebHome", "WebNotify", etc.) are copied.

In either case you will want to be sure to verify that your new web has all the custom modifications that you desire. Any TWikiVariables defined in the form below will automatically be set in the WebPreferences of the new web.

Adding a New Web

Create a new web by filling out this form.
Note: Keep the number of webs to a minimum! Don't create a new web for each little project. Cross-linking topics is easier, and searches are faster, if there are only a few larger webs.

Name of new web:		The name must start with an upper case letter, followed by upper or lower case letters or numbers. Specify a short name to avoid long URLs.
Based on web:	_default _empty Blog Blog/Calendar Blog/RideLog Homeorgau Main Sandbox TWiki TestCases	Select a TemplateWeb
Web color:		Enter a StandardColors code for the web
Site Map:	Yes   No	Include this web in the site map
Description:	Enter a short description of the web. Write Web.TopicName instead of just TopicName if you include links. This description will be used in the SiteMap
Use to...	Continue the sentence describing the intended use. This is also for the SiteMap
Hidden:	Yes   No	Specify if you want to exclude the web from a "search all webs" search. This will not prevent users accessing the web. It will simply hide it from searches.

Notes:

• You must have ROOTCHANGE access to create a top-level web (one with no parent)
• Only the person who created it has permission to change the WebPreferences in the new web

Hierarchical Webs

You can only create hierarchical webs (webs within webs) if the {EnableHierarchicalWebs} setting in configure is enabled. Hierarchical webs are currently enabled.

Note: You might not need hierarchical webs. TWiki topics already have a parent/child relationship within a web, which is shown in the breadcrumb. Try to keep the number of webs to a minimum in order to keep search and cross-referencing simple.

You can create hierarchical webs via the Adding a New Web form above, by using a slash- or dot-separated path name which is based on an existing web name in the Name of new web: field.

Example:

To create a subweb named Bar inside a web named Foo, use Foo/Bar or Foo.Bar as the new web name in the form above.

Subweb Preferences are Inherited

The preferences of a subweb are inherited from the parent web and overridden locally. Preferences are ultimately inherited from the TWiki.TWikiPreferences topic.

Example Preference Inheritance for Sandbox/TestWeb/SubWeb.SubWebTopic topic:

1. TWiki.TWikiPreferences site-wide preferences
2. Sandbox.WebPreferences inherits from and overrides settings in TWiki.TWikiPreferences
3. Sandbox/TestWeb.WebPreferences inherits from and overrides settings in Sandbox.WebPreferences
4. Sandbox/TestWeb/SubWeb.WebPreferences inherits from and overrides settings in Sandbox/TestWeb.WebPreferences
5. Sandbox/TestWeb/SubWeb.SubWebTopic inherits from and overrides settings in Sandbox/TestWeb/SubWeb.WebPreferences

Navigation

The Pattern skin (default) indicates Subwebs by indenting them in the sidebar relative to their level in the hierarchy.

Renaming or Deleting a Web

Rename a web via the Tools section in each WebPreferences topic. You may delete a web by moving it into a Trash web.

Permissions

You may only rename a web if you have the following permissions

• You must be allowed to rename and changes topics in the web you want to rename
• You must be allowed to rename topics in the parent web of the web you want to rename
• If the web is a root web (i.e. it has no parent web) then you must have permission to both create and rename root webs. These permissions are controlled by the ALLOWROOTCHANGE preference, which can be set in Main.TWikiPreferences.
• If you move the web to another parent web you must be allowed to create and change topics in the new parent web.

When you rename a web TWiki will try and update all links that refer to the old web. You should note that links only get updated in topics that you are allowed to edit. If you use access rights in the TWiki installation it is generally best to let an administrator rename webs to avoid too many broken links.

Edit Conflicts

If anyone is editing a topic which requires updating, or which lives in the web being renamed, a second confirmation screen will come up which will indicate which topics are still locked for edit. You may continue to hit the refresh button until an edit lease is obtained for each topic which requires updating (the "Refresh" button will change to "Submit"), or hit "Cancel", which will cancel your edit lease on all affected topics.

Renaming the webs in the distribution

It is possible, though not recommended, to change the names of the webs in the distribution.

If you plan to rename the Main web, remember that TWiki stores user topics in this web. That means that every WikiName signature - Main.SomeUserName - points to it and would need updating (unless the variable, %USERSWEB%.SomeUserName, is used throughout). This potentially large change can be performed automatically if you rename the web from the Tools section of WebPreferences, as described above.

If you want to rename the TWiki or Main webs, remember they are referred to in the TWiki configuration. You will need to change the {SystemWebName}, {UsersWebName} and/or {LocalSitePreferences} settings in the configuration using the configure interface.

Renaming the webs in the distribution is not recommended because it makes upgrades much more complicated.

Related Topics: AdminDocumentationCategory, AdminToolsCategory