File is read-only

[Pat Bensky]

Using Mac OS 10.5.8 ...

A client has given me a couple of Indy documents. Not sure what version they are in (how do you tell?) but I am opening them in CS5. When they are opened is says (Read only) in the title bar and I can't re-save them, either with the sme name or a different one. I've gone into the Info panel and changed the persmissions to Read Write for everybody - this makes no difference.

What's the story?

Pat

--
*************************************************
CatBase - The Database Publishing Solution
tel: +44 (0) 1462 454522
fax: +44 (0) 1462 454566
w: http://www.catbase.com
skype: pat.bensky
Find great gift ideas at GiftGofers.com!
*************************************************

[steve harley]

On Tue, Apr 19, 2011 at 16:50, Pat Bensky <pbe...@gmail.com> wrote:

Using Mac OS 10.5.8 ...

A client has given me a couple of Indy documents. Not sure what version they are in (how do you tell?) but I am opening them in CS5. When they are opened is says (Read only) in the title bar and I can't re-save them, either with the sme name or a different one. I've gone into the Info panel and changed the persmissions to Read Write for everybody - this makes no difference.

if InDesign can't Save As, then it's not a Finder privileges issue, it's an InDesign issue; but just for kicks you could use Get Info in the Finder to check whether the file is locked

[Pat Bensky]

The files are not locked.
What sort of InDesign issue?

--
you are subscribed to "InDesign talk" on Google Groups, to post: send email to indesi...@googlegroups.com, to unsubscribe: send email to indesign-tal...@googlegroups.com, for more options visit http://groups.google.com/group/indesign-talk

[Pat Bensky]

If I save it into a different folder it appears to be OK. If I try to save it into the same folder as the original, it says that the document is damaged and it can't be saved. Hmmm.

[Bret Perry]

For version of ID, if you open a file, then go to File… File Info… then at the bottom of the info window it will say Application Adobe InDesign 7.0 (7.x is saved as CS5, 6.x is CS4 - etc.)

You have checked permissions, but only mention POSIX permissions (the ones that you can see in Get info)

Did or do any of the permissions in Get info say "custom" ? Does it have an "@" in the permissions viewed in terminal?

If they do , you also have ACLs (access control list --"advanced multi-group inherited type permissions") and need to clear them.

You can also check in the terminal: 

ls –le /filepathname

You can remove ACLs in terminal with chmod –RN /filepathname

Or maybe the file's permissions are good, but the folders above it are not (all folders from the start to the file must be accessible for write)

OR if on a server, you might have an invisible flag set on the file, view them in Terminal with:

ls –lO /filepathname

(LS –LO but el's and es's in lowercase and O in uppercase) 

But I bet in your case it is the folder(s).

[steve harley]

On Tue, Apr 19, 2011 at 17:24, Pat Bensky <pbe...@gmail.com> wrote:

If I save it into a different folder it appears to be OK. If I try to save it into the same folder as the original, it says that the document is damaged and it can't be saved. Hmmm.

your trouble reports seem inconsistent -- now it seems that InDesign _can_ Save As but before you said it couldn't, and now you mention a "document damaged" message; without more info now i can only guess -- could be folder permissions, disk corruption, an actual damaged document, an InDesign bug, a plug-in missing ... or maybe it's as simple as a left over lock file that needs to be deleted?

[C F Majors]

I have seen this before. If I copy a disk to the drive, it seems to
make a read-only sector. Copy the job files/folder out of there to
your drive and all should be well.

Or not!

HTH.
Carol

> --
> you are subscribed to "InDesign talk" on Google Groups, to post: send email
> to indesi...@googlegroups.com, to unsubscribe: send email to
> indesign-tal...@googlegroups.com, for more options visit
> http://groups.google.com/group/indesign-talk
>

--
Carol Majors / Publications unltd
Raleigh NC
.   .   .   .   .   .   .   .   .   .   .   .

[KBL Graphics]

Bret, I'm having nightmare permissions issues with a new iMac on my network here in the office...

If I use terminal for <You can remove ACLs in terminal with chmod –RN /filepathnam>

Is this ALL the info I need to type into terminal? I don't use terminal very much, so I'm a bit gun shy!

The apple tech tells me "this issue isn't covered under my apple warranty and BY DEFAULT, and folder created BY this new Mac ONTO a Mac server is "read only". Like I said, nightmare!

Thanks for any help!!!  Ken

[steve harley]

On Wed, Apr 20, 2011 at 10:28, KBL Graphics <kblgr...@comcast.net> wrote:

If I use terminal for <You can remove ACLs in terminal with chmod –RN /filepathnam>

Is this ALL the info I need to type into terminal? I don't use terminal very much, so I'm a bit gun shy!

since you mention your files appear read-only on a server, it will work if 1) the server supports ACLs and 2) ACLs are your issue

also note that chmod -R takes a folder as an argument and modifies everything contained in the folder, not the folder itself; so you could open Terminal, type

  chmod -RN<space>

(where "<space>" means type a space character, not the literal text)

then from Finder drag the folder containing the problem files into the Terminal (this will copy the path to that folder onto the command line); then hit return and you'll strip ACLs from all files in that folder and all the enclosed folders; if there's an error, you may have to precede the command with "sudo "

[Bret Perry]

On Wed, Apr 20, 2011 at 10:28, KBL Graphics <kblgr...@comcast.net> wrote:

If I use terminal for <You can remove ACLs in terminal with chmod –RN /filepathnam>

Yes, of course /filepathname is to be replaced with your actual path to the folder with problems…

See what Steve H. had to say… be careful with terminal, spaces are important. 

IF you are on Snow Leopard on desktop and have moved to 10.6.5 or later, be aware that there is a bug that duplicates ACEs on any folder copied to or copied on an Apple server.

This causes the ACLs to become corrupt and permissions fail after several copy operations on a particular folder. (i.e. If you copy it 3 times, the 3rd copy will be "bad") No warnings until you try to access it.

We have rolled back to 10.6.4 until Apple fixes the bug. It only affects Finder copying, copying in terminal is fine.

If you are having the read-only problem on all the folders you copy to server, probably your user profile is incorrect, or the area (folder) you are copying to has incorrect permissions.

The folder you are copying to should be set to allow read-write for your or your group, and anything copied there should inherit the read-write permissions.

Here are a few links to get you started:

http://support.apple.com/kb/ts1402

https://discussions.apple.com/message/12146310?messageID=12146310

http://macos-x-server.com/wiki/index.php?title=Chflags_Intro

http://reviews.cnet.com/8301-13727_7-20007737-263.html

http://reviews.cnet.com/8301-13727_7-10329825-263.html

http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line

From: steve harley <garba...@gmail.com>
Reply-To: "indesi...@googlegroups.com" <indesi...@googlegroups.com>
Date: Wed, 20 Apr 2011 13:33:56 -0400
To: "indesi...@googlegroups.com" <indesi...@googlegroups.com>
Subject: Re: [ID] File is read-only