Part 1 - exception CLI

• in the IDE:
  1. open the core/units/admin/admin_events_handler.php file for editing
  2. replace the \AdminEventsHandler::OnDeploy method body with the throw new LogicException('Testing.'); code
  3. save changes
• in CLI:
  1. execute the ./in-portal event:run adm:OnDeploy -v command
  2. confirm that:
     • an exception class/message/backtrace is displayed
     • an exception message and backtrace are separated by a *single* empty line
     • there is a *single* empty line before/after displayed data (exception class+message+backtrace block in a whole)
     • the 1st frame in a backtrace points to the line with a throw ... statement in it
• login to the Admin Console
  1. go to the Logs & Reports → System Log section
  2. confirm that the above-thrown exception was properly logged (the 1st backtrace frame doesn't point to the line with the throw ... statement in it)

Part 2 - fatal error CLI

• in the IDE:
  1. open the core/units/admin/admin_events_handler.php file for editing
  2. replace the \AdminEventsHandler::OnDeploy method body with the trigger_error('Testing', E_USER_ERROR); code
  3. save changes
• in CLI:
  1. execute the ./in-portal event:run adm:OnDeploy -v command
  2. confirm that:
     • a fatal error message/backtrace is displayed
     • a fatal error message and backtrace are separated by a *single* empty line
     • there is a *single* empty line before/after displayed data (fatal error message+backtrace block in a whole)
     • the 1st frame in a backtrace points to the line with a trigger_error( ... statement in it
• login to the Admin Console
  1. go to the Logs & Reports → System Log section
  2. confirm that the above-triggered fatal error was properly logged (the 1st backtrace frame points to the line with the trigger_error( ... statement in it)

Part 3 - SQL error Web

• in the IDE:
  1. open the core/units/admin/admin_events_handler.php file for editing
  2. replace the \AdminEventsHandler::OnDeploy method body with the $this->Conn->Query('SELECT * FROM NonExistingTable'); code
  3. save changes
  4. enable the Debug Mode
• in Web:
  1. login to the Admin Console
  2. go to the Tools → System Tools section
  3. press the Deploy button
  4. confirm that an exception (due to an SQL error) is displayed in Debugger
  5. go to the Logs & Reports → System Log section
  6. confirm that the above-thrown exception was properly logged (the 1st backtrace frame doesn't point to the line with the throw ... statement in it)