tshenry
(Taylor)
8월 7, 2025, 10:45오전
122
Okay, the component has been updated
https://github.com/tshenry/discourse-trust-level-avatar-flair/commit/b0b38c8c5cfe9d803ec6fa53e89449e17c82a69d
The update relies on a very recent core update — DEV: Improve user handling and access in post components by megothss · Pull Request #34013 · discourse/discourse · GitHub . If you are on 3.5.0.beta9-dev, you will need to be running that commit in order for this component to work. I have added a compatibility file to help protect most cases, but if you are someone who likes to update themes/components manually, please check your Discourse version.
4개의 좋아요
Was doing some maintenance today and saw this had been updated. Thanks for taking the time to do so, it is appreciated.
4개의 좋아요
Hi, after weeks of working fine, I have now this error in the console:
Well, well, if I disable the TC Trust-Level Avatar Flair the issue disappear…
But I must say, I had this TC installed long before the issue of replies not displaying arose…
The error I have in the console:
[image]
2개의 좋아요
tshenry
(Taylor)
10월 3, 2025, 12:48오전
126
Very strange! Will take a look and see if I can figure out what’s going on.
3개의 좋아요
tshenry
(Taylor)
10월 3, 2025, 2:25오전
127
@patrickemin I’ve pushed a fix for the deprecation notice that I’m hoping may also prevent the error you were encountering (I could not reproduce the error, just the deprecation notice). Can you see if the issue clears up after you update the component?
1개의 좋아요
Unfortunately, no, the issue (replies not visible until I refresh manualy the page) is still here.
1개의 좋아요
tshenry
(Taylor)
10월 3, 2025, 2:33오전
129
Try one more update I figured out the way to reproduce the issue right after I posted and pushed another fix.
1개의 좋아요
Not any better… Same issue.
tshenry
(Taylor)
10월 3, 2025, 2:36오전
131
Is there any chance you didn’t refresh the page you used to test after updating the component a second time?
I was getting the includes error in your screenshot after the first update when posting a reply, but I cannot reproduce any error now after the last update.
1개의 좋아요
Good catch, it’s now working ! Thanks !
1개의 좋아요