In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Relationship Graph

[ View Issue ] [ Dependency Graph ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0000436	[In-Portal CMS] Template System	task	always	2009-12-04 13:04	2010-01-11 22:01

Reporter	alex	View Status	public
Assigned To	alex
Priority	normal	Resolution	fixed
Status	closed

Summary	0000436: Changing behavior of "m_Comments" tag to better support internal comments
Description	Currently <inp2: tags inside HTML comment tags are not processed, but there are cases, like: <!--[if IE 6]><script type="text/javascript" src="<inp2:m_TemplatesBase/>/js/min-max.js"></script><![endif]--> when they should work. Currently we have tag <inp2:m_Comment>...</inp2:m_Comment> that doesn't show it's contents after parsing. It's pretty useless since we can write comments in form <!--## to remove ##--> that will do the same without additional tags. I propose we make <inp2:m_Comment> tag create areas in template where <inp2: tags inside comments could be parsed (it will change NParser->InsideComment mark and then restore it's back at the end). Resulting code will be: <inp2:m_Comment><!--[if IE 6]><script type="text/javascript" src="<inp2:m_TemplatesBase/>/js/min-max.js"></script><![endif]--></inp2:m_Comment> We could also rename this tag to make sure it's named by the action it does.
Additional Information