Quick links: Content - sections - sub sections
EN FR

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
en:changelog:1.2beta1 [2010/03/30 19:53] – bballizlifeen:changelog:1.2beta1 [2010/04/30 19:50] – laurent
Line 20: Line 20:
 ===== Migrating from Jelix 1.1.x ===== ===== Migrating from Jelix 1.1.x =====
  
-== Modules management has changed == +Read [[en:manual-1.2:installation:migrate|the corresponding chapter]] in the manual of Jelix 1.2.
- +
-In the configuration file,  @@unusedModules@@, @@trustedModules@@ and @@checkTrustedModules@@ are not used anymore. There is now a "modules" section, in which the level access of each modules is declared. The option is the module name plus ".access". The value should be: +
- +
-   * 0: if the module is not used at all (default value if the option is not created) +
-   * 1: the module is used (you use its dao, forms, business classes etc from an other module), but is not publicly available (it is not accessible from the web). +
-   * 2: the module is used and is accessible from the web +
- +
-example: +
-<code ini> +
-[modules] +
-testapp.access = 2 +
-junittests.access = 2 +
-jWSDL.access = 2 +
-jacldb.access = 0 +
-jacl2db.access = 1 +
-jauthdb.access = 1 +
-jauth.access = 2 +
-</code> +
- +
-== modules installation == +
- +
-To use a module, a module should be "installed". In fact, there should be a new file "installer.ini.php"  which contains, for each entrypoints, the list of installed modules, and for each of them, the installed version. New commands "installapp" and "installmodule" are provided to install and upgrade modules. +
- +
-== Migrating == +
- +
-A "migrate" command is provided, in order to do needed changes in configuration file of your existing application made with jelix 1.1., and to create this installer.ini.php file. +
- +
-  * replace the lib/ directory by the lib/ of Jelix 1.2 +
-  * verify that your project.xml is ok, that it contains a <jelix> tag with the max version to "1.1". +
-  * in your configuration files (defaultconfig.ini.php and other ini files): +
-     * set @@checkTrustedModules@@ to "on" +
-     * removed from modulesPath, directories where you don't use any modules +
-     * list all modules which can be called from the web in @@trustedModules@@ +
-     * list all modules you don't use at all in @@unusedModules@@ +
-  * go into lib/jelix-scripts/ and run @@php jelix.php --yourapp migrate@@ +
-  * removed all files from temp/yourapp/ +
-  * read the next section, to do changes in your code +
-  * test your application. it should be ok. +
-   +
-A new a installation script yourapp/install/installer.php has been created, so you can use it later (in a command line) to install or update easily your application. You can create scripts into the install/ directory of your modules, which will be called to install or upgrade your modules. Documentation soon. +
- +
- +
-== Other migration steps == +
- +
-  *  The support of old action selectors and old class naming used as of Jelix 1.0 beta, have been removed. You should change your selector and class name if you migrate from a very old version of Jelix < 1.0. +
-  * If you use directly jelixuser.dao.xml, you should change your selector: it has been moved from the jauth module to jauthdb module. +
-  * if you made your own jDb driver with a plugin for jDaoGenerator, you should change some methods calls, since some of them have been renamed. A refactoring has been made and you can redefine more methods. +
  
 ===== Details of changes ===== ===== Details of changes =====

en/changelog/1.2beta1.txt · Last modified: 2012/04/15 08:26 by laurent

Recent changes RSS feed Creative Commons License