Anonymous | Login | Signup for a new account | 2024-03-29 00:33 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001146 | [In-Portal CMS] Front End | bug report | always | 2011-10-17 08:19 | 2012-07-25 05:32 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001146: Tag "st_CachedMenu" sets incorrect "template" parameter to menu elements (v 5.1.0) | ||||
Description |
Below is the code, that could be to display website menu top level: <inp2:m_DefineElement name="menu_element"> <a href="<inp2:m_Link template='$template' m_cat_id='$cat_id' use_section='$use_section'/>"> <inp2:m_Param name="title"/> </a> </inp2:m_DefineElement> <inp2:st_CachedMenu render_as="menu_element" category_id="1"/> This code works before and after In-Portal 5.1.0 version. Problem arises, when developer tries to use "template" parameter directly without passing it to m_Link tag. For example here the result of <inp2:m_Param name="template"/> tag before & after In-Portal 5.1.0 release: before 5.1.0 release: "path/to/template" after 5.1.0 release: "id:434" (434 is ID of a section, that is displayed in menu) Attached patch restored pre 5.1.0 behavior related to "template" parameter value. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |