stoo2000

I replied to your PM, but for anyone else reading this. The account creation is being blocked by the Spam Defense service -

I haven't had any reports of either things being an issue. Bouncer doesn't really run any complex database queries so I'm not sure why you would be seeing an issue like high CPU usage. Please create a ticket here: https://ipb.silvesterwebdesigns.com/support (you will need to register if you haven't already). Make sure you include as much information about the issue as possible and provide an FTP/AdminCP login.

Notifications can only be linked to one place and that's the feedback that has been left.

If you're using v1.2.3 you won't have any issues with upgrading. --The only issue may be if you use PHP 8 and v1.2.2 or earlier (but that would already be an issue, it isn't specific to 4.7) Yes, there will be! If you use v1.2.3 you won't have any PHP 8 compatibility issues anyway.

I'm really confused why this topic even exists since we've talked via PM before this.

The update for this has just gone out!

The current version will still be functional, the new version isn't quite ready yet unfortunately. I have sent you a PM about your renewal. Thanks Stuart

It seems fine in my testing, PHP 8 compatibiity is the biggest issue in 3rd party resources and those issues were addressed in a previous release. There is a small update coming however where I'll set the compatibility for 4.7

It should be done this week 🙂

If your SendGrid API key is still populated in the SendGrid integration it'll still try to use it and check the web hook is configured properly - For example, you might still want to process bounces in response to a newsletter you've sent via a different platform without sending your Invision Community email via the same method. If you temporarily enable the integration and then remove the API key, it'll stop trying to use SendGrid. I will add a decay for the error messages to the next release so they'll eventually vanish.

That looks like you have a Node (may be a forum) that is assigned to a Club that no longer exists. I suspect you may see the same kind of error appear if you open the form on the front end to move a topic to another forum?

I'm a bit delayed with it due to some other things that are going on at the moment. Looking at your other topic, this SSO isn't what you're looking for. Have a look at 'option B' in the document @Randy Calvert linked you to -

It was $30 at the time. Thanks for letting me know about those links, I have updated them. Depending on your community set up, you would have to consider CDNs too. The uploaded image may already be in an edge cache with a long TTL whereby updating the source won't actually make any difference.

I had an app on the Marketplace a few years ago that integrated with kraken.io to optimize all images as they're uploaded. It wasn't popular enough for me to keep supporting it though.

It should be in the next month or two. I don't want to rush (irony is not lost on me) something that is so critical to many sites without it being well tested first.

A new version will be out soon (major rewrite and upgrade), but the current version is still compatible with 4.4/4.5/4.6 and fully supported.

Certainly, since you may need to send me credentials, please create a ticket here: https://ipb.silvesterwebdesigns.com/support (you will need to register if you haven't already).

That's a cachebust that changes each time CKEditor is built (with each Invision Community release). It makes your web browser load the image from the server again instead of using a local cache. You shouldn't however be changing any core files, whether they're JS or PHP. The right way to do this would be to make your own CKEditor theme/skin (it could be based on one of the ones shipped) but then have your customised image within that skin so it doesn't get overwritten every time you update.

It's still working and fully supported with the latest version of Invision Community. It jsut doesn't yet abide by the data storage sections of the Marketplace Guidelines so I haven't been able to update the compatibility version yet. That's where things get a bit tricky because there's a fair amount of data that needs to be moved during an upgrade without affecting the SSO functionality. An updated version is progressing well though (essentially a complete rewrite) and I should start beta testing it soon. Justin has been in touch with me and I haven't yet got a complete picture of what the issue is, but hopefully I should be able to get access soon and look further into it.

Hi Brian, Yes, my WordPresss SSO plugin can do this. I think the majority of my customers that use it also use it in combination with MemberPress. Please let me know if you have any questions.

Thanks for the mention 🙂 The 4.6 version is a complete rewrite, so it's taking a little longer than a typical update would and needs extensive testing before it's ready for release. I have replied to @Oyvind Dahl , the issue does initially look like a server issue, but I'm happy to look further.

Yes, I definately want to do this. Do you have any specific rules/triggers in mind?

The updated version is now available, thanks for your patience 🙂 That is not correct. As noted in our previous conversation about it, this was because your emails were failing to send through SES and a query Invision Community was running to update a flag on failed emails was taking a long time (due to the large number of failed emails).

Coming right up.

No, Mailbouncer does not interact with the email error logs at all. I would suspect you have a large number of emails that failed to send and the update query is taking a long time. Invision would be the best to help you with this.