Skip navigation
Kevin B Long
Kevin B Long Calculating status...
Currently Being Moderated

Relative paths for assets with multiple Muse users

Jul 19, 2012 8:15 AM

Tags: #adobe #path #muse #relative #adobe_muse #directory #asset #literal #relinking

I have created a shared folder in Dropbox that allows various people with responsibility for editing my site, each with a licensed copy of Muse, to access the Muse files. All the assets required for the site sit alongside or in a subdirectory beneath the main Muse file.

 

But because the literal path to the dropbox folder (or any other shared folder I suppose) contains their user name, and because the link point to the shared folder might be arranged differently on their machine (some people mount dropbox in "Documents", others elsewhere), the literal path to the Muse file differs per user.  I guess this is true even on the same computer with different users.

 

As a result of these literal paths differing, when opening the Muse site, even when all assets required by the site are in the same folder or subfolder as the main muse file, each user is prompted to relink assets every time they open it after someone else has and relinked from their side.

 

Is there no way to have Muse look at relative paths instead of literal paths to avoid this?

369 Views   2 Replies   Latest reply: Kevin B Long, Jul 20, 2012 2:59 PM
 
Replies
  • Colby Ausen
    Currently Being Moderated
    1. Colby Ausen,
    Jul 20, 2012 2:00 PM   in reply to Kevin B Long
    Report

    Unfortunately it isn't possible to look at relative paths instead of literal right now. This is a good feature request though and I will take it up with the development team!

     

    Muse auto-links all of the assets after the first warning dialog, though, correct? And out of curiousity, how is this multi-user workflow going for you?

     
    |
    Mark as:
  • Kevin B Long
    Currently Being Moderated
    2. Kevin B Long,
    Jul 20, 2012 2:59 PM   in reply to Colby Ausen
    Report

    Yep, after the first warning, and going through the handful asset updates (one per folder/location), it "sticks" and works fine even after quitting and restarting Muse.... just until another editor opens it up and relinks.  What I haven't tried though is intentionally NOT updating assets when I feel like the changes I need to make don't really involve them, and seeing how that works back for the primary editor -- would they be saved having to relink, would the file avoid corruption, etc.

     

    Multi-user workflow is the way my business continues to move, and the way I want to increasingly work with Adobe tools like Muse and Lightroom. With the exception of the asset linking, it works effectively -- I can have someone else do most of the work, and I review the changes.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points