Dll

Will this also hide quotes from ignored users within other member's posts?

Are you running cloudflare? If so, I'd recommend whitelisting your ip and seeing if that solves the problem.

Yes, this has been an issue for years. I've seen it reported countless times. Wouldn't it be useful to have a bug tracker for this type of thing....

Honestly, that makes no sense. Giving a guest a sub-par experience of a community is not a smart way to attempt to entice them to join. There is already a link on the forum index page to the thread (eg the one linked from the thread title), so the link with the time on it is basically a duplicate in any case. Therefore there's no SEO or crawlability upside to having it like that, and no SEO downside to treating it the same as for logged in users, but with a nofollow.

The most likely reason is less bot visits (crawlers) due to the SEO related changes.

That sounds like a really bad idea from a UX perspective. I can only assume it's for SEO, but there's no need to sacrifice ux for that, whats wrong with just nofollowing those links?

Yes, the same here.

How many more times are we going to see this sort of thread on here before Invision sort out the renewal of certificates for their cloud clients, it can't be that complicated, surely?

I'm using chrome on windows 10 and chrome on chromeos.

I've never received one from here either.

It doesn't happen on the stock theme for me, I suspect it's because you have the Make Tutorial link there as well which is forcing it to overflow. Maybe create an icon for the bookmark link and edit that into the template?

I don't know if this is still the case, but these used to default to 'all time', reducing that to a few weeks or months should really speed it up.

It would make sense, but ips management aren't fans of cloudflare, so... https://invisioncommunity.com/forums/topic/435988-cloudflare-security-leak/?do=findComment&comment=2679551

@Michael.J is there any chance of you updating the listing in the marketplace so we can get this for 4.6 at all please?

I think you're maybe being a little unfair to Invision here. It seems like most plugins get reviewed much more quickly than that, and without knowing when those 'late' ones were uploaded and whether they have been rejected or not makes it impossible to judge. The bookmarks example is a prime one - the author has said they would upload a new version after their previous one was rejected, but since they haven't confirmed when they did (if they have), or responded in the support thread for a few weeks since, it's maybe unreasonable to pass judgement on the situation and place blame on Invision.

I've seen this happen recently as well.

Any updates on this please @Fosters?

I don't think you can expect a developer to worry about a glitch in a beta version of a browser.

I'm not as I don't have it as yet, but it doesn't allow you to buy it through the marketplace for 4.6 at the moment, as it's not marked as compatible.

We've had this sort of thing happen before, and found that switching off template disk caching in ACP>System>Settings>Advanced configuration solved it.

Hi @Michael.J - are you planning to release this for 4.6?

I really feel like there are four issues at play in all of this. The price rise Personally, this is the one which, although I can understand the issues it's causing for some, is in my opinion, the least controversial of all that's gone on over the last few days. Things get more expensive, the product is very different to what it was since the last increase in price, and so personally I have no problem with it. As long it goes hand in hand with a discernible and ongoing improvement in the quality of the product. There's work to be doing, rough edges to smooth and features which need adding. I do see why this may cause people to move away from Invision though - everything has its price and there are (and always have been) cheaper (and even free) alternatives. The support change On the face of it, this looks terrible. But in a way it's all in the telling as it's not really a big change, assuming it works as Invision are saying - eg things that need a ticket will end up in one. For me it's one of those that needs to be given a chance to see if it works as advertised or not - if it ends up being poor then it'll need addressing/reverting to tickets urgently. Communication This leans into everything else really. Had the price rise been communicated in advance, then that may have mitigated a lot of the upset it's caused. If the support changes had been communicated more clearly, that would also have stopped so many people assuming various different versions of what it is that Invision are apparently planning to do. It's an ongoing weak point with Invision in my view. There's no doubt that Invision make us feel less valued as paying customers than anyone else we spend our money with, sadly. Does Invision care? This is often about communication and the perception that it gives. I mean how many times can you screw it up so royally that you leave your customers confused or angry or both? With Invision it's frequent, it's frustrating and it's entirely avoidable. If you refuse to learn, refuse to take it seriously and don't change the way you do things after so many years and so many occasions, why should your paying customers keep giving you the benefit of the doubt? It's not enough to say you care as you're picking up the pieces of another mess, or arriving back onto the scene of another feature left on the shelf for months with zero communication (think mobile app, as one example). You need to show you care, and you need to step up and own the problems that are of your own making by showing some flexibility. EG - maybe look at a longer period of 6 month invoicing for existing customers who request it, offer a discount code for those with renewals within 3 months or something - just do something, anything to show it's not all pr style fake 'regret' just to play for time until everyone calms down or gives up. It's very little effort on your side in the great scheme of things, but could make a massive difference to the customers you're doing it for. Oh, and finally (long post, sorry), look after your third party developers - you need them, so show some gratitude and a spirit of partnership by working with them.

Apologies, I did misread your reply, so my reply makes no sense.

Edit: Was talking rubbish.

Wow. I didn't know that. I thought the switch to community support was all about offering better support and a 'live knowledge base'. So, if it's a better way to go, why limit it to self-hosted customers? Those poor cic customers will be missing out, surely?