Development

Upgrade1.1-ReviewLog (diff)

You must first sign up to be able to contribute.

Changes from Version 1 of Upgrade1.1-ReviewLog

Show
Ignore:
Author:
GaryFx (IP: 71.232.85.188)
Timestamp:
08/13/08 07:46:13 (9 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Upgrade1.1-ReviewLog

    v0 v1  
     1Review the output of the upgrade task carefully. 
     2 
     3Many of the messages will identify obsolete files that can be deleted.  Those don't need to be handled immediately, but should be noted for deletion towards the end of the upgrade process. 
     4 
     5In some cases, the messages will say  
     6{{{ 
     7>> config      If you made some customization in this file, 
     8>> config      please migrate the content to the configuration classes. 
     9}}} 
     10Most commonly, these will be {{{config.php}}} files.  You should review each of these files, and if necessary, migrate the changes to either the ProjectConfiguration class or ApplicationConfiguration classes. 
     11 
     12In other cases, the upgrade task will have determined that you have modified a file, and issue a slightly different message, such as 
     13{{{ 
     14>> config      You made some customization in the following file: 
     15   ..../web/backend.php 
     16>> config      Please, upgrade manually (new code appended as a comment) 
     17}}} 
     18 
     19In this case, the upgrade task has added the new code, facilitating the job of merging your code with the new versions.