Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-2062 Sp2: Big text engine: Display optimizations
  3. JAHIA-2065

SP2 big text: one break line is worth nothing + removes styles + put FCKEditor switching box after the editor

Details

    • Sub-task
    • Resolution: Done
    • Major
    • WCM 5.0 SP3
    • WCM 5.0 SP2
    • None
    • Sp2

    Description

      I recopy the bug (jahia-1304) as there is no way to move it under this new section.

      The goal is to remove the break line which is worth nothing between the drop downs and the WYSIYG editor. Then to remove the CSS by default (=keep the option but with only one CSS activated... and if only one CSS is activated we do not need to show the drop-down "available CSS" any more). Finally please put the FCKEditor + AVailable CSS line AFTER the editor. So with all the other improvements suggested (cf parent bug), FCK should be launched straight ahead after the title of the field and then could be resized at a larger size.

      TestRail: Results

        Attachments

          1. screenshot-1.jpg
            screenshot-1.jpg
            152 kB
          2. screenshot-2.jpg
            screenshot-2.jpg
            93 kB
          3. screenshot-3.jpg
            screenshot-3.jpg
            19 kB

          Issue Links

            Activity

              [JAHIA-2065] SP2 big text: one break line is worth nothing + removes styles + put FCKEditor switching box after the editor

              There was a configuration error in the default htmleditors_config.xml

              pap@commaro.com_old Benjamin Papez (Inactive) added a comment - There was a configuration error in the default htmleditors_config.xml

              Looks like Jahia tries to load something in the corporate_templates and not in the corpv2 (I am using the corpv2)

              scroisier Stephane Croisier (Inactive) added a comment - Looks like Jahia tries to load something in the corporate_templates and not in the corpv2 (I am using the corpv2)

              I now have a JSS error when tryint to enter a new blog entry (with IE6) when goiing into my blog main:content on the build 18510 (cf screenshot)

              scroisier Stephane Croisier (Inactive) added a comment - I now have a JSS error when tryint to enter a new blog entry (with IE6) when goiing into my blog main:content on the build 18510 (cf screenshot)

              The editor combobox was moved below the editor.

              The CSS combobox was removed completely. We do not offer the functionality anymore to let the editor choose a CSS.
              The CSS is still determined via the htmleditors_config.xml. The list of available CSS is parsed and the first CSS which maches the template is taken (selectors are either the <allowed-sites>, or if the CSS is <shared> then also the <allowed-templatesets> could be determined). You can reference a CSS within the site's template structure and you can use a %SITE_NAME% placeholder instead of the sitename.

              If you want to overload the automtic determination of the CSS, you can also set a specifc CSS to a BigText, by setting a field property, like this (taken from the blog definition):

              <%
              jData.containers().declareFieldDefProp("blogBody",
              JahiaFieldDefinitionProperties.FIELD_STYLESHEET_ID_PROP,
              "corpv2_blog");
              %>

              You have to make sure that there is an entry for the key "corpv2_blog" in the htmleditors_config.xml.

              Beside the CSS file, which will be used in the editor, In this configuration file you could also set the styles definition XML file, which controls which styles are displayed in the combobox by the FCKeditor.

              pap@commaro.com_old Benjamin Papez (Inactive) added a comment - The editor combobox was moved below the editor. The CSS combobox was removed completely. We do not offer the functionality anymore to let the editor choose a CSS. The CSS is still determined via the htmleditors_config.xml. The list of available CSS is parsed and the first CSS which maches the template is taken (selectors are either the <allowed-sites>, or if the CSS is <shared> then also the <allowed-templatesets> could be determined). You can reference a CSS within the site's template structure and you can use a %SITE_NAME% placeholder instead of the sitename. If you want to overload the automtic determination of the CSS, you can also set a specifc CSS to a BigText, by setting a field property, like this (taken from the blog definition): <% jData.containers().declareFieldDefProp("blogBody", JahiaFieldDefinitionProperties.FIELD_STYLESHEET_ID_PROP, "corpv2_blog"); %> You have to make sure that there is an entry for the key "corpv2_blog" in the htmleditors_config.xml. Beside the CSS file, which will be used in the editor, In this configuration file you could also set the styles definition XML file, which controls which styles are displayed in the combobox by the FCKeditor.

              People

                pap@commaro.com_old Benjamin Papez (Inactive)
                scroisier Stephane Croisier (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases

                      Packages

                        Version Package
                        WCM 5.0 SP3