1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
%INCLUDE\{"UtilTempDocNote"\}%
%TOC% %STARTINCLUDE%
# <a name="Managing_Topics"> Managing Topics </a>
_Browser-based rename, move, and delete for individual topics_
## <a name="Overview"> Overview </a>
Select **Rename/move** when viewing a topic to change its name, move it to another TWiki web, or delete it:
1. **Select** target web if other than the current web - chose <code>**Trash**</code> to delete a topic
2. **Enter** the new topic name - default is current name <br />**_NOTE:_** You will be warned if there are locks or if there is a name conflict
3. **Select** from the list of links to the topic that will be changed those to OMIT from changes (by default, all referring links will be updated)
4. **Click** on **Rename/Move** to rename/remove topic will be renamed and links to the topic updated as requested.
* If any of the referring pages are locked then they will be listed
* You can correct these later by again pressing Rename/Move
### <a name="Referring_Topics"> Referring Topics </a>
Referring topics are found using the the %SEARCH% variable, see the template <code>**searchrenameview.tmpl**</code>. First, matching topics in the current Web are listed - matches are to _topic_. Next, all Webs (including the current one) are listed that match _web.topic_. Because %SEARCH% is used, Webs marked in [[WebPreferences]] as NOSEARCHALL will not show up in the search for refernces to the _topic_ being changed.
Changed references are kept are as short as possible, i.e. _topic_ is used in preference to _web.topic_.
<a name="DeleteTopic"></a>
### <a name="Deleting_a_Topic"> Deleting a Topic </a>
Deleted topics are moved to the `Trash` web - NOT physically erased from the server. All webs share `Trash` - in case of a name conflict with a topic already `Trash`, the user is alerted and asked to choose a new name.
#### <a name="Clearing_the_Trash"> Clearing the Trash </a>
**_NOTE:_** The `Trash` web should be be cleared periodically, by archiving the contents if required (recommended), then deleting the files from the `Trash` directory.
## <a name="Redirecting_from_an_Old_Topic"> Redirecting from an Old Topic </a>
You can use [[TWikiMetaData]] to place a command in %TWIKIWEB%.WebTopicViewTemplate and %TWIKIWEB%.WebTopicNonWikiTemplate that will show if a topic has moved by searching for the tag %META:TOPICMOVED\{...\}%. Customize something like this:
> %<nop>METASEARCH{type="topicmoved" web="%WEB%" topic="%TOPIC%"
> title="This topic used to exist and was moved to: "}%
## <a name="Impact_of_Topic_Access_Settings"> Impact of Topic Access Settings </a>
Permissions affect the rename function in various ways. To rename a topic, you need both change and rename permissions. To alter refer4ing topics, you need change permission. See [[TWikiAccessControl]] for information on setting up access permissions.
## <a name="How_Rename_move_Works"> How Rename/move Works </a>
* %SEARCH% is used with a special template to show text in topics that requires updating to point to the new topic and/or web name. This includes relevent [[TWikiMetaData]] definition.
* User chooses which topics will be altered
* `<pre>` and `<verbatim>` are honoured - no changes are made to text within these areas
* Topic is moved (if locks allow)
* References are changed (locks and permissions permitting)
* Any referring topics that can't be changed due to locks are listed - user can change them at another time.
## <a name="Known_Limitations"> Known Limitations </a>
**Rename/move** in is fairly complicated due to the dynamic generation of links. Ideally, it would be possible to run the required part of rendering in a way that would allow identification of the text to be changed. Unfortunately, these hooks don't exist in TWiki at present. Instead, %SEARCH% is used with a special template to show the text to be changed, and the selected topics are then altered. One drawback is that `search` can show matches that will not be updated because of case differences. Other mismatches to actual rendered output are also possible as the approaches are so different.
The following shows some limitations of square bracket processing.
> [[Old Topic]] => [[NewTopic][Old Topic]]
> [[old topic]] => [[NewTopic][old topic]]
> [[old t opic]] => not changed
> [[OldTopic]] => [[NewTopic]]
|
