XOOPS Cube Legacy 2.1 migration guide (for XOOPS 2.0.x users)

Getting first

XOOPS Cube Legacy 2.1 does not have System module, that XOOPS 2.0.x had. If you migrate from XOOPS 2.0.x, you can keep using a System module to avoid some troubles with some XOOPS 2.0.x modules. But some preference parameters move to another new XOOPS Cube modules.

Module management

• You can manage modules on Legacy 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.
• 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' is ported to User module.

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.

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 you cannot use it, until you go to 'Install block' page and click install icon of block which you want to install at
• If you uninstall the block, it moves back 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.