Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted September 12, 2024Sep 12 When I view my Recent Badges (on here) from my profile the Rank Progress does not show the date. Yet, when you view the Members Badges from ACP (Manage Badges) the date earned is populated with the actual date. Is this a bug?
September 13, 2024Sep 13 Community Expert Its likely that was when they were recalculated. Are you seeing an issue on your own site?
September 13, 2024Sep 13 Author Yes, I'm seeing similar. But why not display the real date as its available?
September 13, 2024Sep 13 Community Expert There would be no accurate date available. You are likely to be seeing the rebuild date. For this reason we dont show the exact date on the front end
September 13, 2024Sep 13 Author No, the real date is available. Take a look at a member in ACP, then click on Manage to get to Manage Badges, there you can see the date earned. Here are some screenshots from my forum, I'm sure you will see the same on here for my account. Also just noticed that its saying the badges were Manually Award but they are all via rules. That looks like another bug.
September 13, 2024Sep 13 Community Expert Badges are different than ranks. Especially, as it looks like those were manually awarded rather than by rules.
September 13, 2024Sep 13 Author Badges are different than ranks. Especially, as it looks like those were manually awarded rather than by rules. Also just noticed that its saying the badges were Manually Award but they are all via rules. That looks like another bug. No, they were not manually awarded, I said that. (I know its Friday and we are looking forward to a rest 🙂 ) Yes we are talking about Ranks not Badges, that is just the name of these pages/sections.
September 13, 2024Sep 13 Community Expert As pointed out, badges are not ranks. You are comparing 2 different things
September 13, 2024Sep 13 Author Yes we are talking about Ranks not Badges, that is just the name of these pages/sections.
September 13, 2024Sep 13 Community Expert Yes we are talking about Ranks not Badges, that is just the name of these pages/sections. Ignoring badges altogether for the time being. The rank would be generated when the rule is ran. Therefore, if you are rebuilding, you would get that date as Marc explained. Not the date which the rule was originally done. For instance, if I met the qualifications for moving to a new rank on January 2024. That would show as what you're see for the rank earned date. However, if I rebuild my achievements on September 13, 2024. I will now being said as hitting the rank on September 2024 as the code recalculated all the rules and saw today, they met the qualifications for that rank.
September 13, 2024Sep 13 Author Ignoring badges altogether for the time being. The rank would be generated when the rule is ran. Therefore, if you are rebuilding, you would get that date as Marc explained. Not the date which the rule was originally done. Yes, that is what I am experiencing but why display the rebuilt date when you have the original date the Rank was awarded as it serves no purpose to the member?
September 13, 2024Sep 13 Community Expert why display the rebuilt date when you have the original date the Rank was awarded as it serves no purpose to the member? In the current design, we don't know what the original and rebuilt are. They are one.
September 13, 2024Sep 13 Author Yes we do, they are listed here as explained above. These were not manually awarded that looks like a bug as they list under the Via Rules tab and not Via Manual Adjustment tab.
September 13, 2024Sep 13 Author Oh, hang on I got lost. Both the Ranks and Badges lost their dates when it was rebuilt in Apr 2023. So all the dates were changed then which is a pity 😞 However, there seems to be a bug. In ACP it claims the badges where manually awarded but in my case they were all Via Rules. Can you check on here if you are seeing the same?
September 16, 2024Sep 16 Community Expert Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.