"Fossies" - the Fresh Open Source Software Archive

Member "yii-1.1.22.bf1d26/UPGRADE" (16 Jan 2020, 26112 Bytes) of package /linux/www/yii-1.1.22.bf1d26.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "UPGRADE": 1.1.21.733ac5_vs_1.1.22.bf1d26.

    1          Upgrading Instructions for Yii Framework v1.1.21
    2          ================================================
    3 
    4 !!!IMPORTANT!!!
    5 
    6 The following upgrading instructions are cumulative. That is,
    7 if you want to upgrade from version A to version C and there is
    8 version B between A and C, you need to following the instructions
    9 for both A and B.
   10 
   11 General upgrade instructions
   12 ----------------------------
   13 - Make a backup.
   14 - Clean up your 'assets' folder.
   15 - Replace 'framework' dir with the new one or point GIT to a fresh
   16   release and update.
   17 - Check if everything is OK, if not — revert from backup and post
   18   issues to Yii issue tracker.
   19 
   20 
   21 Upgrading from v1.1.21
   22 ----------------------
   23 
   24 No significant changes were made.
   25 
   26 Upgrading from v1.1.20
   27 ----------------------
   28 
   29 No significant changes were made.
   30 
   31 Upgrading from v1.1.19
   32 ----------------------
   33 
   34 No significant changes were made.
   35 
   36 Upgrading from v1.1.18
   37 ----------------------
   38 
   39 If you are outputting validation errors directly without using `CHtml` or `CActiveForm`, make sure
   40 to encode them properly depending on context you are outputting them into.
   41 
   42 Upgrading from v1.1.17
   43 ----------------------
   44 
   45 No significant changes were made.
   46 
   47 Upgrading from v1.1.16
   48 ----------------------
   49 
   50 - If you're using CApcCache with APCu, set `useApcu` to `true` in the component config.
   51 - Undocumented usage of regular expressions outside parameters in URL rules was considered a bug (#3348). Regular
   52   expressions are now escaped properly so if you rely on previous behavior, please update your code.
   53 
   54 Upgrading from v1.1.15
   55 ----------------------
   56 
   57 - CFileValidator now clears attribute after validation in case attribute is marked as `safe` in `rules()` which is default.
   58   The reason is that file uploads were often handled incorrectly by using real database attribute which lead to ability to
   59   write arbitrary data into database column.
   60 
   61   If you've followed [wiki article about uploading files](http://www.yiiframework.com/wiki/2/how-to-upload-a-file-using-a-model/),
   62   you need to mark attribute as `unsafe`:
   63 
   64   public function rules()
   65   {
   66       return array(
   67           array('image', 'file', 'types'=>'jpg, gif, png', 'safe' => false), // <--- here
   68       );
   69   }
   70 
   71 - CErrorHandler now runs errorAction for errors, which appear via AJAX request.
   72   If you use CErrorHandler::errorAction, make sure it handles AJAX request properly.
   73 
   74 - The possibility to use callables for values of CDetailView introduced a problem with string being interpreted as
   75   PHP functions. CDetailView now only allows anonymous functions to be called, all other values will be taken as value.
   76 
   77 - We updated the `framework/utils/mimeTypes.php` with more file extensions from the http apache project.
   78   Due to this fact some of the assignments have changed so if you rely on the mimeType detection of `CFileHelper`
   79   you need to check if your code works with the new mime type assignments.
   80   You can use a custom `mimeTypes.php` file to bring back the old behavior if needed by specifying the second parameter
   81   of `CFileHelper::getMimeTypeByExtension($file, $magicFile='path/to/your/mimeTypes.php')`.
   82 
   83 - We upgraded the bundled jQuery version to 1.11.1. Previous version was 1.8.3.
   84   There were breaking changes in the jQuery API which you can find in the jQuery blog:
   85   <http://jquery.com/upgrade-guide/1.9/#changes-of-note-in-jquery-1-9>. The [jquery-migrate plugin](https://github.com/jquery/jquery-migrate/)
   86   can help checking your code for deprecated functionality.
   87 
   88 - jQueryUI was updated. Check the upgrade guides for [1.10](http://jqueryui.com/upgrade-guide/1.10) and
   89   [1.11](http://jqueryui.com/upgrade-guide/1.11).
   90 
   91 - The implementation of `CSecurityManager::encrypt()` and `decrypt()` were changed to be more secure.
   92   If you use these methods to encrypt your data, you should take the following steps to use the new version:
   93 
   94   1. Decrypt existing data that were encrypted using `legacyDecrypt()`.
   95   2. Change key via application config (encryptionKey property of securityManager component) to the one that conforms
   96      to recommendations.
   97   3. Encrypt the data using `encrypt()`.
   98 
   99   You can disable key validation by setting validateEncryptionKey property of securityManager component to false but
  100   if it strongly not recommended.
  101 
  102 - Namespaced controllers in subdirectories should now have subdirectory in namespace. Previously it was possible to
  103   use the same namespace for both controllers in root directory and subdirectories.
  104 
  105 
  106 Upgrading from v1.1.14
  107 ----------------------
  108 
  109 No significant changes, 1.1.15 was a security fix release.
  110 
  111 Upgrading from v1.1.13
  112 ----------------------
  113 
  114 - CUploadedFile::getInstancesByName() now cannot handle a single file upload. Either change your upload field name to
  115   be something like `ImageUpload[]` or, to keep backwards compatibility in your app, handle it like the following:
  116 
  117   $this->ImageUpload = CUploadedFile::getInstancesByName('ImageUpload');
  118   if (empty($this->ImageUpload)) {
  119       $this->ImageUpload = array(CUploadedFile::getInstanceByName('ImageUpload'));
  120   }
  121 
  122 - CActiveRecord::count() now respects group by and having. If your code relied
  123   on ignoring it your application may break and should be updated.
  124 
  125 - Vendors: phlymail's Net_IDNA was replaced by PEAR Net_IDNA2. The latter library is better maintained than the former.
  126   In case your code relies on bundled phlymail's Net_IDNA you should change it a bit. Old way of encoding IDNs:
  127 
  128       require_once(Yii::getPathOfAlias('system.vendors.idna_convert').DIRECTORY_SEPARATOR.'idna_convert.class.php');
  129       $idnaConvert=new idna_convert();
  130       $result=$idnaConvert->encode($value);
  131 
  132   New:
  133 
  134       require_once(Yii::getPathOfAlias('system.vendors.Net_IDNA2.Net').DIRECTORY_SEPARATOR.'IDNA2.php');
  135       $idna=new Net_IDNA2();
  136       $result=$idna->encode($value);
  137 
  138 - CAPTCHA appearance has been changed. Non-free Duality.ttf font (used by CCaptchaAction) replaced by open/free
  139   SpicyRice.ttf. New font is distributed under SIL Open Font License version 1.1. Do not forget to adjust font path
  140   in case your application relies on Duality.ttf font file.
  141 
  142 - CSecurityManager::computeHMAC() method is now public and third parameter has been added. You must change signature
  143   of this method in the extended child class to fit new circumstances. Otherwise an E_STRICT error will be issued.
  144 
  145 - CClientScript::registerScriptFile() and CClientScript::registerScript() methods signature changed.
  146   Update your subclasses that override registerScriptFile() or registerScript() if any.
  147 
  148 - CActiveRecord::refreshMetaData() now clears meta data for all objects of the particular Active Record class.
  149   Also CActiveRecord::refreshMetaData() will not create new meta data at once - new CActiveRecordMetaData instance
  150   will be created on the first demand.
  151 
  152 - Oracle related note: in case you're using COciSchema::resetSequence() or CDbSchema::resetSequence() methods with
  153   the Oracle database, keep in mind that its behavior has changed to be consistent with the same methods for
  154   the other database management systems. Please refer to its documentation for more details and don't forget
  155   to adjust your code respectively.
  156 
  157 - Signature of the CJuiInputWidget::resolveNameID() method has changed. If you're overriding this method you must
  158   change your code to fit it. This method now accepts two parameters, it means you have to adjust code of the
  159   overlapped descendant method signature as follows:
  160 
  161       protected function resolveNameID($nameProperty='name',$attributeProperty='attribute')
  162 
  163   And ancestor method call to:
  164 
  165       parent::resolveNameID($nameProperty,$attributeProperty);
  166 
  167 - In case you've used your own relation types extended from `CHasOneRelation` or
  168   `CHasManyRelation` make sure you update these to reflect moving `through` property
  169   from both these to `CActiveRelation`.
  170 
  171 - CSecurityManager::generateRandomKey() has been deprecated in favor of CSecurityManager::generateRandomString().
  172   Try not to use it anymore and avoid CSecurityManager::generateRandomKey() method in your code.
  173 
  174 Upgrading from v1.1.12
  175 ----------------------
  176 - Both jQuery and jQueryUI were updated. Check [jQuery UI upgrade guide](http://jqueryui.com/upgrade-guide/1.9/)
  177   and [jQuery release notes](http://blog.jquery.com/2012/08/09/jquery-1-8-released/).
  178 
  179 - We completed the behavior of CFormatter::sizeFormat() which has been introduced in Yii 1.1.11. If you are using it with your own translation file
  180   you have to move your translations to the `yii` category in `yii.php` file  which is handled by the application component `coreMessages`.
  181   We also fixed the default translation strings to be correct English and apply to choice format, so you have to adjust your translation file keys.
  182 
  183 - Be sure to clean all your existing cache during the upgrade. The cache values from CDbCommand has been
  184   changed to an array to be able to store false values (returned when no records are found).
  185 
  186 - Make sure all your event handlers in behaviors are public methods, as we are not supporting protected methods as event handlers anymore.
  187 
  188 - We fixed the calls to CActiveRecord::beforeFind() for consistency so that beforeFind() now always gets called for every relation
  189   on eager loading even if the main query does not return a result. This has been the case for all CActiveRecord::find*()-methods
  190   already but now also applies for findBySql() and findAllBySql().
  191 
  192 - Criteria modification in CActiveRecord::beforeFind() did not apply to the query when model was loaded in a relational context.
  193   Since version 1.1.13 changes to query criteria made in beforeFind() now also apply to the query when model is loaded in a relational context.
  194   The main problem here is that you can not use the `t`-alias for your table anymore, you have to change your code to
  195   use the table alias currently in use as this is different in relational context.
  196   You can get that alias by calling `$this->getTableAlias();` in your active record class
  197   or `$this->owner->getTableAlias()` in behavior context.
  198 
  199   Example:
  200      $criteria->condition = 't.myfield = 1';
  201   You need to change that to:
  202      $alias = $this->owner->getTableAlias();
  203      $criteria->condition = $alias.'.myfield = 1';
  204 
  205 - Make sure you are using `CCaptcha::checkRequirements()` method for checking whether CAPTCHA could be rendered successfully in your environment.
  206   `extension_loaded('gd')` expression is not enough and wrong because CAPTCHA could be rendered via ImageMagick with fallback to GD since 1.1.13
  207   (thus checking code is not simple as it seems).
  208 
  209 - In case you're using MSSQL driver make sure authentication credentials you use have permissions to use
  210   `sys.extended_properties` system view. This is critical for retrieving additional metadata on tables.
  211 
  212 Upgrading from v1.1.11
  213 ----------------------
  214 - Changes in CCookieCollection::add() (introduced in 1.1.11) were reverted as they were triggering E_STRICT on some old PHP-versions
  215   If your application relies on these newly added changes. You should change your code from
  216 
  217 		$cookies->add(new CHttpCookie($name, $value));
  218   to
  219 		$cookies[$name] = new CHttpCookie($name, $value);
  220 
  221 
  222 - CActiveRecord::resetScope() method signature changed. Please update your subclasses that override resetScope() if any.
  223 
  224 Upgrading from v1.1.10
  225 ----------------------
  226 - API of public method CConsoleCommand::confirm() changed. If you are overriding this method make sure to update your code.
  227   The method now has a 2nd parameter for the default value which will be used if no selection is made, so you have to
  228   adjust the signature to fit
  229 
  230       public function confirm($message,$default=false)
  231 
  232   and the parent call to
  233 
  234       parent::confirm($message,$default);
  235 
  236 - API of protected method CConsoleCommand::afterAction() changed, if you are overriding this method make sure to update your code.
  237   method now has a 3rd parameter for application exit code, so you have to adjust the signature to fit
  238 
  239       protected function afterAction($action,$params,$exitCode=0)
  240 
  241   and the parent call to
  242 
  243       parent::afterAction($action,$params,$exitCode);
  244 
  245 - CDateFormat::format() now will return null if the parameter $time is null. Previously it would return 1/1/1970.
  246 
  247 - If you are using CJavaScript::encode in your application with parameter coming
  248   from user input, set second argument to true:
  249 
  250       CJavaScript::encode($userInput, true);
  251 
  252   It will disable prefixing parameters with "js:". If you need to pass JavaScript
  253   expression it's now preferrable to wrap these with CJavaScriptExpression:
  254 
  255       CJavaScript::encode(new CJavaScriptExpression('alert("Yii!");'), true);
  256 
  257   Note that second "safe" parameter doesn't affect CJavaScriptExpression in any way.
  258 
  259 
  260 Upgrading from v1.1.9
  261 ---------------------
  262 - Previously xSendFile() was returning false if the file was not found.
  263   This has been removed to allow relative file paths. If you are relying on this check,
  264   you will need to do it manually before calling xSendFile().
  265 
  266 Upgrading from v1.1.8
  267 ---------------------
  268 - CConfiguration::createObject, CController::paginate and CHtml::getActiveId deprecated since 1.0.x were removed. Use
  269   Yii::createComponent, new CPagination directly and CHtml::activeId respectively.
  270 
  271 - In CErrorHandler::handleException() the checking for ajax call has been removed
  272   as it was preventing to customize the display of the exception during an ajax call.
  273 
  274 - Previously in case of validation error the CSS "error" class was not added to the row container at all when
  275   checkBoxList or radioButtonList where used. This is fixed now and proper "error" CSS class is added to the row
  276   container but in case of validation error, all labels from the list are shown in red because of the CSS rule.
  277 
  278   To fix this and display only the attribute label in red:
  279 
  280   in <projectdir>/css/form.css the line:
  281 
  282      div.form div.error label
  283 
  284   should be changed to
  285 
  286      div.form div.error label:first-child
  287 
  288 - If you've used "through" ActiveRecord option in your relation definitions it's good to update code as shown below.
  289   Old style of defining this option still works but is now deprecated.
  290 
  291   Change
  292 
  293 ~~~
  294 class Group extends CActiveRecord
  295 {
  296     public function relations()
  297     {
  298   		return array(
  299   			'roles'=>array(self::HAS_MANY,'Role','group_id'),
  300   			'users'=>array(self::HAS_MANY,'User','user_id','through'=>'roles'),
  301   		);
  302   	}
  303 }
  304 ~~~
  305 
  306   to
  307 
  308 ~~~
  309 class Group extends CActiveRecord
  310 {
  311     public function relations()
  312   	{
  313   		return array(
  314   			'roles'=>array(self::HAS_MANY,'Role','group_id'),
  315   			'users'=>array(self::HAS_MANY,'User',array('user_id'=>'id'),'through'=>'roles'),
  316   		);
  317   	}
  318 }
  319 ~~~
  320 
  321 
  322 Upgrading from v1.1.7
  323 ---------------------
  324 - CDbAuthManager will now quote columns and tables referenced in its SQL code.
  325   If your auth tables were created in a case-insensitive fashion (e.g. on PostgreSQL)
  326   while your DBMS is case-sensitive, this change may cause DB query errors.
  327   To fix this issue, you will have to rename the table names and columns, or re-create
  328   the auth tables by following the SQL code given in framework/web/auth/*.sql.
  329 - jQuery was upgraded to 1.6.1. Check your client side code and if you have issues consider
  330   downgrading to 1.5.1 or 1.4.4.
  331 
  332 
  333 Upgrading from v1.1.6
  334 ---------------------
  335 - Make sure you are using latest stable PHPUnit 3.5 if you are using unit tests.
  336 
  337 
  338 Upgrading from v1.1.5
  339 ---------------------
  340 - In CActiveRecord::relations(), if a relation involves composite foreign keys, the foreign key
  341   columns must be separated by commas now. Previously, the columns can be separated by either
  342   commas or spaces. If your mode code are generated by Gii or yiic shell, you do not need to
  343   worry about this.
  344 - CLDR data was updated to a newest available version so data formats, month
  345   names and other regional data can be changed.
  346 
  347 
  348 Upgrading from v1.1.4
  349 ---------------------
  350 - CHtml will no longer render null attributes for HTML tags. This means if $htmlOptions is
  351   array('class'=>null), it will no longer render the 'class' attribute in the HTML tag.
  352   it would render the class attribute as class="". We expect this will not cause much trouble
  353   in upgrading. However, in case problems happen, you may set the attribute to be an empty string
  354   to solve them.
  355 
  356 - Now by default CWebLogRoute does not render logs in FireBug for ajax calls.
  357   To get logs rendered for ajax calls in FireBug set CWebLogRoute::ignoreAjaxInFireBug to false
  358 
  359 - The implementation of CCache::flush() was changed a little. Child classes should now implement
  360   a flushValues() method. If you use any custom cache class with flush functionality, you should
  361   rename the flush method accordingly.
  362 
  363 - The prompt and empty options used in CHtml methods will NOT be HTML-encoded anymore. It will now
  364   always convert ">" and "<" into "&gt;" and "lt;", respectively. This should be sufficient in most
  365   cases. But if your application uses some other special characters, or if you allow user inputs
  366   to be used as prompt and empty text labels, please call CHtml::encode() explicitly on these option
  367   values.
  368 
  369 
  370 Upgrading from v1.1.3
  371 ---------------------
  372 - Zii was merged into Yii so if you are using SVN to keep framework
  373   up to date, you'll need to delete 'framework/zii' and then update it.
  374 
  375 Upgrading from v1.1.2
  376 ---------------------
  377 - When using the skin feature, you now need to explicitly configure
  378   the 'enableSkin' property of 'widgetFactory' application component
  379   to be true. Also, if you have configured the 'widgets' property, you
  380   should rename it to be 'skinnableWidgets'. These changes are due to
  381   the introduction of the global widget customization feature.
  382   Please see the guide (the "Theming" section) for more details.
  383 
  384 - CAutoComplete is now deprecated and will be removed in Yii 1.2. Consider
  385   using CJuiAutoComplete.
  386 
  387 - Now it's not possible to reuse CActiveFinder. So if you have code like this:
  388 
  389   $finder = Post::model()->with('comments');
  390   $posts1 = $finder->findAll();
  391   392   $posts2 = $finder->findAll();
  393 
  394   you should rewrite it to:
  395 
  396   $posts1 = Post::model()->with('comments');
  397   398   $posts2 = Post::model()->with('comments');
  399 
  400 - The 'condition' declared in the scopes of the related AR classes will now
  401   be put in the 'ON' clause of the JOIN statement when performing relational AR queries.
  402 
  403 
  404 Upgrading from v1.1.1
  405 ---------------------
  406 
  407 Upgrading from v1.1.0
  408 ---------------------
  409 - CHtml::beginForm() will automatically generate hidden fields to represent
  410   the parameters in the query string when the form uses GET method.
  411   To avoid submitting duplicated query parameters, you may use createUrl()
  412   to explicitly specify the action of the form. You may also need to remove
  413   the hidden fields that you previously render for the same purpose.
  414 
  415 - The code generated by yiic tool is changed. If you are using yiic tool
  416   to generate new CRUD code on a previously generated skeleton, you are recommended
  417   to run "yiic webapp" again to re-generate the skeleton. Make sure you backup
  418   your work before you do this.
  419 
  420 - CMenu now renders the 'active' CSS class for the 'li' tag instead of the
  421   hyperlink tag. You should adjust your CSS code accordingly if you use CMenu
  422   in your application.
  423 
  424 - CUrlManager::parsePathInfo() is changed to be non-static. If you override
  425   this method or your existing code calls this method directly (neither is common),
  426   you need to change your code accordingly.
  427 
  428 - CController::forward() will exit the application by default now. If you want
  429   to keep the old behavior, you may pass false as the second parameter.
  430 
  431 - The jQuery copy included in the framework has been upgraded to version 1.4.2.
  432   This may cause some incompatibility problems to your existing jQuery code or plugins.
  433   If you want to keep using version 1.3.2, you may do so by configuring
  434   CClientScript::scriptMap property.
  435 
  436 - The default theme for JQuery UI widgets was changed from 'smoothness' to 'base'.
  437   If you are using 'smoothness', you will need to manually download this theme from
  438   jqueryui.com and configure the 'theme' property of the JQuery UI widgets accordingly.
  439 
  440 
  441 Upgrading from v1.1rc
  442 ---------------------
  443 - CRudColumn is renamed as CButtonColumn
  444 - CDataColumn.dataField and dataExpression are renamed as name and value, respectively
  445 - The alias name for the primary table in an AR query is fixed to be 't'
  446 
  447 Upgrading from v1.1b
  448 --------------------
  449 
  450 Upgrading from v1.1a
  451 --------------------
  452 - CSort::attributes is changed. Now the array keys refer to attribute names
  453   and array values refer to virtual attribute definitions. Please read the
  454   API documentation for this property to learn more details. This change will
  455   affect your code only when you explicitly specify this property.
  456 
  457 Upgrading from v1.0.x
  458 ---------------------
  459 - Application and module parameter names are changed to be case-sensitive.
  460   In 1.0.x, they are case-insensitive.
  461 
  462 - For tabular input, using Field[$i] is not valid anymore. Attribute names
  463   should look like [$i]Field in order to support array-typed fields
  464   (e.g. [$i]Field[$index]).
  465 
  466 - Please read the Guide for further details on how to upgrade from v1.0.x to v1.1.
  467 
  468 Upgrading from v1.0.12
  469 ----------------------
  470 
  471 Upgrading from v1.0.11
  472 ----------------------
  473 
  474 Upgrading from v1.0.10
  475 ----------------------
  476 
  477 Upgrading from v1.0.9
  478 ---------------------
  479 
  480 Upgrading from v1.0.8
  481 ---------------------
  482 - ActiveRecord lazy loading is changed for optimization purpose. Previously,
  483   when lazy loading occurs, the related table will be joined with the primary
  484   table. Now, the related table will be queried without joining the primary table.
  485   As a result, if you are using lazy loading and the corresponding relation
  486   declaration includes reference to the primary table, the query will fail.
  487   To fix this problem, please specify the lazy loading query options with the
  488   actual primary table column values.
  489 
  490 Upgrading from v1.0.7
  491 ---------------------
  492 - A directory imported using Yii::import() will have precedence over
  493   any existing include paths. For example, if we import 'application.models.*',
  494   then the corresponding directory will be searched before any other
  495   existing include paths. This also means, a directory imported later will
  496   have precedence over directories imported earlier. Previously, this order
  497   was reversed. This change may affect you if you have several classes with
  498   the same name and they are imported via different directories. You will need
  499   to adjust the import order of these directories to make sure your existing
  500   applications are not broken due to this change.
  501 
  502 
  503 Upgrading from v1.0.6
  504 ---------------------
  505 - Default named scope will no longer be applied to INSERT, UPDATE and
  506   DELETE queries. It is only applied to SELECT queries. You should be aware
  507   of this change if you override CActiveRecord::defaultScope() in your code.
  508 
  509 - The signature of CWebUser::logout() is changed. If you override this method,
  510   you will need to modify your method declaration accordingly.
  511 
  512 
  513 Upgrading from v1.0.5
  514 ---------------------
  515 
  516 
  517 Upgrading from v1.0.4
  518 ---------------------
  519 - CWebUser::checkAccess() takes an additional parameter to allow caching
  520   the access check results. If you override this method, you will need to
  521   modify your method declaration accordingly. Because the new parameter will
  522   enable caching the access check results by default, please double check
  523   your code containing this method call to make sure the behavior is as expected.
  524 
  525 - CDateParser has been renamed to CDateTimeParser
  526 
  527 
  528 Upgrading from v1.0.3
  529 ---------------------
  530 - The signature of CWebModule::init() is modified. Its parameter is removed.
  531   If your application uses modules, you have to modify your module class
  532   files accordingly.
  533 
  534 
  535 Upgrading from v1.0.2
  536 ---------------------
  537 - Controllers that are organized in subdirectories are now referenced
  538   using the ID format "path/to/xyz". Previously it was "path.to.xyz".
  539   If you use "path.to.xyz" in your application, you have to modify it
  540   to "path/to/xyz".
  541 
  542 - CHtml::coreScript() is removed. If you used this in your application,
  543   please use the following alternative:
  544 
  545   Yii::app()->clientScript->registerCoreScript($name);
  546 
  547 
  548 Upgrading from v1.0.1
  549 ---------------------
  550 - Due to the introduction of the scenario-based massive assignment feature,
  551   we removed CActiveRecord::protectedAttributes(). Please use safeAttributes()
  552   to specify which attributes are safe to be massively assigned.
  553 
  554   For more details about scenario-based assignment and validation,
  555   please read the following tutorial section:
  556 
  557   http://www.yiiframework.com/doc/guide/form.model#securing-attribute-assignments
  558 
  559 - The signature of CModel::validate() has been changed to:
  560 
  561   CModel::validate($scenario='', $attributes=null)
  562 
  563   That is, the order of the two parameters has been swapped. If your application
  564   contains code that invokes the validate() method (of either a CFormModel
  565   or a CActiveRecord object) with some parameter, please make sure you fix
  566   the parameter order.
  567 
  568 - The usage of CActiveRecord::with() and the 'with' option in relations
  569   has been changed. In order to query child relations, we should specify the 'with'
  570   parameter/option like the following now:
  571 
  572   Post::model()->with(array('comments', 'author.profile'))->findAll();
  573 
  574   Previously, this should be written as:
  575 
  576   Post::model()->with(array('comments', 'author'=>'profile'))->findAll();
  577 
  578   If your code does not involve child relations (like 'profile' in the above),
  579   nothing needs to be changed.
  580 
  581   This change has been introduced in order to support dynamic relational
  582   query options. For example, we can specify that comments be sorted in
  583   descending order (assuming in the relations() method it is specified as
  584   ascending order):
  585 
  586   Post::model()->with(array(
  587       'comments'=>array('order'=>'createTime DESC'),
  588       'author.profile',
  589   ))->findAll();
  590 
  591 
  592 Upgrading from v1.0.0
  593 ---------------------
  594 - An $scenario parameter is added to both CModel::beforeValidate() and afterValidate().
  595   If you override these methods in your child classes (form models, AR classes),
  596   make sure you change the method signature accordingly.