ContributionsMost RecentMost LikesSolutionsSupport Case ID Migration and URL Redirect What's Changing In our enhanced support portal (for more details, refer to this article), all support cases have been assigned new case IDs. However, we've made it easy to find your existing cases: Your original case ID is preserved in both the case title and dedicated search field Automatic URL redirect ensures your bookmarked links continue to work How URL redirect Works When you click on an old support portal link, our system automatically: Identifies your original case ID Finds the corresponding new case ID Redirects you to the correct case in the enhanced portal Troubleshooting redirect issue If you are trying to open a case and have been redirected to this page, it means we couldn't locate it. Please check: URL accuracy: Ensure the case ID in your link is correct Case Age: Case before 2023 may not have been migrated Direct search option: Visit Case Portal | Atlas and search using your original case ID Need Help? If you are still unable to access your case, please contact support@khoros.com, and our team will assist you prompty. Re: Join node/group 301 API error Hello yogeshdixit, You are missing "node:" in variable section. Just update your variable with the following: { "nodeId": "node:grouphub:test-open-gh" } Re: Sign-in modal displaying text keys - Status changed to: ResolvedRe: Sign-in modal displaying text keys This has been fixed now. Re: UX Issue on feed - Status changed to: Resolved StanGromer - Issue has been fixed now. Re: Frequent logouts on mobile / trouble logging in Hello CarolineS, Apologies for the inconvenience. There is no change in the functionality, we just have changed the flow from username/password to email/password. Even no limit change in password. Request you to pls clear your mobile browser cache and try entering the password manually (don't use auto fill). Still, if you see issue exist for you, we can jump on a quick call and sort it. Regards, Abhishek Gupta Re: How We Built It: Since you were gone component Hello tyw , Sorry to hear that!! Ideally, that should not be a case as truncating the notification is a core functionality, but still somehow that is not working for you. Kindly add below code to the bottom of the same component: <@liaAddScript> ;(function ($) { var length = 10; // Whatever length you want to truncate the notification var length = length-3; // 3 dots will also be part of total truncated string length const notificationFeed = document.getElementsByClassName("lia-notification-feed-item")[0]; const description = notificationFeed.getElementsByClassName("description")[0]; var pathname = description.getElementsByClassName("lia-link-navigation")[0].innerHTML; var trimmedPathname = pathname.substring(0, Math.min(length,pathname.length)); description.getElementsByClassName("lia-link-navigation")[0].innerHTML = trimmedPathname + "..."; })(LITHIUM.jQuery); </@liaAddScript> Let me know if you need any further help on this. Regards, Abhishek Gupta Re: http.client.request post() issue Hello djondinium Not really sure why are you passing three parameters in http.client.request - protocol, host, url. Can you simply use following call with just one parameter url and see if that works: <#assign response = http.client.request(url).body("{ 'grant_type':'refresh_token', 'refresh_token':'${upAuth.refreshToken}', 'client_id':'${upAuth.clientId}', 'client_secret':'${upAuth.clientSecret}' }", "application/x-www-form-urlencoded").post()> Regards, Abhishek Gupta Re: How We Built It: Since you were gone component Had a call with adriana4u and helped her adding CSS tweaks on their community end. Regards, Abhishek Gupta Re: How We Built It: Since you were gone component Hello adriana4u You have to make some CSS tweaks to make it work in your community. Example add the following to your custom component at the very top: <style> .lia-component-quilt-community-hero .custom-community-hero .lia-component-notificationfeed-widget-notification-feed-item:first-child { display: inline; margin: 0; } .lia-component-quilt-community-hero .custom-community-hero .lia-component-notificationfeed-widget-notification-feed-item { background: transparent; border: 0; display: none; } .lia-component-quilt-community-hero .custom-community-hero .since, .lia-component-quilt-community-hero .custom-community-hero .lia-component-notificationfeed-notification-list, .lia-component-quilt-community-hero .custom-community-hero .lia-component-notificationfeed-notification-list * { display: inline; float: none; width: auto; } </style> Even after adding the above css to your custom component you may have to add some css tweaks to make it work based oon your community. Regards, Abhishek Gupta