Question
Normally, when a non-existent wiki word is used on a page, there is a little "?" created that links to the new topic. However, in all such situations, on my Twiki, those links now extend beyond the "?" to include large blocks (I think to the end of the paragraph) of the rest of the page. As a simple example, I have a simple test topic that looks like this:
NonExistingWikiWord followed by text that
is included in the link. AnotherNonExistingWikiWord
<p>The next sentence is not.
%MAKETEXT{'abc'}%
-- Main.SeanDavis - 18 Oct 2007
This gets rendered (using the print skin and with javascript includes, etc. excluded, to keep things simple) as:
</head>
<body class="natBody natPrintBody">
<div class="natBodyContents">
<div class="natMiddle natMain">
<div class="natMainContents">
NonExistingWikiWord<A }%="" topic="" this="" create="" title="%MAKETEXT{" rel="nofollow" NonExistingWikiWord?topicparent="Sandbox.SpreadSheetPluginTest"" Sandbox="" edit="" href="%SCRIPTURLPATH{">? followed by text that
<p />
is included in the link. AnotherNonExistingWikiWord<A }%="" topic="" this="" create="" title="%MAKETEXT{" rel="nofollow" AnotherNonExistingWikiWord?topicparent="Sandbox.SpreadSheetPluginTest"" Sandbox="" edit="" href="%SCRIPTURLPATH{">?
<p />
<p>The next sentence is not.
<p />
<p />
'abc'
<p />
-- <a href="/twiki/bin/view/Main/SeanDavis" class="twikiLink">SeanDavis</a> - 18 Oct 2007
<p />
</div>
<div class="natMainFooterContents"></div>
</div>
</div>
</body>
</html>
<!-- template: view.print.nat.tmpl -->
<!-- template: strings.nat.tmpl -->
<!-- template: javascript.nat.tmpl -->
This is very strange to me and I do not know where to begin to look for the problem.
Thanks,
Sean
Environment
--
SeanDavis - 19 Oct 2007
Answer
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
I answered my own question. For whatever reason, the NEWLINKFORMAT variable in my local installation in the
TWikiPreferences was causing the problem. After either removing it or cleaning it up, the links are working fine.
--
SeanDavis - 19 Oct 2007