Marc

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.

Please disable 2 factor authentication on your account. I notice you have another topic open, and these both seem very much related. I think this is simply a language pack that is disabled

It doesnt contradict this, no. What it looks like happened is you have the names set on another language pack. Are you running more than one pack?

This is incorrect. The link itself was posted by the user. What has not happened is that the user has likely not intentionally posted a ukraine image. It is a link to an image on an external site, which means that external site has control over what image it is.

Based on the document you have mentioned there, its actually an experimental feature just in edge

I have tagged our developers who are better placed to be able to answer the question for you there. Someone will be in contact as soon as possible

Unfortunately that may well be the case. While I understand its affecting all your applications, we are unable to tell you how you can fix those items without disabling them to readd things, as we simply didn't write those applications so wouldn't really know. While I'm very sympathetic to the issue you have there, its simply not something we are able to fix even if we wanted to. Why is it you are unable to disable, out of interest? I know why you dont want to uninstall, as that would lose data, but its not clear why you would not disable? Did you do the manual upgrade route?

Having looked at this on your site, I would suggest first of all reverting these changes. It appears you are using an alternative solution to S3 with the S3 storage handler. This is something which of course would not have been tested by Invision as it's not something we officially support. This is very likely why you are having issues. In addition to that, it seems there is a modified file on your system, and that file is the storage handler file There are quite a few other issues there such as not using INNODB, not yet being on UTF8MB4 which are likely not related. However your system is also not running the latest version, which also may cause you issues. There are repeating system log errors relating to CURL on search, but between these there are also timeouts on curl related to backblaze, which is likely why you had issues initially

I'm very sorry to hear you feel that way, as that is certainly not our intention. You asked how to do something that there is simply not a way in which to do, other than changing the location of each and letting it move them, which is what was stated above. So as far as what you have asked here, we have answered. It does need to be noted here, we would not manage your site on your behalf, and this has never been the case. This is no different here to what it would be within a ticket. You have mentioned here you moved to S3, but the files have not been moved, and also asked what files. The answer to the question there is if you have moved all locations to S3, you would move all files in your uploads directory. There is nothing you would exclude there. If you are moving individual items in the list, you are going to need to move them first to another location on disk (so that you then know what files), then move them to S3. There is no other way in which you can determine which files are which.

Please could you provide me with a link to an item which is broken? I can then get a ticket created and that escalated

Yes, that is correct. The quick search is a content search. In order to search members you would like the search icon without entering anything to get to the advanced search, then click to search members

Sorry, it appears your topic was missed there. Do you have a link to the blog item so I can take a look for you?

Yes you have details, but those access details do not have access to your site files. They cannot access the path you have added there

No problem at all. Glad you managed to get to the bottom of it regardless