Skip to content

Phab Guy

← Adobe InDesign

My feedback

1 result found

  1. windows long paths not supported

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Adobe InDesign: Bugs » Others  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Phab Guy commented  · 

    This issue also seems to affect Bridge CC and thus other applications in CC. For example, try this:

    1. Using Bridge, locate a file in deep folder hierarchy. The path including file name needs to be > 260 charaters.
    2. Right click the image file.
    3. Choose Place > In Photoshop
    4. ERROR: Script Alert: Error: Expected a reference to an existing File/Folder.

    NOTES:
    1. Long Paths are enabled on this PC, confirmed in the Registry.
    2. The Photoshop is Photoshop 2021, latest release.
    3. Photoshop *CAN* open this same image through its own dialog box.

    My conclusion is that Bridge also has a problem with Long Path filenames on Windows.

    Phab Guy supported this idea  · 
    An error occurred while saving the comment
    Phab Guy commented  · 

    FYI, this is my bug report. I posted it before "signing up" for InDesign User Voice.

    The lack of long path support has a number of consequences for InDesign users on Windows. E.g.
    - My standard Job management folder structure has 3 levels organized by years and job numbers. Within that, I maintain all the suppled files for each job. If my client supplies their assets within their own hierarchical folder structure, I want to maintain that for consistency. Thus, it is easy enough to exceed 260 characters.
    - Packages shipped between systems could trigger a problem. Just placing a package into an existing hierarchical folder structure could cause that package to be unloadable by InDesign on that system.

    My workaround plan is to rename and move all the assets for my current job. It involves 300 images and captions which I want to load with Data Merge. This is going to create a longer term asset management issue, so I hope Adobe will fix this issue right away.

    This is not a typical "feature" or "enhancement" request. This is asking Adobe to correctly and fully support the file system it is running on.

    Thanks for your consideration.

Feedback and Knowledge Base

(thinking…)