[Sommaire] [Imprimer]

   1  
   2           Upgrading Instructions for PRADO Framework v3.0.6
   3           =================================================
   4  
   5  !!!IMPORTANT!!!
   6  
   7  After installing the framework, remember to delete everything under
   8  your PRADO application's assets and runtime directories.
   9  
  10  
  11  The following upgrading instructions are cumulative. That is,
  12  if you want to upgrade from version A to version C and there is
  13  version B between A and C, you need to following the instructions
  14  for both A and B.
  15  
  16  Upgrading from v3.0.5
  17  ---------------------
  18  - TRepeater does not render <span> anymore for empty item template.
  19  - constructUrl() now encodes ampersand by default. This should have minimal
  20    impact on any existing PRADO applications, though.
  21  - TDataGrid does not generate default table styles. This may affect
  22    the appearance of existing PRADO applications that use TDataGrid.
  23  - If TUrlMapping is used, you need to set the UrlManager property of
  24    THttpRequest to the module ID of TUrlMapping.
  25  - TJavascriptLogger toggle key is changed from ALT-D to ALT-J. 
  26     Use the ToggleKey property chanage to a different key.
  27  
  28  Upgrading from v3.0.4
  29  ---------------------
  30  - TFileUpload::saveAs() will return false instead of raising an exception
  31    if it encounters any error.
  32  - TDropDownListColumn.DataField is renamed to DataTextField and
  33    DataFormatString is renamed to DataTextFormatString.
  34    A new property named DataValueField is added.
  35  
  36  Upgrading from v3.0.3
  37  ---------------------
  38  - The 'Static' value is changed to 'Fixed' for the Display property of 
  39    all validators as well as TValidationSummary, due to conflict with PHP keywords.
  40  - The 'List' value is changed to 'SimpleList' for TValidationSummary.DisplayMode.
  41  - The 'List' value is changed to 'DropDownList' for TPager.Mode
  42  - This change affects existing client-side javascript handlers such as
  43    <com:TRequiredFieldValidator ClientSide.OnSuccess="xxx" />
  44    All ClientSide javascript event handlers (such as ClientSide.OnSuccess)
  45    are by default wrapped within the function block.
  46         function(sender, parameter){ // handler code }
  47    You may override this behaviour by providing your own javascript statement block
  48    as "javascript:MyHandlerFunction", e.g. ClientSide.OnSuccess="javascript:MyHandlerFunction"
  49    or ClientSide.OnSuccess="javascript:function(validator,sender){ ... }"
  50  
  51  
  52  Upgrading from v3.0.2
  53  ---------------------
  54  - The minimum PHP version required is raised to 5.1.0 and above.
  55    If your server is installed with a lower version of PHP, you will
  56    have to upgrade it in order to run PRADO applications.
  57  - The signature of TControl::broadcastEvent() is changed from
  58    broadcastEvent($sender,TBroadCastEventParameter $param) to
  59    broadcastEvent($name,$sender,$param).
  60    This makes the call to broadcastEvent() to be consistent with raiseEvent().
  61  
  62  Upgrading from v3.0.1
  63  ---------------------
  64  - Postback enabled control will always disable default client-side browser action.
  65    This is due to google toolbar's interference of event stopping scheme.
  66    This modification should only affect user-derived postback javascripts.
  67  
  68  Upgrading from v3.0.0
  69  ---------------------
  70  - URL format is modified when THttpRequest.UrlFormat=='Path'.
  71    This modification affects both the URLs generated by calling constructUrl()
  72    and the URLs understood by PRADO. In particular, PRADO now understands
  73    the following URL format:
  74    /index.php/ServiceID,ServiceParam/Name1,Value1/Name2,Value2/...
  75    In v3.0.0, the above URL is written as:
  76    /index.php/ServiceID/ServiceParam/Name1/Value1/Name2/Value2/...
  77  - TControl::onBubbleEvent() has been changed to TControl::bubbleEvent().
  78    This change only affects user controls that override this method.
  79  
  80  Upgrading from v2.x and v1.x
  81  ----------------------------
  82  PRADO v3.x is not backward compatible with v2.x and v1.x.