GopiB
Khoros Alumni (Retired)
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Script tag in blog HTML getting incorrectly encoded
Hi CarolineS I tested with your code snippet on my dev instance and it works fine. I am inserting the same snippet here for a quick test. (Btw, I have set the language to HTML/XML.) <div class="wistia_responsive_padding" style="padding: 56.56% 0 0 0; position: relative;"> <div class="wistia_responsive_wrapper" style="height: 100%; left: 0; position: absolute; top: 0; width: 100%;"><iframe src="https://fast.wistia.net/embed/iframe/XXXXXXX?videoFoam=true" width="100%" height="100%" name="wistia_embed" frameborder="0" scrolling="no" allowfullscreen="allowfullscreen" webkitallowfullscreen="webkitallowfullscreen" title="Wistia video player" allowtransparency="true" class="wistia_embed" mozallowfullscreen="mozallowfullscreen" oallowfullscreen="" msallowfullscreen=""></iframe></div> </div>609ViewsSign in to react to this post5CommentsRe: Script tag in blog HTML getting incorrectly encoded
Hi Lindsey , I would recommend using the code sampler plugin to insert code in RTE mode itself. This is specifically designed and built for use cases where community users want to share code samples. If for some reasons, user still needs to manipulate the html, then please refer to Allowed HTML Tags in the Community text editor for details of html tags allowed.ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
Re: Khoros Communities 19.3 Release
Not sure why the ':/' in examples under 'API Changes' section is still getting converted to emoji! Same text here in the comment (https:// or even https:/ ) doesn't get converted. Could it be because the examples had spaces around ':/'?ViewsSign in to react to this postCommentsRe: Lithium Community 19.1 Release Notes
CarolineS The concerned Engineering team is actively working on it.ViewsSign in to react to this postCommentsRe: Lithium Community 19.1 Release Notes
louisamartin As it is a new email template, you will have to make the desired changes as done for other templates. From the release note: To view and edit the @Mention Content Notification template: Sign in to Community and go to Studio. Go to Text Editor > Email Text. Select @Mention Content Notification from the email template drop-down list. Click View. Make changes to the email text as needed and click Save.ViewsSign in to react to this postCommentsRe: Lithium Community 19.1 Release Notes
TeroRe From the release note above: Content Mentions default notifications are configured in Community Admin. Members can configure their notification preferences, too: For admins: Users > Notification Defaults > Notifications > Posts my content is @mentioned in. For members: My Settings > Subscriptions & Notifications > Notification Settings > Posts my content is @mentioned in.ViewsSign in to react to this postCommentsRe: Lithium Community 19.1 Release Notes
Hi KateF Yes, you just need to change and save from 1 to 2 for Mentions under Studio > Features to upgrade to Mentions Version 2 which brings the Content Mentions. The arrows you see indicate availability of newer versions of the features. You should ideally be updating all features to latest versions. You can try out the updates on the staging environment first before updating the prod instance.ViewsSign in to react to this postCommentsRe: Lithium Community 19.1 Release Notes
Hi lilim Yes, this new version of the editor allows customisation of toolbars.ViewsSign in to react to this postComments
609Views
5CommentsYou’ve seen all recent content