Deprecated and phasing out features
- Print
- DarkLight
- PDF
Deprecated and phasing out features
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This document outlines features that are no longer supported in Rocket.Chat or are scheduled for removal in future updates (deprecated). It also serves as an early notice for workspace managers to adjust and optimize their workspaces accordingly. Please note that this information is subject to change with future releases and may not include every deprecated feature.
Breaking changes in upcoming versions
Rocket.Chat Server v7.0.0
Platform and database enhancements
We have upgraded the platform to Meteor 3.0 and Node.js 20, bringing in the latest security improvements, bug fixes, and performance optimizations. However, this update may require environmental adjustments, especially if your application relies on older Node.js features or Meteor packages. Developers should review their environment and ensure all dependencies are compatible with these new versions.
With MongoDB 4.4 reaching end-of-life, we have discontinued its support in favor of MongoDB 7.0. The new version offers enhanced performance, security improvements, and new features like support for multi-document ACID transactions. If you're still using MongoDB 4.4, an upgrade is necessary to maintain compatibility with our platform. It’s important to test your database migration thoroughly to avoid potential data or performance issues.
Security and compliance updates:
Enhanced security for app installations: Starting with this release, the ability to upload private apps is now restricted to our premium plans (Starter, Pro, and Enterprise). This change helps us maintain the integrity of Rocket.Chat's customization options while safeguarding the exclusive features of our paid plans. By limiting private app uploads, we ensure that only licensed users can fully tailor their experience, protecting the value and security of our platform.
The ability to install apps from a URL will be removed.
Additional settings and permissions removal: Unused settings such as
UI_Click_Direct_Messageand theview-historypermission have been removed to comply with security best practices and reduce clutter.
Permissions and endpoint enhancements:
New permissions for room management in teams: New permissions (
create-team-channelandcreate-team-group) have been added to enhance control over room creation within teams. These permissions integrate closely with team management functions and ensure proper visibility and control.Improved error messaging for login attempts: The login process will no longer suggest which credential is incorrect, returning a generic "Unauthorized" error instead to enhance security.
Room sync overhaul: LDAP Teams Sync and Channels Sync have been merged into a unified Room Sync section. This restructuring optimizes LDAP synchronization and removes redundant settings, enhancing overall performance.
Omnichannel and integration adjustments:
Fixes for stuck omnichannel rooms: A migration will correct the statuses of inquiries linked to rooms that are closed but still listed as active due to systemic issues.
Removed dependencies: The dependency on the
meteor/checkpackage has been removed from all v1 endpoints to avoid errors and enhance performance.
Air-gapped workspace restrictions for commercial licensing
Starting with this release, if you're running Rocket.Chat in an air-gapped environment, you'll need a commercial license. Since our standard build includes commercial code, we need to ensure compliance with our licensing agreements. Only premium plan users can operate in these isolated setups to keep things secure and above board.
Removal of deprecated features
Several outdated features have been removed to streamline the codebase and improve overall system performance:
HipChat importer removed: Due to the discontinuation of HipChat, the HipChat importer is no longer supported. If you’re still migrating from HipChat, consider using alternative import methods or manually migrating your data.
Unused oauth settings removed: We’ve pruned unused and outdated OAuth settings to simplify the configuration process. If your system still relies on these deprecated settings, update your configurations to avoid potential authentication issues.
API endpoint replacements and removals: The following older API methods and endpoints have been deprecated in favor of newer, more efficient ones.
Method/Endpoint | Replacement | Deprecated Since | Removed in Version |
|---|---|---|---|
Replaced by rooms.delete endpoint | 5.4.0 | 7.0.0 | |
Replaced by rooms.nameExists endpoint | 5.1.0 | 7.0.0 | |
insertOrUpdateUser | Users upsert no longer allowed; method to be completely removed | 6.7.0 | 8.0.0 |
Replaced by chat.delete endpoint | 6.2.0 | 7.0.0 | |
Replaced by users.checkUsernameAvailability endpoint | 5.4.0 | 7.0.0 | |
Replaced by emoji-custom.list endpoint | 5.4.3 | 7.0.0 | |
refreshClients | Now triggered by assets.setAsset and assets.unsetAsset | 5.4.0 | 7.0.0 |
removeWebdavAccount | Replaced by webdav.removeWebdavAccount endpoint | 5.1.0 | 7.0.0 |
Mailer:unsubscribe | Replaced by mailer.unsubscribe endpoint | 5.4.0 | 7.0.0 |
Mailer.sendMail | Replaced by mailer endpoint | 5.4.0 | 7.0.0 |
reportMessage | Replaced by chat.reportMessage endpoint | 6.2.0 | 7.0.0 |
getPasswordPolicy | Replaced by pw.getPolicy endpoint | 5.1.0 | 7.0.0 |
livechat:addAgent | Replaced by livechat/users/agent (POST) endpoint | 5.2.0 | 7.0.0 |
livechat:addManager | Replaced by livechat/users/manager (POST) endpoint | 5.2.0 | 7.0.0 |
livechat:getCustomFields | Replaced by livechat/custom-fields endpoint | 5.2.0 | 7.0.0 |
livechat:getNextAgent | Replaced by livechat/agent.next/:token endpoint | 5.2.0 | 7.0.0 |
livechat:loadHistory | Replaced by livechat/messages.history/:rid endpoint | 5.2.0 | 7.0.0 |
livechat:loginByToken | Replaced by livechat/visitor/:token endpoint | 5.2.0 | 7.0.0 |
livechat:pageVisited | Replaced by livechat/page.visited endpoint | 5.2.0 | 7.0.0 |
Replaced by livechat/visitor endpoint | 5.2.0 | 7.0.0 | |
livechat:removeAgent | Replaced by livechat/users/agent/:_id endpoint | 5.2.0 | 7.0.0 |
livechat:removeDepartment | Replaced by livechat/department/:_id endpoint | 5.2.0 | 7.0.0 |
livechat:removeManager | Replaced by livechat/users/manager/:_id endpoint | 5.2.0 | 7.0.0 |
livechat:saveDepartmentAgents | Replaced by livechat/department/:_id/agents endpoint | 5.2.0 | 7.0.0 |
livechat:saveSurveyFeedback | Replaced by livechat/room.survey endpoint | 5.2.0 | 7.0.0 |
livechat:searchAgent | Replaced by livechat/users/agent/:_id endpoint | 5.2.0 | 7.0.0 |
Replaced by livechat/offline.message endpoint | 5.2.0 | 7.0.0 | |
livechat:setCustomField | Replaced by livechat/visitor endpoint | 5.2.0 | 7.0.0 |
livechat:setDepartmentForVisitor | Replaced by livechat/visitor endpoint | 5.2.0 | 7.0.0 |
livechat:discardTranscript | Replaced by livechat/transcript/:rid (DELETE) endpoint | 6.4.0 | 7.0.0 |
livechat:getAgentOverviewData | Replaced by livechat/analytics/agent-overview endpoint | 6.4.0 | 7.0.0 |
livechat:getAnalyticsOverviewData | Replaced by livechat/analytics/overview endpoint | 6.4.0 | 7.0.0 |
livechat:removeTrigger | Replaced by livechat/triggers/:_id (DELETE) endpoint | 6.5.0 | 7.0.0 |
livechat:requestTranscript | Replaced by livechat/transcript/:rid endpoint | 6.4.0 | 7.0.0 |
livechat:saveAppearance | Replaced by livechat/appearance endpoint | 6.4.0 | 7.0.0 |
livechat:saveInfo | Replaced by livechat/room.saveInfo endpoint | 5.3.0 | 7.0.0 |
livechat:saveIntegration | Replaced by omnichannel/integrations (POST) endpoint | 6.2.0 | 7.0.0 |
livechat:saveTrigger | Replaced by livechat/triggers endpoint | 6.4.0 | 7.0.0 |
livechat:webhookTest | Replaced by livechat/webhook.test endpoint | 5.4.0 | 7.0.0 |
livechat:getAgentData | Replaced by livechat/agent.info/:rid/:token endpoint | 6.4.0 | 7.0.0 |
addOauthApp | Replaced by oauth-apps.create endpoint | 6.2.0 | 7.0.0 |
pw.getPolicyReset | Replaced by pw.getPolicy endpoint | 6.3.0 | 7.0.0 |
licenses.get | Replaced by licenses.info endpoint | 6.5.0 | 7.0.0 |
licenses.isEnterprise | Replaced by licenses.info endpoint | 6.5.0 | 7.0.0 |
channels.images | Replaced by rooms.images endpoint | 6.8.0 | 7.0.0 |
livechat/room.transfer | Replaced by licenses/room.forward endpoint | 5.2.0 | 7.0.0 |
livechat/inquiries.queued | Replaced by livechat/inquiries.queuedForUser endpoint | 5.4.1 | 7.0.0 |
The following parameters have been removed and replaced.
Type | Name | Parameter affected | Description | Deprecated Since | Planned to be removed in |
|---|---|---|---|---|---|
Endpoint | ALL ENDPOINTS | Removed to avoid malicious queries. Check alternatives for each endpoint. | 5.0.0 | 7.0.0 | |
Endpoint | ALL ENDPOINTS | query | Removed to avoid malicious queries. Check alternatives for each endpoint. | 5.0.0 | 7.0.0 |
Method | authorization:removeUserFromRole | roleId | This parameter will no longer be interpreted as the role name as a fallback (use id instead). | 4.6.0 | 7.0.0 |
Method | authorization:deleteRole | roleId | This parameter will no longer be interpreted as the role name as a fallback (use id instead). | 4.6.0 | 7.0.0 |
Method | authorization:addUserToRole | roleId | This parameter will no longer be interpreted as the role name as a fallback (use id instead). | 4.6.0 | 7.0.0 |
Method | apps (POST) | downloadOnly | This parameter will no longer be accepted. | 6.6.0 | 7.0.0 |
Endpoint | role | This parameter will no longer be interpreted as the role name as a fallback (use id instead). | 4.6.0 | 7.0.0 | |
Endpoint | appId | This parameter will no longer be accepted (use clientId or _id instead). | 6.0.0 | 7.0.0 | |
Endpoint | roleName | This parameter will no longer be accepted (use roleId instead). | 4.6.0 | 7.0.0 | |
Endpoint | roleName | This parameter will no longer be accepted (use roleId instead). | 4.6.0 | 7.0.0 |
This update is critical for maintaining the operational integrity, security, and efficiency of Rocket.Chat workspaces. Workspace managers should review these changes carefully and begin preparations for a smooth transition to version 7.0.0.
For more detailed information, check out our GitHub release page.
Was this article helpful?