Squad Games

One additional question and/or feature request:
It would be awesome if there was conditional logic for the tags to only show if they have been filled out.
So if a user answered question X with 123 but left question Y blank the topic post template could be setup to show both if both were fully filled out?

Thanks for this update!

The issue: when someone let’s a subscription (product subscription or regular subscription) expire, they will later not be able to buy it again, because the invoice on file prevents a new subscription. But the existing subscription also cannot be renewed because the invoice has expired. This can only be solved by intervention from an admin (manually finding and deleting these invoices), but there might be hundreds of those and it would require a constant monitoring of expired invoices. 
The solution: The check that prevents a new subscription with an invoice on file should be removed or adjusted. Someone who doesn’t have a subscription anymore, because subscription and invoice have expired, must be treated like anyone who never had a subscription. Both groups should see exactly the same offers because their status in relation to these subscriptions is the same. 
Why it matters: People run into this problem all the time and it’s not just an inconvenience, it it costing them money, because people who would want to pay cannot pay and probably just give up. Here are just a few examples from the recent days (and I have observed this and commented on it for years): 
Subscription buttons don't show up. (yesterday)
Subscriptions Bug (yesterday)
invoice has expired but member cannot renew (7 days ago)
The development time to fix this is probably much cheaper than having IPS support deal with this issue for years, constantly identifying the issue and guiding people through the process of the possible work-arounds. So it would be a win-win situation to finally fix this. 😉 

On mobile, when you are viewing a thread and you click on the search tool, you're redirected to the search page rather than have a search input embedded on the same topic as it does for the desktop version, this results on the "This topic" search option not displaying on mobile, it would be nice to somehow have that.

On mobile, when you are viewing a thread and you click on the search tool, you're redirected to the search page rather than have a search input embedded on the same topic as it does for the desktop version, this results on the "This topic" search option not displaying on mobile, it would be nice to somehow have that.

Passing this from our moderation team:
It appears that when a user has been banned, the forum will no longer allow @-pinging them.
It's a minor inconvenience for our moderator team (because they have frequent need to refer to them in reports and things). Of more concern, however, is that it publicly exposes a user's discipline status.
When we apply any sort of discipline to a user (queueing, banning, even spam flagging), it is important that nobody but the affected user can tell that anything has happened. By design, when we ban user X, other users can't see that X is banned.
However, the fact that a banned user can't be pinged anymore means that a regular user could try to ping them, find themselves unable to, and realize what's up with the user, which seems not okay to me.
 
Is this something that can be fixed? It seems like a relatively new change to the forum; I'm pretty sure we used to be able to @-ping banned users.

I see... thanks for the quick answer Jim.

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 !

Thanks very much indeed for this rapid response.

I'm afraid that I'm very chary of mucking around with the theme and we keep ours as a standard theme but with colour changes.

Any time we get any problems with third-party routines, the first question is always whether we have a custom theme and so I prefer not to go there.

I rather hope that somebody will come along with a plug-in which will deal with the matter – and of course it would be nice if the Invision team didn't assume to "know what's best" for their customers and the probably millions of people who rely on those forums for one reason or another.

I understand that at the top of the Invision development tree are 11 developers. I'd be interested to know what the decision-making process is when they decide to change long-standing forum cultures and not even allow Choice.

Seems a bit Republican to me.

I've successfully managed to migrate an existing Invision Community to a containerised set up on AWS Fargate. I've upgraded to 4.5.4.2 and everything is working as expected except I cannot get it to detect that php-redis is installed.
My httpd and php-fpm run in separate containers with httpd handing over to php-fpm via TCP 9000. Could this be the reason it cannot detect php-redis? Is there a way to force the software into making the redis options available?
My apologies - php-redis wasn't installed. Don't I feel the fool?

We do not publicly disclose how spammers are identified because it would only give those who wish to circumvent the protections more information as to how to go about it.
We use information from many sources (Stop Forum Spam, SBL, etc.) as well as Invision Community installations that report back to the spam service to devise a score that represents the probability the user is a spammer. As with any system, there can be false positives. You can either work with the user to register their account (i.e. manually from the AdminCP to "pre-register" the account for them), or you can submit a ticket and we can take a look on our end and make a determination as to whether or not to remove the block against the user. Unfortunately, however, we can't really get into "how it works" outside of that.