Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Debugger is a powerful tool, which allows to inspect In-Portal activities that were performed to generate the page (e.g. SQL queries performed, request contents, etc.).

Here is how it works:

  1. during page generation a debugging information is written into /system/.restricted/debug_@SID@.txt file
  2. extra code is added to a page, that will show:
    1. a mini debugging toolbar (at page top)
    2. a mini debugger report (at page bottom)
  3. clicking on "Show Debugger" button in the debugger toolbar OR pressing F12 will:
    1. make AJAX request to website and get that generated debugger report
    2. show debugger report back to the user

This all works nice when page is reloaded completely, but when it's an SPA website, where each page is loaded via AJAX and debugger panel always points to first generated report then it's not so good.

I propose to replace debugger report in case if new debugger report arrives with new page load via ajax.

Related Tasks

  • No labels