리더보드가 다시 로드되고 반복됩니다

[inj3ct0r]

Hi, Leaderboard repeat names on default settings

[JammyDodger]

Could you be a little more specific? I can’t see any repeated names in the screenshot.

[inj3ct0r]

testuser 108 he is the last user in forum
under storm he is the first user in leaderboard

the scroll down leads me to this number

and i only have 111 member in the forum

[JammyDodger]

Oh yes, I see. You get to those with 0, and then it carries on with some more. Let me see if I can replicate this on my test site.

I’m afraid it works as expected on my test site, @inj3ct0r. Does the issue still happen for you in safe mode with themes and unofficial plugins disabled?

[inj3ct0r]

i did it but still same

[JammyDodger]

Hmm. It does seem to be increasing in multiples of 108. Do you get any errors in your browser console when you refresh the page? Or is there anything in your /logs page that could provide more of a hint?

If you could share a link to your forum that may help us see what’s happening.

[Don]

Yeah, this seems to a bug. I can repro this. This is really odd. It seems the spinner on the bottom is activate on the leaderboard sometimes and load the members list again.

Repro:

1. Create a leaderboard (I created with TL3 group to be a fewer (43) member)
2. Go to the leaderboard
3. Scroll down to the bottom (if the spinner isn’t activate on the bottom reload the page and scroll down again).

On the video you can see the cheers always reloads and start over after the bottom loader activates.

No error in console or /logs.

[JammyDodger]

@Don

재현 방법:

1. 리더보드를 생성합니다. (멤버 수가 적도록(43명) TL3 그룹으로 생성했습니다)
2. 리더보드로 이동합니다.
3. 맨 아래로 스크롤합니다. (맨 아래에서 스피너가 활성화되지 않으면 페이지를 새로고침한 후 다시 아래로 스크롤합니다.)

해당 단계를 따라 이 문제를 재현할 수 있습니다. (스피너를 트리거하려면 빠르게 아래로 스크롤해야 했습니다.)

이 문제를 Contribute > Bug 채널로 옮기겠습니다.

다시 한번 감사드립니다, Don.

[Falco]

@Don

Create a leaderboard (I created with TL3 group to be a fewer (43) member)

So the trigger is having less than a single page of users in a leaderboard?

[Don]

I tried it now with TL2, TL3, TL4 (347) user. Same result. I think not the fewer (less than a page) user is the trigger. I think maybe we didn’t notice this until now because we didn’t scroll down fully to the bottom of the list.

[inj3ct0r]

[selase (Selase Krakani)]

@inj3ct0r and @Don The issue has been resolved with the most recent plugin update. Thanks for the report and the detailed steps provided for reproducing the issue.