Welcome to the RapidWeaver Community Forums, where you can chat with RapidWeaver users from around the world!
RW/OSX Lion interaction? Permissions?
ararimu
Posts: 3Members
G'day,
I'm running RW 5.2.2 on OS X Lion on an iMac with in SSD + 1TB drive. Booting is from SSD, data is stored on 1TB drive. The site I'm working on is based on the v. nice Cre4mi theme. I recently upgraded to Stacks 2, but the issue was apparent before this.
There appears to be some weirdo interaction with file permissions inside the RW sandwich (package file). I can't find any definitive answers in this forum to this.
Lion has this habit of locking files after a certain number of days, but this is not the issue. I'll open the file, do a bit of work, try to save and RW can't save it because it reports that the file is locked. The file is NOT locked, but the permissions don't seem to be right.
In a fit of frustration, I added all users read/write permission to the enclosing folder and copied to the enclosed items. That fixed things, but when I go back into RW and make a change such as adding some text, I can't save again.
Looking into the document package (the RW "Sandwich") I see that the top level of items has this set of permissions:
So something is mucking up the privileges before the next save.
Has anyone see this? It _appears_ to be RW and not one of the extensions, but I'm not sure. This is a serious interruption to workflow!
Thanks for listening, all ideas considered.
Rob
I'm running RW 5.2.2 on OS X Lion on an iMac with in SSD + 1TB drive. Booting is from SSD, data is stored on 1TB drive. The site I'm working on is based on the v. nice Cre4mi theme. I recently upgraded to Stacks 2, but the issue was apparent before this.
There appears to be some weirdo interaction with file permissions inside the RW sandwich (package file). I can't find any definitive answers in this forum to this.
Lion has this habit of locking files after a certain number of days, but this is not the issue. I'll open the file, do a bit of work, try to save and RW can't save it because it reports that the file is locked. The file is NOT locked, but the permissions don't seem to be right.
In a fit of frustration, I added all users read/write permission to the enclosing folder and copied to the enclosed items. That fixed things, but when I go back into RW and make a change such as adding some text, I can't save again.
Looking into the document package (the RW "Sandwich") I see that the top level of items has this set of permissions:
ls -al /Volumes/theData/Documents/Athenaeum/web\ site/athenaeum_web_cre4mi_deep_blue.rwsw total 24 drwxrwxrwx 6 r admin 204 25 Jan 18:15 . drwxrwxrwx 34 root admin 1156 25 Jan 18:15 .. -rw-r--r-- 1 r admin 3667 25 Jan 18:15 Contents.plist drwxr-xr-x 3 r admin 102 25 Jan 18:15 DefaultPageAttributes drwxr-xr-x 10 r admin 340 25 Jan 18:15 Pages -rw-------@ 1 r staff 6347 20 Sep 09:44 README.txtchanging all of these back to read/write:
ls -al /Volumes/the /Volumes/theData/Documents/Athenaeum/web\ site/athenaeum_web_cre4mi_deep_blue total 24 drwxrwxrwx 6 r admin 204 25 Jan 18:06 . drwxrwxrwx 33 root admin 1122 25 Jan 18:10 .. -rw-rw-rw- 1 r admin 3667 25 Jan 18:06 Contents.plist drwxrwxrwx 3 r admin 102 25 Jan 18:06 DefaultPageAttributes drwxrwxrwx 10 r admin 340 25 Jan 18:06 Pages -rw-------@ 1 r staff 6347 20 Sep 09:44 README.txtfixes the problem...until I make any change to one of the html pages and the permissions are skewed again.
So something is mucking up the privileges before the next save.
Has anyone see this? It _appears_ to be RW and not one of the extensions, but I'm not sure. This is a serious interruption to workflow!
Thanks for listening, all ideas considered.
Rob
Comments
Since the instant Lion rebooted, last july, up to today I'm still experiencing, after two Lion updates and a couple of OS *clean installs*, random read/write issues with files stored on external HDs
AppleCare "geniuses", at first, put the blame on Adobe (LightRoom is the only app I use to manage files stored on external HDs) then on WD and HD manufacturers in general :-0
Usually an eject/reconnect, or a reboot, solves these issues but... I guess it doesn't help in your situation, sorry
paolosavonuzzi.org
Yep, I'm with you on the Lion flakiness. It is definitely a cantankerous beast. This mac came with Lion, so not really an option to go back to Snow Leopard.
I could tell OS X to ignore permissions on that second (internal) drive, but that's not really an option on the network.
I've not seen this with any other app (including LightRoom), which is why I am scratching my head on here
Rob
I figured this would be related to USER Permissions, so I did a get info on data volume, set it to everyone read/write, which didn't fix the issue. Closed and opened the get info, then saw a new setting appear in front of my eyes where MY account couldn't read and write the data drive (but other admin accounts could). Changed that setting, copied to enclosing folders and all is sweet.
I suspect that RW was the only program affected, because the files it writes are packages with all sorts of nuances.
The real question in my mind is "what actually caused all of this"...something I doubt I will ever find out. This was a clean install of Lion (came with the computer) so I couldn't even blame upgrades. Oh well!
Later
Rob
"what actually caused all this"? the issue I have in Lion with external HDs is that *sometimes* one, the other or both become read only
when this happens, no need to play with permissions: just eject, remount ad all is fine again :-0
paolosavonuzzi.org