Bulletin/Advisory Information:
Clients who use custom Login Pages may find that problems occur if the .jsp files are not updated to keep pace with changes to the Application. This happens because changes such as the addition, removal or change of functionalities indirectly impacts the behavior of customizations that are made to the Login Page.
All custom Login Pages should be tested in Stage, or Test prior to the Production upgrades. If problems are found, re-build the page based on the default login.jsp template file from your site.
There are a few best practices to keep in mind when developing a Custom Login page:
- Custom elements, including HTML, should be wrapped within a <bbNG:genericPage> element.
A copy of this tag, including some additional attributes, can be found within the default login.jsp template file.
- In addition to the <bbNG:genericPage> wrapper, <script> tags should be further nested within a <bbNG:jsBlock> element.
This is particularly important for any code pertaining to animations or other programmed changes to the page's content.
- In addition to the <bbNG:genericPage> wrapper, <style> tags should be further nested within a <bbNG:cssBlock> element.
- References to external JavaScript or CSS files should use the <bbNG:cssFile /> and <bbNG:jsFile /> tags, respectively, along with corresponding href attributes. Other file types may require the use of the <%@ include /> tag with a file attribute.
Examples of most or all of these can elements be found in your site's template login.jsp file.
Documentation regarding Login Page customizations is available at help.blackboard.com :
Ultra Experience
https://help.blackboard.com/Learn/Administrator/SaaS/User_Interface_Options/Ultra_Experience/Institution_Branding/Customize_the_Login_Page
Original Experience
https://help.blackboard.com/Learn/Administrator/SaaS/User_Interface_Options/Original_Experience/Brands_Themes/Customize_the_Login_Page
Disclaimer:
Anthology Enterprise Client Support does not offer support for the customization, maintenance or modification to custom HTML, JavaScript, or CSS. This restriction includes custom Login Pages. Such customizations must be done by each institution according to their specific needs; problems caused by outdated or incorrect custom code cannot be accepted as Support Incidents. Clients requiring support with customizations may engage Anthology Consulting for a charge.
