Stuart Silvester

Thank you for letting us know, this should be fixed in an upcoming release.

Thank you for letting us know, this should be fixed in an upcoming release.

Thank you for letting us know, this should be fixed in an upcoming release.

CSS files in Pages aren't tied to any specific theme, the CSS file you create is the same across any theme that is used on your community. It simply isn't possible to use those plugins.

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

Thank you, we've made a small adjustment for this to be included in a future release.

Thanks for your feedback, I have generated an internal report for this. However, since it's really a very low priority issue I cannot guarantee if and when we would make any changes.

Thank you for letting us know, a fix for this issue is pending review and should be included in a future release.

That's coming from Google Charts.

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

Custom emoji (emoticons) should contain dimensions, providing that the are populated in the database (see core_emoticons). I suspect you may have some values missing, maybe they're really old emoticons.

You can get the 'all activity' stream as an RSS feed for consumption. Click stream options in the top right when you're on that page.
The REST API doesn't have any activity stream abilities at this time. - It does have the ability to search though which could return useful results.

Thanks, this will be fixed in the next beta.

@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.

Your community is configured to not allow remote images. AdminCP > System > Settings > Posting > Allow remote images?
When you edit the post, the remote images are changed to an URL to comply with this configuration.

The key in Postman for the POST parameter would be
fields[22]
And then specify your value
 
 

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
 

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.

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.

Thank you for bringing this issue to our attention! I can confirm that this was a bug and it has been addressed for a future maintenance 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.

This issue was due to the original image files (that we use to generate thumbnails) being missing from the storage location. These were able to be restored from an old backup and regenerating the thumbnails again fixed the issue. We've also added a check to the process for a future release to make sure the original image exists before removing the existing thumbnails.

Hi,
We're seeing an SSL error when trying to connect to your community, this is due to your server not supporting TLS 1.2 (it only supports TLS 1.3). Typically, servers should support a minimum of TLS 1.2 in addition to TLS 1.3 for maximum compatibility (older consumer devices may not be able to access your community either).
Your server administrator should be able to assist with this if you're not quite sure what it means.

The Instagram embeds now appear to be functioning correctly. A number of customers reported the same thing but the embeds were still loading in the software. This appears to have been an issue on Instagram.

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