Akenefick
Genius
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Badges for returning members
Not sure if you are on Aurora or Classic but briefly looking at the docs it looks like they are the same when it comes to badge rules. So, you can award a badge based on sign in date like this signin_date > "2025-05-01" But you only want users that have been inactive for a long time too which I don't think you can do directly, so I would use a role for that. Export a list of users who have not logged in since whatever cutoff date you had in mind and import the list with a role like "Inactive" for example. (hopefully you can do that in Aurora if that's what you are on) Then you can chain them together like this signin_date > "2025-05-01" AND user.role.name in [‘Inactive’] I have never done this so I would test first but I think that should work.Re: Session Key auth 302 Failure
I think what CarolineS said is probably the issue created via the admin console with a username & password Even if your community has SSO you can create a non SSO account in admin. Create new users ( - Lithium Community That is what you should use. Also, if you are trying to do this on stage you will need to include the HT access username and password or ask support to whitelist your IP for stage, so you don't need it. Also, not sure if you are on Aurora or Classic. I am only familiar with classic however, based on Matt's option 1 here Can someone walk me through authenticating and using Postman with Aurora? | Atlas I think it is the same for Aurora.Re: json query syntax matches AND OR
Hi Koben are you on Aurora or Classic? I'm still on classic and only really familiar with that. So, here's how you would match multiple tags on classic with AND logic. GET https://community.yourcommunity.com/api/2.0/search [ { "messages": { "fields": [ "author.avatar.message", "author.login", "author.view_href", "author.rank.name", "author.rank.icon_right", "author.rank.color", "subject", "post_time", "post_time_friendly", "view_href", "replies.count(*)", "metrics.views", "user_context.read", "replies" ], "constraints": [ { "board.id": "aktestboard", "depth":0, "tags.text": "tagone" }, { "tags.text": "tagtwo" } ], "limit":10, "subQueries": { "replies": { "fields": [ "author.login", "author.view_href", "author.rank.name", "author.rank.icon_right", "author.rank.color", "post_time" ], "limit": 1 } } } } ] The important part being the constraints "constraints": [ { "board.id": "aktestboard", "depth":0, "tags.text": "tagone" }, { "tags.text": "tagtwo" } ], And if you want an OR logic instead you would do it this way "constraints": [ { "board.id": "aktestboard", "depth":0, "tags.text":{ "in":[ "tagone", "tagtwo" ] } } ], You can find a lot of guidance on Json queries here The Community API v2 request And all the message fields and constraints etc. here messages I suspect since you're looking for tags instead of labels you might be on Aurora but if not happy to help if you have any more questions.Broadcast private message with API not being sent to all users
Hi Everyone, Seeing something a little strange that I can't figure out. Working on a custom component that sends a broadcast message to all the voters on an idea. Testing on stage I see only around half of the messages are sent no matter how many I send (sometimes over sometimes under). So, for example, a message that was supposed to have 200 recipients might only send to 120. You can see below there were 201 voters in this case. The large console log that says bodyString is the body of my API call and I copied it and double checked. All 201 users were present in the body. But the response from the call shows only 122 recipients. And it is not a consistent limit. If I send to 800 users, it goes to 339. However, if I send to 800 users from the out of the box private message page all 800 go through. I am only able to test this on stage with large numbers so I'm not sure if it could just be an issue on stage. I don't want to spam hundreds of real users to test on production 😀 Has anyone else got any experience with this? ThanksRe: Boosting a User
I think the way to do that is with a role requirement for the rank. You can create a rank where the only requirement is a role. Then you could manually assign that Rank by giving the user the required role. Some things to keep in mind, rank is awarded by going down the list and finding the first rank the user meets the requirements for. So, the rank's position in the list matters. Also, remember you can have multiple ranks with the same name but different requirements. So, for example, if you have a rank named "Expert" that requires 5 accepted solutions, but you want to be able to boost a user to that rank manually you can create a second rank named Expert that requires a role instead. You could achieve the same result with a single rank with a rank formula like this (net_accepted_solutions >= 5) || hasRole("Product Expert") where || means or.
