Stuart Silvester

They've posted a link that you've chosen not to allow through link filtering. - AdminCP > System > Settings > Posting > Links & Email Addresses.

They've posted a link that you've chosen not to allow through link filtering. - AdminCP > System > Settings > Posting > Links & Email Addresses.

I haven't tested with 2.x or newer, OpenSearch & Elastic Search release updates very quickly, often (previously) with breaking changes.

I believe we're using 1.2, which is the latest version AWS OpenSearch Service supports.

Thank you, this has been fixed for an upcoming release.

Thank you for letting us know, I was able to reproduce the issue. I have created an internal bug report so we can fix this for an future release.
When you only allow a single file to be uploaded, the linked field is disabled however it isn't re-enabling when you delete the uploaded file.

Thank you, this has been fixed for an upcoming release.

This issue has been fixed for 4.6.12.

I haven't tested with 2.x or newer, OpenSearch & Elastic Search release updates very quickly, often (previously) with breaking changes.

Thanks for the updates :).

I haven't tested with 2.x or newer, OpenSearch & Elastic Search release updates very quickly, often (previously) with breaking changes.

We haven't used XMLRPC since version 3.4. it's a very old thing.

Sitemaps are automatically submitted to Google when they're generated/updated. 
However, if you want it to be viewable in Google Search Console you still need to submit it for it to show up in the UI. <community_url>/sitemap.php is the correct URL to submit

That suggests there is an unexpected response from your server, likely a PHP error.
Can you check your server PHP log to see if there was anything logged at the same time as you started the upgrade?

CKEditor 4.18.0 will be included with our upcoming April release beta.
You are free to upload your own CKEditor theme if you wish to use a different one than default (the IPS CKEditor theme).

Security updates for PHP 7.4 come to an end this year, we're going to be moving to a newer version of PHP and Invision Community 4.5 will simply not work with newer PHP versions.
As noted above, it's important to keep up with security related updates and patches. We're doing our part to make sure that is happening, and you should also want to make sure you're using our latest releases to make sure that you're also up to date with any fixes.

This is a problem with your server, you will need to contact your web host/server administrator for assistance.
Your AdminCP URL is showing the actual error "Unknown storage engine 'InnoDB'"

This issue will be fixed in our upcoming 4.6.12 release.

Thank you, we've fixed this for the final release.

For lazy loading, images must have a width attribute so the page doesn't jump around whilst it's loading (this also applies when we do native lazy loading). This isn't something we're going to address at this time since it's a little involved and would require rebuilding any post with an attachment.

It looks like the template for your widget may be out of date. It's missing attributes in the source code that should be present. Although I'm also seeing search engines listed which isn't default so it may be that you're using a 3rd party enhancement that the author needs to update.

These are not errors, DEBUG_LOG will log lots of things for development purposes, including every single HTTP request the community makes (which is what this is).
You really must be careful about posting these types of logs, especially when it includes access tokens for remote services. I had edited your post to remove the sensitive information.

You're using an older version (4.6.10) that had a bug that prevents some functionality from working properly (this was patched soon after the initial release). However, in this case it means that you will need to perform a manual upgrade.
https://invisioncommunity.com/4guides/welcome/install-and-upgrade-r259/#manualupgrade
 

@OptimusBain As a follow-up, you can enable a setting to allow a 'renew' button to appear on the manage purchases page. In the product settings (Client Area Settings tab), you can enable the "allow customer to renew?" setting and optionally configure the limitations for this.
This will enable your customers to renew the product subscription after it expires.

Thank you for your report, I have committed a potential fix for this issue that should be included in a future release.