Charles

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 resources to build ways to monetize and build your community.
Of course, we realise this may cause concern for the few that use it heavily, so I wanted to let you know that:
We will help anyone that uses the support desk feature to find an alternative and plan a migration.
We will create and strengthen native APIs to enable apps like Zendesk and Helpscout to access your community data for use in custom fields, etc.
We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating support data to another service.

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

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.

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.

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.

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 profile status updates system is a holdover from decades ago and will be removed in Invision Community 5.

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 resources to build ways to monetize and build your community.
Of course, we realise this may cause concern for the few that use it heavily, so I wanted to let you know that:
We will help anyone that uses the support desk feature to find an alternative and plan a migration.
We will create and strengthen native APIs to enable apps like Zendesk and Helpscout to access your community data for use in custom fields, etc.
We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating support data to another service.

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.

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 resources to build ways to monetize and build your community.
Of course, we realise this may cause concern for the few that use it heavily, so I wanted to let you know that:
We will help anyone that uses the support desk feature to find an alternative and plan a migration.
We will create and strengthen native APIs to enable apps like Zendesk and Helpscout to access your community data for use in custom fields, etc.
We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating support data to another service.

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

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.

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.

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.

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.

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 profile status updates system is a holdover from decades ago and will be removed in Invision Community 5.

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

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 resources to build ways to monetize and build your community.
Of course, we realise this may cause concern for the few that use it heavily, so I wanted to let you know that:
We will help anyone that uses the support desk feature to find an alternative and plan a migration.
We will create and strengthen native APIs to enable apps like Zendesk and Helpscout to access your community data for use in custom fields, etc.
We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating support data to another service.

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.

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 resources to build ways to monetize and build your community.
Of course, we realise this may cause concern for the few that use it heavily, so I wanted to let you know that:
We will help anyone that uses the support desk feature to find an alternative and plan a migration.
We will create and strengthen native APIs to enable apps like Zendesk and Helpscout to access your community data for use in custom fields, etc.
We will work with you to help migrate your data. Please contact us if you'd like to learn more about migrating support data to another service.

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.

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.