CarolineS
Boss
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Khoros Communities 26.1 Release Notes
FWIW, this is working fine for us (Classic, 26.1 (26.1-release r2601190002 / Commit Id: 13e7d91622b8e3210ab096bdfd524174e3636f30 ). Hopefully fixed for everyone else too! (though I can't confirm it was ever broken for us)278ViewsSign in to react to this post0Comments- 777ViewsSign in to react to this post0Comments
Reinstate "top engaged contributors" monthly blog
I think it's sad that the Atlas Highlights blog series has stopped since July 2024 (the last one I can find... July 2024 Atlas Highlights ) It'd be nice to at least recognize the few contributors who remain in this community... per community best practices. I imagine this could be fairly easily generated via AI 🙃1.1KViews1CommentRe: Regarding O2 Community Forum Registration
Good luck, mobilelinksuk! Hope this issue gets resolved soon by the o2 team.2.2KViewsSign in to react to this post0CommentsRe: Why do PageScripts changes require a Community Restart?
LucyL maybe someone at Khoros could help answer this?1.2KViewsSign in to react to this post1CommentRe: Khoros Communities 25.10 - Release Notes
We are also still on 25.9 on staging (Classic Community), despite it being past the maintenance window for October 21 (unless I am confused and the October 21 maintenance window starts at 11:59 pacific? I may well be confused?). LucyL any knowledge of what's going on with the 25.10 release?1.2KViewsSign in to react to this post1CommentRe: Khoros Communities 25.10 - Release Notes
Just reviewed the Khoros Maintenance Windows doc and confirmed that the Oct 21 maintenance window should have happened 01:00 AM - 05:00 AM PDT1.2KViewsSign in to react to this post0Comments- 1.1KViewsSign in to react to this post0Comments
- 1.9KViewsSign in to react to this post6Comments
coreNode.permissions.hasPermission context object probably is the closest you can get. But it's rather limited as you can only check for the current user AND current node. E.g. you cannot use it easily in a navigation component to show/hide elements without reading permissions.
I'm wondering what you are trying to build though that wouldn't work with Khoros built-in permissioning? The API is quite good at hiding stuff where the current user doesn't have read permissions. Isn't that sufficient for your use case?
278Views
0Comments
