Stuart Silvester

We have released a patch for this issue. To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue. To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue. To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue. To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

You'll need to convert your database to utf8mb4, in MySQL `utf8` no longer exists and is an alias for `ut8mb3` so when you're running these queries to fix the collation, MySQL is changing it to utf8mb3 instead and thus you have this loop.
In the AdminCP, go to the Support page and you should see an option for converting to UTF8MB4.

2030 at the earliest, I'd say.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

Hi,
No, we're not going to distribute other developers IP through a method they did not agree to.
If you have the app installed, you already have the files on your server. A competent developer would know where to look to get those and build whatever changes you want on top of that.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

Hi,
No, we're not going to distribute other developers IP through a method they did not agree to.
If you have the app installed, you already have the files on your server. A competent developer would know where to look to get those and build whatever changes you want on top of that.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

We have released a patch for this issue.
To apply, please go to AdminCP > Support > 1st (or top left) box will have a "Optional Patch Available" link. Click it and follow the instructions.

Give the beta a try, see if the new way we handle the icons flushes out the cache. It's unlikely we'll be making any other changes to the beta before final release.

PHP 8.2 will be fully supported in Invision Community 5.
Whilst it may work with earlier versions such as 4.7, it isn't officially supported (there may be issues) and will likely mean that developers mode is unusable..

Right, but if your Cloudfront/Cloudflare configuration said "Cache this static image for 1 year" for example; The device (iPhone) itself is going to cache that resource for a long time and not check the CDN/Website for a newer version.

If they were https:// they'd be displayed inline as expected, however that's something you would need to do prior to the conversion. At this point, fixing them manually would be your only solution.

Right, but if your Cloudfront/Cloudflare configuration said "Cache this static image for 1 year" for example; The device (iPhone) itself is going to cache that resource for a long time and not check the CDN/Website for a newer version.

If you're using a CDN with default cache-control headers for static files, it's very likely that the device itself is caching these resources. The good news is that the current beta (4.7.15) introduces cache-busting for web app icons, so that may resolve your issue after upgrading.

Hi,
By default Invision Community won't embed http:// images (note these are not vBulletin attachments but externally linked images) since they'll cause the page to show insecure warnings. In this situation the image is replaced with a link.

If you're using a CDN with default cache-control headers for static files, it's very likely that the device itself is caching these resources. The good news is that the current beta (4.7.15) introduces cache-busting for web app icons, so that may resolve your issue after upgrading.

Hi,
By default Invision Community won't embed http:// images (note these are not vBulletin attachments but externally linked images) since they'll cause the page to show insecure warnings. In this situation the image is replaced with a link.

If you're using PHP mail, do you have it specified in AdminCP > Email Settings > Additional Parameters?

It has been that way for about a decade now (since early v4 development), Signatures aren't as an important as they used to be and very often add a lot of clutter.
As a work around though; if you enable the show signatures to guests setting, that preference will be retained into a newly registered account.