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!

View Revisions: Issue #359		[ All Revisions ] [ Back to Issue ]
Summary	0000359: Two different urls will lead to same physical template on Front-End

Revision	2009-10-08 11:42:22 by Dmitry
Description	In case, when physical template link is build using st_CachedMenu tag, then actual path to template in structure (if any) is used for url. In case, when m_Link tag is used without st_CachedMenu tag, then url is actual path to template on disk. For example: 1. "terms-and-conditions" - st_CachedMenu variant 2. "terms" - m_Link variant

Revision	2009-10-08 11:40:08 by Dmitry
Description	In case, when physical template link is build using st_CachedMenu tag, then actual path to template in structure (if any) is used for url. In case, when m_Link tag is used without st_CachedMenu tag, then url is actual path to template on disk. For example: 1. "terms-and-conditions" - st_CachedMenu variant 2. "terms" - m_Link variant

Revision	2009-10-08 11:40:08 by Dmitry
Description	In case, when physical template link is build using st_CachedMenu tag, then actual path to template in structure (if any) is used for url. In case, when m_Link tag is used without st_CachedMenu tag, then url is actual path to template on disk. For example: 1. "terms-and-conditions" - st_CachedMenu variant 2. "terms" - m_Link variant