Hi niksonawanePlease make sure that you are using different Plugin,
Dialog, feature namesApart, from that, you should be using different
integer index at Line 46 -tbGenerator.addElement(GROUP,
plg.Plugin.SORT_FORMAT, this.pickerUI,
10);andtbGenerator.addElement(GROUP, plg.Plugin.SORT_FORMAT,
this.pickerUI, 11);
Hi @om_vineetAs I explained in my previous comment, Inserting
pre-rendered HTML pieces doesn't really seem to be recommended by the
SPA frameworks (React even names the method
"dangerouslySetInnerHTML").We actually already have some of this problem
with the RTE that returns HTML and that must be injected into
React/Angular in that ugly way. As future enhancements, we might
therefore rather do that the RTE uses Markdown syntax for such cases, so
that there's no more HTML at all mixed up in the JS...
The fix for that would be to modify the XSS config to allow it from here
-/libs/cq/xssprotection/config.xmlBut, please note that it's not
recommended to modify it. This html is not allowed as per the XSS config
(I am not aware of the reason). So, best is to avoid using this. You
could try to search on google if it's a valid and secured html. If it
is, you can try to modify the xml
Which AEM version are you on ? The popover should be closed before
moving to the maximized dialog. RTE handles that by itself at least on
the latest version.Calling any event directly would only hide this
problem, not really solve the issue. You could see some other issue as a
side effect.Can you try it on a latest SP/CFP installation, otherwise
report it as an issue ?
Hi Matt-H- I would like to get answers to a few questions from your side
to better understand your issue.Can you specify which AEM version are
you using ?Whichever version you are one, can you check after installing
the latest SP and CFP for that one ?This seems to work fine for OOTB
Text component on a 6.5 instance.Did you check if your issue exists with
a Core Text component ?Also, btw, are you trying this on a iPad or a
smaller screen because otherwise I can't think of any possibility for
CUI...
Hi Matt-H-I think you are mixing two things here.The error/warning is
browser console that you see is not related to your use-case/issue. I
think this shows up, in general, if you edit any OOTB Text component and
seems like a minor bug.Your issue seems like something we fixed some
time back.The issue was this -RTE Plugins are not loading on opening RTE
second timeNot sure which version you are on, but we fixed it in
-6.5.06.4.2.0and 6.3.2.1So, I suggest you to try with those versions or
higher ...
Hi @vasudevaraog73192255Did you check my last comment related to XSS
Antisamy rules ?Because this is also happening because of the same
reason. The reason is not RTE, but XSS.If this is not clear, Checkout
Page 28 of the Slides from my recent Gem session
-https://helpx.adobe.com/content/dam/help/en/experience-manager/kt/eseminars/gems/AEM-Rich-Text-Editor-RTE-Deep-Dive1/jcr…
And you will also find a small demo related to this just after this
slide in the video -AEM Rich Text Editor (RTE) Deep Di...
Hi @manikanthar12951933I see some examples for the same on the public
github spaces for Adobe-Consulting-Services and
Adobe-Marketing-Cloud.e.g.https://github.com/search?q=org%3AAdobe-Consulting-Services+cq%3Alisteners&type=Code
https://github.com/search?q=org%3AAdobe-Consulting-Services+afterdelete&type=Code
https://github.com/search?q=org%3AAdobe-Marketing-Cloud+cq%3Alisteners&type=Code
https://github.com/search?q=org%3AAdobe-Marketing-Cloud+aftercreate&type=Code
HTHHanish
Can you try to re-structure your configuration as specified here and
check -aem-authoring-hybrideditors/_cq_editConfig.xml at master ·
Adobe-Marketing-Cloud/aem-authoring-hybrideditors · GitHub Configuring
Multiple In-Place Editors
HiI can confirm that this issue was fixed in 6.4.3.0It's mentioned in
AEM 6.4 Service Pack Release Notes as -When the rich text editor is
combined with multiple fields, the Uncaught TypeError: fieldAPI.getName
is not a function at foundation.js error occurs. NPR-27146: Hotfix for
CQ-4253155
If you are using the latest Core Text component, you could edit the
Template of the page and then edit the Policy of the Text component and
check the Feature 'Show inserted image modification options' under
Plugins
Yes, exactly.You could also check it here at
http://localhost:4502/crx/de/index.jsp#/content/we-retail/us/en/user/jcr%3Acontent/root/responsivegrid/texthttp://localhost:4502/crx/de/index.jsp#/content/we-retail/us/en/user/jcr%3Acontent/root/responsivegrid/text
that the persisted html contains the background style. Now, If you go to
the Preview mode, where RTE is not available, you would notice that the
background color is not present. So, it's being removed by the XSS
Antisamy rules indeed
> using @i18n directives while content authoring/component html fileNot
sure what exactly you mean here. FWIU, @i18n directives are used in HTL.
For SPA components, html will not be provided by HTL, but will be
generated client-side via the SPA JS. You might want to use the
clientside i18n API - Granite.i18n.get
HiClicking on the alert will close it.If you click on spellchecker
twice, I guess two overlapping alerts are added to the dom (this
behavior could be improved), so you would have to click on it twice to
remove both of them from the dom.
HiYou don't need to configure anything specifically in RTE for
this."When the spellcheck plugin is activated, the RTE uses dictionaries
for each appropriate language. These are then selected according to the
language of the website by taking either the language property of the
subtree or extracting the language from the URL"For more details, See
the doc present at these locations for different versions :6.2 :
Configuring the Rich Text Editor 6.4 : Configure the Rich Text Editor
plug-ins
dineshc12261746> Is there a way we can makesure only coral ui2 RTE is
loading on 6.3 without changing anything in libs ?Thanks for noticing
this. Please overlay those nodes under /apps and make those changes. We
are working on getting the documentation corrected wrt this asap.> we
have few custom plugins in RTE ,these custom plugins are not coming up
in RTE editor in 6.3 SP1 as it is by default loading in coral ui 3
Ideally, your custom plugins, if not using any RTE internal classes,
should wor...
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.
