Hi All, Any idea on this issue? I found this Text Component where "Paste as Text" and "Paste from Word" are available as options and buttons are visible how they would look in a Touch UI view.I checked the core components for the "text" component (v2) but the "rtePlugins" node doesn't seem to have ...

Hello All,I am trying to use the rte touch ui component in which I want to add paste options that were available as part of Classic UI.For example as highlighted in below image.I found from Configure the Rich Text Editor  that I can add the 'edit' property and value "*" to include the cut, copy, pas...

Hello smacdonald2008​,Any response from the TouchUI experts?

Unable to view the url (redirects to Adobe Experience Manager ) Please help updating the url

True, good point. Despite that I am able to get to my custom js on click of ok which I think is fine.. ? so that I can perform desired logic.However there might be something fundamentally wrong if I am doing something 6.0 way..Thanks for reaching out to the TouchUI people..Regards

Hi All,I am following this article - Adobe Experience Manager Help | Using Event Handlers in Adobe Experience Manager Touch UI Components  to create a listener js file and do desired logic when Ok or 'Tick' is clicked. I am able to get within the custom js file after following the steps.The desired ...

Thanks Arun. using nul instead of null fixes the issue related to null file.However I didn't mention in primary question. I also see the same error as mentioned in the link you added. Below is what I see.Exception in thread "sling-oak-5" java.lang.NullPointerException        at org.apache.sling.comm...

There were no modifications made when I started the instance and saw the null file.

Hello All,Noticed when starting AEM jar for first time. After I see the quickstart folder, I go to bin and hit the start.bat the instance starts, but at the same time a file named as 'null' is created.Below is a snapshot of the folder view. Below is the content of null file if opened with text edito...

"Now whether I use inplace editor or dialog editor, same value is displayed":  this is good, I was just mentioning that before I was seeing different when using inplace vs dialog editor. But now when using/referring to core component that issue is seen no more.Later, after that I mentioned what the ...