iWork not iWorking on SMB in Mavericks

As long as you don't use icloud there is no problem. If you do use icloud and you save your iwork '09 document on icloud. Once you've opened it in the icloud beta version, you can't open it anymore. That's why you need the new iwork anyway.

Yes I know all that, but iCloud is not the only way to share documents and a heavy price to pay if you can't create what you want in the first place.

Peter

I'm using OSX Server 10.6.8 and have all SMB services turned off, so I have to assume that using AFP doesn't solve the problem. I, too, see the mystery folders appear.

I'm a bit confused by the comment that "This is an option for those who had iWork '09 installed previously" (or words to that effect).

Does reverting to iWork '09 solve the problem regardless if it had been installed or not? I.e., I've got one machine I have only had '13 on. I anticipate that I can put '09 on it and delete '13 and all will be well (after documents are reverted, that is).

Correct?

Pages '09 worked and continues to work.

The problem as I understand it is the new Pages/Numbers/Keynote 5 file formats.

Peter

From my experience, it seems that the .1 update released last week fixes this SMB bug across the iWork suite. Anyone else have similar joy?

It does appear that it might indeed have fixed the SMB issues. I feel like I might jinx it by saying so, but my Pages docs stored on our SMB server appear to be saving correctly.

I can confirm that the save bug certainly on my SMB server seems to have gone in .1

I've got anecdotal evidence that it hasn't been fixed for AFP, though why there would be a difference, I don't know.

We'll be experimenting over the next day or two with the .1 version and I'll let you know.

It appears to save OK with AFP-mounted volumes as well. But how long do we use it before declaring victory, because I just had a user report that she saved it to her local Desktop and it created a new folder for each attempted save, still never saving the actual document. (And she sent a screenshot to me to prove it. Smart woman!)

Anybody else seen this behavior?

People have reported that Desktop behavior with Pages '09 documents, which are zipped bundles, if they have Stuffit Expander installed, and its preference to automatically expand archives on the Desktop set. But I think you are referring to Pages 5.1 documents, which have a different structure, so that wouldn't apply.

Oh. My. Goodness. That is about as unobvious as it gets!

Indeed that one lone client had StuffIt Expander installed. I had her remove it and the problem disappeared. Thank you very much, Jeff!!

The interesting thing is that this is a Numbers 3.1 installation (your assumption is correct, though the version numbers are different across the iWork suite) and it is definitely creating a zipped bundle or something which gets gorked by Expander.

I just tried the process on my desktop with the source document she used (which was a plain old text CSV file) and it does get saved as a package on my desktop. But I don't have Expander installed, so it gets left alone.

Thanks again, Jeff!

Unfortunately, I am still seeing all kinds of problems with Pages 5.1 on SMB:

- "You don't have permission to write to the folder that the file is in."

- "The location of the document cannot be determined."

- Documents are often silently corrupted without error when saving to SMB.

- Even moving files to the desktop temporarily and moving them back to a share is not stable; I just got "Some images are missing because they were deleted from the document." and all the images from the .pages doc were gone - nice!

So for me, the iWork update didn't solve anything.

There are other apps misbehaving on shares too with Mavericks, so it seems to me the real problem is in the base system and not in iWork. Something seems fundamentally f-ed up there (SSHFS is broken in horrible ways too). Complex magic happening in the background such as auto-versioning and bundles make any problem worse, of course.