-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.0.0
-
Fix Version/s: 5.2.0-RC1
-
Component/s: Template System
-
Labels:None
-
External issue URL:
-
Change Log Message:Fixes problem, where m_include tag wasn't processing strip_nl parameter
-
Story Points:1
-
External issue ID:1302
-
Copy Issue Key:
-
Patch Instructions:
One of the powerful In-Portal features is an ability to create blocks of HTML that can be reused multiple times later. For example:
<inp2:m_DefineElement name="some_element">
... some html here ...
</inp2:m_DefineElement/>
Then these elements can be used via <inp2:m_RenderElement name="some_element"/> tag in any template.
Usually we have multiple blocks definitions in a dedicated templates and you need to include that template via <inp2:m_include template="path/to/block_definitions/template"/> tag to be able to use them.
To increase readability of these files (that only contains blocks) we add some empty lines between block declarations. As a result all these empty lines between block declarations are added into resulting HTML page.
To solve it we started adding strip_nl="2" parameter into m_include tag, like this <inp2:m_include template="path/to/block_definitions/template" strip_nl="2"/>, but it wasn't ever processed by that tag.
After a deeper investigation I've found that none of:
- js_escape
- html_escape
- strip_nl
- trim
are being processed in that tag.
- mentioned in
-
Wiki Page Loading...