#### Migration from XOOPS2 to XOOPS Cube 2.1 Legacy

##### Getting first

All of system module's feature are active because XOOPS Cube 2.1 is development status. You'll need these old features to solve your troubles. These features will be ported to 'Legacy module' until stable release.

##### Module management

- You can manage modules on 'Legacy system' module.
- 'Install module' and 'Module management' has each control page.
- Click 'Module management' menu to manage your installed modules. Click 'Install module' menu to install new modules.
- Legacy system's module installer keeps some bugs now. And, it doesn't implement all function of system module's installer.
- Old system's installer set group permission by the user who execute install. New Legacy system's installer set group permission to an administrator group only.

##### User management

- 'User management', 'Group management', 'Group permission', 'Avatar management' and 'Sending mail' will be ported to user module.
- However, 'Sending mail' hasn't ported yet.

##### Theme management

- Each renderer systems (Theme engine) are used for management themes.
- We think that DB template manager is property of the renderer. Therefore, template manager is ported to Legacy renderer which has compatibility with XOOPS2's smarty environment.

New!

##### Block management

- XOOPS Cube 2.1 Legacy environment changed an opinion about block feature. You need install block before you set block to your site. New Legacy system handles it by visible flag.
- If you install module, the module's blocks are registered to XOOPS Cube + Legacy, but it isn't able to use. Click install icon of block which you want to install in 'Install block' page.
- If you uninstall the block, it returns to the list of 'Install block' page.
- You can't edit uninstalled blocks' group permission, target column and target module. But, uninstalled blocks keep these parameters. When you re-install the block, block installer recovers last parameters.