Item750: INCLUDINGWEB and INCLUDINGTOPIC will cause confusion when used in an INCLUDE chain
Priority: Urgent
Current State: Closed
Released In: 1.0.1
Target Release: patch
Applies To: Engine
Component: System web topics
Branches:
what i should have written :/
topics that use INCLUDING* will trip up users - especially when they include something that is already INCLUDED - consider someone making a rss feed, so they
INCLUDE Main's rss topic - they get a topic that show's Main's rss feed (until i fixed
WebRssBase to use BASEWEB)
original bug report
because System .
WebChanges uses
INCLUDINGWEB
, which is the next WEB up the
INCLUDE chain, a topic that includes a topic that includes
WebChanges will not do what it should.
WebChanges, and all the System web topics need to be converted from
INCLUDINGWEB
to
BASEWEB
for 1.0.1 .
this bug means anyone using topics that point to
WebChanges will see the TWiki web's changes, not what it used to - so urgent !
--
SvenDowideit
Good catch. To assist and get it closed I did this one
--
KennethLavrsen - 13 Jan 2009
there are alot more topics with the same problem,
basically, all Web* topics are likely to be included in a chain. for eg,
WebRss may be made by the user INCLUDING{Main.WebRss} which then INCLUDES{System.WebRss} - resulting in their rss feed saying that they are getting the changes of the 'Main' web.
same issue wrt INCLUDINGTOPIC, but even more subtle
but i've found a further oddity if you
INCLUDE{System.Macros} - see
Item771
--
SvenDowideit - 15 Jan 2009
ok, so the Web* topics are all done, and
Item771 deals with the related issues for the Var* topics.
--
SvenDowideit - 05 Feb 2009