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!
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories
  

View Revisions: Issue #306 [ All Revisions ] [ Back to Issue ]
Summary 0000306: Parameter "result_to_var" doesn't work for m_Param tag
Revision 2009-09-18 07:53:09 by alex
Additional Information Problem is hidden in "result_to_var" parameter implementation code. There are two places, where this parameter is processed:
* compiled template code
* PostProcess method of TagProcessor class

1. for non-pair tags this parameter is processed in both places
2. for pair tags this parameter is processed on in 2nd place (PostProcess method).

PostProcess method set's tag result to parser parameter on current deep level. That raises a problem, when deep level is changed after that. For example: all pair tags change deep level and they automatically loose parameter value, when deep level is restored.

I propose, that we should move all "result_to_var" parameter processing into compiled template code to avoid such problem in future.

=====================

In case if we comment-out "result_to_var" processing in PostProcess method, then there is fatal error about missing "_TagProcessor" in all grids in administrative console.
Revision 2009-09-18 03:24:23 by alex
Additional Information Problem is hidden in "result_to_var" parameter implementation code. There are two places, where this parameter is processed:
* compiled template code
* PostProcess method of TagProcessor class

1. for non-pair tags this parameter is processed in both places
2. for pair tags this parameter is processed on in 2nd place (PostProcess method).

PostProcess method set's tag result to parser parameter on current deep level. That raises a problem, when deep level is changed after that. For example: all pair tags change deep level and they automatically loose parameter value, when deep level is restored.

I propose, that we should move all "result_to_var" parameter processing into compiled template code to avoid such problem in future.

Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories
  

Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker