mirror of
https://github.com/yiisoft/yii2.git
synced 2025-11-02 13:02:24 +08:00
Fix #18461: Add missing UPGRADE info, fix wrong bug ID
This commit is contained in:
@ -26,7 +26,7 @@ Yii Framework 2 Change Log
|
||||
- Bug #18414: Fix `AssetManager::appendTimestamp()` not appending timestamp for website root in sub-directory (Isitar)
|
||||
- Bug #18426: Fix check for route's leading slash in `yii\widgets\Menu` (stevekr)
|
||||
- Bug #18435: Fix ensuring Active Record relation links' keys to be strings (bizley)
|
||||
- Bug #18435: Change the check order whether an object is an implementation of `Arrayable` or `JsonSerializable` in `\yii\base\ArrayableTrait::toArray()` and `\yii\rest\Serializer::serialize()` (spell6inder)
|
||||
- Bug #18437: Change the check order whether an object is an implementation of `Arrayable` or `JsonSerializable` in `\yii\base\ArrayableTrait::toArray()` and `\yii\rest\Serializer::serialize()` (spell6inder)
|
||||
- Bug #18442: Fix calls with array access to string (bizley)
|
||||
- Enh #18381: The `yii\web\AssetManager` `$basePath` readable and writeable check has been moved to the `checkBasePathPermission()`. This check will run once before `publishFile()` and `publishDirectory()` (nadar)
|
||||
- Enh #18394: Add support for setting `yii\web\Response::$stream` to a callable (brandonkelly)
|
||||
|
||||
@ -51,6 +51,13 @@ if you want to upgrade from version A to version C and there is
|
||||
version B between A and C, you need to follow the instructions
|
||||
for both A and B.
|
||||
|
||||
Upgrade from Yii 2.0.39.3
|
||||
-------------------------
|
||||
|
||||
* Priority of processing `yii\base\Arrayable`, and `JsonSerializable` data has been reversed (`Arrayable` data is checked
|
||||
first now) in `yii\base\Model`, and `yii\rest\Serializer`. If your application relies on the previous priority you need
|
||||
to fix it manually based on the complexity of desired (de)serialization result.
|
||||
|
||||
Upgrade from Yii 2.0.38
|
||||
-----------------------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user