Finding where code is coming from is sometimes the first step in troubleshooting so yes.
But while we actually had a tool that did this automatically, it couldn't reach into "Every" template whereas Miva could.
more importantly would be output sort of like this:
<!-- Miva Screen: 'XXXX' called --->
<!-- Miva Action: 'CTAX, OPAY called -->
<!-- Miva Non-Fatal: Could not find variable named g.something -->
Announcement
Collapse
No announcement yet.
Global Debug Mode
Collapse
X
-
Can you give me some examples of where you have used this type of debug mode in the past? What type of stuff are you troubleshooting? It is just finding what template the code is located?
Leave a comment:
-
Global Debug Mode
While we (as in most developers) do this in our own modules, code and systems, it occured to me that Miva could build in a "Debug" mode quite handy. For example,
HTML comments identifying all template calls and actions.
Dump of all non-fatal errors or responses from functions (as HTML comments).
for example.Tags: None
- 1 like
Leave a comment: