Dll

17 minutes ago, Jordan Miller said:

There was no great way to share this news. 

In advance would have been a start. 

Any clarification on what this means for support for those with existing licences which are over 30 days old? Is it only available through the forums from now on unless you buy priority support? 

I should have kept my face shut when I was suggesting Invision raise prices.

But, in all seriousness I have no issue with the increase itself. But for a company that's apparently expert in all things communication, it's a bit weird to see it just dropped in there with a site redesign rather than pre-announcing it, emailing customers in advance or whatever else. 

The site does look waaaay better than it did though. 

Would it be possible to add more filtering to the members who are shown the message, rather than just using member groups? Specifically, what we'd be interested in would be a time since joined filter - as we don't think it's too worthwhile showing the prompt to someone who has recently joined. So for instance, we could filter it so someone who's joined <365 days ago wouldn't see it?

It's in profiles, next to posts etc. All the badges awarded so far are showing as well. I'll raise a ticket?

Since 4.6.6 ranks and badges are now visible during a rebuild, is this by design or a bug?

I'm hoping it's a bug, as it creates confusion. 

@Matt - this is working fine for us beyond 365 days and  rebuilding only gives awards to people who have logged in > than the number of days since registration to trigger the rule. Is this likely to be because we prune the IP and device logs after that period?

Well, I don't know when you last ran the rebuild or what version you're running. But if it was a while ago or prior to the latest version, perhaps it'll work as you'd expect now. As it certainly is for our community using 4.6.5.1 and appears to be working the same way on this community as well. 

3 minutes ago, iacas said:

I asked to have the ticket re-opened. But for the fifth time or so… that's what they told me. That it's working as designed. They also told me to create this feature request.

Just out of interest, based on what you're saying, this user on your site should have been awarded your one year badge, but haven't. Why would that be?

https://thesandtrap.com/profile/62125-teal379/

Well, as I say, that's not what we're seeing and it's not what's happening on here. 

10 minutes ago, iacas said:

IPS is saying, and I saw on my own forum, that "when" is triggered by a rebuild of the achievements.

And again I'll ask you to please stop posting here, as apparently you should file a bug, because the software is working as designed on my site, per IPS.

I'll stop posting after this, as it's obviously difficult for you when someone has an opposing point of view. But, here's a user on this community who registered in 2004 and hasn't logged in since. Based on how you're saying the system works, they should have the one year in badge that IPS use, but don't.

https://invisioncommunity.com/profile/63016-notacake/

We know that IPS have rebuilt their ranks/badges at least once, so I assume that means this community isn't working in the way you're describing either.

I'm just telling you what we're seeing. It's different to what you apparently are, but I can categorically tell you that the behaviour on our community when running a rebuild is not at all what you're describing.

We can go round in circles for hours here. But ultimately, if that were the case, every single person registered on our community prior to certain dates would be awarded longevity badges, and that simply isn't the case. We rebuilt just a few days ago, and the only people who have been awarded the badges are those who have logged in enough days after registration for the rules we've set to apply. 

Just now, iacas said:

It does. You've got this one wrong. I had a whole support ticket about it. The "user logs in" event in the rule is triggered by the rebuild of the achievements.

Honestly, I don't. It may not be the case on your community, but we have a clear difference in the numbers of people who have been awarded these sort of badges and the numbers of people who have been registered long enough to receive them if it was solely based on the difference between the date of the rebuild and their date of registration.

5 minutes ago, iacas said:

That's my point.

If someone creates an account on September 7, 2010, and never visits the site again, if you rebuild achievements on September 7, 2021… they'll be awarded the "10 years of membership" (3650 days) achievement.

That's why I want something that recognizes a time frame of active membership.

No, you've misunderstood my meaning. From what I've seen on our community, if someone signs up on September 7th 2010 and never visits again, rebuilding achievements on September 7th 2021 doesn't award them anything. But if they sign up on September 7th 2010, their last visit was on September 7th 2020 and you rebuild on September 7th 2021, then they will be awarded the 10 year badge. As I say, it's based on their last visit, even if that wasn't recent but was > than the number of days after their registration set in the rule. 

@iacas - this isn't how the system has behaved on our community. The rebuild appears to look at the last logged in date and gives the badge based on that. What that does do is award people badges for longevity even if they haven't logged in recently, as long as their last login was > the number of days after their registration for the rule that's been set. But that seems reasonable enough to me. 

It doesn't work that way. It's based on when the user logs in, so won't award it to someone purely for registering a year ago and not logging in since. 

The thing is, unless the image sizes are specified on the page, it doesn't matter which method you use, the page will still jump around as it loads. So, instead of height: auto, as it seems to be at the moment, the height of image thumbnails really should be set to the correct number of pixels. 

This is throwing an error for us on 4.6.4 using php 8 (was fine on php 7). 

Quote

TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /var/www/html/forum/system/Theme/Theme.php(860) : eval()'d code:2575
Stack trace:
#0 /var/www/html/forum/system/Theme/Theme.php(860) : eval()'d code(2575): count(NULL)

3 minutes ago, Stuart Silvester said:

Flagging as a spammer does do this if the 'delete' content option is selected.

Oh ok, didn't know that. Thanks. 

1 minute ago, Stuart Silvester said:

As you've noted, keeping the accounts there prevent the email address from being used again.

There is one issue with that, in that flagging as a spammer doesn't strip the profile, which quite often gets links, about me's etc added to it by the spammers. Unless this has changed in 4.6?

Hi, just wondering if this allows you to  add tags to topics in bulk at all?

@Fosters - any news on when the 4.6 compatible version is going to be released please?

Any particular reason you bought a new certificate since SSL appears to be included in hosted ips products?

While we're at it, how about bringing back internet explorer 3?