Page 5.0, Number 3.0, and Keynote 6.0 file would not save to shared NTFS folder

Question

Level 1

8 points

Page 5.0, Number 3.0, and Keynote 6.0 file would not save to shared NTFS folder

Originally I thought it is OS 10.9 problem. As I revert to '09 version, all files can be save to a network NTFS shared folder or drive once again. I have post it in OS Maverick section, and I post this again in iWork Pages for Mac section and hopefully right Apple personal can read it. I can open these files with out any problem and user has the proper credential. The problem exist when I try to save the file back to shared folder, it will display error message saying I do not have the proper permission and the file will become corrupted (display as a folder, not a file). Hopefully this issue can be fixed ASAP.

iMac (21.5-inch Mid 2011), OS X Mavericks (10.9)

Posted on Dec 19, 2013 10:50 PM

Reply

Answer 1

fruhulda

Level 6

15,161 points

Dec 19, 2013 11:35 PM in response to Coolmaster01

Have you tried correcting the permission?

Why struggle with Pages 5 when Pages 09 works so much better. Pages 5 is badly stripped version of Pages. Not all new is better than the old, not even when for free.

Reply

Answer 2

Coolmaster01 Author

Level 1

8 points

Dec 19, 2013 11:42 PM in response to fruhulda

It is not a permission issue as all other programs including iwork '09 can read and write to that shared folder just fine. Your are right that not all new version is better, although the new interface and full compatibiity to iOS does look attractive.

Reply

Answer 3

Dec 20, 2013 2:34 PM in response to Coolmaster01

How is the new interface better?

It is muddled, obscure and requires multiple extra steps to get things done as well as eating up a large chunk of screen real estate.

The "full compatibility" does not extend to other versions of the iWork software, nor eMails. So really it is full compatability with itself.

Except not so much Pages for iCloud beta.

Apple has actually removed 90+ features from Pages 5 and what is left is not working that well. That is a heavy price to pay for a new interface, even if that interface actually did what it was claimed to do, make life easier for users.

This particular problem with .pages packages not being parseable by other server software also introduces a problem of the files themselves not being parseable by anything else wanting to see the content. Not exactly a good sign from a company that has just trashed the previous file format, after trashing that of the predecessor to iWork, AppleWorks and lots of other software before and since that.

But who wants to read their own files? Just look at that interface!

Peter

Reply

Answer 4

Coolmaster01 Author

Level 1

8 points

Apr 7, 2014 7:02 PM in response to Coolmaster01

The access issue has been resoved in the latest Page 5.2, and I presume also for Number and Keynote.

Reply