Item12598: Give subwebs first-class URL behavior
Priority: Normal
Current State: Duplicate
Released In: n/a
Target Release: n/a
I can use
http://wiki.cfcl.com/bin/view/Projects as a URL.
I will be sent to
http://wiki.cfcl.com/bin/view/Projects/WebHome.
However, I cannot use
http://wiki.cfcl.com/bin/view/Projects/ISLE as a URL;
instead, I have to use
http://wiki.cfcl.com/bin/view/Projects/ISLE/.
This behavior is inconsistent, annoying, and unnecessary.
IIRC, it was chosen because of the possibility of conflict
between a subweb and a topic.
However, the resulting behavior breaks the Principle of Least Astonishment
and may cause confusion in some cases.
So, here is a suggestion for a minor, and largely backward-compatible,
revision of this behavior:
- If there is no conflicting page (eg,
Foo.txt
), map Foo
to Foo/WebHome
.
- If a conflicting page (eg,
Foo.txt
) exists, display it, but add a note that it should be moved to Foo/WebHome
.
- If both
Foo.txt
and Foo/WebHome.txt
exist, display Foo.txt
, but add a note that the pages should be merged.
--
RichMorin - 11 Oct 2013
At Yahoo!, I would create a topic Foo in every subweb Foo (redirection got Foo/WebHome) as a workaround. I shouldn't have needed to do that.
--
VickiBrown - 11 Oct 2013
Hm, can't reproducing it over here using foswiki/trunk and
lighttpd. I get the correct sub's webhome. Ahttp://localhost/Web/SubWeb displays the Web.SubWeb.WebHome page ...
Maybe this is an apache config problem?
--
MichaelDaum - 12 Oct 2013
I can reproduce it on foswiki.org, but not on trunk
vs.
vs.
However I have a very vague recollection that this might be working as intended. I don't recall if it was a feature request. I'm hesitant to make a fairly significant operation change like this in 1.1.9.
--
GeorgeClark - 12 Oct 2013
The fix in trunk was done by
Item9225 It was a feature:
FallBackToTopicWhenTrailingSpaceAndNoSuchSubweb. Closing this as a duplicate.
--
GeorgeClark - 13 Oct 2013