ContributionsMost RecentMost LikesSolutionsRe: About the Aurora member Profile page On both my community and the Khoros community, if I (as a non-admin) go and look at another users profile who has a Bio set in their profile page .. I can't see it. I can see it in my community when I view their profile as an Admin I don't know if you have a Bio set, but I can't see any Bio for you: Re: About the Aurora member Profile page Why is none of the information you enter in your profile edit page shown on your actual profile i.e. you bio, is it a setting I need to change Re: Khoros Communities 26.2 Release Notes [Updated] Any word on this fix? Re: Khoros Communities 26.2 Release Notes [Updated] Lief I noticed the same thing, and yes defiantly not in the release notes. The approved / solved thing is just confusing especially as they are different shades of green. Folks try to work out why and come up with some amazing misunderstandings. Like you I would like to have the option to turn it off. Our moderation is done from the moderation panel not the community front end. Re: Khoros Communities 26.2 Release Notes [Updated] MiladC / LucyL We have just had 26.2 put on our stage enviroment and all our builds are now failing, why? because there is no 26.2 SDK in khoros-aurora-sdk - npm can you fix? Re: How to determine if a given node is visible to the public? Sorry Folks, I need to spend more time in here. You could also do this using GraphQL Queries: query MyQuery { permissionsForCoreNode(id: "board:example") { ... on ForumPermissions { __typename readContent { access inheritedAccess { access } } readForum { access inheritedAccess { access } } updateFeaturedWidget { access inheritedAccess { access } } } } } In this example we are querying the permissions set on the core node "board:example", specifically this is a forum board. To demonstraight this graphQL call I have used 3 different permissions they are: Forum >> Read Content Forum >> Read Forum Forum >> updateFeatureWidget Why this last one? I want to demonstrate that this is pulling the default permissions for the node not the user context permissions, this will be demonstrated by the fact i am using an Administrator API role to pull this information and the administrator has this last permission set to assign. When I run this graphQL i get this response: { "data": { "permissionsForCoreNode": { "__typename": "ForumPermissions", "readContent": { "access": "INHERITED", "inheritedAccess": { "access": "GRANTED" } }, "readForum": { "access": "INHERITED", "inheritedAccess": { "access": "GRANTED" } }, "updateFeaturedWidget": { "access": "INHERITED", "inheritedAccess": { "access": "DENIED" } } } } } this tells you that the permission at this node is inherited as 'GRANTED' This graphQL is actually very very powerful, not only can it tell you what the default role is at this node but also where it was inherited from. I am not sure though, you may need to make this call using a graphQLAdmin call (I haven't tested that part) and if you do then you will need to put it in an Endpoint to prevent malicious users intercepting it and manipulating the call. Re: Khoros Communities 25.12 Release Notes This is looking more and more like an over zealous scanner but I do think the description of these cookies could be 'clearer' not just on their purpose, when they are dropped, what happens if they aren't dropped and can they be turned off? Re: Khoros Communities 25.12 Release Notes LucyL , I reached out to support, and it looks like it is indeed not dropping on page load - however because it doesn't expire on logout if you have been to the page before and it has not expired it will behave as if it was dropped on page load. Anyways we are still looking into it and I will let you know if I need anything else from you, tbh I can't help feeling a recent trend towards dropping cookies instead of looking at better, perhape more effective, ways to store - use and retrieve this data. Re: Khoros Communities 25.12 Release Notes LucyL Sorry we have another cookies issue from this release: LithiumLocalePreferences (For Classic and Aurora communities) 3 Used to keep track of the user’s preferred language 24 hours Increase in number of calls to verify user language preference. Language preference order may be altered or may default to browser selected preference. For Aurora - If this cookie is not present, a query will be executed to retrieve the language. If the user does not have a value in their preferences, we will use the browser's `Accept-Language` header. We took this to mean it was only dropped on login, but it seems to be being dropped on page load this changes its categorization for us. Can you confirm? Re: Khoros Communities 25.12 Release Notes Fixed day-of-week misalignment in analytics "Match day of the week" year-over-year comparisons. Really? Going to re-open our bug on this one. Revision: 25.12 (25.12-release r2512231126) Commit Id: 6f44f032fc2fa9d9bf7da881b8e205ae33861db9 Timestamp: 0