UpgradeTwiki writes a LocalSite.cfg containing all config parameters which have changed against their defaults, but erroneously takes Cairo and not Dakar defaults.

In Dakar's TWiki.pm, PubUrlPath and ScriptUrlPath are explicitly set to a bogus default "NOT SET", whereas TWiki/Upgrade/TWikicfg.pm compares against the Cairo defaults of /twiki/pub and /twiki/bin, respectively.

Since the URLs are a matter of web server configuration and not TWiki upgrade, I'd suggest to write them explicitly to LocalSite.cfg regardless of their Cairo values (by setting the assumed default values to undef):

--- TWikiCfg.pm.orig    2005-09-26 13:50:33.350383200 +0200
+++ TWikiCfg.pm 2005-09-27 12:58:53.396238300 +0200
@@ -105,9 +105,9 @@
     print CFG old2new($defaultUrlHost, "http://your.domain.com",
                       "{DefaultUrlHost}", 1 );
-    print CFG old2new($scriptUrlPath, "/twiki/bin",
+    print CFG old2new($scriptUrlPath, undef,
                       "{ScriptUrlPath}", 1 );
     print CFG old2new($dispScriptUrlPath, "/twiki/bin",
                       "{DispScriptUrlPath}", 0 );
-    print CFG old2new($pubUrlPath, "/twiki/pub",
+    print CFG old2new($pubUrlPath, undef,
                       "{PubUrlPath}" );
     print CFG old2new($dataDir, "/home/httpd/twiki/data",

Ahm... I should note that this patch is untested right now.

---

The assumption during upgrade is that the upgraded TWiki is going to be operating under the same URLs as the original Cairo, so it is correct for it to use the Cairo values in the typical cases. It will get it right as many times as it gets it wrong. The only way to resolve this would be interactively, and I debate if it is worthwhile trying to do that at this late stage.

CC

---

The assumption is all ok - but UpgradeTwiki and TWiki.pm don't agree what the "defaults" are!

Let me try to explain it in some detail:

• In Cairo, I have PubUrlPath and ScriptUrlPath set to /twiki/pub and /twiki/bin, their respective Cairo defaults.
• UpgradeTwiki (in TWikiCfg.pm) finds that PubUrlPath and ScriptUrlPath are still set to Cairo defaults (which are hardwired in TWikiCfg.pm), therefore does not write them to LocalSite.cfg.
• TWiki.pm does not find values for PubUrlPath and ScriptUrlPath and defaults them to 'NOT SET' which breaks links.

Of course everything is fine once I run configure, which initializes the URL paths from its own URL. And I agree that interactive resolution is no good idea. I just hoped that UpgradeTwiki would get it right from the start. Dakar ought to use the Cairo values if possible. But to get there it should either have the same default values for PubUrlPath and ScriptUrlPath, or the upgrade tool should omit them from LocalSite.cfg only if they match Dakar defaults. The patch I suggested is doing the latter, though one could as well keep the default values for PubUrlPath and ScriptUrlPath in TWiki.cfg.

-- TWiki:Main.HaraldJoerg

Undeferred, post Dakar CC

---

By this time, either everyone has upgraded or their not going to. Given the pressure of other more critical requirements, i'm dropping this.

CC