Dexter_X

Solved that problem by ourselves using short words in translation (to french). But you can modify your string values and set "Message", "Content" and "Ignore", that will be just fine. 😉 

There is a good Idea I got from another post to improve achievements system : allow a milestoned rule to be repeatable. 
What does it mean ?
Let's do it through an example :
Consider you've a standard (current system) milestoned rule giving points and a badge to a user creating 20 topics. The user will get points and badge once the milestone is reached an it is over. 
It is a good behavior from my point of view. But if you want to award users every 20 created topics, you'll need to create a rule for the 40th topic, the 60th topic and so on...
Now let's consider a "repeatable" rule :
If you take the same rule and "check the repeatable checkbox in the rule" (don't be afraid  this does not exist - yet -), the rule will give a badge and the points each time the user reach 20 new topics. (and not each time the user creates a new topic from its 20th one because 21 > 20). In other words : once the 20 created topics reached, the user get awarded and an internal counter is reset to 0 until the user creates 20 new topics (so until the users creates 40 topics, and so on).
 
Of course the principle could be applied to any milestoned rule and it may even reduce the amount of rules we'll need to define.
One last thing : when a user gets twice the same - repeatable - badge, it should be displayed twice in his profile awarded badges list.
 

Hey team, it's that time of the week again 🤯 
I wanted to take this opportunity to highlight a few new topics created by you all that have been a lot of fun to read and think about while I do the dishes. 
But before we get to that, check out this list of fixes and updates our development team smashed out in the last week alone:
 
- Added a Delete query as an upgrade step to remove old 'best_answer' notifications.

- Fixed an issue where Content Item Controllers returned 200 by default when they should return 404 or 403 (not found or forbidden).

- Fixed some language evaluation issues when PHP 8 is used.

- All buttons in #elUserNav now use the correct text color.

- Fixed an issue where it was possible to upgrade incorrectly when renewals were removed, and the new package had upgrade set to pro-rata.

- Fixed a race condition that can happen when Stripe sends a web hook request very quickly after charging a customer (renewals & device payments).

- Fixed an issue when upgrading to 4.5.0 with duplicate keys when consolidating the referrer tables.

- Fixed an issue when creating a record in the Admin CP and choosing another member as the author would not fire achievements for that author

-Improved logging for errors returned by Elastic Search.

- Fixed an issue where Topics would not refresh when selecting Forums in Fluid view. 

- Fixed the rank title not displaying correctly in new rank notification emails.

- Set a default value for the search flood time when creating a member group.

- Set a default value for the 'Time user must wait before download starts' group setting while creating a member group. (Downloads)

- Added support for Brightcove video embeds.

- Fixed an issue where the Oauth1 Login Handler would use a not existing method to log any upcoming errors. 

- Fixed broken links in the our picks widget.

- Fixed an issue where achievements would show in a hovercard for a member in a group that has achievements disabled.

- Fixed downloading files with non-latin character downloaded with corrupt characters in Edge and Chrome.

- Fixed an issue wehre copying a topic to a database would result in an IN_DEV CSRF key warning.
 

Now for the community content 🥲 
@Dexter_X conjured up a bunch of innovative ideas to enhance and elevate our newly-launched Achievements feature. 
 
 
Which inspired @wegorz23 to dream up their own spin-off.
 
There's also this pretty fun topic showing off our offices made by @Jimi Wikman. If you haven't already, upload a photo there and share your work environment. 
 
 
@Pavel Chernitsky took the time to share thoughts on Invision Community and how we can better things. There's always potential for topics like that to turn sour, so thank you for being constructive and allowing us the opportunity to hear you. 
 
 
And because I was so impressed with Dexter's Achievements contributions, here's one more topic they created that deserves your undivided attention:
 
Thank you for creating topics! It's the lifeblood of our community, and we love to hear from you so we can continue the forward momentum. 
Which was YOUR favorite topic? Have an idea for a topic but are too timid to post? Take a chance! There's no time for shy 😉 
Looking forward to chatting with you in the replies below!

We decided to create our own solution to overwrite badges, add some progress bar to next badge and to show users how many and what badge is next.
Like how many post he have and how many days on site.
I have working on addon to do it.
 

Just wondering why the label for Clubs still says 'New' on the homepage. It's been a while... no?

Another possibility regarding badges awarding are the badges the users can own while they keep on certain amount per time.
For example a user posts more than 30 posts / week : owns a "keep on" badge that could be named : "active contributor" (or something like that). So if the user goes under the 30 posts / week he looses the badge until he goes to that rate (or more)...
That could promote participation in a more permanent way.
Regarding milestones and points on that kind of rules I don't know if it can be useful. Milestones could be set on something like "owns that badge since 1 month" (so based on time) ; points make sense only if there are milestones (from my point of view)...

Thanks, don't forget to take a look here :
 
 

Another possibility regarding badges awarding are the badges the users can own while they keep on certain amount per time.
For example a user posts more than 30 posts / week : owns a "keep on" badge that could be named : "active contributor" (or something like that). So if the user goes under the 30 posts / week he looses the badge until he goes to that rate (or more)...
That could promote participation in a more permanent way.
Regarding milestones and points on that kind of rules I don't know if it can be useful. Milestones could be set on something like "owns that badge since 1 month" (so based on time) ; points make sense only if there are milestones (from my point of view)...

Another possibility regarding badges awarding are the badges the users can own while they keep on certain amount per time.
For example a user posts more than 30 posts / week : owns a "keep on" badge that could be named : "active contributor" (or something like that). So if the user goes under the 30 posts / week he looses the badge until he goes to that rate (or more)...
That could promote participation in a more permanent way.
Regarding milestones and points on that kind of rules I don't know if it can be useful. Milestones could be set on something like "owns that badge since 1 month" (so based on time) ; points make sense only if there are milestones (from my point of view)...

Ooooh I like this. It would be interesting if, while having this badge, they're moved to a new group (say a group with additional privileges). If they don't meet the 30 posts that week they're downgraded back to their original group (and thus losing the perks). 

Another great concept! 👏 

Hi, 
The reputation system is still "alive", it is just not displayed anymore in the author's pane (left side of a post). We've restored it back by modifying the template in the theme. It is a little "tricky" because there is three places where you need to do it in your theme forums/front/topics/postContainer template file : 
. to restore reputation badges/levels, around original line 110, add the following code after the </li> :
{{if $comment->author()->reputationImage()}} <li data-role='reputation-image' class='ipsPadding:half'> <img src='{file="$comment->author()->reputationImage()" extension="core_Theme"}' title='{{if $comment->author()->reputation()}}{$comment->author()->reputation()}{{endif}}' alt=''> </li> {{endif}} so you'll obtain something that looks like this, considering surrounding code :
</ul> </li> {{if $comment->author()->reputationImage()}} <li data-role='reputation-image' class='ipsPadding:half'> <img src='{file="$comment->author()->reputationImage()" extension="core_Theme"}' title='{{if $comment->author()->reputation()}}{$comment->author()->reputation()}{{endif}}' alt=''> </li> {{endif}} {{endif}} {{if $comment->author()->member_id}} so, it is important to place the new code after both </ul> and </li> ending the counters line.
 
. To restore the reputation counter, add the following code around original line 96, just after the <ul class="ipsList_reset ipsType_light ipsFlex ipsFlex-ai:center ipsFlex-jc:center ipsGap_row:2 cAuthorPane_stats"> :
<li data-role='reputation-badge'> {template="reputationBadge" group="global" app="core" params="$comment->author()"} </li> so you'll obtain something that looks like (considering surrounding code) :
<ul class="ipsList_reset ipsType_light ipsFlex ipsFlex-ai:center ipsFlex-jc:center ipsGap_row:2 cAuthorPane_stats"> <li data-role='reputation-badge'> {template="reputationBadge" group="global" app="core" params="$comment->author()"} </li> {{if isset( $comment->author_solved_count )}} <li>  
Edit for mobile display (add back reputation counter on mobile devices display) :
. To restore the reputation counter in mobiles display, add the following code around original line 57, inside the <h3> just after the {template="userLink" group="global" app="core" params="$comment->author(), $comment->warningRef(), TRUE, $comment->isAnonymous()"} and before the </h3>
&nbsp; <span class="ipsType_medium">{template="reputationBadge" group="global" app="core" params="$comment->author()"}</span> so you'll obtain something that looks like (considering surrounding code) : 
<h3 class='ipsType_sectionHead cAuthorPane_author ipsType_break ipsType_blendLinks ipsFlex ipsFlex-ai:center'> {template="userLink" group="global" app="core" params="$comment->author(), $comment->warningRef(), TRUE, $comment->isAnonymous()"} &nbsp; <span class="ipsType_medium">{template="reputationBadge" group="global" app="core" params="$comment->author()"}</span> </h3>  
Save your template file, reload your topic : job done !

Another possibility regarding badges awarding are the badges the users can own while they keep on certain amount per time.
For example a user posts more than 30 posts / week : owns a "keep on" badge that could be named : "active contributor" (or something like that). So if the user goes under the 30 posts / week he looses the badge until he goes to that rate (or more)...
That could promote participation in a more permanent way.
Regarding milestones and points on that kind of rules I don't know if it can be useful. Milestones could be set on something like "owns that badge since 1 month" (so based on time) ; points make sense only if there are milestones (from my point of view)...

Actually we can recompute badges for all members, but for an unknown reason some users do not get the badges they should and others got too much badges... 😑
In our case recompute all the members badges takes more than 3 hours (it has been long testing our rules system...), it will be useful if we could "rebuild a single user" badges/ranks set, for the users detecting wrong badges & rank attribution...
It may also be useful for testing purposes : tests the rules set on a single user goes more fast than on the whole community...

There was still some remaining bugs, I prefer to have a clean version than a new update every 3 days... V4.6.4 seems to be the "good one", so be patient... 😉 

I like the idea. However I would like to exclude user groups (and not only members) in the settings. Like excluding experts (not per user basis, but per group), who would like to see their full names to get more publicity. Or applying the setting only to paid user groups, like VIP users paying for their privacy 😉 

Actually we can recompute badges for all members, but for an unknown reason some users do not get the badges they should and others got too much badges... 😑
In our case recompute all the members badges takes more than 3 hours (it has been long testing our rules system...), it will be useful if we could "rebuild a single user" badges/ranks set, for the users detecting wrong badges & rank attribution...
It may also be useful for testing purposes : tests the rules set on a single user goes more fast than on the whole community...

I have people wanting to create more detailed Icons and Rank Badges.  The problem is that they are so small you can't see any detail on the images.  I think it would be nice to be able to view a larger image via lightbox from the users profile/badge page.

This would be useful or even recompute badges for a specific group.  Our community is fairly new, less than a year with over 5000 members and recomputes take about 1 hour+,  so I can imagine as it gets bigger what that will look like.

Hi, 
The reputation system is still "alive", it is just not displayed anymore in the author's pane (left side of a post). We've restored it back by modifying the template in the theme. It is a little "tricky" because there is three places where you need to do it in your theme forums/front/topics/postContainer template file : 
. to restore reputation badges/levels, around original line 110, add the following code after the </li> :
{{if $comment->author()->reputationImage()}} <li data-role='reputation-image' class='ipsPadding:half'> <img src='{file="$comment->author()->reputationImage()" extension="core_Theme"}' title='{{if $comment->author()->reputation()}}{$comment->author()->reputation()}{{endif}}' alt=''> </li> {{endif}} so you'll obtain something that looks like this, considering surrounding code :
</ul> </li> {{if $comment->author()->reputationImage()}} <li data-role='reputation-image' class='ipsPadding:half'> <img src='{file="$comment->author()->reputationImage()" extension="core_Theme"}' title='{{if $comment->author()->reputation()}}{$comment->author()->reputation()}{{endif}}' alt=''> </li> {{endif}} {{endif}} {{if $comment->author()->member_id}} so, it is important to place the new code after both </ul> and </li> ending the counters line.
 
. To restore the reputation counter, add the following code around original line 96, just after the <ul class="ipsList_reset ipsType_light ipsFlex ipsFlex-ai:center ipsFlex-jc:center ipsGap_row:2 cAuthorPane_stats"> :
<li data-role='reputation-badge'> {template="reputationBadge" group="global" app="core" params="$comment->author()"} </li> so you'll obtain something that looks like (considering surrounding code) :
<ul class="ipsList_reset ipsType_light ipsFlex ipsFlex-ai:center ipsFlex-jc:center ipsGap_row:2 cAuthorPane_stats"> <li data-role='reputation-badge'> {template="reputationBadge" group="global" app="core" params="$comment->author()"} </li> {{if isset( $comment->author_solved_count )}} <li>  
Edit for mobile display (add back reputation counter on mobile devices display) :
. To restore the reputation counter in mobiles display, add the following code around original line 57, inside the <h3> just after the {template="userLink" group="global" app="core" params="$comment->author(), $comment->warningRef(), TRUE, $comment->isAnonymous()"} and before the </h3>
&nbsp; <span class="ipsType_medium">{template="reputationBadge" group="global" app="core" params="$comment->author()"}</span> so you'll obtain something that looks like (considering surrounding code) : 
<h3 class='ipsType_sectionHead cAuthorPane_author ipsType_break ipsType_blendLinks ipsFlex ipsFlex-ai:center'> {template="userLink" group="global" app="core" params="$comment->author(), $comment->warningRef(), TRUE, $comment->isAnonymous()"} &nbsp; <span class="ipsType_medium">{template="reputationBadge" group="global" app="core" params="$comment->author()"}</span> </h3>  
Save your template file, reload your topic : job done !

It was not there in 4.5 either

In this kind of system (we have the same...) I would rather put the "repeatable" flag on the last/highest rule, so the user goes through all the levels you've defined (usually following an exponential curve) but it is never finished : the users can still got twice or more the last one. Seems a good way of "never ending" to me... 

There is a good Idea I got from another post to improve achievements system : allow a milestoned rule to be repeatable. 
What does it mean ?
Let's do it through an example :
Consider you've a standard (current system) milestoned rule giving points and a badge to a user creating 20 topics. The user will get points and badge once the milestone is reached an it is over. 
It is a good behavior from my point of view. But if you want to award users every 20 created topics, you'll need to create a rule for the 40th topic, the 60th topic and so on...
Now let's consider a "repeatable" rule :
If you take the same rule and "check the repeatable checkbox in the rule" (don't be afraid  this does not exist - yet -), the rule will give a badge and the points each time the user reach 20 new topics. (and not each time the user creates a new topic from its 20th one because 21 > 20). In other words : once the 20 created topics reached, the user get awarded and an internal counter is reset to 0 until the user creates 20 new topics (so until the users creates 40 topics, and so on).
 
Of course the principle could be applied to any milestoned rule and it may even reduce the amount of rules we'll need to define.
One last thing : when a user gets twice the same - repeatable - badge, it should be displayed twice in his profile awarded badges list.
 

There is a good Idea I got from another post to improve achievements system : allow a milestoned rule to be repeatable. 
What does it mean ?
Let's do it through an example :
Consider you've a standard (current system) milestoned rule giving points and a badge to a user creating 20 topics. The user will get points and badge once the milestone is reached an it is over. 
It is a good behavior from my point of view. But if you want to award users every 20 created topics, you'll need to create a rule for the 40th topic, the 60th topic and so on...
Now let's consider a "repeatable" rule :
If you take the same rule and "check the repeatable checkbox in the rule" (don't be afraid  this does not exist - yet -), the rule will give a badge and the points each time the user reach 20 new topics. (and not each time the user creates a new topic from its 20th one because 21 > 20). In other words : once the 20 created topics reached, the user get awarded and an internal counter is reset to 0 until the user creates 20 new topics (so until the users creates 40 topics, and so on).
 
Of course the principle could be applied to any milestoned rule and it may even reduce the amount of rules we'll need to define.
One last thing : when a user gets twice the same - repeatable - badge, it should be displayed twice in his profile awarded badges list.
 

In this kind of system (we have the same...) I would rather put the "repeatable" flag on the last/highest rule, so the user goes through all the levels you've defined (usually following an exponential curve) but it is never finished : the users can still got twice or more the last one. Seems a good way of "never ending" to me...