7 Components: the Function Pages - Developers

29 &TWiki::Store::readFile(
30 $TWiki::remoteUserFilename );
31 my @line = split( /\n/, $text );
32
33 # entry of new file
34 my $newtext;
35
36 # find current user in file
37 for (my $i = 0; $i < scalar(@line); $i++)
38 {
39 if (!grep(/\|$theRemoteUser\|/,
40 $line[$i]))
41 {
42 $newtext .= $line[$i]."\n";
43 }
44 }
45
46 # save new file
47 &TWiki::Store::saveFile(
48 $TWiki::remoteUserFilename, $newtext );
49
50 # display confirmation page
51 TWiki::redirect($query,
52 TWiki::getOopsUrl("Main", "WebHome",
53 "oopslogoff", $theRemoteUser));
First of all, a few preparations are made that refer to the work relationship
(lines 4-13). This is necessary to be able to integrate the libraries
in the next step (lines 16-19). The variable $query (line 21)
will be required later when a confirmation message is displayed. In
line 24f., the current user is determined if there is a corresponding
entry. Otherwise, the value of $theRemoteUser is “guest.”
Now, the registration file must be loaded and split into individual
lines for further processing (lines 28-31). Note that we do not use
absolute file names and paths here, but rather the names specified in
Twiki.cfg (via $TWiki::remoteUserFilename). Next, we see
the heart of the script (lines 33-44): We put together the text ($newtext)
of a new file in which all entries are adopted that do not contain
the name of the current user (line 39). This text saves the script
in the file (lines 47f). Then, we redirect the browser to the display of
a logout confirmation. (lines 51-53). When doing so, we make use of
the Oops scripts that is generally used in TWiki to display messages.
The first two parameters of TWiki::getOopsUrl indicate the
TWiki page to which the OK link leads. The next entry refers to the
14.6 A Mixed Strategy for Authentication �
�
�
215