Stuart Silvester

We've overhauled how this works in 4.7 to make it much more user friendly. If you're happy to use a beta, you can install it by visiting the Client area , clicking into your license and then click the beta link in the top right. This page will give you an overview of how the beta process works and what you can expect. Alternatively, you can wait for general availability of the new version.

It was a code fix, specifically it was related to the use of Pages when using the external dispatcher. The fix will be included in an upcoming release.

@Randy Calvert's overview is on the money. I would like to add an extra point though. If you think you've got a security concern, please let us know privately (this can be via HackerOne or our contact form). Please do not post it publicly.

We expect Marketplace resources to be compatible with the same versions that the version of the software it is for is compatible with. There have been a few exceptions to this ( I'm thinking of something @CodingJungle wrote ) where the PHP requirements were clearly stated in the description.

We'll doubly make sure we look at it then 👍🏻

I would consider that a bug, we address this in other areas where there's only one possible node. I have created an internal report for this.

Thanks! We'll have this corrected in a future release.

It can depend on which part of the development process we're in when these items are posted (they're extracted directly from the change log that we post with each release). In a normal minor release (4.x.X) when we release the first beta, the version becomes 'locked'. From that point on we'll only include either really important fixes or fixes for issues that may have been introduced by the beta release. In short, if we're in the beta process, the list included in these types of topics would largely (but not exclusively) be for the following months update. If it's listed here, it's something that has been fixed and will be in a near future release. You should watch the release notes however for the definite list of what's included in each update. https://invisioncommunity.com/release-notes/

It's possible that you're using a different PHP version/install on command line to the web server. It would be worth checking that /usr/bin/php is the right executable.

We've fixed this issue for an upcoming release.

It's also worth noting that the service worker registration failure in Firefox is normal, as it suggests in the message. Firefox doesn't support service workers when using Private Mode browsing.

I have created a support ticket so we can look further into this for you.

Yes, that's right. Having the limits set too high can be counter productive. Take your PHP info values for example, you're saying that the upload process can send you a 5120M file, but PHP only has 360 seconds (maybe less than this if you use FastCGI) and 768M of memory to process it. Changing your 5120M values back to around 8M should be fine and allow chunking to work properly.

Default values are used if the member hasn't set their preference for the notification type. It's fixed in 4.7 so you don't really need to do anything 🙂

Hi Aris, Community pages (including RSS) can be cached by edge-caches, especially if the request is being made as a 'guest'. The difference is that you're likely logged in with your member account when you're looking at the RSS feed in your browser. The delay shouldn't be too long, but you can cachebust the URL by adding your own randomised parameter i.e. ?cb=timestimp

You'll need to convert the tab-separated values to CSV, you should be able to do this in Excel. I have committed a change for an upcoming version to output a CSV to be consistent with the import. -- It was changed about 4 years ago due to some character corruption issues when using non-ASCII characters but I've implemented an alternative fix for that issue.

Marketplace views are cached, it has just been approved about 50 minutes ago. You'll see it show up soon.

I appreciate it may be too late now, but if you've still got a copy of that database can you export core_log to an SQL file and send it to me via PM?

It looks like you have some old files present from a previous beta that no longer exist. Which versions are you upgrading from and to? You should be able to delete applications/core/setup/upg_107002/queries.json from your server and then continue the upgrade.

Do you have any upgrade related errors in the core_log table? Your error suggests that code ran more than once which shouldn't be possible.

Thank for your follow-up via ticket @AlexWebsites. We've got some fixes for this issue coming in the next 4.7 beta.

Thank you for your report, I have created an internal report for this so we can look into it.

Thank you for your report, this has been corrected for an upcoming release. @Colonel_mortis thanks for letting me know about Comby, looks like a much nicer solution than writing regex to search and replace.

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

Thank you for letting us know, I can confirm that this is a bug in Invision Community and a fix for this issue will be included in an upcoming release.