This is a collaborative development project to allow the configuration of the login page without the need of customizing core
To be defined
Changes planned to be included in 3.0rc3
- New Design according to above screenshot
- Error messages displayed in the login process are shown inside the login page, instead in a separate error page
- The 'yourCompany' logo is displayed with the image configured in the system, this image can be missing/empty but layout is still shown correctly
- The 'yourItService' is also shown as configured in the system (can be empty also) in this case it is not shown (and the text is also not shown) and the rest of the images in that are displayed centered
- The 'project hosted at' message can be configured to not be shown, but this feature is restricted to users of a basic or professional edition
- The 2.50..3.00 transition skin will be modified to also apply in the login page
- This skin modification will also change i.e. the layout/design of all buttons (i.e. OK / Cancel) everywhere in the application
- The configuration guide (for 3.0) will be updated with the new configuration options.
- All changes do only apply to 3.0 even if they are technically included in 2.50MP24 (nothing should change when running 2.50)
- Need to research way to select installed transition skin as being active by default (ie. template/modulescript)
At least 3 changes are needed in the login page:
- Change the title of main page from Openbravo to their product name
- Hide the YourITService box
- Hide the SourceForge.net box
The favicon should also be configurable for ISVs. Not sure if "Copyright Openbravo 2001-2010" should also be configurable.
There are two approaches to solve this (flexibility vs. control):
- Login can be implemented by external modules (with some requirements) and then configured to use that one.
- Login can be configured with some parameters (Application title, hide IT box, etc)
The preference is to go for the configuration option (login is configurable and a module can deliver the configuration). Since the login screen is very important for our brand, this way we can keep more control of what ISVs can and cannot do with it.
This seems to be a perfect case for "premium functionality" and this configuration should only work in conjunction with an active professional instance and be ignored in a Community Edition.