You can find a bunch of related text strings when searching for "browser" in the studio's text editor. The strings browser-support.alert.text and page.browser_unsupported.message look like relevant The message should be triggered by unsupported browsers listed in Khoros' Supported browser information - Do you need it to show with different configurations? What's motivating you to get this message to disappear? Visitors on unsupported browsers won't be able to use all your community functionality, so you would really want them to use a supported browser. Do you mind sharing which outdated browsers you see still being used in your userbase? ... View more

Yes, CSS is the way to go here. You could use something like this which will hide the 4th entry in the notification settings list. .MyProfilePage .lia-notifications-settings-form .lia-form-row:nth-of-type(5) { display: none; } ... View more

This is most likely related to how you obtain this property. Can you share which API call and version you are using to obtain the sso_id? ... View more

If you click the working Quick Reply button you should see - on the same page without a new page loading - a new message field opening below. Here's how it can look like: Members can add a message (without the use of the full blown message editor though) and post straight away with the use of JavaScript functionality. Similar to what you see here on Khoros Community minus the editor. I recommend you use the Khoros case portal to have support check quick replies are enabled in your community backend configuration as well. Once that has been ruled out it's about ensuring the quickreply component is actually inclduded in your layout. Support can help you with that as well. ... View more