Hi,
This issue still remains
Will there be a fix coming for this?
Trust level 3 user title disappearing
Hi,
This issue still remains
Will there be a fix coming for this?
Trust level 3 user title disappearing
It should be fixed since January. What are the steps to reproduce the issue? It works when I do the following:
/my/preferences/account)The selected title is still visible.
hey, I was redirected from this topic:
I still have this issue and from my observation this happens to all other badge related titles when date changes, while Iām not 100% sure about it.
A user report this issue to me and hereās what I tested yesterday:
Is there a way to verify that itās related to date change other than changing pc timezone setting? I tried this but it does not work (title did not disappear) .
I appreciate any suggestions, thanks
i also got this report from a user. i could not reproduce it using my old way, that acctually is fixed ,but somehow the user managed to get its title removed :S
The user sed he will try to figure out the logic how he managed to do it.
@HeyRR @gerhard OK THIS IS RANDOM
It seems that the title gets removed always 20:00 meaning 8:00 PM at the evening Finland local time. GMT +3 .
Something happens at that time? Some Cron job?
Thanks to @HeyRRās description Iāve identified the issue. Itās the BadgeGrant background job which doesnāt handle localized badge names.
Iām going to merge that tomorrow.
Thanks, I can see the badge is still there after rerunning the BadgeGrant job.
However, it seems thereās another issue related to this BadgeGrant job. I used to manually bulk assign some badges(eg. give out first like or receive first like) to users who cannot get it automatically because such like is given or received in restricted category.
but when the BadgeGrant job was triggered, all users who get such badge from manually bulk assign will lose it.
My Tests:
Manually assign a default badge which a user cannot get it automatically due to restricted category issue but he/she meets the requirement. Badge will be removed after running BadgeGrant.
Create a customized badge with some SQL, e.g. grant this badge when user post new topic in a specific category. Manually assign this badge which a user cannot get it automatically due to restricted category issue but he/she meets the requirement. Badge will be removed after running BadgeGrant.
Create a customized badge, no SQL. Manually assign this badge which a user cannot get it automatically due to restricted category issue but he/she meets the requirement. Badge stays after running BadgeGrant.
I guess this is the correct behavior as all those manually granted users does not meet the SQL query and hence will be kicked out from candidate group. But if thatās the case then most discussion in below topic will make much less sense for forums which has very active restricted categories. Also, to my understand, short-term solution becomes impossible.
Any suggestion here? I can simply stop doing that but just curious if thereās a way to deal with it.
You can stop this by turning off the āRun revocation query dailyā setting, but you may not be able to do that for built-in badges.
Is this deployed to all services? We are still seeing this issue. https://keskustelut.inderes.fi/
EDIT: Oh i guess master is not automatically deployed to all discourse hosted services i guess. When it is supposed to be released?
Thanks for the reminder. Iām going to make sure your site gets deployed on Monday.