Customer activated the option on the System Admin-> Configuration->LMS_ADMIN-># Sets debugging pages for online support => contentTestPagesEnabled=true and nothing happens when the content it is launched.
Learming Management System (LMS)
Reproducing the Issue
Activation to true the contentTestPagesEngable in System Admin-> Configuration->LMS_ADMIN-># Sets debugging pages for online support => contentTestPagesEnabled=true and nothing happens when the content it is launched.
The functionality for the contentTestPagesEnabled is a deprecated functionality that it was used before for Cs to troubleshoot, this was based on the use of a Java Applet as it is described bellow.
This will enable the deprecated Java Applet debug. And will only function when useJsletInsteadApplet is set to false.
This will allow the Test pages to be accessed. Suggested to move the test pages to the content server to avoid this.
If the content Structure page is cut in half (bottom is white) its because of this setting.
This setting is global and should not be set on in production environments. (basically never use this)
useJsletInsteadApplet – defaulted to true. This is the new implementation for our old Java applets. The applets will be turned on when this is disabled, but are not being updated any longer.
Right now the best procedure to troubleshoot Content issues it is using fiddler logs where you can see what it is sent from the LMS server to the content Server and the reply back, find attach the guide of how to set up fiddler.
Fiddler it is a third party application that it is free and that we use in Customer Support to analyze the response and what information it is transfer. Also we use httpwatch to measure performance between servers find also attached the guide.
Use of Fiddler application to get the fiddler logs where you can see the interaction between LMS and the content Server.
- Java Applet