You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I know that it should be written under WRAP plugin discussion page; but, no comments were available. My problem is conflict between listing blog items and using <WRAP column half> and using <h1> elements. For example,
<WRAP column half>
====== Wiki page ======
- Some items
- Some items
- Some items
- Some items
</WRAP>
<WRAP column half>
====== Blog entries ======
{{blog>blog:a_blog?3&inline}}
</WRAP>
The above should be displayed
====== Wiki page ======
- Some items
- Some items
- Some items
- Some items
should be in left side; and,
======= Blog entries ======
===== first blog item =====
xxxxxxxxxx
===== second blog item =====
sssssssss
should be right side. But, blog items does not have ===== (2nd header, <h2>); but, has 1st header, <h1>.
If I remove all the <WRAP column half> elements, the page renders correctly. I hope I made myself clear. :-( Thanks for reading!
The text was updated successfully, but these errors were encountered:
The problem is that the blog plugin automatically tries to find the right header level by searching in the already printed HTML output. However, in the case of the wrap plugin, it won't find the right level. I guess the easiest solution would be to add an extra flag to the blog syntax for overriding the automatic level detection.
Hello, I know that it should be written under WRAP plugin discussion page; but, no comments were available. My problem is conflict between listing blog items and using
<WRAP column half>
and using<h1>
elements. For example,The above should be displayed
should be in left side; and,
should be right side. But, blog items does not have
=====
(2nd header,<h2>
); but, has 1st header,<h1>
.If I remove all the
<WRAP column half>
elements, the page renders correctly. I hope I made myself clear. :-( Thanks for reading!The text was updated successfully, but these errors were encountered: