Matt
-
Posts
70,143 -
Joined
-
Last visited
-
Days Won
649
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Projects
Release Notes v5
Invision Community 5 Bug Tracker
Forums
Events
Store
Gallery
Everything posted by Matt
-
Why would you want to restrict some groups from downloading their PII or exercising their right to be forgotten? These are universally needed features. -
Yeah, it's been discussed a lot internally for years regarding cookie versus local storage. We do use local storage for somethings, but the downside is that it is not exposed to the PHP layer, which means you'd need to manage any preferences those settings control completely in client side scripting.
-
Hi Patrick, Thanks for sharing your concerns. The QA process is a bit like being the goal keeper in a football game (ok, soccer if you insist). You're never remembered for the dozens of saves you make, you're only remembered for the ones you let in. We have developed a robust development process where every single commit we make is peer reviewed before being committed into our repository. We then test it on a private staging site, and then we release betas for a few weeks before releasing the final version. Unfortunately, a few things have slipped through and these have been fairly complex issues which are difficult to test with a small group. Fortunately, we do have a patch system that allows us to get fixes to you almost instantly via the AdminCP. We always review internally when things go wrong, and we will do based on the information you've provided.
-
I do not think that we should be awarding points to private messages at all, so I'll discuss that with the team. Regarding the follow/unfollow - that is true but you can only do that once per content item/node. It is a design choice as we did not want to start removing points when content was deleted as it may drop people back down ranks. You can design the system to reward follow/react much less than posting, etc so anyone that wants to spend hours clicking buttons doesn't get a lot from it.
-
Yes but during 5’s lifecycle we will be removing it and using native. Any new front end functionality is mostly native.
-
From 2025 onwards, I would assume v4 will be critical fixes and security updates only. In terms of EOL, 8.0 becomes EOL in November, but I would expect that many thousands of customers would still be using 8.0, and we'd continue to use that as our lowest possible PHP version.
-
Invision Community 5 will support PHP 8.2. We've spent a few weeks really cleaning up the codebase as PHP becomes more strict about typing. It's unlikely v4 will support 8.2 as it'd need roughly the same amount of work.
-
No, but you can use the new modal view in your content items. You'll just need to drop in the template call in the relevant part of your template to add the button: {template="analyticsItemLink" app="core" group="system" params="$item"}
-
Animated GIFs button not working
Matt replied to OptimusBain's topic in Classic self-hosted technical help
We've updated the ACP UI for the next release. -
Spam is very frustrating, and we've been having discussions at what we can do about it. In the mean time, the best way to avoid spammers posting publicly is to set your default members group to require post approval until 2 pieces of content have been manually approved. (ACP > Members > Groups > Content tab) Whilst it means you'll need to approve the posts of new members, it will stop spammers from getting visible content. Remember to flag those accounts as spammers so it feeds back to our system. We do use various tools to determine spam, including various honey pot databases but it can take a short while to catch up with fresh waves. We want to put more focus into post-registration spam capturing in the near future.
-
It looks like the key that our Giphy rep set up has now been blocked, likely because of the sale. I can reach out again but I think we'll just adjust the set-up to recommend you set up your own custom key.
-
It looks like another network attack. These are very common and we have a lot of technology to deflect and mitigate it but now and again we need to scale up a bit to meet demand. This can take a minute or two and you may get very short pockets of slow loading or some 504s like you hit this morning. We are seeing an abnormal amount of blocked requests, so someone is having fun somewhere.
-
We will be improving the mobile experience in v5.
-
We can probably work on the labelling, but I'm not keen on making it a high level item like that. It's not something most people will want to think about when they are on the site.
-
No, it is not mandatory.
-
Not in this version. This is more about data privacy than a general de-activate/re-activate function. With the functionality we have, when you enact the right to be forgotten, and it has been approved, the data is altered permanently with no way to undo it.
-
For now, we'll keep it so administrators must approve until we get a little more comfortable with the features. We wouldn't want large parts of an established community destroyed by content being de-attributed or removed without a final admin check.
- 35 replies
-
- 13
-
-
-
-
You can choose to delete, or anonymise the posts (the IP addresses are removed, and the content presented as if it was from a Guest). When a member requests to be forgotten, it will anonymise their content. Cleaning embedded quoted content is something we're working on for a future version.
-
Not true. We do add a line at the end of every blog explaining which platform the feature is for. We have products and packages for every budget. You don't have to, we have the classic self hosted version. Our "cloud" platform isn't just cloud storage. It's a bespoke platform that happens to use cloud micro services. Cloud storage != Invision Community platform. It's not, we've just committed to self-hosted for Invision Community 5, now in heavy development.
-
That’s fine. We have products for every budget.
-
Classic (and cloud) discussion is very welcome in almost all areas of this community. The cloud platform and classic version share the same base code. In fact, all of our development time so far with v5 has been on things that benefit classic as well as cloud. There certainly isn't any neglect.
-
That's correct, v5 won't have a concept of stand-alone plug-ins. But there's two things to keep in mind: 1) v5 will have numerous changes to how applications are developed (significant changes to template hooks and code hooks) 2) v4 will still allow plugins, and will be supported and heavily used for at least a few more years. So moving plug-ins into applications for v4 is a waste of time unless you have a major update or other compelling reason. Just moving the code from a plug-in into an app because a different version of the software with a different set of development tools won't support plug-ins is not helping you or us. Moving v4 code based plug-ins into applications for v5 will not help, as the code will not work with v5, so right now it's a waste of time.
-
Hi all, This is just a quick post to let you know that while stand-alone plug-ins are deprecated in version 5, there is no need to convert your plugins to applications right now. There are significant changes coming to how third party templates and code interacts with the v5 framework changes which means any plug-in or application will need a lot of work for Invision Community 5. Simply converting a plug-in into an app won't future proof it, so it is a waste of your time at this point. We're in the very early stages of making these framework changes but will get information to you as soon as we have everything figured out. Also a reminder that v4 will have a multi-year deprecation, and we expect to work on both v4 and v5 for quite a while with a fairly slow migration over to v5 for the first chapter of its life, so I would think the majority of sales would still come from v4 for at least another year or so. Thanks!
-
Answered quite comprehensively here:
-
It likely got merged into one of the other topics on the subject.
