SuzieH
Khoros Alumni (Retired)
Joined 13 years ago
User Profile
User Widgets
Contributions
Full HTTPS Encryption for all Communities
Lithium is moving all customer communities to full HTTPS encryption. This change better protects your organization and your end-users, while paving the way for performance improvements and great, new features. Lithium is deprecating support for the following community configurations with Community release 18.2 (March 2018): HTTP-only community mode "Mixed mode" HTTPS support These configurations will remain available through 18.7 (August 2018). After 18.7, support for these configurations will be removed. Lithium is reaching out to impacted customers over the next several weeks with instructions to initiate their migration to HTTPS. Customers will only need to take a few simple steps in order to complete this important change. What does HTTPS do? Authenticates the website to the end-user Encrypts all data and communication passed between the end user and the community Safeguards customer data, preventing attacks Why switch to HTTPS now? Major browser and search vendors are making changes to flag pages that are delivered over HTTP as 'not secure' after July 2018. HTTPS is also a factor in search engine ranking. It's presumed that search vendors will add weight to HTTPS in their ranking formula this year. Simply put: moving to HTTPS is the right thing to do for you and your customers. Protecting your end-users online is an absolute priority for us at Lithium. Moving Community to HTTPS-only support is the next, right step toward keeping your end-users and their data safe.8KViewsSign in to react to this post3CommentsCommunity Syndication in the Developer Documentation Portal
As I was working on the documentation for Khoros's Community Syndication Message List component, I kept thinking about different ways I wanted to use Community Syndication in our Developer Documentation Portal. For those unfamiliar with Community Syndication, check out this guide and these blogs. Over the years, folks have asked us why our developer docs are not in Atlas. The simple answer is that some content just doesn't lend itself well to a knowledge base. API reference documentation falls into that category. That said, I wholeheartedly believe in the power of Community, and I wanted a bridge between the Dev Doc Portal and Atlas. We've got a vibrant and active Developer Discussion forum and I didn't want to disrupt engagement there. I also thought about users coming to the Dev Doc Portal from outside of Atlas -- say following a link to them sent from Khoros Support, Services, or a Customer Success team member. How can we guide those users to the Developer Discussion forum and all of the other great content on Atlas? The Community Syndication Message List gave me the perfect solution. I'd like to share how easy it was to implement. Here's what I did I placed two instances of the component on the developer.khoros.com landing page. Both show messages from the Developer Discussion forum. One displays Latest Topics and the other displays Latest Solutions. Here's how I did it I wanted to keep my first implementation simple. I chose to pull content from a single board, but use two separate instances to highlight latest topics vs. solutions. Here's my content definition in Community Admin for my Latest Solutions message list: I played with a Card view vs. a List view as well as some other styling formats in Admin to test what my content would look like. Developer Discussion posts aren't image-heavy, so Card View wasn't particularly engaging. I found the List view more readable. I also omitted the View count from the message because, at this time, the view count includes bot traffic. (We've got this issue in our backlog.) Here's where I landed with my layout configuration. I placed my Common Script snippet in the <head> of my Dev Doc Portal landing page. Then, I placed my Component Code in my <body> where I wanted the component to render. The styling actually looked pretty good out of the box, but I did want to make some minor changes to match the developer.khoros.com look and feel. I made the component title more prominent and I made the message subject text color match the theme colors of the Portal. I also wanted to put my two components (Latest Topics and Latest Solutions) side by side so that both messages lists would be visible "above the fold." Using the instructions in About Message List Syndication, I created a custom version of the Community Syndication skin and made some small variable overrides. My overrides are outlined in red. That took care of basic color styling, but I still needed a few bits of styling in the CSS on my external site. With some help from my colleagues AmyS and RyanPi, I added some CSS classes. .message-list { display: flex; flex-direction: row; margin-bottom: 40px; } .boogie { flex: 0 100%; margin: 0 10px; } .boogie iframe { display: flex; flex: 1 1 auto; } I replaced the body script generated in Admin with the following so that it used my custom Community Syndication skin to pick up my variable overrides and made use of my external CSS. <div class="message-list"> <div class="boogie"> <li:component id="content.syndication.widget.message-list" location-display-id="category:Developer" discussion-style="forums" number-of-messages="6" sort-by="date-desc" component-title="Latest Topics in Developer Discussion" number-of-messages="6" skin-id="devdiscussionsyndication" ></li:component> </div> <div class="boogie"> <li:component id="content.syndication.widget.message-list" location-display-id="category:Developer" discussion-style="forums" number-of-messages="6" sort-by="date-desc" component-title="Latest Solutions in Developer Discussion" number-of-messages="6" discussion-style-attribute="accepted solutions only" skin-id="devdiscussionsyndication" ></li:component> </div> </div> The result was what you see today on developer.khoros.com. How long did this take? Once I got my testing setup in order, the Message List took me roughly a day to implement. This included coordinating with the Atlas team, recruiting CSS help, testing on stage, and pushing to production. I will note that the Message List component isn't intended to be displayed two components side-by-side. The component is designed with responsive design in mind and by default, it spans the full width of the area and then collapses to mobile viewports elegantly. But I knew that I wanted these to be next to each other and I also know that the vast majority of Dev Doc Portal users are viewing our docs on a laptop, not on mobile. You might have different circumstances. I was able to handle the skin variable overrides on my own, but I did need help with some of the other CSS work. I also coordinated with Atlas team members AndyK and LisaI. They set me up to test against our Atlas stage instance. I created my Message List definition in Admin in our stage environment, as well as my custom Community Syndication skin that I would be using for my message lists. I can use this custom skin on any future messages lists that I want to put on the Dev Doc Portal. I added my Dev Doc Portal stage instance domain in the whitelisted section in Community Admin > Content Security. From there, I reviewed the content display in my Dev Doc Portal stage environment to be sure that all looked good on that end. Once I was happy with what I was seeing, I worked with my Community team to push my custom skin changes to production and added my syndication snippets to the production version of developer.khoros.com. Finally, I added the Dev Doc Portal production domain to the Content Security whitelist and added my custom CSS, script, and code to my landing page and header HTML in my Dev Doc Portal production environment. And then it was live! It was delightfully easy. Update: January 2021 Upon the launch of our Developer Blog, I updated the "Latest Topics in Dev Discussions" to include the latest articles from the blog. The component is now titled "Latest Dev Network Content" and includes Developer Discussion forum topics and Developer Blog articles. Here is the updated li-component code I use to render the Message List component embedded on the developer.khoros.com landing page: <li:component id="content.syndication.widget.message-list" location-display-id="category:Developer" discussion-style="forums,blogs" component-title="Latest Dev Network Content" number-of-messages="6" sort-by="date-desc" show-kudos="false" skin-id="devdiscussionsyndication" ></li:component> What's next? In the future, I see an opportunity to evaluate how the Developer Discussion forum uses tags and labels. That would allow me to create separate Message Lists dedicated to Khoros Communities, Care, and Marketing platforms, and even go more granular to topics like FreeMarker solutions, OAuth questions, Modern Chat questions, and so on... The next release in the Community Syndication product line will be a commenting syndication feature that will work with forums. My hope is that we'll make that bridge between the community and our dev doc portal even stronger by bringing the capability to start a topic in a component in the Dev Doc Portal and have it mirrored in Atlas. Can't wait to see what Community Syndication brings next!ViewsSign in to react to this postComments17.6 Release Notes
The 17.6 Release includes the ability to enable Content Security Policy (CPS) for ActiveCast components, as well as additions to our FreeMarker and Community APIs. Important upgrade information New features API changes Announcement - EOL of Responsive skin beta versions You found it. We fixed it. Important 17.6 upgrade information As part of the 17.6 upgrade for APAC and North American customers, there will be a short period of downtime as we roll out new Redis clusters in our data centers. The expected downtime is less than 10 minutes. Your upgrade will be during your local, standard maintenance window. If you have any questions about this release or our upgrade schedule, please contact Lithium Customer Support. New features Enable and configure Content Security Policy (CPS) for ActiveCast Content Security Policy (CPS) is a security layer added to identify Cross Site Scripting (XSS) and data injection attacks and to lessen any damage caused by them. Prior to 17.6, customers using ActiveCast had to contact Lithium to enable Content Security Policy and whitelist domains allowed to syndicate ActiveCast components. We now allow you to configure this feature yourself. Any domains whitelisted for your community previously will appear in the Community Admin > System, Content Security tab. If no domains are added, then ActiveCast components are rendered in an iframe and will not render on any domain. API changes In 17.6 we've released additions to the following APIs and deprecated a FreeMarker method. Community v2 FreeMarker Deprecated calls Community v2 API Note: Release-specific reference documentation for Community API v2 resources becomes available when the Lithium Community upgrades to the latest release version. The upgrade usually occurs one to two weeks after we announce that a new release is available. To view which version the community is running, go to https://community.lithium.com/status/version. We've added support for: Create and Update actions on the Board resource A new Messages_Read resource Create and Updated HTTP actions supported on the Board resource We have made the Create and Update HTTP actions publicly available for the Board resource. See examples in the Board resource documentation in the Developer Documentation Portal. Example POST Required fields: conversation_style, id POST /community/2.0/mytenantid/boards HTTP/1.1 Host: api.lithium.com Content-Type: application/json Cache-Control: no-cache client-id: czY8mbW76Ac/Wz6+bAMhCm+sW5WSyhAO2odh28TB1/c= { "data": { "type": "board", "id": "DeveloperDiscussion", "conversation_style": "forum", "title": "Developer Discussions" } } Example PUT Required fieds: none PUT /community/2.0/mytenantid/board/DeveloperDiscussion HTTP/1.1 Host: api.lithium.com Content-Type: application/json Cache-Control: no-cache { "data": { "type": "board", "description": "This is a place for developers to discuss Lithium APIs " } } Messages_read collection We have added the Messages_Read resource to the Community v2 API. The message_read resource is used to mark a message read or unread. You can set the read/unread status of a single message, multiple messages, or an entire thread (topic and all child replies). Example POST Required fields (one of the following -- do not use these together in the same request): message_id - the ID of the message to mark as read/unread message_id - IDs of multiple messages to mark as read/unread topic_id - the topic ID of a thread (marks the entire thread as read/unread) POST /community/2.0/mytenantid/messages_read HTTP/1.1 Host: api.lithium.com Content-Type: application/json Cache-Control: no-cache client-id: czY8mbW76Ac/Wz6+bAMhCm+sW5WSyhAO2odh28TB1/c= { "data": { "type": "message_read", "mark_unread": "true", "message_ids": "518, 659", "user": "32" } } FreeMarker Get message ID from edit and reply pages The Reply Page, Mobile Reply Page, and Edit Page now return a message FreeMarker context object. This enables you to get the ID of the topic message being replied to (for new replies) or the ID of the message being edited. See the page.context.message documentation for more information. Get user avatar details We have added new methods to the user FreeMarker context object to get the avatar URL, width, and height for the user in context. The methods enable you to get URL, width, and height details for the default avatar size, as well as favicon, inline, print, and profile sizes. See the FreeMarker user context object for details. Deprecated calls We have deprecated the FreeMarker method: utils.html.stripper.from.gdata.strip(String html) We recommend using utils.html.stripper.from.owasp instead. See the utils FreeMarker context object documentation for details. Announcement - EOL of Responsive skin beta versions The beta program for the Lithium community platform's Responsive skin concluded at the end of July 2016 when the generally available release of the Responsive skin became available to all customers and communities. As a next step, all beta skins will be removed from the platform with our 17.10 release, currently scheduled for November 2017. If your community is using one of the beta skins at that time, the upgrade to 17.10 will trigger an upgrade to the latest release version of the Responsive skin. If you're currently using a beta version of the Responsive skin, please be sure you've take the appropriate steps to adopt and deploy the general release version of the skin in advance of this date. If you have questions or need assistance, please contact [email protected]. You found it. We fixed it. We have fixed a bug that led Facebook Connect to stop working correctly after upgrading to 17.5. This fix has been backported to 17.5. We have resolved an issue where using the @modal directive in a custom component would not work properly. This fix has been backported to versions 17.3, 17.4, and 17.5. Resizing the TinyMCE editor in the Rich Text tab in edit and post pages now works as expected with Responsive skins. Comments on hidden images (images placed inside a hidden album) are no longer visible to anonymous users when viewing Print pages, such as the Blog Article Print Page. We have fixed styling in the Search Page so that labels on messages in the search results no longer look like a link. Check out the previous 17.5 Release Notes.ViewsSign in to react to this postComments17.8 Release Notes
Community release 17.8 provides: New Features API Changes Bug Fixes New Features Updates to Lithium Case Portal We have made several updates to Lithium Case Portal: Users who have permission to View or Create a case can now edit cases in the community, as well as edit custom and non-custom case fields. Previously, cases were read-only and could not be edited. Contact Lithium Services to perform this kind of customization. We have expanded the column-wise sorting functionality of results in the Case Portal. Previously, you could only sort results according to options configured for static columns such as “Created Date” and “Last Modified Date”. You can now configure sorting for all columns. In other words, you can now sort or list the results in the Case Portal based on options that you configure for any column. Contact Lithium Services to perform this kind of customization. You can now apply additional filters to Case Portal results. Previously, the Case Portal could filter results only based on their origin. You now have more control over filter configuration so that you can customize the results displayed in the Case Portal to your needs. API Changes Community V2 - Additional reason codes added to /allowed endpoint responses The /allowed endpoint is used to verify whether the current user has the correct permissions to make a Community API v2 call. The response includes a reason_code field, as described in Verifying permissions. We have added the following reason codes: 100 – Ok or Unknown 106 – Entity not found 107 – Entity does not support action 108 – Constraint check failed You Found It. We Fixed It. Using the id field as a constraint on the outbox_notes resource (SELECT subject FROM outbox_notes WHERE id = '35') now works correctly in a LiQL query in order to filter private messages in a user's outbox by user ID. Queries to the messages collection filtered by conversation.last_post_time (SELECT id, board, conversation.last_post_time, post_time FROM messages WHERE conversation.last_post_time < 2015-07-01T22:29:11-07:00 AND depth = 0 ORDER BY conversation.last_post_time DESC limit 10) now correctly returns topic messages where the last post in the topic thread is within the range specified in the WHERE clause. We fixed an issue where community users were receiving duplicate notification emails. Links in Groups components that take the user to the Pending Requests tab in the Group Members Page now take you to the correct location. The Pending Requests tab in the Group Members Page now shows the invite date/time. Sitemaps for nested TKBs now display properly. CSS formatting of <p> tags in private messages has been fixed to remove the unnecessary whitespace. We fixed an issue seen in 17.6 where images uploaded with a message post and resized using the rich text editor caused an error if the images did not have HTML width and height attributes set. No action is required by customers. Existing images will render even if the height or width have incorrect values. If there is incorrect height or width specified for an image when posting new messages or editing existing messages, the message will not be posted and an error message will be displayed in the form. The query returned for the messages.query field in LiQL queries like SELECT * FROM tags WHERE messages.id = '233' now returns the correct LiQL statement. Previously the query would return a value like SELECT * FROM messages WHERE tag.id = '57', which is not valid because we do no support tag.id in the WHERE clause. Now the value returns a statement with a valid query syntax using tags.text. For example: SELECT * FROM messages WHERE tags.text = 'test'ViewsSign in to react to this postCommentsLithium Community 17.10 Release Notes
Similar to last year, the 17.10 Release will be the last Community release of the year, to better accommodate our Holiday Production Freezes. We'll be back in early January with 17.12, which will include all feature and bug fixes for November and December. Now, let's get to the good stuff! Community 17.10 brings several new features and bug fixes. New Features Admin Metrics update Upgraded video player UI text update for Permalink feature Product Catalog XMLImport Tool New Lithium Salesforce Connector 3.9 features and configuration tasks Admin Metrics update We discovered a bug that began in June 2016 and perpetuated until this release, which undercounted usage for certain metrics, specifically Server Requests and Page Views. Lithium Social Intelligence (LSI) metrics, such as Human Page Views and Visits, were not impacted by this bug. Since we bill you based on Server Requests and Page Views, this means that we might have been undercharging you. Since this was our mistake, we will not bill you for any potential past overages. This bug is now fixed, and the correct data has been backfilled in the 17.10 release. Moving forward, you might see a change in your usage data from what you have typically seen. The average variance of past usage was 10-40%. If your usage now exceeds the Usage Limits stated in your contract with us, your Lithium Customer Success Manager will be in touch to discuss. One of our key, company values is to take customer success personally. We apologize for any inconvenience this error might have caused, and we look forward to sharing in your success. If you have any questions, contact your Customer Success Manager. Upgraded video player Videos hosted in the community (using third-party, Ooyala, Inc.) now use the latest Ooyala player (v4). All customers are automatically upgraded to the latest versions. There is nothing that you need to do to take advantage of this new version. The main difference between v3 and v4 is how the player loads. In v3, the player loads using Flash by default, with HTML 5 as the fallback. With v4, the player loads HTML 5 as the default with Flash as the fallback. UI text update for Permalink feature Over time, the term Lithium has used to describe our Permalink function has matured. Before the concept of "permalink" existed, we used the term "highlight", shown here: This antiquated term has caused some confusion among users, so we've decided to update the term to "Permalink". If you prefer to retain the older term, "highlight", you can manually change it back by editing the default text keys. Learn how to edit default text keys. Here is the list of text keys you would need to revert 'Permalink' to 'Highlight'. See Edit a default text key for instructions. menubar.highlight_message = Permalink menubar.highlight_message@place:blog@message:root = Permalink menubar.highlight_message@place:blog@message:reply = Permalink menubar.highlight_message@place:idea@message:root = Permalink menubar.highlight_message@place:idea@message:reply = Permalink menubar.highlight_message@place:contest@message:root = Permalink menubar.highlight_message@place:contest@message:reply = Permalink move_message.targetmessage.targetmessage.target_message_id.description = ... choose "Permalink This Message" in the message's "Options" menu ... Product Catalog XML Bulk Import Tool We have released a new bulk product catalog XML import tool to integrate your product catalog with Community. This tool is used with our Ratings & Reviews, Product Mentions, and Product Questions features. (Product Questions is currently in closed beta.) Previously, Community Admin and the Community API enabled you to add, edit, and delete a single product and or product category at a time. The bulk import tool enables you to create manual and scheduled catalog syncs of your full product catalog. Integrate your product catalog describes the product category and product XML schema definitions (XSDs), how to validate your product catalog file, and the different methods offered to sync your data. New Lithium Salesforce Connector 3.9 features and configuration tasks The Lithium Salesforce Connector 3.9 brings you the ability to enable email notifications for case comments, as well as a few bug fixes. As part of the upgrade process, you must also perform a few manual configuration tasks. To learn how to install or upgrade the Salesforce Connector, check out About the Salesforce and Lithium integration. Case Comment email notifications You can configure your Salesforce integration to send email notifications to the case contact when anyone adds a comment to a case. By default, this option is disabled. To enable case comment emails, go to Lithium Connector for Salesforce > Custom Settings > Feature Settings and turn on the Enable Case Comment Emails option. Additional configuration tasks Salesforce does not permit you to perform certain tasks while upgrading the from version 3.6 or 3.7 of the connector package to version 3.9. As such, you must manually perform these procedures: Attach email template to workflows Update email templates Add remote site settings Attach email templates to workflows To manually attach email templates to workflows: Log in to your Salesforce account. Go to Setup > Create > Workflow & Approvals > Email Alerts. Click Edit for the Send mail to Contact (with access) on case creation email alert. In the Email Template field, specify Notify_customer_on_new_case_creation_with_URL_vfp as the value. Click Save. Go to Setup > Create > Workflow & Approvals > Email Alerts. Click Edit for the Send mail to Contact (with access) on case status change email alert. In the Email Template field, specify Notify_customer_on_case_status_change_with_URL_vfp as the value. Click Save. Update email templates To edit and update Salesforce email templates: Log in to your Salesforce account. Go to Setup > Communication Templates > Email Templates. Click the Notify customer when new case comment is added (without access) email template to open it. Click Edit HTML Version. In the HTML Email Content region, find {!Case.LiSFIntegration__Last_Case_Comment__c} and replace this text with #LastCaseComment. Click Save. Add remote site settings If you are installing version 3.9 of the connector package, you must add your remote site settings. Log in to your Salesforce account. Go to Set up > Remote Site Settings > New Remote Site. Specify values of the following fields: Remote Site Name: SFSelfInstance Remote Site URL: Specify the value as described in the sample below: https://your_instance.salesforce.com Where, your_instance is a placeholder for the name of your instance. You can find the name of your instance by looking for the value of the Instance field in Setup > Company Information. Note: You must enter this value in lowercase. For example, if the value of the Instance field in your configuration is “NA10”, you must specify “na10.salesforce.com” as the value of the Remote Site URL field. Click Save. You Found It. We Fixed It. Avatars no longer resize unexpectedly when a user creates a message with an image in it. Accepted solution notification emails were being sent to the person who accepted the solution instead of the person who posted the solution. This is now fixed. Highlighting (permalinking) a topic message now works as expected when the conversation thread is sorted newest to oldest. The last answer submitted to a Q&A board was not being displayed. All answers now display as expected. Using a number as a search parameter now returns messages with the number in the body or subjects as expected. Federated Search would fail if the environment contained any Knowledge Article whose Deployment Status remained in the “In Development” state. The connector now displays the relevant search results, and this issue has now been fixed. Clicking the New Community Postback Comment button would fail to open the page to create a Postback comment, resulting in an error. This issue would occur if the environment contained any TKB article whose Deployment Status remained in the “In Development” state. This issue has now been fixed. We have fixed an issue where using Federated Search would sometimes display the “URL doesn’t exist” error message. All occurrences of this issue have now been fixed. We have fixed an issue where Case email notifications did not work as expected. However, email notifications for any case now include a link to the support portal only if the Community URL field is configured. If the Community URL field is not configured for a specific case, the Support Portal link in the email appears as plain text. We have fixed an issue with Federated Search where links to TKB articles created in Salesforce did not work. In other words, links to TKB articles in the Federated Search results list displayed a “URL No Longer Exists” error when clicked. This issue has now been fixed. We have fixed an issue that caused case status updates sent from Salesforce to Lithium Community to not work as expected, in Salesforce instances that used batch service.ViewsSign in to react to this postCommentsLithium Community 17.12 Release Notes
Happy New Year! We hope that 2018 brings all kinds of good your way. Community release 17.12 includes all features and bug fixes since release 17.10 in order to accommodate our Holiday Production Freeze. New Features API Changes Bug Fixes New Features Case Portal column-wise search Updates to Product Questions events Add Previous and Next links in the TKB Article Page Coming soon! The Lithium Community iOS SDK Case Portal Search We have expanded the functionality of the Case Portal search feature. You can now filter case portal search results based on text strings that you enter in the column-wise search fields. The columns in the Case Portal Search Results page now support search. You can configure the following columns as searchable: Id Title Status Author Origin createdDate Priority lastModifiedDate closedDate To configure column-wise search for your case portal columns, contact Lithium Services. Updates to Product Questions events As described in Register Product Questions event listeners, the Product Questions ActiveCast component generates events in JavaScript that correspond to the state of the component and actions made on messages within it. We have added message depth and message details to the action context for the LITHIUM:messages.post event. Note: The Product Questions component is currently in open beta. The action context will now look something like this for the LITHIUM:messages.post event: { message: { author: // author ID and login body: string // body of the message depth: inst // position of the message in the thread. 0 = topic, 1 = first-level reply subject: string // subject of the message uid: int } } Add Previous and Next links in the TKB Article Page We have enabled the article-navigator page-level component, which adds Previous and Next links, to work on the TKB Article Page. The links enable a user to move through articles in a knowledge base by post date (most recently posted articles displayed first). This component does not respect ordering defined in Community Admin. Note: The article-navigator component can be used only on the Blog Article Page and the TKB Article Page. The article-navigator component adds the Back To Knowledge Base, Previous, and Next links shown in the screenshot below. You must add this component in XML view in Studio or by editing the TkbArticlePage.quilt.xml in the Community Plugin SDK. This example XML includes the article-navigator component. If you are using the latest version of the TKB feature, your quilt XML should look something like this: <?xml version="1.0" encoding="UTF-8"?> <quilt extends="Common" layout="one-column"> <add to="common-header"> <component id="helpfulness-display" wrapper="lia-page-header"/> </add> <add to="main-content"> <component id="article-navigator" /> <component id="article" /> <component id="rating-feedback-list" /> <component id="comments" /> </add> </quilt> Coming Soon! Lithium Community iOS SDK In May of 2017, we announced GA of our Community Android SDK. That made a lot of folks happy and also made a lot of folks say, "That's great! What about iOS?" Our team has been working hard on a Community iOS SDK since the release of the Android SDK. Watch our Online Communities blog for the announcement of our Lithium Community iOS SDK beta program toward the end of January. API Changes We have added new methods to the utils, coreNode, and message context objects. New utils methods for sequences You can now remove items from a sequence and remove duplicate items from a sequence. utils.sequence.remove(sequence,itemToRemove) removes all occurrences of the given item. <#assign input = ["a", "a a a", "aa a", "A", "a"] /> <#assign res = utils.sequence.remove(input, "a") /> <#-- resulting sequence is ["a a a", "aa a", "A"] --> utils.sequence.unique(sequence) removes duplicate items from a given sequence <#assign input = ["131", "135", "251", "131", "135"] /> <#assign uniqueInput = utils.sequence.unique(input) /> <#-- resulting sequence is ["131", "135", "251"] --> Get the description from coreNode We added the coreNode.description method to the coreNode context object. To display the description of the node in context as defined in Community Admin, for example, you would use an interpolation like this: ${coreNode.description} Retrieve views metrics from the message context object We added the metrics.views method to the message context object. To retrieve and display the number of views for the message in context, for example, you would use an interpolation like this: ${env.context.message.metrics.views} You Found It. We Fixed It. We have improved the error validation workflow of the New Case Page in the Case Portal. If validation fails, the page now retains the entered data and indicates the fields in which the error occurred. We have improved the notifications workflow for Case Portal users. You can add contacts to the “Additional CC” field in the Email Notification region to copy these contacts on case-related notifications. To enable this feature, contact Lithium account team or Services. We have fixed an issue that displayed an Invalid Authorization Response error message while publishing video files with Knowledge Base articles. Videos uploaded to Knowledge Base articles now play after the articles are published. We fixed an issue that logged a user out of their session while trying to post a product question using the Product Questions ActiveCast component. We have improved the workflow of the Password Reset token to increase security while using the password reset option. We fixed a migration issue that moved message replies to the wrong message thread on the destination board. We also improved our migration workflow to detect and repair database inconsistencies more efficiently. Answers posted to a Q&A Board now appear without requiring a page refresh. We have fixed a URL-related error where the “jump-to/first-unread-message" string was being displayed in the URL for Knowledge Base articles when the Jump to first unread post in a topic option was selected in My Settings > Preferences > Linear Layout. Matching search terms in search results are now highlighted in both the title and body text in the Community search results for Responsive sites. We have improved the download management workflow for private attachments when the Make all attachments public option is not selected in Community Admin > System > File attachments. Previously, if the user who uploaded the private attachment logged out and then tried to access the file, Community displayed an error message. With this fix, the attachment is either downloaded if the user has the necessary permissions or an “Access Denied” error message is displayed. You can now disable the Accepted Solutions feature for group posts on Responsive communities. In Forum and Group boards, the UI no longer incorrectly navigates to the first unread post in the thread when a user clicks or taps the Reply button. This issue occurred only when the Jump to first unread post in a topic option was selected in My Settings > Preferences > Linear Layout. The Jump to first unread post in a topic option in My Settings > Preferences > Linear Layout no longer affects what happens when a user clicks or taps the New column in the Community UI. Now when a user clicks or taps the New column, the user is always taken to the first unread post in a topic (as expected) regardless of the how Jump to first unread post in a topic is configured. The “Powered by Lithium” logo now redirects to the correct URL. We have improved how Lithium Social Intelligence (LSI) reports information for the Minutes to First Solution column in the Forums category. Previously, if the timestamp of an accepted solution preceded the timestamp of the forum or thread itself, LSI recorded a negative integer value in the Minutes to First Solution column. (This event occurred only when an older thread with an accepted solution was merged with a newer thread.) For these types of events, LSI now records a value of "0" instead of recording a negative value. Quotes used in message replies now display @mentions correctly. Note that there is still an outstanding issue where an @mention in quoted text triggers a duplicate notification email.ViewsSign in to react to this postCommentsLithium Community 18.1 Release Notes
Community release 18.1 brings bug fixes and minor improvements to Moderation Manager. We are also happy to announce the Community iOS SDK open beta program, the Salesforce Lighting Connector 4.0 open beta program, and version 1.2.5 of the Community Android SDK. New Features API Changes You Found It. We Fixed It. New Features Community iOS SDK Open Beta Program Lithium Salesforce Lighting Connector 4.0 Beta Program Define the length of a message displayed in Moderation Manager Community Android SDK version 1.2.5 Deprecation Announcement: asset.get in Skins Spam Quarantine Alert Messages in Forum Boards Community iOS SDK Open Beta Program We are pleased to announce the Lithium Community iOS SDK Open Beta Program. The iOS SDK makes it easy for developers to integrate Lithium Community in their iOS apps quickly and easily. Developers can get started with the mobile-support user interface (UI) or go deep with a fully-customizable API-backed integration. We've tried to make getting the iOS SDK up and running as easy as possible. Check out the SDK projects on GitHub, and follow the instructions to get started. You can use our example project as both a starting point and a way to see how the libraries can work together in your app. GitHub: Lithium Community iOS SDK Core GitHub Lithium Community iOS UI Components GitHub: Lithium Community iOS SDK Example Note: In order to create the best possible product and experience, we will continue to iterate on the SDK throughout the beta period. Features may change before the product is generally available. We will post updates and changes in the Current Betas forum. See the Getting Started with the iOS SDK Open Beta article in our Online Communities blog for all the details you'll need to start your iOS integration. Lithium Salesforce Lightning Connector 4.0 Open Beta Program We are happy to announce our open beta program for the new Lithium Salesforce Lightning Connector. This connector is now available in beta to support the Lightning Experience and to ensure continued compatibility with updates introduced by Salesforce. Watch the Online Communities blog next week for an article with details about participating in the beta program. The Lightning version of the connector includes the following new features: UI redesign and refresh The Lightning experience provides a redesigned UI and an overall update to the look and feel of the connector. The redesign does not change any of the functionality or workflows, but the arrangement of components in a page or the layout of some pages may have changed as part of the design improvements. Additional information in tooltip format In the Lightning experience, hover over highlighted text to find additional information about a user or component. This information appears in the form of a tooltip or pop-over and supports rich text including clickable links. Drag-and-drop capability for the Record Page The Lightning experience of Salesforce now includes drag and drop functionality while adding and arranging page components. See Install and use the Salesforce Lightning Connector for installation and configuration instructions. See Features of the Lithium Salesforce Lightning Connector to learn more about the new connector. Define the length of a message displayed in Moderation Manager We have added the Length of the message that displays in Moderation Manager setting to the Community Admin > Mod Tools page. This setting defines how much of a message to display in Moderation Manager. An empty value displays the entire message. (This is the default setting.) Set the field to 2-500 (characters) to truncate the message to the desired length. Community Android SDK Version 1.2.5 We've released a new version of the Community Android SDK. In this version, SDK initialization is decoupled from synching the Android app with the Community server. This decoupling requires that you make a separate call to sync your app with the Community server after initialization but before making any calls to the Community REST API. See details and examples in the Community Android SDK wiki. Deprecation Announcement: asset.get in Skins We will stop supporting asset.get("destination_url")to reference assets in skins in 18.4 and begin migrating customer skins that use the FreeMarker method. See Deprecation Announcement: FreeMarker in Skins for details about the migration path. Note that you will continue to use the asset context object when referencing assets in component and endpoint FreeMarker code. Spam Quarantine Alert Messages in Forum boards We have added visual alert messages to topic and reply posts marked as spam in Forum boards. (Support for this feature in other board types to come in a future release.) These new alerts appear when Community users come to a post that has been marked as spam via a permalink, say in a Community email digest or in a source from outside the community. The message will differ depending on the user viewing the message. Administrator and Moderator View An Administrator or Moderator sees a message that reads "Marked as spam. Visit the spam quarantine to manage this message" and includes a link to the Spam Quarantine page. If the message marked as spam is a reply, the reply message is hidden and the alert appears directly under the subject. Message Author View When the message author arrives at the message via a permalink, the author sees a message that says "Marked as spam. If you believe this is an error, submit an abuse report." The message includes a link that opens an abuse report form. If the message marked as spam is a reply, the reply message is hidden and the user sees the alert directly below the topic subject. General User View Users who are not Administrators, Moderators, or the message author see a message saying that the message is not available. API Changes Moving messages in a Lithium Community can cause orphaned messages (where messages have a root ID different from the topic message of the message thread). The /messages/linear call in Community API v1 now skips orphaned messages in the response; however, the /message/linear/count call does not omit orphaned messages. Due to the different behavior between calls, you might see a discrepancy between the number of items returned from each. If you experience a discrepancy between the number of results returned between /messages/linear and /messages/linear/count, contact Lithium Support to resolve the root ID issues with orphaned messages. You Found It. We Fixed It. If the currently logged-in user had more than one community user associated with the same email ID, then, the postback action was associated randomly to one of the users associated with this email ID. To fix this issue, we have added a Fallback Community User field to Feature Settings. To configure the fallback user: Log into your Salesforce account. Go to the Custom settings tab > Feature Settings. Click Edit. In the Fallback Community User field, specify the valid community Username of the user that you want to configure as the preferred user for postback options. This is used when there is more than one community user associated with this email id or in scenarios where a community user does not exist. Note: If you do not specify a fallback user, the user associated with postback actions will be the default user specified in Salesforce > Custom settings tab > Community Settings. Click Save. We have fixed an issue where an invalid file name error was encountered while trying to save Sass-related changes in Studio even though a valid file name was specified. We have fixed an issue where Private Categories were being duplicated in the hamburger navigation menu created by the common.widget.slide-out-nav-menu component for Responsive sites. This error would occur only if a user logged back in after an open Community page timed-out. We have fixed an issue where new users could be duplicated if the new user was using a mobile device to view a page containing Active Cast content served by an SSO-enabled, horizontal-scaled (HS) community. We have improved the workflow of the Password Reset token to increase security while using the password reset option. We have fixed an issue that caused localized versions of the Moderation Reason Notification email template to be inconsistent with the original content specified in the primary version of the template. Localized versions of the email template are now are consistent with the original version. Previously, a conflict would occur if SAML was enabled while using the URL Fetcher feature. This conflict between SAML and the URL Fetcher feature has been resolved. We have fixed an issue that caused messages with JavasSript to be posted as messages containing the complete code if the Notify Moderators of filter action (board reports, email, or private message) option was enabled. The content filter notification would bypass normal HTML perms check. This issue has now been resolved. The MATCHES operator in LiQL queries now handles custom fields as expected in the WHERE clause. We fixed a regression that caused the MATCHES operator in LiQL queries to handle “one or more” search cases incorrectly. The MATCHES operator once again works as described in the “Query for one or more terms” section under Combinatorial searches in the WHERE clause. We have fixed an issue where updates from Salesforce to Lithium Community did not work as expected when the Community used the Lithium API Proxy. To fix this issue, we have added two new fields to the Community Settings page in Salesforce. Note: You must contact Lithium Support to get the value of one of the new settings. Follow these steps if you have API Proxy enabled for your community and have a Salesforce integration: Contact Lithium Support and ask for the Tapestry Context Name for your community. Log into your Salesforce account.Go to the Custom settings tab > Community Settings. Click Edit. (If you have not created a custom configuration, then click Create.) Select the Is Proxy Enabled checkbox. In the Context Name field, specify the context name you received from Lithium Support. Click Save. We fixed an issue where, when a post had multiple labels, all the labels took the user to the same destination rather than the appropriate label page for the specific label.ViewsSign in to react to this postCommentsLithium Community 18.8 Release Notes
Community release 18.8 includes improvements to several notification email templates that simplify template logic and improve localization capability. We have also completed an upgrade to AngularJS 1.7.3, and we will be migrating customers off Freemarker in CSS/SCSS files. New Features API Changes You Found It. We Fixed It. New Features Updates to Notification Email Templates Deprecation Update: FreeMarker in Skin Files Upgrade to AngularJS 1.7.3 Updates to Notification Email Templates We have made changes to the following notification email templates: Digest subscription notification (email_content.template.digest_notification.text) General subscription notification (email_content.template.immediate_general.text) @Mention notification (email_content.template.mentions.text) If you have customized any of these templates, review the customizations and update the templates to use the new logic described below in order to take advantage of these improvements. If you have not customized these email templates and are still using the out-of-the-box versions, you don’t need to do anything. Note: If you have customized versions of the templates, you will see a Use Default button displayed in the Text Editor > Email Text template in Studio after you have selected the email template in and clicked View. If you are using the Community Plugin SDK, you will see the template in your plugin directory under <PLUGIN ROOT>/res/lang/text.<LANGUAGE CODE>. The Digest subscription notification email template now includes support for Product Associations, a feature that is currently in closed beta and that we will be announcing as Generally Available in an upcoming release. The General subscription notification and @Mention notification email templates now use new logic to build the introduction section of the email template that describes the event that triggered the notification, and now use different logic to build the footer that explains why the end user received the notification (i.e. names the subscription). The new logic is performed by two methods on a new Velocity context object called templateHelper. The templateHelper context object and methods provide improved localization support and use new text keys to build the introduction and footer text. Important: The change to the footer in the General subscription notification and @Mention notification email templates is a breaking change. To give you time to prepare for this change, we have made sure that your email notifications will continue to work with the 18.8 and 18.9 releases. However, you must complete your email template customizations by the 18.10 release. If you do not make these changes before upgrading to 18.10, notifications using these templates will fail. Also, if you customize these email notification templates between the time that your stage instance has been upgraded to 18.8 and your production instance is being upgraded to 18.8 and publish your changes to production, the affected notifications will not work until your production instance is upgraded to 18.8. You can edit a customized email template using Studio or the Community Plugin SDK. (See Email Templates in the Community Plugin SDK documentation for more details.) To edit your customized email template in Studio: Go to Studio > Text Editor > Email Text. Open the Select Email Template menu and choose the email template you want to work with. Click View. Copy your existing, customized template content (plain text and HTML versions). Review your template with the changes described in this document. Depending on the extent and location of your template customizations, you will either: - Revert to the updated default version of the email template by clicking Use Default and then adding your customizations to the default. - Add the updated logic described below to your custom version. Click Save. About the introduction text changes The introductions in the General subscription notification and @ Mention notification email templates now include the templateHelper.getIntroText(boolean) method: $templateHelper.getIntroText(true) When true, the getIntroText method creates the introduction text as Plain Text. When false, it creates introduction text as HTML. In the General subscription notification template, the templateHelper method replaces the logic below, which has been removed from the template. (The context objects in the removed portion of the template are still available in context and supported). #set ( $eventUser = "") #set ( $eventUserRanking = "") #set ( $eventText = "") #set ( $eventDetails = "") #if($notification.message.editRequestSave) #set ( $eventDetails = "and has requested a review") #elseif($notification.message.publishRequestSave) #set ( $eventDetails = "and has requested it to be published") #end #if ($notification.newlyVisible || !$notification.message.edited) #set ( $eventUser = "${notification.message.author.login}") #set ( $eventUserRanking = "${notification.message.author.ranking.name}") #if ($notification.moved) #if ($notification.merged) #set ($eventText = "merged a") #else #set ($eventText = "moved a") #end #else #set ( $eventText = "posted a new") #end #else #set ( $eventUser = "${notification.message.lastEditUser.login}") #set ( $eventUserRanking = "${notification.message.lastEditUser.ranking.name}") #if ("${notification.message.board.discussionStyle}" == "tkb") #set ( $eventText = "edited an") #else #set ( $eventText = "edited a") #end #end ${eventUser} (${eventUserRanking}) ${eventText} ${notification.message.localizedObjectType} in ${notification.message.board.title} on ${notification.formattedDateForMessageEdit} in the ${community.title} ${eventDetails}: About the footer changes The footer uses the templateHelper.footerText method. This method replaces the ${footerReason} call in the General subscription notification and @Mention notification email templates. templateHelpfer.footerText takes no parameters. It simply builds the footer section that describes why the notification recipient received the notification. Important: The ${footerReason} context object is no longer supported in the General subscription notification and @ Mention notification email templates. If you do not update your email templates to incorporate this change, the footer in these templates will break. New text keys used by templateHelper The templateHelper methods used by the General subscription notification and @ Mention notification email templates use new text keys. The text keys use the following naming conventions. You can modify these text keys as needed in Studio > Text Editor > Community Text. Text keys used by templateHelper.getIntroText(boolean) use the prefix notification.email.intro-text. Example notification.email.intro-text.post.html.text = {0} ({1}) posted a new {2} in {3} on {4}: Text keys used by templateHelper.getFooter use the prefix notification.email.deduplification.footer Note: For more details about the new text keys used for intro text on the General Subscription Notification email template and placeholder descriptions, see this article. Example notification.email.deduplification.footer.mention_product_reply.text = You are receiving this email because you were @mentioned and the message matches your subscription to a product and a reply. Email template diffs Diffs are available in the patch file in the attachments section of this blog article. Deprecation Update: FreeMarker in Skin Files In Community release 18.1, we announced a deprecation path for the FreeMarker asset.get("<destination URL>") method within Community skins. We have reviewed all customer plugins and have identified those communities using the method within skin CSS/SCSS customizations. After the 18.8 upgrade, we will run a separate script to migrate affected customers so that skins referencing assets in the Asset Library use the correct syntax. As a result of the migration, browsers will ignore CSS/SCSS declarations using asset.get("<destination URL>"). The new syntax uses a Sass function called asset instead of the $asset.get FreeMarker function used previously. The migration will change a reference to an asset like this: background-image: url(${asset.get("/html/assets/disappear.gif")}); to this: background-image: url(asset("/html/assets/disappear.gif")); The script will be run on all communities' stage and production environments. Lithium Support will send a communication to all customers when the migration is complete. If skins in your community are affected by this migration, you will see an entry in your version history in Studio > Versions that reads "freemarker asset.get wrapper migration". If you see this entry, be sure to test your skins in your stage and production environments to verify that assets in the Asset Library referenced in the skin appear properly. Important: If you use the Community Plugin SDK and your community skins were updated as part of the migration, you must export skins from your stage environment to get the migration changes into your local environment. To export skins from Studio, run the following command from your SDK plugin root: li export-studio-plugin --points "skin" --force To export skins from the SDK, run: li export-plugin Upgrade to AngularJS 1.7.3 In 18.7, we announced that we would be upgrading from AngularJS 1.4.8 to the latest 1.7.x version. Our upgrade is complete and Lithium Community now uses AngularJS 1.7.3. You can review changes to the Angular library in Angular's changelog. The only customers affected by this upgrade are those who have used our Angular integration. This group is a very small set of customers, most of whom worked with a Lithium Partner, iTalent, to implement our Lingotek integration for translation. iTalent has confirmed that the upgrade does not have an impact on those integrations. We are reviewing the remaining customizations. The remaining customers who have used our Angular integration do not have active customizations in production. We are evaluating those customizations to ensure that the upgrade does not affect the functionality. While we do not expect any issues as a result of this upgrade, file a ticket with Lithium Support if you experience any issue involving an Angular integration customization. API Changes LiQL Update We now support the != operator in the WHERE clause with the board.id field on the Messages collection. Example SELECT id FROM messages WHERE category.id = 'someCategoryDisplayId' AND board.id != 'someBoardUnderThatCategoryDisplayId' You Found It. We Fixed It. We fixed an issue that was preventing communities from establishing a database connection and resulted in Community timeouts We fixed an issue identified in 18.7 that triggered a new thread notification when custom metadata keys were updated on a message. This issue affected only communities on 18.7 with custom metadata keys created for them at the message-level We fixed accessibility issues with the Upload Avatar dialog. Screen readers now inform the users when the image is being uploaded and provide a message when the upload is finished On mobile devices, menu navigation from the hamburger menu icon is accessible now on IOS using the switch control options The Community API v2 now correctly returns all users with the same login name as opposed to returning only one user The blog scheduler now displays 24-hour time correctly in Community Admin when scheduling a blog post Customers no longer receive an exception when an SCSS file name uses only one to three characters. TKB comments are sorting again as expected in non-responsive communities Nested TKBs now appear as expected in the Community Board List component (forums.widget.board-browser-list). Time-based queries with the Bulk Data API are once again working properly.ViewsSign in to react to this postCommentsLithium Community 18.10 Release Notes
2018 is coming to a close. The 18.10 Release will be the last Community release of the year to accommodate our Holiday Production Freeze. We'll be back in early January with Community 18.12, which will include all feature and bug fixes for November and December. New Features API Changes Bug Fixes Documentation Errata New Features Product Associations Community structure performance improvement Richer auto-suggest search results Create different SEO titles and descriptions for each variant of a custom page Configure the number of email escalations allowed per topic/post Product Associations We've introduced a new feature called Product Associations and have made changes to our Product Mentions feature. With Product Associations, community members can easily create, find, and interact with discussions about specific products anywhere in the community. This allows brands to seamlessly curate experiences around specific products and helps customers discover all the information they need faster. You can watch an overview of Product Associations here (starting at minute 17:00). Note: The Product Associations feature is designed for use with the Responsive Skin. While you can add product associations to messages in a community using a non-responsive skin, these supporting Products components and pages will not work properly. Product Associations and the improved Product Mentions features require upgrading to Products v2 in Studio > Features. About Product Mentions and Product Associations Mobile screenshots New components What's changed with Product Mentions Product subscriptions New product API support Product Mentions and Product Associations documentation About Product Mentions and Product Associations In Community posts, customers can use hashtags to mention products in the message body. This is supported on desktop and mobile devices. When the customer types the # symbol, a drop-down menu appears. As the customer types, more characters matching products in the product catalog appear as suggestions. These product mentions (also referred to as #mentions) appear as hyperlinks in the message body. Mentioned products appear in below the posted message body in a component called product-snippet. When a user hovers over the product mention in the body (in desktop view only), a hovercard appears with a link to take the user to your commerce site. Behind the scenes, a product mention creates a product association between a product and the message in which the product is referenced. This association is essentially metadata on the message. In addition to a message author, other community members (Administrators, Moderators, and users with specific permissions) can also create product associations by adding them in a new Associated Products field in the Post Page, Edit Page, and Reply Page. Products associated with messages in this way also appear in the product-snippet component but are not added as hyperlinks in the message body. Clicking a hyperlink or on an image in the product-snippet component takes the user to the Product Page in the community. Mobile screenshots Product Associations are supported on mobile devices. New components To support Products, we've added new components: Top Associated Products Product Message List See Product Association pages and components for full details. Top Associated Products The Top Associated Products component displays products with the highest number of associated messages scoped to a Community, Category, or Board. The Top Associated Products component is not included in any pages by default. You must add it manually in Studio or using the Community Plugin SDK. In Studio, you'll find the component under the Products section of the Components list on the Page tab. Product Message List The Product Message List component displays a list of messages associated with the product in context. This component can be used only on the Product Page. The component displays one of the following message lists: Latest Topics - Topics most recently posted to the selected node that have associations with the product in context Latest Replies - Replies that have associations with the product in context most recently posted to the selected node Top Topics - Topics with the most kudos that have associations with the product in context My Topics - Topics that have associations with the product in context posted by the user in context What's changed with Product Mentions As of 18.10, when Products v2 is enabled in Studio > Features: The auto-suggest in the product mentions drop-down menu now includes an image of the product. The product-snippet component has a new look and new functionality: The product carousel is no longer supported. Instead, the user selects a View All link to display all associated products in the product-snippet component. Selecting a product mentions hyperlink in the message body or a product in the product-snippet component takes the user to a new page called Product Page (ProductPage.quilt.xml) instead of taking the user to the Product URL for your commerce site defined in the Product Catalog. The user navigates to the product in your commerce site using the View in Store buttons in the product mention hovercard and the Product Page. The product-snippet is supported only in the Responsive Skin when Products v2 is enabled. The product-snippet component is not supported in non-responsive skins. Product subscriptions Community members can now subscribe to products and request notifications regarding product-related activity. Product subscriptions are set at the Community level. Customers can subscribe to products in the Product Details page by selecting the Subscribe option in the Options menu. Once a customer subscribes to a product, the customer can unsubscribe from it either in the same Options menu or in the subscriptions list view in the Subscriptions & Notifications > My Subscriptions tab in the My Settings page in the Community. See Product subscriptions for more details. Note: We do not support creating product subscriptions via the Community API. New product API support We've added API support for several Product Association and Product Mention tasks. See Product Association and Product Mention API examples for instructions to: Post a message with product associations Post a message with a product mention Post a reply with product associations Edit product associations on an existing message Remove all product associations from a message Add or remove a single product association to an existing message Retrieve products association details Retrieve posts that mention or are associated with a product Product Mentions and Product Associations documentation See these TKB articles to get started with Product Associations and the updated Product Mentions features: About Product Mentions and Product Associations Product Mention and Product Association workflows Enable Product Mentions and Product Associations Set Product Mention and Product Association permissions Product Association pages and component Product subscriptions Product Association and Product Mentions API examples Feature versions - Products Community structure performance improvement For large community sites that have a massive number of nodes (in the thousands/tens of thousands), the Community Structure tab (Admin > Community Structure) used to take an unacceptably long time to load the node tree or, in some cases, not load at all. We have re-tooled the way that this page and the node structure load for large sites to prevent this delay/failure from happening, and now the community structure (regardless of size) should load in a couple of seconds. By default, this configuration change is disabled (since not all communities are large enough to require it). If you have a community with thousands of nodes and would like to take advantage of this lazy-load option, open a Support ticket and request to have it enabled. When enabled, opening the Community Structure tab will load the first 500 nodes and provide previous/next links to view additional nodes. Note: You can request to have the number of nodes per page increased (up to 1000), but as you increase the page size, it will take a bit longer to load. Richer auto-suggest search results To help you find the answers you need faster, we have improved the auto-suggest search results experience. Note: This improvement requires upgrading to Search 3.1 in Studio > Features. Previously, when you searched, the matching auto-suggest results displayed the subject of the post, making it difficult to differentiate between the suggested results: Now, auto-suggested results provide more detailed information, including a text snippet, number of replies the post has received, creation date, and board name. Note: Like the previous version of this experience, it is Responsive-friendly and will truncate and re-layout information based on the size format and available Additionally, the displayed metadata for each result (text snippet, number of replies, date of last activity, and board name) adjusts according to the width of the search bar. So long as the width is at least 800 pixels, all metadata content displays in full. Create different SEO titles and descriptions for each variant of a custom page When you want to create a community page that’s different from one of our pre-defined templates/quilts, you can create a custom page. Additionally, you can edit the text keys to define the title and description of this page to aid in SEO. Previously, when you created a custom page that used variables to display content for different versions of the page, each version used the same title and description. (For example, when your custom page contains posts filtered by label-names that exist in your community). Starting with 18.10, you can define different titles and descriptions for each version of the page, which in turn, can improve SEO for these pages. For example, you can use label names to set a specific SEO title and description for each variant of a custom page. To create different titles/descriptions for each variant of a custom page: Go to Studio > Advanced > Page Initialization. In the Content field for the Page Initialization script, add this FreeMarker snippet: <#if page.name == "TestCustomPage"> <#assign pageIdVariant = webuisupport.path.rawParameters.name.get("label-name","")> <#if pageIdVariant?length gt 0> ${page.content.head.setTitle(text.format("page.TestCustomPage." + pageIdVariant + ".title"))} ${page.content.head.setDescription(text.format("page.TestCustomPage." + pageIdVariant + ".desc"))} </#if> </#if> where label-name is the path parameter used for the custom page Click Save. In Studio > Text Editor > Custom Text, add the following keys (2 keys per page variant): page.TestCustomPage.label1.title = The Title of the page is label1 page.TestCustomPage.label1.desc = The description of the page is label1 page.TestCustomPage.label2.title = The Title of the page is label2 page.TestCustomPage.label2.desc = The description of the page is label2 where label1 and label2 are different labels on the community. We have added new FreeMarker methods on the page and webuisupport context objects. See FreeMarker updates for more details. Configure the number of email escalations allowed per topic/post Lithium supports three ways to escalate a topic/post: Email Salesforce case Salesforce Knowledge Article Customers using CRM connectors (Salesforce or Microsoft Dynamics) can now configure (via a Support ticket) the number of times a topic/post can be escalated by email. Because Lithium doesn’t dictate how companies follow-up on escalations, increasing the number of times users can escalate a topic can help users drive the follow-up, in case they haven’t heard back or continue to have a problem/question. If you wish to allow escalations via email multiple times for a topic/post, you must open a Support ticket. This configuration option is only available for customers using a CRM connector. Note: The Salesforce case and knowledge article options are still set to 1. API Updates We have made added new methods to the page and webuisupport FreeMarker context objects, and we have added new fields, constraints, and CRUD support to the Messages, Products, and Product_Categories Community API v2 collections. FreeMarker updates webuisupport.path.rawParameters.name.get("<name>", "<default>") page.content.head.setTitle("<title>") page.content.head.setDescription("<description>") webuisupport.path.rawParameters.name.get("<name>", "<default>") Returns the plain text value of the path parameter present in a URL. If the value of the path parameter is notspecified, the method returns the default value as passed to this method. Compare this method to webuisupport.path.parameter.name.get("name"), which returns the specified path parameter as an object. Tip: Using this new method means that you no longer need to convert the object returned from webuisupport.path.parameters.name.get("name")to a string using webuisupport.path.parameters.name.get("name").text. For example, in a URL like this: https://lithosphere.lithium.com/t5/custom/page/page-id/topics-by-label/label-name/mycustompage the following code snippet would return the value of the label-name path parameter ("mycustompage"). <#assign pageIdVariant = webuisupport.path.rawParameters.name.get("label-name","")/> page.content.head.setTitle("<title>") Sets the title for the page in the <title> tag within the <head> element of the page in context. Takes the title parameter as a string. The following snippet: ${page.content.head.setTitle("Some Page Title")} would render to: <title>Some Page Title</title> page.content.head.setDescription("<description>") Sets the description in the <meta> tag description attribute for the page in the <head> element. Takes the description parameter as a string. This code snippet: ${page.content.head.setDescription("some page description")} would render to: <meta name="description" content="some page description"> Community API v2 updates We've made updates to the Message, Product, and Product_Category objects. Message resource updates We have added new constraints on the Message resource and support for the following actions using the Community API v2. See Product Association and Product Mention API examples for CRUD examples. Post a message with product associations Post a message with a product mention Post a reply with product associations Post a reply with a product mention Edit product associations on an existing message Remove all product associations from a message Add or remove a single product association on an existing message New Message constraints products.id products.includes product_category.id product_category.id The following constraints enable you to: Get messages with a specified product association SELECT id, subject, view_href FROM messages WHERE products.id = 'sauconyRide10gtx' Get messages with a specified product association, filtered by product category SELECT id, view_href, href, subject, body FROM messages WHERE products.id = 'sauconyRide10gtx' AND product_category.id = 'runningShoes' AND product_category.depth <= 0 AND products.includes = true Return messages filtered by the specified product category SELECT id, view_href, href, subject, body FROM messages WHERE product_category.id = 'runningShoes' AND product_category.depth <= 0 AND products.includes = true Return messages associated with product categories and child categories up to three levels deep SELECT id, view_href, href, subject, body FROM messages WHERE products.id = 'sauconyRide10gtx' AND product_category.id = 'runningShoes' AND product_category.depth <= 3 AND products.includes = true Product resource updates New Product fields status - The status of the product in the product catalog (active or inactive). Inactive status is the equivalent to a soft delete. Inactive status is set on a product if a product previously included in the product catalog is no longer included in the import XML file or when a product is deleted in Community Admin. You cannot set or edit a product status as inactive via the Community API at this time. Inactive products are returned in LiQL queries only when they are requested specifically in the WHERE clause. See the Constraints section for an example. New Product constraints status tag_scope.board.id tag_scope.category.id tag_scope.community.id tag_scope.conversation.id tag_scope.message.id The following constraints enable you to: Filter products by status (active or inactive) SELECT id FROM products WHERE status = 'inactive' Return products mentioned in or associated with messages scoped to the message, conversation, board, category, or community level SELECT * FROM products WHERE tag_scope.board.id = 'runningShoes' SELECT * FROM products WHERE tag_scope.category.id = 'womensShoes' SELECT * FROM products WHERE tag_scope.community.id = 'lithium' SELECT * FROM products WHERE tag_scope.conversation.id = '572' SELECT * FROM products WHERE tag_scope.message.id = '81' Product_Category resource updates New Product_Category fields status - The status of the product category in the product catalog (active or inactive). Inactive status is the equivalent to a soft delete. Inactive status is set on a product category if a product category previously included in the product catalog is no longer included in the import XML file or when a product category is deleted in Community Admin. You cannot set or edit a product category status as inactive via the Community API. Inactive product categories are returned in LiQL queries only when they are requested specifically in the WHERE clause. See the Constraints section for an example. New Product_Category constraints status The new constraint enables you to: Return inactive product categories SELECT id FROM product_categories WHERE status = 'inactive' You Found It. We Fixed It. Text properties editable in Studio now support UTF-8 characters. UTF-8 is a compromise character encoding that can be as compact as ASCII (if the file is just plain English text) but can also contain Unicode characters (with some increase in file size). UTF stands for Unicode Transformation Format. The “8” means it uses 8-bit blocks to represent a character. The number of blocks needed to represent a character varies from 1 to 4. Learn more about UTF8. Note: If you have a Unicode character in an English text properties file (text.en.properties and text.en_gb.properties), use the Unicode representation of the character. For example instead of the following: header.nav.Japanese = 日本語フォーラム use this: header.nav.Japanese = \u65e5\u672c\u8a9e\u30d5\u30a9\u30fc\u30e9\u30e0 We have reduced the time to save skin changes in Studio made in the Wrapper tab. The time to save changes is now around 5-10 seconds. The Community API v1 and v2, and FreeMarker context objects like env.context.message now return anchors appended with the correct domain Adding “//” after the domain name in the URL will no longer cause redirects from links/breadcrumbs on the page. It will instead redirect to a “404-Page Not Found” Page. This is to avoid phishing attacks and make the application more secure. Please note that “//” added to the end of the community URL or any URL while using the application is not and cannot be controlled in any way, and it doesn’t lead to any phishing attack scenario and the application is not vulnerable. Components, endpoints, and macros that have no displayable content can now be saved as expected again in Studio. You can now use object tag in the HTML tab of the editor to view the PDF embedded in a message. Example : The focus now comes back to the Upload Photo button in the TinyMCE toolbar when the photo uploader is dismissed by selecting either the Close button or Esc. The Date display format field in the Community Admin > System > Date and Time tab, used to define how dates are displayed and validated in the system, no longer restricts the format to three options selected from a drop-down list. Now, users can enter any date format they like, as long as the format the Java's SimpleDateFormat syntax. These format characters are not allowed: a H k K h m s S (hours, minutes, seconds, milliseconds, AM/PM). Note that this field does not affect time display settings. Time display format is controlled by the Time display format field in the same tab. Documentation Eratta The current tooltip for the Front page welcome text field in Community Admin > Content > Announcement page is misleading. The field is used by the Welcome component (common.widget.welcome ) and the Featured Content component (community.widget.featured-content). The text of these components can be scoped to the Community, Category, and Board-level. While the two components use the same field for content, the components use different styling. We will be updating this tooltip and in the component documentation in the next releaseViewsSign in to react to this postCommentsKhoros Communities 19.12 Release Notes
Khoros Communities 19.12 brings: New Features API Updates Bug Fixes New Features Group Hubs GA Private Messages v3 GA Enhancements to Search Subscriptions GA Group Hubs GA In the 19.8 Release Notes, we announced Early Access for our exciting new Group Hubs feature. Group Hubs is now in General Availability (GA). Group Hubs are our next generation to Groups. Therefore, we plan to sunset the legacy Groups feature late 2020. We believe you will find the extended capabilities and improvements to the user experience more than enough motivation to adopt this new way for your community users to interact. Group Hubs is enabled by default for all new Khoros Communities customers. Also, Group Hubs will be enabled by default for any customers who do not have Groups and are on Responsive. Any customers with Groups currently enabled must migrate to Group Hubs. Work closely with your Customer Success Manager (CSM) during the migration. See Group to Group Hubs migration for an overview of the migration path. Khoros will not initiate Group Hub enablement. After reading through the migration documentation, contact your CSM to begin the process. Group Hub membership types Every group hub has a membership type that controls access to the hub. A group hub can be: Open Closed Hidden In Open group hubs, all community users can browse and kudo all content, reply to posts, and comment on posts. Group hub members can create new content as well as browse, reply, and comment. Closed group hubs are visible to all users, but only members of the group hub can access content. Non-members do not have read or reply permissions for closed group hubs. Content in closed group hubs appears in the search results to group hub members only. Non-members who try to access a closed group hub are directed to a page explaining that the group hub is closed and that the user must request access. Members can create new content as well as browse and reply to existing content. Community users access Hidden group hubs either by invitation or by being added to the group hub directly in Community Admin. Hidden group hubs are hidden from non-members in the Community UI and cannot be searched. Non-members attempting to access the URL to a hidden group hub’s Group Hub Page or child nodes are directed to an error page. Requirements Group Hubs requires: Community version 19.12+ A Responsive skin Private Messages version 2+ Note: The Private Messages feature is required to send invitations to group hubs and to receive notifications that requests to join have been approved. In addition to Private Messages being enabled for the community, the community member receiving the invitation and receiving the approval notification must explicitly opt-in to receive private messages in My Settings > Preferences > Private Messenger. Important! Group Hubs provides new components. Two of these components, Group Hubs and My Group Hubs are not included on any pages by default. We recommend adding the Group Hubs component to the Community Page and/or the Category Page. We recommend placing the My Group Hubs page on the View Profile Page and/or the Community Page. See Group hub components to learn more about how these components work. See to learn how to add a component to a page. Group Hub Analytics With this release, Group Hub analytics are available in Community Analytics (formerly Lithium Social Intelligence). You can view metrics related to Group Hub activities on your Community using Group Hub analytics. The Community Analytics page now displays all the board types aligned under the All Apps tab. A new tab called Group Hubs is listed under the CONTENT tab. The metrics provided here are similar to the existing ones in Community Analytics. Additionally, information related to membership details like subscriptions added and removed to group hubs, number of members joined or left the group hub, invites sent and accepted are provided. Group Hub APIs Community API v2 supports Read actions via LiQL queries to the Grouphubs and Memberships collections. Create, Update, and Delete actions will be supported in the upcoming Community release 20.1. Update: The Memberships collection has deprecated with release 20.1. We recommend against creating any customizations using the Memberships collection. See the 20.1 Khoros Communities release notes for the new membership APIs. We are so sorry. We are making updates to the Membership API once again. Please wait until 20.3 when we will release the final updates. Group Hub integration with Khoros Care Group Hubs content flowing into Khoros Care will be supported in the upcoming Community 20.1. Group Hubs documentation Find Group Hubs documentation in the Group Hubs knowledge base. We recommend the following articles for an overview: About Group Hubs Group hub discovery and engagement Group Hubs API support Group Hubs best practices Group to Group Hubs migration Private Messages v3 GA In the 19.12 Release, we're announcing the GA of Private Messages v3. With the GA Release, we have added these features: Changes in Mobile View Option to copy/paste a comma-separated username list in the Send To field Search within private messages Upload files as attachments API support for threaded private messages Note: With the release of Group Hubs, when a group hub name is added to the Send To field, all the members having membership with the group hub are added. Changes in Mobile View We have introduced a new design for Private Messages UI in Mobile View. All functionalities remain the same. Messages grouped by conversation in threaded format Expanded view of a conversation Option to copy/paste comma-separated username list in the Send To field With this release, you can now paste a list of comma-separated usernames. This feature is useful when you have a list of users whom you want to send messages on a regular basis. You can copy/paste the list of user names in the Send to field and the usernames are automatically derived. Any invalid Usernames are removed from the list and the rest are added. An error message is displayed stating which Username was removed. Search within Private Messages To help you find messages in a crowded inbox, we have introduced search functionality. This is available in both desktop and mobile views. Just type the text you are looking for in the search bar. You can also choose from where you want to pull the message to narrow down your search. Click the Close (X) icon to navigate back to the Inbox. Note: Searches are not case sensitive and search for the exact match. Upload files as attachments You can now upload files as attachments to your private messages. Members must have the Upload file attachments to Private Messages permission to add attachments to private messages. You can find this permission under Admin > Users > Permissions. With these permissions set, you can also drag-and-drop/upload file attachments when composing private messages: API support for threaded private messages In the 19.12 release, we have added API support for Private Messages feature version 3. Threaded private messages (Private Messages v3) uses new Community API v2 objects: notes_thread - represents a private message thread threaded_note - represents a message in a private message thread private_messages_view - represents the view of the private message mailbox: inbox or outbox The Private Messages v3 APIs are independent of the inbox_note and outbox_note objects. Customizations that include inbox_note and outbox_note should continue to work after upgrading to Private Messages v3, but inbox_note and outbox_note do not support the threaded message UI. The Community API v2 enables you to: Create a threaded message between one sender and one recipient Create a new note in an existing thread Create a threaded message to multiple users (non-broadcast) Create a threaded message (broadcast) Reply to a private message (single recipient) Reply to a private message (multiple recipients) Retrieve private messages on a private message thread Retrieve private notes threads for a user Mark private message threads as read or unread Delete private message threads See the following guides in the Developer Documentation Portal for more information: Private Messages APIs and feature versions Threaded private message API support Enhancements to Search Subscriptions (GA) Search Subscriptions trigger notifications when a post containing a set of keywords created primarily by the community admin or moderator is posted to the community. Some communities use top-level categories to partition their community by some criteria (for example, different languages). The current Search Subscription feature sends notifications to members regardless of the top-level category. That is, the member is notified even if the subscribed keyword is posted in a different top-level category. This is also the case when the top-level categories are of different languages. To reduce the notification noise, this enhancement restricts the scope of notifications to the top-level category that the member most recently saved the search subscription. In the below example, the member belongs to Portugal top-level category, but logged into Argentina top-level category. If he/she hits SAVE, he/she moves from Portugal top-level category to Argentina. The member is notified only when apples, oranges are posted in Argentina top-level category and not when posted in Portugal. A message is displayed as highlighted below. Email notifications contain the post text and the link to the post, so that you know why you are notified. The notification also has the option to reply via email and have it posted to the thread. Even if the post contains the search text appearing multiple times, only one notification is sent. If the text appears in the Subject of a reply to a post, then notification is not sent. Note: To enable this feature, open a Support ticket. Learn more about Search Subscriptions. API Updates Community API v1 Get the count of unread messages in a board or category To deliver on this idea from kandulmadhu, we have added the following endpoints to Community API v1 to retrieve the count of unread messages in a board or category for the current user: /boards/id/[id]/messages/unread/count /categories/id/[id]/messages/unread/count Pass the ID of the board or the category in the endpoint path. cURL examples (Session Key authentication) curl -X GET \ 'https://[COMMUNITY DOMAIN]/restapi/vc/boards/id/[BOARD ID]/messages/unread/count?restapi.response_format=json' \ -H 'li-api-session-key: [SESSION KEY]' curl -X GET \ 'https://[COMMUNITY DOMAIN]/restapi/vc/categories/id/[CATEGORY ID]/messages/unread/count?restapi.response_format=json' \ -H 'li-api-session-key: [SESSION KEY]' Note: If using OAuth, pass Authorization and client-id in the header as described in the The Community API v1 call. Response example { "response": { "status": "success", "value": { "type": "int", "$": 14 } } } Community API v2 Private Message API (threaded private messages) We've added the notes_thread and threaded_note objects and CRUD support for Private Messages feature version 3. See Threaded private message API support in the Developer Documentation Portal for full details. See Return promoted topics first in a LiQL response We've added the is_promoted field and the include_promoted constraint to support returning Promoted topics at the top of LiQL responses. When is_promoted is true in a response from the messages collection, the topic has been promoted in search results in Community Admin > Content > Promoted Search. The is_promoted field can be used in a SELECT statement. When include_promoted is set to true in the WHERE clause of a query to the messages collection, any topics defined in Community Admin > Content > Promoted Search appear first in the result set followed by the organic search results (search results regardless of promoted items). For any given search, a maximum of two promoted topics are returned in the response. Promoted topics are included in the response in addition to the number of items specified by LIMIT in your query. For example, if you set LIMIT to 5 and two promoted items exist, the results set will include 7 items. This matches the experience of the Community UI, which includes promoted items at the top of search results and also again in the response. The ORDER BY clause defines the order of the organic search results, whereas the Priority of promoted search items (set in in Community Admin) dictates the order of the promoted results. See About Promoted Search and Create Promoted Search rules to learn more about the Promoted Search feature. Example query SELECT subject, id, author, view href FROM messages WHERE subject MATCHES 'dogs' AND include_promoted = true ORDER BY post_time DESC LIMIT 5 You Found It. We Fixed It. We have improved the performance when returning badge counts. We have improved security against Cross-Site Scripting (XSS) when submitting an attachment as part of a topic or reply. We have fixed an issue where customers were seeing JavaScript errors like the following when landing on Forum Page or loading the Message Editor: TypeError: aa is undefinedlia-scripts-body-min.js:formatted:42636. Issues with customers experiencing a Cloudfront timeout error for requests taking longer than 60 seconds have been resolved. Subscription notifications are now being sent properly after Blog and TKB articles are published after being saved multiple times as a draft. We have fixed an issue where the @mention drop-down list was not showing the correct results even when the exact username was entered in the UI. @mentions is now working as expected. TinyMCE with Editor v2 no longer adds an unwanted "http://" to the URL when creating an anchor within the same page. Performance issues with label-based searches when hierarchical labels is enabled have been resolved. We have fixed a bug with Alt-Text on images where the Alt-Text was set to the image file name if no Alt-Text was specifically set on an image using the alt attribute of the <li-image> element, even if the image had a caption. Now, the image caption is set as the Alt-Text unless a user manually overrides the alt attribute in the HTML tab in the Editor. If no caption is set, and there is no alt attribute defined, the Alt-Text will default to the image file name. Community error pages now include CSP or X-Frame-Options headers. Due to inconsistencies with Search subscription notifications, we no longer allow customers to create search subscriptions with search terms entered on multiple lines. For example, a user can no longer enter: Peaches Apples Pears This fix helps ensure that the Community app recognizes and interprets the subscription correctly and that customers receive Search subscription notifications as intended. The notification after the successful nomination now says "Success! This topic was nominated as an article to the <board title>. View Dashboard." instead of "Success! This topic was nominated as an article to the <board ID>. View Dashboard." Customers reported losing the ability to copy/paste images into the Editor from the clipboard with Community release 19.9. We have fixed this issue. We have resolved "Resource not found" errors encountered when inserting an image with the Image Uploader and then editing the uploaded image. Relative dates are now translated into Russian correctly. Image links to images uploaded to Community and rejected via moderation now correctly show an 'unavailable' image instead of the rejected image. Selecting Options > Print in a TKB comment now takes you to the Print Page as expected. Floated topics that were unfloated and then floated again at a later date now appear at the top of the message list as expected, instead of retaining its original float timestamp.ViewsSign in to react to this postComments
8KViews
3Comments
