Quark Forums

I asked this question a year ago, both on here and directly to quark support.

Why does Quark save files and collect images with permissions: owner: Read Write group: Read others: None

Even though Mac OS X defaults for files created by an application are Owner: Read Write Group: Read Others: Read

A year ago I was using Mac OS X 10.5 and Quark 7 (through to 7.5) and at the time quark tech support said they couldn't reproduce this and gave up!

But now I have a brand new laptop with Mac OS X 10.6.1 fresh install, the first thing I installed was Quark 8.1 and still it saved and collected images with the wrong permissions, ( saved to local drive no network involved)

So it was clearly not related to my set up as was suggested.

Why does quark save with these permissions when all other applications follow the default permissions set in uMask settings.

I'm not really looking for a solution this time, just an explanation would be good

is no one else coming across this problem?? How are you handling different people working on the same job (after it has been collected)

 

nitro:

is no one else coming across this problem??

Since you asked...no, I have not. 

I wish I knew why it was happening then, set up two brand new laptops recently, only thing installed on them other than the OS was a fresh copy of quark downloaded from the website. I've installed 15 copies of quark at various times on different macs and every single one behaves the same - yet no one else seems to have it!

We have the same problem and our Quark-support gave us this two forum "answers": ============================== "Here is your problem: You need a server. Or a Mac that is capable of running OSX server, or a PC that runs server software (Windows or Unix/Linux). Based on the information you mention above I am assuming that al three Macs are using OSX client. That is, none of them are using OSX server. The problem with this is that Apple designed security in to the OSX client. So, any file you save/write retains the permissions of the owner and is only changeable by the owner. Only server software allows what you are trying to do. Even if you have the exact same named account on all three machines and use that acount only, you will still have problems because at a base level there is an account id that is different on each Mac. There are some other options such as DAVE, by Thursby, but it's expensive and I don't think really practical in this case. You could try and external drive which all users can connect to and the "host" Mac has "ignore permissions on this drive" set, but I don't think that will work. I'm sorry, but Apple mainly designed the client file sharing just to be a matter of copying files back and forth, not as a workgroup. " =============================== =============================== That is not the ACL you want. It won't give you "real" read/write access. What you want to run: chmod +a "everyone allow write,append,writeattr,writeextattr,file_inherit,directory_inherit" chmod +a "everyone allow add_file,add_subdirectory,delete_child,writeattr,writeextattr,directory_inherit" This way newly created files and folders (as well as subfiles and subfolders of those newly created folders) will have the ACE (ACLs are made up of ACEs) needed to give 'everyone' Read&Write. It gets Read ability from the POSIX privs (Read Only) automagically set on the folder when it is created. It then gets the Write ability from the ACL. When you view the folder in the Finder's Info Window, you will see three entries for 'Everyone' this is correct. One entry is from the POSIX privs while the other two are the ACEs you added above. Hope that helps." =============================== I will say that this is NOT i Mac, client or server problem. It is really a "new" Quark problem based on how other applications work.

Thanks, but we do have a Server - Mac OS X 10.5.8 unlimited, so the first answer doesn't apply and our ACL's are already set up as described - basically quark is crap!

Well... QuarkXpress is not crap in my opinion, but the way it writes permissions are not quite normal. As far as I know (cant say more), this is one thing that Quark is currently looking into. So hang on there. Soon there will probably be an update to download :)

Its been like this since Quark 7, even if they fix it they will only fix Quark 8 meaning we have to spend £4000 to upgrade, I've been talking to quark support about this for 2 years - its a real drag for us cos I have to go onto server admin every day and re-propegate permissions so the designers can carry on with their work

ok...... hmm. This seems to be a "non existing" problem. The support we have hired are in a possision that is closer to Quark in the food chain, so to speak, so maybe we have more luck with it. We'll see.

nitro:

Why does Quark save files and collect images with permissions:
 owner: Read/Write
 group: Read
 others: None

Even though Mac OS X defaults for files created by an application are
 Owner: Read/Write
 Group: Read
 Others: Read

(...) I'm not really looking for a solution this time, just an explanation would be good

 

Hi,

I never experienced that problem you describe in any version of QuarkXPress since I started to use it in 1991. And I usually exchange files with other users... the only problem I still see is that QuarkXPress still doesn't add a file extension when I save a new document. I always have to add .qxp (for prject files) or .qxt (for templates) when "saving as...".

