beacampos
Ace
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Khoros Communities 22.10 Release
hi CarolineS wow, thanks for catching that up. Indeed many of us use Grammarly internally. Although i would not like to ask them to disable it, since it's very useful to make sure the posts are well written. I will do a test with that for now. Thanks for the tip!Re: Khoros Communities 22.10 Release
Hi team, unfortunately we are still receiving the same HTML issues for any type of message. Both public posts and even on private messages, it is still showing up. This is very disappointing because we are trying to do simple posts and messages with the regular styling from the Khoros text editor, and keep getting these messages. My fear is that this is happening with all our users, which is a nightmare and it will stop them coming back to the community to try posting again, since they're experience is being very bad. Is anyone else facing this still? Could Khoros team provide another bug fix for this because it's been impossible to post anything. ccing Mercedes_ORe: Khoros Communities 22.10 Release
thanks, BlakeH There are multiple issues, and no code seems to be working well. Even when we use Khoros' own HTML codes. See below an example from our technical writer: I've got an article in draft, \which includes the "Insert/edit code sample" that Khoros provides = <li-code lang="markup">whatever</li-code> for some reason, every time I enter and exit Preview mode, it adds <p> </p> in front of and after the previous code then when I went to replicate the bug in a new article, the <li-code lang="markup">whatever</li-code> gives HTML errors the HTML error only shows when Khoros' own code for a new article, <div class="lia-message-template-content-zone"> </div>, is present in the HTML codeRe: Khoros Communities 22.10 Release
JasonHilland keithkelly having the same issue with HTML errors here. Out of the blue it's become a nightmare to post new things or edit previous one, anything triggers an HTML error. It's taking ages to just do one post. Not really sure what triggered this problem, since it used to work just fine. Did anyone find any resolution?
