31,003
edits
Setup Other: Difference between revisions
Jump to navigation
Jump to search
m
→For SaaS / Cloud hosting integrators
Emheyarssi (talk | contribs) |
Tag: 2017 source edit |
||
| Line 1,179: | Line 1,179: | ||
*'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed. | *'''MAIN_MIN_NB_ENABLED_MODULE_FOR_WARNING''' ► If set to N, the warning saying modules are not activated will be shown if number of activated module is < N (Having this variable not defined is same than having it set to 1). This may be usefull if you preinstall an application with some modules already loaded by default and you want to keep the warning to be sure the user will enable other modules he need, even if some modules are already enabed. | ||
*'''MAIN_SETUP_MODULES_DESC''' ► If your installation is already done with activated module, the help message to explain how to enable a module on the setup page is hidden. You can keep it visible by adding this option to 1. | |||
*'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version. | *'''MAIN_NO_UPGRADE_REDIRECT_ON_LEVEL_3_CHANGE''' ► The page to make the migration is not shown automatically when you deploy files of version X.Y.Z+delta over an installation with a database version X.Y.Z. The upgrade page will be shown automatically only if there is a change on value of X or Y in version. | ||