Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

save as missing in lion

For those of us who make modifications to a document on a regular basis, but need to retain the previous versions, or who need to keep the same revised document in several places, the removal of "Save As" is a disaster. In order to save as, you must, apparently, first export the document as a WORD or PDF, then after doing that, close the pages document, (Then a save as comes up,) allowing one save as and automatically closing the document. I have a series of files that i must keep in several locations, and they all change weekly, but I must be able to reference past copies as well. It aqppears that the only way to do this is to buy WORD and forget about Pages. Surely this must be a mistake by a committee who does not do word processing, or am I alone in this type of use?

I WORK, Pages-OTHER, Mac OS X (10.7)

Posted on Jul 25, 2011 12:00 PM

Reply
270 replies

Jul 29, 2011 1:00 PM in response to David Gnotta

I try to explain since the beginning but it seems that my English isn't clear enough.


Maybe you may describe the entire process in plain English for other users.


Thanks for the feedback.


Yvan KOENIG (VALLAURIS, France) vendredi 29 juillet 2011 21:59:59

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community


To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

Jul 31, 2011 8:08 AM in response to Kappy

I agree and we need to keep pushing Apple to fix this. Saving in Lion is sooo poorly implemented, I can't begin to express how frustrating it is.


Here's a simple example from using TextEdit, but it's just as bad in Pages and all the other apps. Consider this:


I open file named database.xml file and edit it with TextEdit. Previously, all I would have to do was hit Cmd-S or go to the File menu and click "Save". Done. That's it.


Now, my save options are:


Close

Save a Version…

Duplicate

Export as PDF…

Revert to Saved


"Save a Version..." creates a new file in the original file location named database.txt -- not what I want to do.


Duplicate creates a new copy and now gives me the new option of "Save…" which still wants to save a text file and will force me to go through a warning dialogue to save over the original document - which I just wanted to save in the first place.


To add insult to injury, if I opened the file by browsing to it, the finder is pointed to the right location. But if I didn't, I have to hunt through my folders and find the location where I want to save the file, change the extension from .txt to .xml, and go through the warning dialogue stating that I'm about to save over a file of the same name.


Again, compare this to the previous work flow:

1. Open the xml document

2. Edit it

3. Click save.


That's it. No changing the friggin' extension, no new versions or duplication or hunting through folders. No warning dialogues.


