Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
[textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
Bug Description: Strange paragraph around a == used in an article
Edit: Simplified the bug description
Reproducible? Yes
Input
Note: Space before notextile. is necessary only here to keep the code block together. The space in the last line is intended.
Some text
==<h3>Some text</h3>==
notextile. <h3>Some text</h3>
==Some text==
notextile. Some text
Some text
Some textOutput
<p>Some text</p>
<p><h3>Some text</h3></p>
<h3>Some text</h3>
<p>Some text</p>
Some text
<p>Some text</p>
Some textI am talking about the strange paragraph surrounding the == (h3) string and about the p wrapping the ‘some text’ string. Update: And not about the <h3> tag :)
- Using a space before
==doesn’t help. - Using
notextile.works as expected
Bug reported.
Related? A form output shows the same behavior
- Removing (!) the
==before and after a form output (if used) doesn’t help. - It’s like the ‘some text’ behavior.
- Shouldn’t TXP be clever enough to check if the form is ‘proper HTML’ or if it is necessary to wrap it in a paragraph?
Last edited by merz1 (2008-03-09 00:51:49)
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
Why don’t you use:
h3. Title
Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
Or
<h3>Title</h3> <!-- there is an space before the opening tag -->Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
The <h3> work fine, even without the ==.
The bug is the wrapping paragraph not the HTML code I published for demonstration purposes. Before it was a pretty ugly code block to demonstrate the problem. Maybe now it is too easy :-)
I discovered the original problem using a ==<txp:output_form form="foo" />==. And long time ago I discovered that <txp:output_form form="foo" /> behaves the same way and started to use the == solution. I don’t know if this is a textile regression in 4.0.6 or if I was too stupid to see it earlier.
- Bug: The problem is that
==whatever is here==will get a p wrapping. - OK: Do the same with
notextile. whatever is hereand all is fine.
Expected (like documented)
Both should produce the same and correct output!
Got it now?
Last edited by merz1 (2008-03-09 01:00:50)
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
#5 2008-03-09 03:37:11
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
The double-quotes are for inline use, whereas notextile is for block use.
Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
OK, then it needs some documentation like “don’t use == at the beginning of a line” which sounds not very Textpatter like.
Wouldn’t it be easier (read: more consistent) to make notextile. and == behave the same.
I see the same problem with an ul inside of a blockquote. For me this also is a bug. I expect to get a pure ul inside of a blockquote and not a p-wrapped one.
Input
Update: Already reported (see comment below). Pls. follow-up there.
bq.. A *simple* example.
* some li text
* some li text
the endOutput
<blockquote>
<p>A <strong>simple</strong> example.</p>
<p> <ul>
<li>some li text</li>
<li>some li text</li>
</ul></p>
<p>the end</p>
</blockquote><p><ul> and </ul></p> don’t look like an expected result.
There are some heavy issues going on with that p-wrap thingy!
Last edited by merz1 (2008-03-10 10:59:32)
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
And here we have a <pre><code> wrapping problem
bc.. A *simple* example.
* some li text
* some li text
the end<pre><code>A *simple* example.
</code>
<code>* some li text
* some li text
</code>
<code>the end
</code></pre>To me this doesn’t look correct.
Get all online mentions of Textpattern via OPML subscription: TXP Info Sources: Textpattern RSS feeds as dynamic OPML
Offline
Re: [textile] 4.0.6: Paragraph around ==<h3>Some text</h3>==
<p><ul>and</ul></p>don’t look like an expected result.
Already reported.
For the inline vs block notextile, it’s already covered in the documentation, albeit not explicitly (look under “Raw HTML”). The first example is inline, whereas the second is block.
Offline