|  |     Graziella,
    
    No you did it completely correctly that's how it works in v3.0.
    It would be nice if the final step were a little more automated but
    you only take the full pain of specifying all the live locations once
    When you do an Update of your application later it should be much
    easier.
    
    regards,
    
    Andrew.D.Wicks
 | 
|  |     The logic behind moving elements into the development area only is
    quite simple.  CM never takes any action which may affect a running
    system. Making elements live automatically affects a running system. 
    Remember that a maintainer can restore an application, but it's the
    system manager's job to make sure that everything is OK before they
    allow users to access the application.  So moving things for movement
    to the live area is the correct course of action, after you test the
    elements which have been introduced onto a system.  After all, how do
    you know that there aren't any bugs in the new elements?
    
    Tony
 | 
|  |     
    Hi Graziella,
    
    To add to .2, keep in mind your shipping Site elements.
    
    With Base elements it's pretty straightforward. The elements all reside
    in the Base area.
    However, packaging Site elements allows you to package elements which
    reside in the Development and/or Live area. It is not restricted to
    only Live elements. So, to help a to prevent a mixed environment CM
    restores all Site elements in Development.
    
    Ciao,
    
    	Simon
    
    
    PS From at least one very big site last week we got the feedback that the
    Restore option would be more useable when no user interaction was
    needed. Currently it is with answers to questions, with a possible MLA,
    etc.
    
    
 |