Anonymous | Login | Signup for a new account | 2024-05-04 07:51 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Horizontal ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001268 | [In-Portal CMS] Front End | bug report | always | 2012-04-26 10:28 | 2012-07-25 05:30 |
Reporter | erik | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001268: Ease of editing Content Blocks | ||||
Description |
On the one hand, it is convenient when the HTML-code, is included in the Content Block as simple as possible (do not have a lot of styles, formatting) - then the user is easier to avoid mistakes in the elements styling. On the other hand, it is desirable that when editing a Content Block looks like on the page, that is, that its elements have the same style as on the page. In order to satisfy both above requirements, I suggest add to ContentBlock tag optional "class" parameter. If this option is specified, then in the CMS-editor window, the value of this parameter is added to the "class" attribute of <body> tag. For example, if class is not specified, <body> tag is the way it is now - <body contenteditable="true" spellcheck="false" class="cke_show_borders">. If in the template is written <inp2:st_ContentBlock num="1" class="big-font"/>, then the "body"-tag will be the - <body contenteditable="true" spellcheck="false" class="cke_show_borders big-font"> That is, we should not include in the CMS-content unit covering element to apply all related styles in the CMS editor window. And the content of CMS block may contain no "class" attributes, but have adequate and powerful styling applied. |
||||
Additional Information |
As a result tag <inp2:st_ContentBlock will have these additional parameters: 1. body_class - class of BODY tag in CKEditor 2. body_id - id of BODY tag in CKEditor Additionally there will be ability to specify "extraCss" parameter in CKEditor configuration file (thanks to Drupal modifications of CKEditor at http://drupal.org/project/ckeditor), that allows any custom CKEditor-wide CSS to be applied along with theme-specific external CSS file. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |