Hi That doesn't look right..  I checked here and we're seeing the above I think your content may have been copy and pasted in from another source like MS Word or a web page as it contains span and inline styles.   What you can do is copy it into Notepad or a simple text editor and then copy and paste it in from here. Maybe you are editing existing content, in that case you can use the HTML view to clean up and remove all those extra elements, making it more like the screenshot above. Let us know how you go! Chris ... View more

Hey.. I'm not sure about the Admin reports, but you could get something like this from the V2 API Browser in Studio using something like this      SELECT author.login FROM messages WHERE conversation.style='idea' AND status.key = 'accepted' AND post_time < 2020-06-09T10:04:30-08:00 AND post_time > 2020-05-01T10:04:30-08:00     BTW. I haven't tested the above ^ so it might need some tweaking @peterlu ? ... View more

@peterlu - didn't we do something like this on CS? if so maybe you could you help @deepu_thomas ?  ... View more

Thanks @JasonHill  @JonL We've done this a few different ways, however the key to making somewhat dynamic notifications emails in Khoros, is by putting html content into a custom text string and then including the custom string in your email templates. So the basic idea is: 1. Create an endpoint which generates the "dynamic" EDM ready html content you wish to add to your Khoros email(s). 2. Then manually copy and paste the output source code into your custom text string (in Studio). 3. Include the text string into your email templates and test them out in Studio. 4. When you're happy do a production push to sync the new content into prod.  Now when an email is fired off by Khoros that content is included in the email. It's not perfect but it is a way to get "recent content" into standard Khoros emails.    ... View more

While working with several Khoros customers in the US and Australia we have noticed this more recently too, however its hard to pin-point an exact cause. TTFB times do seem to be higher across the board but we only have data going back 6 months on most instances. Some of the items we've worked on, in no particular order; Pre-loading assets such as primary font(s). Using the API toolbox to pinpoint high API usage custom components and refactor / improve or even review to remove.  Adjusting JS code so that it loads async and moving things to the end of the document that are not needed prior to content painting. Setup CSS so that text is rendered before the fonts are loaded  font-display Employing app-cache for heavy operations, not to be over-used since it can make things worse if used incorrectly. Caching policies on some CDN loaded assets aren't set correctly. Some other observations; CDN (or browser) blocking when loading >10 assets at once. Due to the nature of Community we see high numbers of DOM objects, not typically a problem on desktops but some mobile devices can struggle.   ... View more