[MNT-10773] You are unable to 'edit online' a MS Office document whose path length is greater than 255 characters Created: 07-Feb-13  Updated: 11-Jun-15  Resolved: 02-May-14

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: AOS / Sharepoint Protocol
Affects Version/s: 4.2
Fix Version/s: 4.2.3

Type: Service Pack Request
Reporter: Lucas Kwon Assignee: Closed Bugs
Resolution: Fixed Votes: 0
Labels: Customer_Success
Remaining Estimate: 0 minutes
Time Spent: 2 weeks, 2 days, 1 hour, 30 minutes
Original Estimate: Not Specified

Attachments: JPEG File message.jpg    
Issue Links:
is cloned by MNT-12031 CLONE - You are unable to 'edit onlin... Closed
relates to MNT-8609 Edit online fails for files whose URL... Closed
is related to by SHA-1358 Remove folder names from document lib... Idea
is related to by MNT-13614 CLONE - Unable to edit file online wh... Closed
is related to by MNT-8609 Edit online fails for files whose URL... Closed
is related to by MNT-13279 Unable to edit file online whenever f... Closed
is related to by MNT-13885 CLONE - Unable to edit file online wh... Closed
Bug Priority:
Category 3
ACT Numbers:

00101745, 00107193 Premier, 00134943, 00130298, 00116106

Build Location: http://releases.alfresco.com/Enterprise%204.2/4.2.3/build-00050/


You are unable to 'edit online' a MS Office document whose path length is greater than 255 characters.

I know this MAX_PATH limitation is associated with the Windows file re-director, however, could you see if we can workaround the issue on Alfresco side?

Steps to Reproduce:
1. In a site's doclib, create a folder and its sub-folders so that the path length to the end MS Office document (e.g. a word file) is longer than 255 characters.
2. Click 'edit online' of the word document created above.

Expected Result:
Users should be able to edit the word document online.

Actual Result:
It displays attached warning message and doesn't open the word document for editing.

Comment by Mike Farman [ 22-Nov-13 ]

We believe there is a workaround for this using alternative mechanism to generate URLs based on a unique ID rather than the path. We plan to investigate this approach with a view to providing an updated module with this workaround. Confirmation and timings will follow once this investigation work is complete.

Comment by Mike Farman [ 22-Nov-13 ]

Brian Remmington Hi Brian, the workdesk guys have also hit this issue and have a solution based on using the GUID rather than the path for the Edit Online URLs (webdav is not affected). The following is from Stefan Kopf that describes the approach. Would it be possible to have offshore look at this? As you can see, we've got several customers affected by this including SAP and PGA. I think it needs to support path and guid based versions of the URLs. GUIDs can be used when the path is to long. This approach as been implemented and proven for Workdesk. Stefan can provide the details is required. This would mean a new version of the VTI module. WDYT?

But there is a possible work-around, that can be implemented on the server side:
You could access documents by their ID instead of their path. Instead of using URLs like this:
You could access this document with this URL:

Comment by Brian Remmington [ 06-Jan-14 ]

Please would you take a look at the idea described in Mike Farman's comment above? What changes would be needed to enable the URL scheme suggested by Stefan (/..../__ID/<...doc_id...>)?

Comment by Jennie Soria [X] (Inactive) [ 20-Feb-14 ]

All SF updated with project number change and customers notified.

Comment by Dmitry Vaserin (Inactive) [ 25-Feb-14 ]

I suggest to use following URL as alternate:


It requires changes in action.js and VtiPathHelper.resolvePathFileInfo() method.
Committed in r63222@https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/BELARUS/V4.2-BUG-FIX-2014_02_10

Base operations works OK(open/edit/save/checkout/checkin), but it is impossible to edit document without closing after CheckIn(issue reproduce without my changes too).
Should I create new issue or just pass information to QA?

Comment by Alfresco QA Team (Inactive) [ 02-May-14 ]

Successfully validated against Alfresco Enterprise v4.2.3 (r68545-b316) schema 6060 - OOTB; RHEL 6.4 x64. Client:Win7x64, FF 28.0

Generated at Mon Jul 13 20:24:33 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.