Stuart Silvester

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

This issue has been fixed, however since it was quite a central low level change it will be in the an upcoming feature release of Invision Community (Feb). 

The upload will resize the image in the end-users browser before uploading it, I would also suspect this issue is coming from their computer.
It's likely that the image doesn't need to be resized to fit within your attachment limitations, but it does to fit within the avatar size limitations.

The upload will resize the image in the end-users browser before uploading it, I would also suspect this issue is coming from their computer.
It's likely that the image doesn't need to be resized to fit within your attachment limitations, but it does to fit within the avatar size limitations.

To be clear, I'm not assigning blame; we create enough of our own bugs 🙂 but it is a working reality that a portion of our support volume is caused by code that is not ours. We have added tools to speed up the debugging but it's not always clear that a third party app/hook is the problem.
There's a lot we can do of course but our problem is just people-hours. We make a loss on the marketplace currently when you factor in battling fraud, chargebacks, as well as debugging support issues. We are OK with that, but it does mean that we do not have a lot of resources to put into it beyond what we already do. I'm also not entirely convinced there's a pool of younger newer coders who would be willing to learn our framework and develop modifications. The problem isn't so much that people are leaving the marketplace (life changes, etc), it's that there's fewer to replace them. Part of the barrier is the cost of course, and I do recognise that but also PHP isn't a "cool" language anymore. Most developers are learning javascript (node, react, etc). This is why our future efforts are in building APIs, events and triggers that JS languages can take advantage of.

From such an old version you'll need to upload the files, switch your server to PHP 8.0.x and run the upgrader from /admin/upgrade. Have a look at our guide here, specifically the 3.x section: 
 

From such an old version you'll need to upload the files, switch your server to PHP 8.0.x and run the upgrader from /admin/upgrade. Have a look at our guide here, specifically the 3.x section: 
 

You'll likely have a hard time getting it to work on anything newer than MySQL 5.5. You don't however need to be able to load the AdminCP to perform an upgrade. You can upload the new v4 files and go directly to the upgrade process.

You would need to look at the $additionalHeaders parameter to get the Reply-To value (if it exists)

Gotcha. Thanks for the insight. 

It should also have rewrites in it to allow the friendly URLs to function.
To get the right rules, go to AdminCP > System > Site Promotion > Search Engine Optimization. Click the download link in the description for the 'Rewrite URLs?' option.

Yes, that's the reason although it wasn't a forgotten temporary thing. For the majority of communities (even huge ones) they don't typically have enough members to get near the limit of MEDIUMINT and it wasn't worthwhile forcing a large number of database changes for those that wouldn't be affected. 
We've got an internal issue for this so we'll make it easier to change these columns when appropriate.
For @David.. as a temporary work around, if you find the lines in the file @teraßyte mentioned ( /system/Application/Application.php on line 2846), temporarily delete the following and then go to the support page in the AdminCP.
if ( isset( $differences['type'] ) and ( $differences['type']['is'] == 'MEDIUMINT' or $differences['type']['is'] == 'INT' ) and $differences['type']['shouldBe'] == 'BIGINT' ) { unset( $differences['type'] ); if ( isset( $differences['length'] ) ) { unset( $differences['length'] ); } if ( isset( $differences['unsigned'] ) and !$differences['unsigned']['is'] and $differences['unsigned']['shouldBe'] ) { unset( $differences['unsigned'] ); } } When you're done running the queries it presents, you can restore that file back to default. As always, it's a good idea to make sure you have a good database backup before making changes to the structure.

Thanks for the fix @Marc Stridgen / team.

HI @Dreadknux
This bug report was investigated recently and some fixes have been implemented for a future release. Since we're in a bug fix only cycle over the holidays. With this fix being a little more involved, it will be included when we restart feature releases around February at the earliest.

This is a Schrödinger's cat isn't it?

If it hasn't been published yet, how can it be viewed?

Yes, that'll be the issue. If you use PHP 7 with 4.7.4+ you will encounter errors as we use code that will only work with PHP 8

Gift cards can be redeemed at /store/redeem where the value is added to the redeemers account credit.

You're right: https://github.com/ckeditor/ckeditor4/issues/2207. Since you did the leg work on this one, you're welcome to bump that issue and let them know it's causing an issue on a current device. (let me know if you would prefer us to report it)

Adjusting the regex does allow the editor to work with that UA.

Go for it.

You're right: https://github.com/ckeditor/ckeditor4/issues/2207. Since you did the leg work on this one, you're welcome to bump that issue and let them know it's causing an issue on a current device. (let me know if you would prefer us to report it)

Adjusting the regex does allow the editor to work with that UA.

The patch for this has now been released. Please visit the support area in your admin CP if you wish to apply the fix for this problem.

We're deploying a patch tomorrow morning to address this issue. Sorry for the inconvenience!

We're deploying a patch tomorrow morning to address this issue. Sorry for the inconvenience!