| 1 | %META:TOPICINFO{author="micha" date="1228130313" format="1.1" reprev="1.2" version="1.2"}% |
|---|
| 2 | %STARTINCLUDE% |
|---|
| 3 | ---+ Managing Webs |
|---|
| 4 | |
|---|
| 5 | _Adding, renaming and deleting webs are all web-based operations._ |
|---|
| 6 | |
|---|
| 7 | %TOC% |
|---|
| 8 | |
|---|
| 9 | ---++ Overview |
|---|
| 10 | |
|---|
| 11 | A site is divided into webs; each one represents one subject, one area of collaboration. Administrators can add/rename/delete webs. |
|---|
| 12 | |
|---|
| 13 | #WebTemplate |
|---|
| 14 | ---++ Choose Web Template |
|---|
| 15 | |
|---|
| 16 | 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. |
|---|
| 17 | |
|---|
| 18 | 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 "%HOMETOPIC%", "%NOTIFYTOPIC%", etc.) are copied. |
|---|
| 19 | |
|---|
| 20 | In either case you will want to be sure to verify that your new web has all the custom modifications that you desire. Any [[macros]] defined in the form below will automatically be set in the !WebPreferences of the new web. |
|---|
| 21 | |
|---|
| 22 | #CreateNewWeb |
|---|
| 23 | ---++ Adding a New Web |
|---|
| 24 | New webs can be created using the WebCreateNewWeb [[AdminToolsCategory][AdminTool]]. |
|---|
| 25 | You must have =ROOTCHANGE= access to create a top-level web (one with no parent) |
|---|
| 26 | Only the person who created it has permission to change the <nop>%WEBPREFSTOPIC% in the new web. |
|---|
| 27 | |
|---|
| 28 | ---++ Hierarchical Webs |
|---|
| 29 | |
|---|
| 30 | You can only create hierarchical webs (webs within webs) if the ={EnableHierarchicalWebs}= setting in [[%SCRIPTURLPATH{"configure"}%][configure]] is enabled. Hierarchical webs are currently %IF{"{EnableHierarchicalWebs}" then="enabled." else="disabled. Without this setting, Foswiki will only allow a single level of hierarchy. With it, you can use multiple levels, like a directory tree, i.e. webs within webs."}% |
|---|
| 31 | |
|---|
| 32 | *%T% Note:* You might not need hierarchical webs. Foswiki 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. |
|---|
| 33 | |
|---|
| 34 | 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. |
|---|
| 35 | |
|---|
| 36 | *Example:* |
|---|
| 37 | |
|---|
| 38 | 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. |
|---|
| 39 | |
|---|
| 40 | ---+++ Subweb Preferences are Inherited |
|---|
| 41 | |
|---|
| 42 | The [[preference settings]] of a subweb are inherited from the parent web and overridden locally. Preferences are ultimately inherited from the [[%SYSTEMWEB%.DefaultPreferences]] topic. |
|---|
| 43 | |
|---|
| 44 | *Example Preference Inheritance for =Sandbox/TestWeb/SubWeb.SubWebTopic= topic:* |
|---|
| 45 | |
|---|
| 46 | 1 =%SYSTEMWEB%.DefaultPreferences= default settings |
|---|
| 47 | 1 =%USERSWEB%.SitePreferences= site-wide settings inherits from and overrides settings in =%SYSTEMWEB%.DefaultPreferences= |
|---|
| 48 | 1 =Sandbox.%WEBPREFSTOPIC%= inherits from and overrides settings in =%USERSWEB%.SitePreferences= |
|---|
| 49 | 1 =Sandbox/TestWeb.%WEBPREFSTOPIC%= inherits from and overrides settings in =Sandbox.%WEBPREFSTOPIC%= |
|---|
| 50 | 1 =Sandbox/TestWeb/SubWeb.%WEBPREFSTOPIC%= inherits from and overrides settings in =Sandbox/TestWeb.%WEBPREFSTOPIC%= |
|---|
| 51 | 1 =Sandbox/TestWeb/SubWeb.SubWebTopic= inherits from and overrides settings in =Sandbox/TestWeb/SubWeb.%WEBPREFSTOPIC%= |
|---|
| 52 | |
|---|
| 53 | ---+++ Navigation |
|---|
| 54 | |
|---|
| 55 | The Pattern skin (default) indicates Subwebs by indenting them in the sidebar relative to their level in the hierarchy. |
|---|
| 56 | |
|---|
| 57 | #RenameWeb |
|---|
| 58 | ---++ Renaming or Deleting a Web |
|---|
| 59 | |
|---|
| 60 | Rename a web via the Tools section in each %WEBPREFSTOPIC% topic. You may delete a web by moving it into a Trash web. |
|---|
| 61 | |
|---|
| 62 | ---+++ Permissions |
|---|
| 63 | |
|---|
| 64 | You may only rename a web if you have the following permissions |
|---|
| 65 | * You must be allowed to rename and changes topics in the web you want to rename |
|---|
| 66 | * You must be allowed to rename topics in the parent web of the web you want to rename |
|---|
| 67 | ! * 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 [[%USERSWEB%.SitePreferences]]. |
|---|
| 68 | * If you move the web to another parent web you must be allowed to create and change topics in the new parent web. |
|---|
| 69 | |
|---|
| 70 | When you rename a web Foswiki 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 Foswiki installation it is generally best to let an administrator rename webs to avoid too many broken links. |
|---|
| 71 | |
|---|
| 72 | ---+++ Edit Conflicts |
|---|
| 73 | |
|---|
| 74 | 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. |
|---|
| 75 | |
|---|
| 76 | ---+++ Renaming the webs in the distribution |
|---|
| 77 | |
|---|
| 78 | It is possible, though not recommended, to change the names of the webs in the distribution. |
|---|
| 79 | |
|---|
| 80 | If you plan to rename the %USERSWEB% web, remember that Foswiki stores user topics in this web. That means that every WikiName signature - =%USERSWEB%.<nop>SomeUserName= - points to it and would need updating (unless the macro style =%<nop>USERSWEB%.<nop>SomeUserName=, is used throughout). This potentially large change can be performed automatically if you rename the web from the Tools section of %WEBPREFSTOPIC%, as described above. |
|---|
| 81 | |
|---|
| 82 | %X% If you want to rename the %SYSTEMWEB% or %USERSWEB% webs, remember they are referred to in the Foswiki configuration. You will need to change the ={SystemWebName}=, ={UsersWebName}= and/or ={LocalSitePreferences}= settings in the configuration using the [[%SCRIPTURL{configure}%][configure]] interface. |
|---|
| 83 | |
|---|
| 84 | %X% Renaming the webs in the distribution is not recommended because it makes upgrades much more complicated. |
|---|
| 85 | |
|---|
| 86 | --- |
|---|
| 87 | *Related Topics:* AdminDocumentationCategory, AdminToolsCategory |
|---|
