Adding webs is a web-based operation; renaming and deleting webs are manual operations done directly on the server.
is divided into webs; each one represents one subject, one area of collaboration. Administrators (in the TWikiAdminGroup
) 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
). 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 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.
Adding a New Web
- Attachments will NOT get copied over along with their topics
- While creating the new web, TWiki will update the following variables in the WebPreferences:
NOSEARCHALL. These variables are used to dynamically generate the SiteMap
- TWiki does not edit the TWiki.TWikiPreferences? to update the
WIKIWEBLIST. This must be done by hand
Renaming or Deleting a Web
Rename a web via the Tools section in each web's WebPreferences
topic. You may delete a web by moving it into a Trash web.
You may only rename a web if you have permissions to rename all the topics within that web, including any topics in that web's subwebs. You will also need permissions to update any topics containing references to that web.
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
If you plan to rename the Main web, remember that TWiki stores user and group topics in
, which by default is
(this is assigned in the site configuration). That means that every WikiName
- points to it and would need updating (unless the variable,
, is used throughout). This potentially large change can be performed automatically with the renameweb function mentioned above, in the Main.WebPreferences
If you want to rename the TWiki web, remember it is referred to by
which is also defined by a configuration setting.
Hierarchical web support is enabled by turning on the
. Without this setting, TWiki will only allow a single level of hierarchy (webs). If you set this, you can use multiple levels, like a directory tree, i.e. webs within webs.
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:
To create a subweb named
inside a web named
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?
Example Preference Inheritance for
TWiki.TWikiPreferences site-wide preferences
Sandbox.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb/SubWeb.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb/SubWeb.SubWebTopic inherits from and overrides settings in
The Pattern skin (default) indicates Subwebs by indenting them in the sidebar relative to their level in the hierarchy.
Related Topics: AdminDocumentationCategory