Migration guide from the Chiba 2 version to the Dubrovka version ################################################################ Upgrade your Novius OS and its applications ******************************************* See :doc:`/install/upgrade` page if you didn't already do it. Migrate your developments ************************** Breaking changes ---------------- .. _release/migrate_from_chiba.2_to_dubrovka/fuelphp: FuelPHP from 1.6 to 1.7.1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Take a look of these three changelog of FuelPHP for backward compatibility notes: * `FuelPHP 1.6.1 `__ * `FuelPHP 1.7 `__ * `FuelPHP 1.7.1 `__ .. _release/migrate_from_chiba.2_to_dubrovka/wijmo: Wijmo from 2013v1.4 to 2013v3.20 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Take a look of release notes of Wijmo between 2013v3.20 and 2013v1.4: http://wijmo.com/wiki/index.php/Version_Histories .. _release/migrate_from_chiba.2_to_dubrovka/migrations.enabled_types.metadata: End of support for config key migrations.enabled_types.metadata ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The config key ``migrations.enabled_types.metadata`` is no longer supported, and method ``Migration::canUpdateMetadata()`` no longer exist. During migration, all files in :file:`local/metadata` are supposed be writable. A new event :ref:`migrate.exception ` is triggered if a migration throws an exception. This event can stop exception propagation. .. _release/migrate_from_chiba.2_to_dubrovka/event.metadata: Event name for extend metadata configuration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This code do nothing in Dubrovka: .. code-block:: php array($first_parameter, $second_parameter))); Replace with: .. code-block:: php 'Application name', //... 'extends' => array( 'application' => 'application_name', 'extend_configuration' => false, ), ); Replace with: .. code-block:: php 'Application name', //... 'extends' => array( 'application_name', ), ); .. _release/migrate_from_chiba.2_to_dubrovka/extends.apps: Config files extended by application extending mechanism ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Config files extended by application extending mechanism must be defined in a subdirectory :file:`apps/application_name/` For sample, if your application A extends the sample.config.php file of the application B. Deprecated location: :file:`local/applications/application_a/config/sample.config.php` Move to: :file:`local/applications/application_a/config/apps/application_b/sample.config.php` .. _release/migrate_from_chiba.2_to_dubrovka/wysiwyg_theme: WYSIWYG theme ^^^^^^^^^^^^^ The use of ``advanced`` theme is deprecated, use only theme ``nos``. Theme ``nos`` is now an extension of ``advanced`` theme. All configuration keys starting with ``theme_nos_`` are deprecated and should be replaced by their equivalent starting ``theme_advanced_``.