I think your administrator basically has to set up the group rights on your network so all your QuarkXPress users (the designers and/or pre press specialists) belong to the same group. That could be "staff" (which is available as a default on your systems) or let your administrator set up a new group "design".

If your admin doesn't know how tu use ls, chown and chmod have a look at <http://oreilly.com/pub/topic/mac>. I'd suggest "Take Control of Permissions in Mac OS X" which is available as an ebook.

I think this could be some kind of workaround in some cases but the problem is still there...why QuarkXpress write permissions in its own way and all other software (Indesign for examplea) is writing permissions as it should be done. My own theory is that it has something to do with temp files, but that is just a vague feeling and has no scientific basis what so ever.

Check out other similar thread, it might help. http://forums.quark.com/t/21415.aspx

I'm surprised you and others don't see this issue - when I can consistently reproduce it on any mac, both at work and on private machines. Collect a job for output then look at the permissions for the collected images - I see RW R NONE for POSIX and the inherited ACL's are missing completely - strangly the collected fonts and profiles have the correct permissions and keep their ACLs

I know this is an old post, but I've had this problem for YEARS. This single issue causes me to not recommend to my company to stay with Quark. I have found certain ways around the permissions problem over the years, but nothing ideal. It is January 2012 and we still use Quark 6.5 for our newsroom. Under Tiger, we do not have a problem. But with Leopard on up Quark writes files with Read/Write, Read and None access. Which is totally useless in a workgroup environment. I actually have had a cron job run to chmod permissions on folders of Quark files every few minutes just to make the files 777. I know this is because Mac OS X is a multi-user OS and Apple has upped security in Leopard and above, blah, blah. But newspapers don't care about this. We need to be able to work on Quark documents without having to go to the Get Info box all the time to set permissions just so somebody can work on a page. Here is my current fix, which is to set a custom umask, but it doesn't work in Quark 9. And I doubt it works in Quark 7 or 8 either. It works for everything Adobe, everything Apple and Quark 6.5 so that GUI applications can write documents with 777 permissions. http://support.apple.com/kb/ht2202 Hope this helps someone, but I still require a way for Quark 9 to write 777 files. This is nauseatingly frustrating and has caused me to detest Quark - a program I used to cherish. Hope someone else is having the same problem. I and every newspaper we print has the same problem. Thanks. — Davy M.

After a few calls to Quark customer service, with no useful solution offered, I think I found a work-around. Evidently Quark 7-9 honors ACL and ACE permissions, but not standard Posix permissions. This is why saving Quark files on a Mac Os X Server with properly configured ACLs works for a workgroup environment allowing more than one person to work on the same Quark file. Mac OS X client does not have a GUI tool to manage ACLs. In my eternal quest for a solution to this problem, I've experimented a lot with setting ACLs and ACEs on a Public folder from the Terminal, finding various snippets of code during Google searches, and getting close to finding a solution. The following code is close, but never did work just right. In the Terminal: sudo chmod +a "everyone allow write,append,writeattr,writeextattr,file_inherit,directory_inherit" /Users/userfolder/Public sudo chmod +a "everyone allow add_file,add_subdirectory,delete_child,writeattr,writeextattr,directory_inherit" /Users/userfolder/Public However, I then discovered a GUI Utility called Sandbox that allows you to inspect and specify ACLs for any folder. Using Sandbox, I allowed everything for my Public folder, and for the Public folder on my test machine, and was then able to create a Quark document on one machine and open, edit and save it on the other machine, and vice versa. I will continue to test this, but my preliminary findings are encouraging. This is the first time I've been able to make this work after trying for years and years to discover a solution. Quark needs to document this better, or ship a GUI tool such as Sandbox so that users will be able to set ACLs on their Mac OS X client computers so that they can work collaboratively without a Mac OS X Server. I think this would prevent many people from jumping to InDesign, although it may be too late now. Note, Sandbox has not been updated for a while and is only vaguely compatible with Mac OS X Lion 10.7. It works fine with Mac Os X 10.5 and 10.6. Note 2: It may be necessary to run both Sandbox on the Public folder as well as the two Terminal commands to make sure everything is wide open and that there are no permission problems or access errors, such as the dreaded Quark −5000 error. Hope this helps. Quark, if you're reading this, I would love to talk to someone in programming about the programming logic of this issue to know if this is a feature, bug, or known issue. I hope my toils can help others who have been struggling with the same problem for years. And if anyone else sees errors in my Terminal commands for setting ACLs, please post.