Details
-
Improvement
-
Resolution: Duplicate
-
Major
-
xCM 4.2
-
None
-
4.2 17039
Description
By default, the FCK CSS is pre-initialized when you open a big text. However the CSS of FCK does not fit with the CSS of the Corpv1 templates. So if you try to use some styles, they are not reflected on the underlying page.
If you now try to change the default CSS (e.g: to the jahia default one - this one should normally automatically reuse the CSS used within the current template so that default styles could be different from one template to the other - I do not know if such a feature still works correctly (or never worked at all 
), changes are applied. But if I reopen my bigtext, the FCK CSS is reinitialized by default (with my previous DIV which are not taken in account).
So this is quite confusing from a end-user point of view (I do not include the fact that from a semantic point of view we then have some unused DIV in the HTML of big text that may cause some problem during migration afterwards as suddently this tags may appear on a new version of the templates).
So:
1) Do we still want to display by default all this "dynamic" CSS? (+1 in order to map by default FCK and other editors to the default Jahia CSS and do not display such a drop down - just comment such an option in the template guide and comment that in the adeqaute config file (I do not know which one)).
2) At least, if another criteria missed me, could we used by default the Jahia CSS which is the one which fit with the underlying template?
3) (for Jahia 5.0 only I presume, as this will be too much changes for the 4.2 and we do not have the time right now) could we serialize within a cookie (or in the DB or elsewhere), the default CSS used so that, when we update a content, the CSS used the first time is correctly reused? (same is true in multilanguage with the "recopy to all languages" option which could serialize somehwere).
TestRail: Results
Attachments
Issue Links
- duplicates
-
JAHIA-1304 FCK Default CSS + storage of CSS used + incompatibility with existing templates
-
- Closed
-
- is duplicated by
-
-
- Closed
-
Activity
Stephane Croisier (Inactive)
added a comment - Ok I am not sure I understand all these problems of CSS/SP/etc...
Historically speaking, from a functional point of view (it was Jahia 2 I think so it is quite old), we added such a feature because a customer wanted to be able to dynamically load the CSS styles used within the current template within the WYSIWYG editor. So for instance on the simple page, the allowed styles would not have been similar that the ones available on the double page. Such a customer also configured the WYSIWYG editor in order to remove all the button excepted the dynamically loaded Styles drop-down within the editor. The goal was simple: avoid that editor use other styles than the ones defined within the JSP.
What I do not understand right now is if such an option still works or not? Do we dynamically load the CSS from the JSP template or is the same set of styles used for all the Jahia templates?
Finally if only one CSS is activated, we might hide the CSS selection drop down box as nobody (99% of the cases) could use it.
Stéphane
Stephane Croisier (Inactive)
added a comment - Ok I am not sure I understand all these problems of CSS/SP/etc...
Historically speaking, from a functional point of view (it was Jahia 2 I think so it is quite old), we added such a feature because a customer wanted to be able to dynamically load the CSS styles used within the current template within the WYSIWYG editor. So for instance on the simple page, the allowed styles would not have been similar that the ones available on the double page. Such a customer also configured the WYSIWYG editor in order to remove all the button excepted the dynamically loaded Styles drop-down within the editor. The goal was simple: avoid that editor use other styles than the ones defined within the JSP.
What I do not understand right now is if such an option still works or not? Do we dynamically load the CSS from the JSP template or is the same set of styles used for all the Jahia templates?
Finally if only one CSS is activated, we might hide the CSS selection drop down box as nobody (99% of the cases) could use it.
Stéphane This error duplicates with JAHIA-1304, so I closed it.
The timeframe for Jahia 4.2 is too short to fix it entirely. I simply made only the Jahia Engine Demo Style the only selectable style in the combobox. The problem with that style was, that the background color of the FCK Editor became transaparent, so I added a body tag in the jahia.css to set it to white. I hop there are no side-effects. So far I could not see any.
The jahia.css is also not really compatible to the templates as it is never included in the templates. The templates use a JSP file as CSS.
To answer your questions: Jahia does not dynamically load the CSS from the JSP template, but the same set of styles is used for all Jahia templates. The only option I saw in the config file, is to distinguish between different CSS files per site, but I have not tested that.
If we remove the combobox, customers might not find out, that the option of configuring own styles exists at all.