This really is a terrible, terrible, terrible, terrible, terrible, terrible, terrible, terrible, terrible (I really can't say it enough), TERRIBLE implementation. SOOOO ANNOYING! Please give us back Save and Save As...


We went from elegant to byzantine. This is the kind of crap we'd expect from Microsoft, not Apple. If you don't have time to call (although there's free support for Lion for 90 days), go to the support pages in the apps (e.g., in Pages go to Pages menu and click "Provide Pages Feedback...")

Jul 31, 2011 8:11 AM in response to KOENIG Yvan

Apple needs to fix this. Having inefficient workarounds to make up for removing a very efficient workflow is unacceptable.


Saving in Lion is sooo poorly implemented, I can't begin to express how frustrating it is.


Here's a simple example from using TextEdit, but it's just as bad in Pages and all the other apps. Consider this:


I open file named database.xml file and edit it with TextEdit. Previously, all I would have to do was hit Cmd-S or go to the File menu and click "Save". Done. That's it.


Now, my save options are:


Close

Save a Version…

Duplicate

Export as PDF…

Revert to Saved


"Save a Version..." creates a new file in the original file location named database.txt -- not what I want to do.


Duplicate creates a new copy and now gives me the new option of "Save…" which still wants to save a text file and will force me to go through a warning dialogue to save over the original document - which I just wanted to save in the first place.


To add insult to injury, if I opened the file by browsing to it, the finder is pointed to the right location. But if I didn't, I have to hunt through my folders and find the location where I want to save the file, change the extension from .txt to .xml, and go through the warning dialogue stating that I'm about to save over a file of the same name.


Again, compare this to the previous work flow:

1. Open the xml document

2. Edit it

3. Click save.


That's it. No changing the friggin' extension, no new versions or duplication or hunting through folders. No warning dialogues.


This really is a terrible, terrible, terrible, terrible, terrible, terrible, terrible, terrible, terrible (I really can't say it enough), TERRIBLE implementation. SOOOO ANNOYING! Please give us back Save and Save As...


We went from elegant to byzantine. This is the kind of crap we'd expect from Microsoft, not Apple. If you don't have time to call (although there's free support for Lion for 90 days), go to the support pages in the apps (e.g., in Pages go to Pages menu and click "Provide Pages Feedback...")

Jul 31, 2011 9:49 AM in response to janinspain

This is a worst-case decline of usability and makes you loose time and disk space...


Talking with an Apple rep, they are being flooded with calls about this regression.



If we ask Apple they will fix this.


http://www.apple.com/feedback/macosx.html


It eludes me why Apple decided to cripple TextEdit (and other Apps) by stripping it of its ability to immediately save a document as HTML, or Web archive, ODT, or the various Word extensions that come with their respective editions.


Previously (on OS X Leopard and Snow Leopard), TextEdit would allow you to employ the "Save As" function not only to save the same document with a different name, but also to have that document saved in a different format.


In TextEdit, you CAN save it in a different format - using the same trick as with preview (i.e. Duplicate and then Save). You are then presented with a dialog that lets you choose the name and format."

This is a "workaround" to get the same functionality out of TextEdit, but Apple not presenting us with a quick option to do this still leaves the application crippled.

Jul 31, 2011 12:05 PM in response to Ziatron

Has one of you looked at the System's help which give that :


User uploaded file

What you are complaining about isn't a choice applied to one or two apps.

It's a feature defined at the system level.

But at this time I'm not sure that I understand well the reproduced page.


Must I understand that we may have the two schemes in a given app

or that we may have

the one with "Duplicate" in the 'modern' applications

and

the one with "Save As…" in the old fashioned ones (like iWork '08 applications) ?


The ability to save in different formats is also available in the Pages's Save… dialog.


Yvan KOENIG (VALLAURIS, France) dimanche 31 juillet 2011 21:05:20

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community


To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

Aug 11, 2011 12:39 PM in response to msw70

I agree with the complaints about the missing Save As button. At first I just could not believe it was not there and then when I tried to save a document off of a memory stick onto the hard disk - which I would normally do through save as in pages or text inside Pages - I had to export it as a Word document to the hard disk before I could eject my stick knowing it was safely stored in two places as the same file - not two different versions which I don't want. As an author Save As is essential to saving and duplicating the same working file on more than one drive and via email for security of the current working copy of the file. It also permits an easy way of creating a second working copy with a new name - for example by adding 1 at the end again in Save As. That it is not there seems to me to indicate not - as Yvan suggests - that we authors have got things wrong and we should all along have been saving documents as templates. It is that Apple software designers do not know how many writers actually write and save their work in Pages. Perhaps before they fix this they could go and interview some of their customers and watch them work. Added to this of course my version of Word does not even work in Lion and the newer versions - which I avoided because they are so memory hungry - apparently also do not work as well as they might in Lion because of bugs. So being forced to export a Word version - since no Pages export is available - just adds insult to injury.

Aug 11, 2011 1:17 PM in response to msnnorthcott

msnnorthcott wrote:


So being forced to export a Word version - since no Pages export is available - just adds insult to injury.

Perfectly odd.


At every time every user may save a copy of the work in progress.

From my point of view it's even easier than it was in the past.


Assuming that I work on azertyuiop.pages.

After 1 hour of work, I want to save the doc in it's current state.

Before Lion I used Save As… to save it say as azertyuiop #12.pages

Doing that, if I remember well, the open document was renamed as azertyuiop #12.pages

So it was a mess to retur to tha main document to type.


With Lion, I just trigger Duplicate which create a new document azertyuiop copie.pages

Which I save as azertyuiop#11.pages.

The source was in "Documents" the newly created one is also in "Documents" which no specific task.

I close the new doc and may continue to work in the original document whose name wasn't changed.



And for those which want to work the old way, Pages 4.0.5 may alwaysbe used under Lion.


As I'm a good guy, if you bought iWork as a package, you may get the 9.0.5 updater on my iDisk (address below)


Download :

koenigyvan:Public:For_iWork:iWork '09:iWork9Update5.dmg.zip



Yvan KOENIG (VALLAURIS, France) jeudi 11 août 2011 22:14:19

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community


To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

Aug 11, 2011 1:48 PM in response to msw70

Here's another fun example:


Let's try to save an existing Pages 09 document as a Pages 08 document.


What you would have done in the old work flow is:

1. Simply click "Save As..."

2. Choose Pages 08 in the dialog

3. Choose a location or change the name.

4. Click OK.

5. Close the document.


What you have to do now:

0. Click "Unlock" if it's an older document because you may be crazy or stupid and need to have an extra hurdle to protect you from yourself.

1. Click File>Duplicate.

2. If you've made changes to the document, click through the dialog to specify whether you want to "Duplicate and Revert" or just "Duplicate"

3. Click File>Save...

4. Choose Save a Copy as Pages 08

5. Change the location and change the name.

6. Click OK.

7. The duplicate and the original are still sitting on your desktop, but you're done with them so let's close them. First the duplicate.

8. Cancel out of the automatic save dialog that pops up on the duplicate because the program doesn't care that you've already saved a copy.

9. Now close the original.

Aug 11, 2011 2:36 PM in response to msw70

Yvan's first work around on this thread was byzantine requiring the creation of a template to save new versions in place of the former File>Save As. The template function in Pages - and iWork generally - is clearly not designed for this. His suggestion above I found by chance after my last post when I saved a duplicate, and then tried to delete it since it was just sitting there on the screen in front of the original. Once I hit File>Delete I was offered the opportunity I would have had with only one menu visit (under Save As) to save it to a new location and with a new name. The same happens if you hit File>Save having once created a duplicate with File>Duplicate. However as you rightly point out this does not fix all potential situations in which Save As was the previous default action for many of us. Having said that I guess I will get used to:


File>Duplicate


New file appearing on screen in front of the original version, and then


File>Save - create new name and designate drive/folder location


This is evidently what the Pages redesigner intended to have replaced Save As with and it works for most - though certainly not all - situations previously covered with half the number of clicks with Save As. But for those of us keen to save our hands from RSI and for more useful things like making another cup of green tea or canoeing in the river after work keeping the number of clicks down in work flow is an important issue.

Aug 13, 2011 12:29 PM in response to msnnorthcott

Here is a way to Save As in a single call.


--(SCRIPT Pages_save_a_copy]

(*

Enregistrer le script en tant que Script : Pages_save_a_copy.scpt

déplacer le fichier créé dans le dossier

<VolumeDeDémarrage>:Utilisateurs:<votreCompte>:Bibliothèque:Scripts:Applications :Pages:

Il vous faudra peut-être créer le dossier Pages et peut-être même le dossier Applications.


Aller au menu Scripts , choisir Pages puis choisir “Pages_save_a_copy”


Le script enregistre une copie du document au premier plan

au format natif de Pages en ajoutant la date et l'heure au nom du fichier.


--=====


L'aide du Finder explique:

L'Utilitaire AppleScript permet d'activer le Menu des scripts :

Ouvrez l'Utilitaire AppleScript situé dans le dossier Applications/AppleScript.

Cochez la case "Afficher le menu des scripts dans la barre de menus".


+++++++++


Save the script as a Script: Pages_save_a_copy.scpt


Move the newly created file into the folder:

<startup Volume>:Users:<yourAccount>:Library:Scripts:Applications:Pages:

Maybe you would have to create the folder Pages and even the folder Applications by yourself.


Go to the Scripts Menu, choose Pages, then choose “Pages_save_a_copy”


The script saves the frontmost document

in the native Pages format in a date_time stamped file.


--=====


The Finder's Help explains:

To make the Script menu appear:

Open the AppleScript utility located in Applications/AppleScript.

Select the "Show Script Menu in menu bar" checkbox


--=====


Yvan KOENIG (VALLAURIS, France)

2011/08/12

*)


on run

local docPath, docName, docFolder, fileName, theExt, newName, newPath

set major_OS to get system attribute "sysv"


(*

Grab infos about the open doc at front *)

tell application "Pages"

tell document 1

set docPath to its path

set docName to its name

end tell

if major_OS ≥ 4208 then savedocName(* Required for Lion *)

end tell


(*

Grab infos about the file from which the doc was open *)

tell application "System Events" to tell disk item docPath

set docFolder to path of container

set fileName to name

set theExt to name extension

end tell


(*

Build an unique name for the new document *)

if theExt is not "" then

set newName to (text 1 thru -(2 + (length of theExt)) of fileName) & (do shell script "date +_%Y%m%d_%H%M%S.") & theExt

else

set newName to fileName & (do shell script "date +_%Y%m%d_%H%M%S")

end if


(*

Create the new file *)

tell application "System Events"


makenewfileat end of folderdocFolderwith properties {name:newName}

end tell

set newPath to (docFolder & newName) as alias


(*

Save a copy in the newly created file *)

tell application "Pages"


savedocumentdocNameinnewPath

end tell

end run


--=====

--[/SCRIPT]

--{code}


Open a document.

Run the script once you will have a date_time stamped copy of its original state.

Make wanted changes.

Run the script which will automatically save the doc adding a date_time stamp to its name.


When you have finished, close the mainb file which will save the late changes if they arent already saved.

If you want to keep the changes in the main doc, leave iot as is.

If you want to retrieve the doc in iots original state, delete the doc and rename the first date_time stamped file removing its date_time stamp.


Yvan KOENIG (VALLAURIS, France) samedi 13 août 2011 21:29:23

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community


To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

Aug 16, 2011 8:48 PM in response to deloyd

I've read through the entire discussion. It looks to me as if there are a number of work-arounds for what has always been simple. I discovered one for myself before I logged-in here; so, yes, I can emulate the functionality of the missing <Save As>.


But my workflow isn't broken, so I don't want to fix it. I'm not opposed to change, mind you. It's just that I want to see how that change is worth the annoyance it causes. Right now I don't. Right now I'm hoping some third party will step up. (You listening, St. Clair Software?)


BTW, "version"? Is this an emulation of Adobe's Version Tracker?

save as missing in lion

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.