-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.2.0-B1
-
Fix Version/s: 5.2.1-B1
-
Component/s: Data Management
-
Labels:None
-
External issue URL:
-
Additional information:
-
Change Log Message:Fixes incorrect section physical template detection
-
Story Points:1
-
External issue ID:1386
-
Copy Issue Key:
-
Patch Instructions:
In-Portal has 2 types of sections/categories in "Structure & Data" section:
- physical - sections, that have 1 template on disk (TPL file) connected to them
- virtual - sections, that share single template (design template) with other sections (pure CMS pages, that just have different content, but identical layout)
Because of that physical sections actually have 2 urls:
- one, that matches TPL file location inside a theme
- other, that match associated section location inside "Structure & Data" section
If developer is required to perform specific actions based on physical template being used to render a page then method kApplication::getPhysicalTemplate can be used.
However I've recently found out, that virtual section has a symlink to a physical section this method sometimes failed to properly detect actual TPL file being used.