• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7700 for generic doc work for TWiki-6.0.2. Use View topic Item7703 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Test on LitterTray: IncludeWebpageTest

The html at the h1 header looks like:

<h1 class="title" title="Permalink &#187; 36 Checks &#038; tips voor usability van formulieren" id="post-233">
         <a href="http://www.usarchy.com/2006/09/tips-usability-formulieren/" rel="bookmark">
         36 Checks &#038; tips voor usability van formulieren         </a>
        </h1>

TWiki interprets the 36 as a numbered bullet list, resulting in a completely messed up page. Setting raw="on" doesn't help.

I would expect TWiki does not do anything with bullet lists, or any item on the page.

AC

Actually, TWiki will still parse the included content, even with the raw parameter set. So, as in this case, if the number of spaces used in the included content incidentially is 3*x, some rendering might kick in.

Added a literal option to INCLUDE to allow for escape of the rendering pass.

-- SP

Isn't the literal option way too high on the nerdometer? With all due respect to compatibility: I'd never ever expect to have an included HTML page processed by TWiki. It is strange enough to have a .txt page processed by TWiki, but this may have its justification if someone attaches a TWiki topic, but for .html this is IMHO pure nonsense.

The <literal> ... </literal> wrapping should be applied to all .html files from the local attachment store, and to text/html files retrieved with getURL, and to no .txt and text/plain files.

-- haj

Would it break installations if we default to literal, so external files are not processed?

AC

We could change spec to add <literal> tags per default and change the parameter to render="on"?

Doing this triggers a compatibility issue, so it should go through the release process if this is the better logic.

As long as it is possible to do both logics with the included content, I'm OK.

-- SP

TWiki:Codev.IncludeNeedsToProcessHtmlLiterally


This should be mentioned in the release notes, closing.

-- SP

ItemTemplate
Summary New litteral option for %INCLUDE% (was: including external web page creates unwanted list items)
ReportedBy TWiki:Main.ArthurClemens
Codebase

SVN Range TWiki-4.1, Mon, 06 Nov 2006, build 11926
AppliesTo Engine
Component

Priority Normal
CurrentState Closed
WaitingFor

Checkins 11947
TargetRelease minor
Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r12 - 2007-01-16 - JasonHill
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback