Anonymous | Login | Signup for a new account | 2023-09-30 10:58 CDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Horizontal ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001302 | [In-Portal CMS] Template System | bug report | always | 2012-05-29 05:39 | 2012-07-25 05:30 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001302: Parameters js_escape, html_escape, strip_nl, trim are ignored by <inp2:m_include .../> tag | ||||
Description |
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. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic![]() In-Portal Open Source CMS |