docs/main/product-overview/deprecated-features.mdx
This page describes features that are removed from support for Mattermost, or will be removed in a future update (deprecated), and provides early notice about future changes that might affect your use of Mattermost. This information is subject to change with future releases, and might not include each deprecated feature.
atmos/camo will no longer be supported as an image proxy. The atmos/camo project has been archived and is no longer maintained. If ImageProxySettings.ImageProxyType is set to atmos/camo, the server will log a configuration error on startup and fail to start; the RemoteImageProxyURL and RemoteImageProxyOptions settings are also removed and will be ignored. Admins should switch to the built-in local image proxy (set ImageProxySettings.ImageProxyType to local) or disable image proxying entirely (ImageProxySettings.Enable set to false) before upgrading. The local proxy requires no external service and includes SVG content blocking and security response headers. See the forum post for full details and migration options.GitLab SSO has been deprecated from Team Edition. Deployments using GitLab SSO can remain on v10.11 ESR (with 12 months of security updates) while transitioning to our new free offering Mattermost Entry, or can explore commercial/nonprofit options. See more details in this forum post.
The TeamSettings.ExperimentalViewArchivedChannels setting has been deprecated. Archived channels will always be accessible, subject to normal channel membership. The server will fail to start if this setting is set to false. To deny access to archived channels, mark them as private and remove affected channel members. See more details in this forum post.
Playbooks has stopped working for Team Edition. Entry, Professional, Enterprise, and Enterprise Advanced plans are automatically upgraded to Playbooks v2 with no expected downtime. See more details in this forum post.
Experimental Bleve Search functionality has been retired. If Bleve is enabled, search will not work until DisableDatabaseSearch is set to false. See more details in this forum post.
Support for MySQL has ended. Our Migration Guide outlines the steps, tools and support available for migrating to PostgreSQL. See more details in this forum post.
The registerPostDropdownMenuComponent hook in the web app’s plugin API has been removed in favour of registerPostDropdownMenuAction. See more details in this forum post.
The web app is no longer exposing the Styled Components dependency for use by web app plugins. See more details in this forum post.
Omnibus support has been deprecated. The last mattermost-omnibus release was v10.12. See more details in this forum post.
Deprecated include_removed_members option in api/v4/ldap/sync has been removed. Admins can use the LDAP setting ReAddRemovedMembers.
Customers that have the NPS plugin enabled can remove it as it no longer sends the feedback over through telemetry.
Format query parameter requirement in the /api/v4/config/client endpoint has been deprecated.
Removed deprecated mmctl commands and flags:
channel add - use channel users addchannel remove - use channel users removechannel restore - use channel unarchivechannel make-private - use channel modify --privatecommand delete - use command archivepermissions show - use permissions role showmmctl user email - use mmctl user edit emailmmctl user username - use mmctl user edit usernameExperimental certificate-based authentication feature has been removed. ExperimentalSettings.ClientSideCertEnable must be false to start the server.
Added logic to migrate the password hashing method from bcrypt to PBKDF2. The migration will happen progressively, migrating the password of a user as soon as they enter it; e.g. when logging in or when double-checking their password for any sensitive action. There is an edge case where users might get locked out of their account: if a server upgrades to v11 and user A logs in (i.e., they need to enter their password), and then the server downgrades to v10.12 or previous, user A will no longer be able to log in. In this case, admins will need to manually reset the password of such users, through the system console or through the mmctl user reset-password [users] command. The new password hashing method is more CPU-intensive. Admins of servers with password-based login should monitor the performance on periods where many users log in at the same time.
/api/v4/teams/{team_id}/channels/search_archived has been deprecated in favour of /api/v4/channels/search with the deleted parameter.
Separate notification log file has been deprecated. If admins want to continue using a separate log file for notification logs, they can use the AdvancedLoggingJSON configuration. An example configuration to use is:
{
"LogSettings": {
"AdvancedLoggingJSON": {
"notifications_file": {
"type": "file",
"format": "json",
"levels": [
{"id": 300, "name": "NotificationError"},
{"id": 301, "name": "NotificationWarn"},
{"id": 302, "name": "NotificationInfo"},
{"id": 303, "name": "NotificationDebug"},
{"id": 304, "name": "NotificationTrace"}
],
"options": {
"filename": "notifications.log",
"max_size": 100,
"max_age": 0,
"max_backups": 0,
"compress": true
},
"maxqueuesize": 1000
}
}
}
}
/api/v4/image endpoint when the image proxy is disabled.Config.ProductSettings, LdapSettings.Trace, and AdvancedLoggingConfig configuration fields.pageSize query parameter from most API endpoints.ExperimentalSettings.PatchPluginsReactDOM. If this setting was previously enabled, confirm that:
PermissionUseSlashCommands.model.CommandArgs.Session.AdvancedLoggingConfig fields, and replaced them with AdvancedLoggingJSON fields which accept inline JSON or a filename.platform binary renamed to mattermost for a clearer install and upgrade experience. All command line tools, including the bulk loading tool and developer tools, also renamed from platform to mattermost.config.json setting to whitelist types of protocols for auto-linking added.config.json setting to disable the permanent APIv4 delete team parameter added. The setting is off by default for all new and existing installs, except those deployed on GitLab Omnibus. A System Admin can enable the API v4 endpoint from the config.json file.config.json