Anonymous | Login | Signup for a new account | 2024-04-25 12:37 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 |
0001386 | [In-Portal CMS] Data Management | bug report | always | 2012-09-03 07:45 | 2012-09-14 10:21 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | resolved | ||||
Summary | 0001386: Incorrect section/category physical template detection | ||||
Description |
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. |
||||
Additional Information | This bug happens on all In-Portal 5.x versions (since symlink term was introduced), but kApplication::getPhysicalTemplate method only exists since 5.2.0-B1 version. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |