Skip to content
CtrlDocsSupport Portal

CtrlShare 2.26.8.0

Released: 2026-09-08 Requires: M-Files 23.6.0.0 or later

A maintenance release that simplifies CtrlShare’s configuration to the one platform it supports — OneDrive for Business — and migrates every existing setup automatically on the first start after the upgrade. No re-authorization is needed.

Changes

Section titled “Changes”
  • Configuration reorganised by concern (configuration version 3.1). The former Drive Configurations list, with its per-entry drive type, is gone. The configuration now reads top to bottom: General, M-Files Configuration, OneDrive for Business (the Microsoft Entra app credentials and the authorization code — nothing else), Access Control (the whitelisted user groups and conditions, which are vault policy rather than connection settings), Workflow Mappings, and Localization Configurations. There is no drive type to choose any more, and the documentation no longer needs to explain one.
  • Folder check-out removed. The hidden, unused folder-level co-authoring feature and its configuration are gone. Documents are still grouped in the per-vault OneDrive folder introduced in 2.26.6.0.
  • Tidier configuration. The hidden legacy Google Drive command labels are no longer stored, and the help texts describe CtrlShare co-authoring instead of “this drive”.

Improvements

Section titled “Improvements”
  • Older CtrlShare UI bundles fail safe. CtrlShare’s user interface and server now agree on a contract version. Should an older UI bundle ever be left installed next to this server version, it shows no CtrlShare commands and raises no errors, instead of misreading a configuration it was not built for. The UI bundles shipped in this package are up to date and unaffected.
  • Safer start-up. Should CtrlShare’s configuration ever fail to load, the co-authoring guards on check-out and workflow transitions now stand aside (and say so once in the vault application log) rather than blocking every check-out in the vault.
  • Paste the whole redirect URL as the authorization code. After approving the connection, you can paste the entire URL from the browser address bar into Authorization Code — CtrlShare extracts the code=… part itself. Pasting just the code still works exactly as before.
  • Cleaner failure when OneDrive is not set up. Check Out stays hidden until the Entra credentials are entered, documents already checked out to co-authoring can still be checked in or released while credentials are missing or being rotated, and a check-out attempted before a token exists no longer leaves the document checked out in M-Files.
  • Documents whose OneDrive copy has disappeared can be released again. If the co-authoring copy was deleted in OneDrive (by an administrator, a retention policy, or an earlier deferred clean-up), Check In and Undo Check Out now detach the document from co-authoring instead of failing on the missing file.
  • A failed check-out leaves nothing behind in OneDrive. When a check-out fails after the file was uploaded, the uploaded copy is removed together with the M-Files rollback, so retries no longer accumulate copies in the connected account’s drive.
  • Sharing updates are gated on the server. Updating the sharing of a co-authoring document now applies the same licence, internal-user and recipient-limit checks as the other sharing entry points, rather than relying on the Share button being hidden.
  • Translated metadata structures. A vault whose value-list items are translated no longer reports its co-authoring documents as belonging to an unsupported platform.
  • No more “Validation Exception” warning in M-Files Admin. The configuration validation reported “Late bound operations cannot be performed on fields with types for which Type.ContainsGenericParameters is true” on every check; the internal helper that triggered it has been rewritten.
  • Task-pane commands follow the selection reliably. In both clients a slow property read for an earlier selection can no longer re-enable Check In, Undo or Share on the document selected afterwards, and in the new client the Open command is hidden again when moving off a document a viewer could open.

Administrator notes

Section titled “Administrator notes”
  • Existing configuration migrates automatically on the first vault start after the upgrade, from any earlier CtrlShare 2.x release. The first OneDrive for Business entry of the old list is carried over and split by concern: credentials and authorization code into OneDrive for Business, whitelisted user groups and conditions into Access Control, workflow mappings into Workflow Mappings. Any other legacy drive entry and the folder check-out settings are discarded and noted in the vault application log; the hidden Google Drive labels simply fall away.
  • No re-authorization is required. The connected OneDrive account’s token is stored separately from the configuration and is not touched by the migration; co-authoring continues without re-entering an authorization code.
  • Upgrading from 2.25.x or 2.26.4.x (the single-Person configuration): the original Person object type, Person Name, Email, Person User Account, Writers and Readers settings become one entry under M-Files Configuration → Person Mappings, of type Object and labelled “Person”. Review it once; nothing else about person resolution changes.
  • Workflow mappings from 2.26.4.2 and 2.26.6.0 receive a generated name (“Workflow mapping 1”, …) because the current configuration requires one. Rename them at your convenience in the admin configuration.
  • How to confirm the migration. After the first start, the vault application log contains the configuration upgrade entries, and the stored configuration (Named Value Storage, ControlledCoAuthoring.VaultApplication / configuration) is stamped "Version": "3.1" and contains an OneDriveConfiguration section.
  • Backup and rollback. Before migrating, CtrlShare stores a copy of the previous configuration in Named Value Storage under ControlledCoAuthoring.VaultApplication.Backup / configuration-before-3.1 (named after the version being migrated to; never overwritten; a later, different pre-migration configuration gets a numbered sibling). To roll back, reinstall the previous CtrlShare version and restore that copy to ControlledCoAuthoring.VaultApplication / configuration. Do not merely delete the Version stamp from a migrated configuration. A configuration saved on a rolled-back build and upgraded again is recognised by its content, backed up, and migrated once more.
  • The value-list item “OneDrive for Business” referenced by the External File Platform property is unchanged and still required.
  • New default redirect URI: http://localhost/ctrlshare. The previous default, https://login.microsoftonline.com/common/oauth2/nativeclient, shows the authorization code only briefly before redirecting away. With http://localhost/ctrlshare registered as a Web redirect URI on the Entra app registration (nothing needs to run on the administrator’s machine), the browser lands on a connection-error page whose address bar keeps the complete URL; paste that URL into Authorization Code. Existing connections are not affected: the migration writes the redirect URI a connected app registration was set up with into the configuration explicitly (configuration version 3.1), so nothing changes for them until an administrator chooses to switch. Only a vault that has no client id yet starts on the new default.
  • The preventCheckout switch is gone. Native M-Files check-out of a document that is checked out to co-authoring is now always blocked (with the configurable block message); the former option to allow it is not carried over by the migration. Use Undo Check Out or Check In to release such a document first.