Edit-in-place Question
by Jason Adams
on
Jul 14, 2008 at 2:23:17 am
I have just set up FCS to use an edit in place drive. The drive itself is connected from another server using AFP. I have been previously using this connected drive without a problem to edit over the network.
My problem is that after I have set up the drive(or I think it is setup) when I try to check out a project in FCS that lives on the Edit-in-place drive it still wants to copy all the files to my local machine.
Is there a way to verify a drive is setup to use Edit-in-place? All i did to set it up was create a device and add the Mac edit in place URL, are there other settings that need to used to turn this feature "on"? As a storage device it works because I can upload to FCS and have assets encode to there.
In the manual there is some vague wording that says that edit-in-place may or may not use the check out feature. If edit-in-place doesn't use the check out/in feature what is the point of even using FCS?
Re: Edit-in-place Question by Andre Simons on Jul 15, 2008 at 1:45:46 am
Verifying a device as edit-in-place:
- look in the devices pane (in the administration window) and make sure you have an edit-in-place URI set up.
- the Mac EIP should start file:/// or file://localhost/
- This must be a valid URI on the client computer. Paste the URI into a web browser on the client and see if it opens the directory in the Finder.
That's about all I can think to do.
Remember that edit-in-place is advisory - that is, if a particular client can not resolve the URI then that client will copy. EIP also doesn't work with contentbases
