|
In-Portal Issue Tracker - In-Portal CMS
|
|
Viewing Issue Advanced Details |
|
|
ID:
|
Category:
|
Type:
|
Reproducibility:
|
Date Submitted:
|
Last Update:
|
|
189 |
[In-Portal CMS] Admin Interfaces |
bug report |
always |
2009-08-06 10:26 |
2009-10-03 07:57 |
|
|
Reporter:
|
Dmitry |
Platform:
|
|
|
|
Assigned To:
|
alex |
OS:
|
|
|
|
Priority:
|
normal |
OS Version:
|
|
|
|
Status:
|
closed |
Product Version:
|
5.0.0 |
|
|
Product Build:
|
|
Resolution:
|
fixed |
|
| |
|
ETA:
|
none |
Fixed in Version:
|
5.0.1 |
|
|
Reference:
|
|
|
Change Log Message:
|
|
|
Estimate Points:
|
0 |
|
|
Summary:
|
0000189: Changes in Options for "Section Template" field for Sections |
|
Description:
|
Currently it's confusing when we have EMPTY field which works as Inherit from Parent. Often users won't put anything there and it will lead to a Fatal Error since NO design template specified.
Propose to do the following:
1. When Adding NEW Top section (ParentId = 1), we'll list only existing designs (taken from drop-down) defaulting to the template specified in cms_DefaultDesign varianble.
This variable will be defined under Admin->Configuration->Website->Advanced: Website Settings as a text field and will default to "platform/designs/general"
Place variable after:[10.05] Config_Site_Time
Variable name will be la_prompt_DefaultDesignTemplate (already in DB) -- Default "Section Template".
I'll add/change it myself in a language pack in a different task.
2. When Adding or Editing the Section of 2+ level deep we'll have list of physical template designs + empty value named [Inherit from Parent] (should be fist selection)
|
|
Steps To Reproduce:
|
|
|
Additional Information:
|
|
| Relationships | | parent of | 0000184 | closed (5.0.1) | alex | Selecting default Section Design |
|
|
Attached Files:
|
|
|
|
Issue History |
|
Date Modified |
Username |
Field |
Change |
|
2009-10-03 07:57 |
administrator |
Note Added: 0000792 |
|
|
2009-10-03 07:57 |
administrator |
Status |
resolved => closed |
|
2009-08-08 13:38 |
alex |
Fixed in Version |
=> 5.0.1 |
|
2009-08-08 13:38 |
alex |
Note Added: 0000279 |
|
|
2009-08-08 13:38 |
alex |
Status |
reviewed and tested => resolved |
|
2009-08-08 13:38 |
alex |
Resolution |
open => fixed |
|
2009-08-08 13:38 |
alex |
Changeset attached |
5.0.x r12231 |
|
2009-08-08 13:25 |
alex |
Note Edited: 0000278 |
bug_revision_view_page.php?bugnote_id=0000278#r161 |
|
2009-08-08 07:36 |
alex |
Note Added: 0000278 |
|
|
2009-08-07 10:48 |
Dmitry |
Relationship added |
parent of 0000184 |
|
2009-08-06 10:52 |
Dmitry |
Summary |
Changes in Options for "Template Design" field for Sections => Changes in Options for "Section Template" field for Sections |
|
2009-08-06 10:52 |
Dmitry |
Description Updated |
bug_revision_view_page.php?rev_id=135#r135 |
|
2009-08-06 10:26 |
Dmitry |
New Issue |
|
|
2009-08-06 10:26 |
Dmitry |
Status |
active => reviewed and tested |
|
2009-08-06 10:26 |
Dmitry |
Assigned To |
=> alex |
|
Notes |
|
|
(0000278)
|
|
alex
|
2009-08-08 07:36
(edited on: 2009-08-08 13:25) |
|
|
Reminder sent to: Dmitry
Phrase prefix "la_prompt_" is deprecated and should not be used (like in "la_prompt_DefaultDesignTemplate" phrase). You should use "la_config_" prefix for configuration variables.
It will also be good to rename all "la_prompt_" phrases to match their use: "la_fld_" or "la_col_" or "la_config_" or anything from wiki, that will match their usage.
I'll change this phrase in this task.
|
|
|
|
(0000279)
|
|
alex
|
|
2009-08-08 13:38
|
|
Fix committed to 5.0.x branch. Commit Message:
1. Fixes 0000189: Changes in Options for "Section Template" field for Sections.
2. Implemented not exactly the way as planned, because administrator can change "Parent Section" from "Content" (top category, where "Inherit from Parent" option in "Template" field not available) to it's child section, where this option should be available. As a result I always show "Inherit from Parent" option, but when administrator manually selects "Inherit from Parent" in "Template" field and "Content" in "Parent Section" field and tries to save changes, I show him an error about that. |
|
|
|
|
|
Closing issues from 5.0.1 version, because version was already released. |
|