I have a TWiki, but no Test.

I'm trying to set up a TWiki on a SuSE Linux system. At present I can reach the WelcomeGuest page; Netscape reports its URL as http://topoi.pooq.com/twiki/bin/view/TWiki/WelcomeGuest But when I try to click on Twiki.Test in the chart of TWiki Webs currently online, I am informed to NOTE: This Wiki topic does not exist yet, and it suggests that I should create the page if I should wish. The URL of this missing Test page is: http://topoi.pooq.com/twiki/bin/view/Test/WebHome

I checked in the actual file system. There is a perfectly good /usr/local/httpd/twiki/data/Test/WebHome.txt file, just as there is a perfectly good /usr/local/httpd/twiki/data/TWiki/WelcomeGuest.txt file. In fact, I hand-edited the /usr/local/httpd/twiki/data/TWiki/WelcomeGuest.txt file (inserting "HaHa" into it using emacs) just to make sure I was indeed seeing that file and not some similar one elsewhere on the net. It's not clear how the path to TWiki could be correct, without the path to Test also being correct.

I have followed the instructions in the installation notes telling me what to do if I am "on a non authenticated server (i.e. not using SSL) and you would like to authenticate users: ". Could that be relevant? I don't see how, but...

• TWiki version: The December, 2000 public release.
• Web server: Apache, as bundled with SuSE Linux.
• Server OS: SuSE Linux 6.4

-- HendrikBoom - 06 Mar 2001

Answer

I had a look at the URL. All topics in all webs are accessible except the Test web as you stated. It looks as if the topics in Test are not there. Since you are saying that the .../data/Test/WebHome.txt file exists, the only thing I can think of is a file permission problem. Make sure that the Test directory and the files in it are readable/writeable by the cgi-bin user (nobody on SuSE?)

-- PeterThoeny - 06 Mar 2001

More Answer

The permissions on the Test directory turned out not to have execute permission set, so of course directory searches failed. I had checked the file permissions, but somehow missed the directiry permissions, After I permitted it, the problem was gone. Oddly, though, the next day the permissions were wrong again -- evidently there;s something I do whihe configuring ans otherwise setting up that damages the permisions. I haven't tracked it down, but it has stopped happening, -- hendrik