Deprecation Tracker

The ability to use a display name as a log in is deprecated and will be removed. Using an email address as part of the log in process is more secure than using a publicly visible display name.

Earlier versions of Invision Community allowed a simple way to promote content to Facebook and Twitter. We have since removed Facebook due to their increasingly stringent policies and reviews on posting programatically. Recently, Twitter have announced new paid API tiers starting from $100/month. While a limited free tier remains, we feel that it is likely that the free tier will be further reduced or removed making this tool redundant. We have chosen to remove it, but will retain the

We are removing support for plugins and instead you should use the applications system. Applications are more flexible than plugins and easier to manage. Any existing plugins can easily be ported to applications and we encourage third-parties to start the process as soon as possible.

The friendly URL (FURL) system is highly recommended currently and will be required in Invision Community 5. All Cloud clients automatically have FURLs enabled automatically so there is no change for those communities.

The profile status updates system is a holdover from decades ago and will be removed in Invision Community 5.

Our new Solved option in forums is replacing the old Questions and Answer forum mode. The current Q&A mode is very limited and "breaks" conversation flow as it is not displayed in a normal order. Most clients have found the new Solved feature sees way more engagement from the community. We will continue to enhance the Solved feature and related support and customer service functions.

This is legacy code for when some self-hosting servers did not come installed with curl. Curl will now be required.

With the release of Invision Community 5, we will begin the process of stopping support for Invision Community 4. This will of course be a long process and we will still provide support and security updates for Invision Community 4 until final end of life.

Braintree, Authorize.net, and 2Checkout are no longer supported but will remain in the platform for now. These legacy payment gateways will no longer be supported and removed in a future release. We recommend you plan a migration to PayPal or Stripe. Note any custom third-party gateways are unaffected.

We want Commerce to be a solution to monetising multiple areas of your community with micro-payments and subscriptions. Our focus will be on that area and physical product sales have now been deprecated and are much better handled by specialist services such as Shopify. We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating physical product data to another service.

When we built our first version of Commerce, very few support desk systems were available. The support desk you have in Commerce today results from our need for a ticket system we could use. Now, there are many email support desk solutions that are a significant improvement on what Commerce offers. Therefore, as we start to shape Commerce into its new form as a robust and feature-rich community commerce tool, we made the decision to deprecate the support desk feature so we can use those resource

This is a legacy way to cache pages for efficiency. Our platform can now be used with a CDN for guest page serving.

PHP 7 is now end of life from the developer and will no longer receive updates or security fixes. As such, we will require PHP 8.

Birthdays will no longer show in the calendar app, but remain optionally visible on member profiles. This is a legacy feature which adds considerable noise to calendar displays.

Facebook Promotional Tools have been removed. Facebook no longer allows API posting to groups and pages.   No action is required. 

VigLink has been removed. VigLink API is no longer working as intended.   No action is required. 

The hosting reselling tools have been removed following their deprecation in September 2020.