Difference: ManagingWebs (29 vs. 30)

Revision 3022 Jul 2006 - TWikiContributor

Line: 1 to 1
 
On this page:

Managing Webs

Line: 36 to 36
 

Notes:

Added:
>
>
  • You have to have ROOTCHANGE access to create a top-level web (one with no parent)
 
  • Attachments will NOT get copied over along with their topics
  • While creating the new web, TWiki will update the following variables in the WebPreferences: WEBBGCOLOR, SITEMAPLIST, SITEMAPWHAT, SITEMAPUSETO and 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
Line: 57 to 58
  If you plan to rename the Public web, remember that TWiki stores user and group topics in this web. That means that every WikiName signature - Public.SomeUserName - points to it and would need updating (unless the variable, %MAINWEB%.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.
Changed:
<
<		ALERT! If you want to rename the TWiki or Public webs, remember they are referred to in the TWiki configuration. You will need to change the relevant settings in the configuration using the configure interface.
>
>		ALERT! If you want to rename the TWiki or Public 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.
 

Hierarchical Webs

Changed:
<
<		Hierarchical web support is enabled by turning on the {EnableHierarchicalWebs} setting in configure. 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.
>
>		Hierarchical web support is enabled by turning on the {EnableHierarchicalWebs} setting in configure. 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.
  TIP 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.
View topic | History: r40 < r39 < r38 < r37 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 1999-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Insights Collaboration TWiki? Send feedback
Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.ManagingWebs.