Switching from Coral UI3 to Coral UI2 in RTE | Community
Skip to main content
dineshc12261746
dineshc12261746
Level 2
April 3, 2018

Switching from Coral UI3 to Coral UI2 in RTE

  • April 3, 2018
  • 5 replies
  • 11046 views

The documentaion below mentions here that, we can switch rte from coralui3 to coralui2 . , However it is suggesting do the changes in libs

Rich Text Editor

As changing anything in /libs might create issues when installing hotfix to SP's . Is there any other way to achieve it ?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    5 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    April 3, 2018

    Excellent share with the community!!

    Kautuk Sahni
    smacdonald2008
    smacdonald2008
    Level 10
    April 3, 2018

    WHy would you want to use Coral 2 in the RTE when using 6.3?

    benjamin_cheria
    benjamin_cheria
    Level 2
    April 3, 2018

    CoralUI3 RTE is broken in 6.3 GA in some instances such as multiple RTEs in the same dialog or multi field. They issues that I was having all seem to be resolved with 6.3.1.2. So if you're having RTE issues in 6.3, install SP1 and CFP2

      smacdonald2008
      smacdonald2008
      Level 10
      April 3, 2018

      The granite.coral multi field works much better than the older granite multi field.

      For example, you do not need to write JS or use ACS-Commons. It works OOTB. See this article on granite/Coral MF -- Building Experience Manager Components using Granite/Coral Resource Types

        dkumar_gobi
        dkumar_gobi
        Level 2
        April 26, 2018

        RTE Issues with multiple tabs and multifield are present is 6.3.2.0 release (April-5-2018 ). Switching to RTE to CoralUI2 from CoralUI3 solves most RTE Multifield issues (Link plugin -pathbrowser fails in multifield etc). Follow the exact steps .Overlay the files in your project.

        https://helpx.adobe.com/experience-manager/6-3/sites/authoring/using/rich-text-editor.html#SwitchingtoCoral2RichTextEditor

          H
          Adobe Employee
          habansalAdobe Employee
          Adobe Employee
          April 27, 2018

          dkumar.gobi It is recommended to use Coral3 RTE and not switch to Coral2 RTE.

          RTE's behavior is not expected to differ wrt using its Coral2 or Coral3 version as long as any custom code is not touching RTE internals. Also, we have resolved most of the issues in RTE (both Coral2 and Coral3) in latest available CFP for 6.3.

          However, If you face any issues while using Coral3 RTE, please report them to us as bugs to get them addressed in the next possible CFP.

            dkumar_gobi
            dkumar_gobi
            Level 2
            April 27, 2018

            Thanks, Will raise Adobe Ticket .Below are the RTE issues faced in CoralUi3 6.3.2.0 release without any custom plugins.

            RTE in Multifield & Multiple RTE in single dialog tab.

                 1) RTE toolbar visually blocks data.Very difficult for authors to select the data

                 2) Link plugin-Path browser doesn't have path lookup , forcing authors to manually type link path

              U
              user09435
              November 8, 2018

              I am facing an issue with coral3 RTE, after installing 6.3.3. service pack. I have custom style tags added into RTE styles plugin, and the list is quite long. When I open RTE styles dropdown (in either full screen or original view), the UI flickers the vertical scroll bar infinitely and does not let content authors select the dropdown value. This is blocking the content authoring. Do we know this as known issue and have a resolution for this?

                P
                prabhath_tavva
                November 28, 2018

                vijayanandvinju​ -- I am using AEM 6.3.3.1 (SP3 with CFP1) and am facing the same issue. Did you find any fix or workaround ?

                smacdonald2008​, kautuksahni aneeta45259594 -- Can you help with this ?

                  U
                  user09435
                  November 28, 2018

                  I raised a daycare ticket - and the Adobe team acknowledged the issue. This is going to be fixed in the CFP2 estimated to be available in January 2019 release.

                  Workaround - flickering does not happen on full screen mode of the authoring dialog.

                    arunpatidar
                    Community Advisor
                    arunpatidarCommunity Advisor
                    Community Advisor
                    November 8, 2018

                    If anyone facing problem of switching RTE focus when click on toolbar (plugins), below JS can be added as authoring or extraClientLibs

                    as workaround.

                    (function($, $document) {

                        "use strict";

                        $document.on("dialog-ready", function(e) {

                            $("coral-dialog .coral-Dialog-wrapper .coral-Dialog-content .coral-Panel").each(function() {

                                var rteItems = $(this).find(".richtext-container");

                                var rteTextItems = $(this).find(".richtext-container>div.coral-RichText-editable.coral-Textfield");

                                if (rteItems.length > 1) {

                                    setTimeout(checkRTE, 100);

                                    function checkRTE() {

                                        rteTextItems.attr("contenteditable", "false");

                                        rteTextItems.on('click', function() {

                                            $(this).attr("contenteditable", "true");

                                            rteTextItems.not(this).attr("contenteditable", "false");

                                             $(this).focus();

                                        });

                                    }

                                }

                            });

                        });

                    })($, $(document));

                    Arun Patidar
                      Terms & ConditionsAccessibility statement

                      Loading footer...