Rich Text Field Not Working

  • 3
  • Problem
  • Updated 6 months ago
  • Acknowledged
Hi - the rich text field on one of our pages is not giving rich text options anymore. I rebuilt the page and omitted the chatter component, which seemed to make the rich text field work again. Once i added the chatter component back to the page the rich text field broke again. 

By 'broke' i mean i click into the field and it behaves like a regular text field instead of showing the formatting options. 

Any ideas?
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb

Posted 2 years ago

  • 3
Photo of Chandra V

Chandra V, Champion

  • 7,558 Points 5k badge 2x thumb
I am seeing this issue also.  RTE is working on a field editor, but not working within a pop up.

Pop Up RTE:


Not in a Pop Up RTE


I'm seeing the same behavior in both Firefox and Chrome.
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Within my visualforce page settings I changed the skuid version to a higher version and that seemed to do the trick.
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,964 Points 10k badge 2x thumb
Hi Kaede, would you mind providing some more information about the changes that you made? I.e. where you made them, what they were, and what their old values were (if you can remember)? I'm not able to reproduce the issue in my dev org on Brooklyn 9.3.1. 
Photo of Chandra V

Chandra V, Champion

  • 7,558 Points 5k badge 2x thumb
I tried that in my sandbox and it didn't fix it for me.  I changed it to version 9.3.

Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
I upgraded to 9.3 as well. Maybe something else fixed it and it was just a coincidence 

I can't remember what the previous values were for the version numbers. 
(Edited)
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
running into this problem again on another page... 

Removing the chatter component makes the rich text fields work properly, but that isn't an actual solution. Changing the page versions does not help. I have upgraded to the most recent version of Skuid. 
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
I really need help here. Updated my skuid version. My users keep having this issue and I don't know how to fix it myself. 
Photo of Amy Dewaal

Amy Dewaal, Official Rep

  • 8,300 Points 5k badge 2x thumb
Kaede,

There is currently an issue where the chatter component and rich text fields don't play nice together (if both are on a page the rich text palette doesn't show up). We'll let you know once a future release fixes this, but in the meantime, the best workaround is to show the Chatter component in an iframe in a template component. You can see an example of how to do that on this post.

Sorry for the inconvenience!
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Has the most recent release resolved this issue?
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Any chance this is resolved yet or will be resolved soon? The workaround is not very elegant. 
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
bump
Photo of Skuidward Tentacles (Raymond)

Skuidward Tentacles (Raymond), Champion

  • 17,756 Points 10k badge 2x thumb
I have experienced this issue but it isn't chatter component related.
I have a page that opens a pop up. On that pop up page, there is a button that opens another pop up. In that second, topmost popup, there is a rich field editor that is not working. As a work around I reconfigured and got rid of the second pop up , so I am fine, but thought I should report it.
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,964 Points 10k badge 2x thumb
I'm sure you've mentioned it elsewhere, but can I ask which Skuid version you're using?
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,964 Points 10k badge 2x thumb
In the latest release, Brooklyn Update 1, Iteration 5, I'm not able to reproduce the behavior you're describing. There may be more relevant details in your scenario, but setting up 2 nested popups with 2 different rich text fields (both built on the same model and object) allows me to see the Rich Text toolbar in both popups. This is in Chrome, by the way.
Photo of Skuidward Tentacles (Raymond)

Skuidward Tentacles (Raymond), Champion

  • 17,756 Points 10k badge 2x thumb
I'm on 9.5.5. I was using chrome at the time. .... strange......
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Has the issue been resolved that would allow for rich text fields and the standard chatter component to exist on the same page?
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,964 Points 10k badge 2x thumb
Hi Kaede, I have a couple follow-up questions:
Which release of Skuid are you using currently?
Are you deploying the pictured Skuid page via Visualforce, or iframe? 

My understanding is that the issue is resolved in Lightning now that Skuid doesn't use CKEditor in Lightning any more, but remains a limitation in Classic. In your videos, it looks like you've got the Classic version of Chatter, instead of the Lightning version. Skuid tries to detect which environment it's in, and load the corresponding version of Chatter. If Skuid isn't inside the Lightning Component, it'll load the Classic Chatter feed like you're seeing here. Have you tried deploying your Skuid page natively with the Skuid Page Lightning component
(Edited)
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Hi Mark! Thanks for getting back to me. 

I'm on version 11.2.11. The skuid page is deployed via visualforce but the chatter component is being included via iframe in order to make it possible for people to "use" it even though it's janky. 

Not sure why it's loading the classic version of chatter even though I'm in lightning experience. 

Our users still toggle between classic and lightning. What's the best way to deploy so it works for everyone regardless of whether they are in lightning or classic?
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
It seems like I can't allow for both lightning and classic overrides if I have two different pages to display based on record type. 
Photo of Kaede Holland

Kaede Holland

  • 3,016 Points 3k badge 2x thumb
Mark - thanks for pointing me in the right direction. I will work on skuid page lightning component overrides for all my objects.

While it is looking a lot better and the rich text + chatter components are rendering properly I'm still running into a strange error when trying to interact with some parts of the chatter feed: https://cl.ly/6cf4b7a85665

Have you seen this before?

Here's the error text
[Cannot read property 'tagName' of null]
Proxy.c()@https://columnfive.lightning.force.com/resource/1541020678000/skuid__SkuidReqsJS:1:73262
Proxy.dispatch()@https://columnfive.lightning.force.com/resource/1537232010000/skuid__VendorJS:2:19404
Proxy.q.handle()@https://columnfive.lightning.force.com/resource/1537232010000/skuid__VendorJS:2:17419
Photo of Mark DeSimone

Mark DeSimone, Official Rep

  • 11,964 Points 10k badge 2x thumb
Kaede, I haven't seen an error like that before, but it sounds like something on the backend is having trouble trying to find an HTML element.  I'm glad this is looking a lot better. Would you be able to share a simple page's XML that's demonstrating this issue (and which actions are causing the error)? I see you're on Skuid 11.2.11, which is just about to up-to-date. 

Also, have you by any chance tried the out-of-the-box Chatter Lightning component alongside your Skuid page, to see if the behavior persists? One of the nice things about Lightning is that you can put components alongside your Skuid pages pretty easily, so if there's nothing about your use-case that requires the Chatter feed to be inside the Skuid page, putting it beside or below the Skuid page in the Lightning App Builder Page might be an option too.