Stuart Silvester

This is the difference between 4.7.7 and 4.7.8. The amount of white space (as noted, defined by the author post information) is exactly the same. The post tools being in the exact same place regardless of the post length is a good change.

This is the difference between 4.7.7 and 4.7.8. The amount of white space (as noted, defined by the author post information) is exactly the same. The post tools being in the exact same place regardless of the post length is a good change.

This is the difference between 4.7.7 and 4.7.8. The amount of white space (as noted, defined by the author post information) is exactly the same. The post tools being in the exact same place regardless of the post length is a good change.

This is the difference between 4.7.7 and 4.7.8. The amount of white space (as noted, defined by the author post information) is exactly the same. The post tools being in the exact same place regardless of the post length is a good change.

As @ThunderBlue noted, you will need to manually upgrade to work around this issue. You can continue to use the automatic update after this.
https://invisioncommunity.com/4guides/advanced-options/server-management/install-and-upgrade-r259/#manualupgrade
 

I just wanted to clarify the NGINX 'issue' (although this would apply to any server/proxy/CDN setup that doesn't pass the required header).
You will need to make sure that the HTTP Authorization header is passed through to PHP. Making that header available will enable Zapier to communicate with your community. You'll also need to do this if you want to use other features that use HTTP authentication such as the REST API.

And they are working!
Only thing is, you don't have badges on the app icon, even though they are enabled?

Did you read his post? Specifically where he wrote that he tried disabling the mentioned application?
Upgrading to 4.7.8 or newer will most likely fix this for you, as one of the calls in the stack trace have been remove. It's related to storing the members current timezone in the database.

It looks like your SSL certificate/server may only allow TLS 1.3, also allowing TLS 1.2 will address this issue. Note that TLS 1.2 is still widely supported across the internet and still required for some services and older browsers.
https://developers.cloudflare.com/ssl/edge-certificates/additional-options/minimum-tls/

I can assure you that we do not have physical drives or servers.

You should be set if you sign out and back in again.

Yes, you can translate the language string. Search for "whosViewing" for the relevant strings.
 
 

Yes, you can translate the language string. Search for "whosViewing" for the relevant strings.
 
 

I wouldn't expect so, we don't have any plans right now to allow SVG upload on the front-end. If there was complete control over the hosting environment (which there isn't with the classic option) it wouldn't be so much of a security risk.

You have something called pro-managed protection blocking the requests we were sending to your server.
Error text: Host: <host> Request: /cookies.html?cdata=8ec7ab5fdd2ece6fb2053d0814614cb6&backurl=https://f<host>/index.php?app=core&module=system&controller=marketplace&pmtry=3 HTTPS: on Protocol: HTTP/1.1 User IP: <ip> Browser: InvisionCommunity/1.0 Referer: Timemark: 1679200791 ErrorCode: 405 ClusterNodeID: M-26  
Your issue is something different that we're looking in to, we'll update your ticket when we have further information.

You can find information about this change here: 
 

You should probably ask whoever writes that software, that is not an Invision Community table structure.

You should probably ask whoever writes that software, that is not an Invision Community table structure.

You must have the old path hard coded in a constants.php file.
On that page you made a screenshot of, the next thing down is a text input for the proper location of the datastore folder. Correct it and click save. It'll give you a new constants.php to upload

Just going to point it out, but irrelevant to the actual question.

PHP 8.2 isn't supported by Invision yet.

It looks like this is something your server administrator has set up to block ZIP/archives that have Java script files in them. See https://sanesecurity.com/foxhole-databases/ - The virus error message is a bit mis-leading, but it's how the database flags the file for ClamAV to reject.
I also want to post a reminder than developer tools should never be used on a live or publicly accessible website.

It looks like this is something your server administrator has set up to block ZIP/archives that have Java script files in them. See https://sanesecurity.com/foxhole-databases/ - The virus error message is a bit mis-leading, but it's how the database flags the file for ClamAV to reject.
I also want to post a reminder than developer tools should never be used on a live or publicly accessible website.

It looks like this is something your server administrator has set up to block ZIP/archives that have Java script files in them. See https://sanesecurity.com/foxhole-databases/ - The virus error message is a bit mis-leading, but it's how the database flags the file for ClamAV to reject.
I also want to post a reminder than developer tools should never be used on a live or publicly accessible website.

Fixed, they can no longer post in Marketplace topics.

@Stuart Silvester
Users from Friends group can post in support topics now?
The user above is in Friends group and obviously didn’t purchase this resource. 
Thank you.